Recommended resources
The freely available resources this lesson will direct you to.
Hello. In the previous lesson, you classified businesses by what customers pay for and what the business controls. Now we will use a different lens: what work must a company perform to create, grow, deliver, and sustain that business?
We will map Microsoft’s activities across Product, Growth, Distribution, People, and Enabling Functions, using its fiscal 2025 annual report. Microsoft is useful because its enterprise software and cloud businesses share capabilities but do not reach customers or earn revenue in identical ways. The objective is a defensible activity map—not a product catalog or a restatement of its income statement. Allow about 40 minutes, including the targeted reading and video.
Choose the right unit of analysis
A company’s reporting segments and an activity map answer different questions. Microsoft reports Productivity and Business Processes, Intelligent Cloud, and More Personal Computing as operating segments. Those divisions help management assess businesses and allocate resources. Our five-stage map instead asks what kinds of work occur within and across those businesses.
Read the segment descriptions selectively. You need enough detail to distinguish Microsoft 365 Commercial, Azure, and Windows—not to memorize their portfolios.
Microsoft’s annual report supplies the primary evidence for our company map. Read how it defines its reporting segments, then compare the commercial drivers of three businesses.
In Operating Segments, read segment purpose. Under Productivity and Business Processes, find Microsoft 365 Commercial Products and Cloud Services and read commercial growth, finishing that sentence. Under Intelligent Cloud, find Server Products and Cloud Services: read Azure services and the sentence beginning Azure revenue. Finally, under More Personal Computing, find Windows and Devices and read Windows OEM demand.
Notice why the unit of analysis matters. Microsoft 365 Commercial growth depends partly on adding users and increasing average revenue per user. Azure revenue is mainly affected by consumption-based infrastructure and platform services. Windows OEM revenue depends substantially on licenses purchased for pre-installation on devices. An activity map for “Microsoft” must accommodate all three; a map for Azure alone would look more focused.
For this lesson, we will map Microsoft as a company, concentrating on its commercial software and cloud businesses and using Windows where it reveals a distinct distribution model. This breadth lets us identify shared activities without pretending that every channel applies to every product.
The five headings are analytical lanes, not departments or a mandatory sequence:
| Lane | Question the map must answer |
|---|---|
| Product | What does the company design, build, and improve for customers? |
| Growth | How does it increase adoption and value captured from its offerings? |
| Distribution | Through which routes are offerings sold, accessed, and delivered? |
| People | Which workforce capabilities make the other activities possible? |
| Enabling Functions | Which operating and corporate systems allow the business to run reliably and at scale? |
An activity can touch several lanes. The discipline is to give it a primary home according to the decision you are analyzing, then show its dependencies rather than counting the same activity five times.
Product and Growth: connect investment to the commercial driver
In Product, place the work that shapes the offering. For Microsoft, this includes developing productivity applications, cloud services, and operating systems; improving security and AI capabilities; and coordinating development across businesses. A particularly consequential choice is whether a capability should be built into an existing offering or offered separately. The map records the activity and strategic choice, not every feature.
Microsoft 365 Copilot illustrates the distinction between Product and Growth. Developing and integrating an AI capability into commercial productivity software is Product work. Deciding which customers to pursue, how to package the added value, and how to expand spending within the installed base is Growth work. The annual report identifies installed-base growth and average revenue per user expansion as drivers of Microsoft 365 Commercial revenue. It does not, from that statement alone, quantify Copilot’s separate contribution to either driver.
For Azure, Product includes the cloud services customers use to build and run applications. Growth asks a different question: what increases the number of customers, workloads, or resources consumed? Its consumption-based revenue makes workload adoption and continuing usage commercially important. For Windows OEM, growth depends in part on device shipments and license attachment. These are different growth mechanisms inside one company.
A short video offers a useful way to keep acquisition and post-sale growth in the same picture:
The SaaS business model & metrics: Understand the key drivers for success
Watch “The SaaS business model & metrics: Understand the key drivers for success” from Web Summit for its treatment of a growth funnel that extends beyond winning an initial customer. It is a generic SaaS model, not a description of Microsoft.
Watch the extended funnel. Focus on why onboarding, retention, and expansion belong in a growth analysis alongside lead generation and conversion. Do not assume its trial-led example applies to all of Microsoft’s enterprise sales.
Growth is about changing the commercial outcome; Distribution is about the route and infrastructure through which an offering reaches the customer. A partner can contribute to both. When analyzing partner incentives or customer acquisition, its role sits primarily in Growth. When documenting the channel through which a customer purchases, its role sits primarily in Distribution. The distinction prevents an activity map from becoming a loosely labeled sales funnel.
Distribution: distinguish route to market from delivery
Microsoft’s annual report describes direct sales, distributors and resellers, digital marketplaces, and original equipment manufacturers (OEMs). Read these as business-specific routes, not interchangeable options available to every offering.
Return to the annual report to see how a diversified company reaches different customer groups. Pay particular attention to which channels are relevant to cloud services and which are specific to devices.
In Distribution, Sales, and Marketing, read the introductory paragraph from customers and channels. Then read the Direct subsection from enterprise agreements. In Distributors and Resellers, read from indirect channels. In OEMs, read from device distribution.
The resulting distribution map is more precise than “Microsoft has a large partner ecosystem”:
- Commercial software and cloud: Customers can transact directly; resellers and partners also participate. The report identifies Cloud Solution Provider as its main partner program for reselling cloud services.
- Windows OEM: Device makers pre-install software on devices they sell. That is a distinct route to users and a distinct commercial relationship.
- Digital routes: Microsoft also sells some products and services through its marketplaces and online stores.
Distribution has an operational dimension as well as a sales-channel dimension. Azure customers access services running on Microsoft’s cloud infrastructure. Providing capacity and operating that infrastructure are necessary to deliver what was sold; signing an agreement alone does not fulfill the promise. Conversely, a data center is not best described merely as a “channel”: it is delivery infrastructure with consequences for capacity, reliability, and cost.
This gives the map diagnostic value. If cloud demand grows but capacity cannot keep pace, the issue may sit primarily in Distribution and its enabling infrastructure, even though the symptom appears as missed Growth. If a reseller cannot explain or implement an offering effectively, the constraint may involve partner enablement and People, not a deficient product.
People and Enabling Functions: make the cross-cutting work visible
People is not a synonym for “human resources.” It captures the workforce capabilities required throughout the business: researchers and engineers shape Product; sales and marketing staff support Growth; operations and support staff deliver services. Hiring, training, deployment, and retention of those capabilities affect what the company can execute.
Enabling Functions are different. They comprise the systems, processes, and governance that let activities operate repeatedly and under control: for example, contract processing, billing and collections, vendor management, finance, legal work, and administration. Human-resources processes belong here as an enabling function, while the skills and capacity of the workforce belong in People. The categories interact but should not be collapsed.
Use Microsoft’s workforce and operations disclosures to give the last two lanes concrete substance. The headcounts are company-wide, so they should not be assigned to Azure or Microsoft 365 individually.
In Human Capital Resources, read workforce allocation. In Operations, read from operating processes, followed by capacity dependencies. In Research and Development, under Product and Service Development, read from development control.
The report places approximately 80,000 employees in product research and development, 44,000 in sales and marketing, 89,000 in operations, and 15,000 in general and administration as of June 30, 2025. These figures demonstrate the scale of different capabilities. They are not a five-stage cost allocation: operations includes several kinds of work, and the disclosure does not tell us how many people support a particular product.
The report also makes an important dependency visible. Microsoft operates data centers and says their expansion depends on inputs including suitable land, energy, networking supplies, servers, and components. For our map, operating cloud capacity is principally part of delivery. Securing inputs, managing vendors, processing contracts, and funding and coordinating capacity are enabling work. The engineers and operations staff who carry it out appear in People. One capacity decision can therefore span three lanes without becoming three separate investments.
Assemble a map that supports a strategic discussion
Here is a compact first-pass map. Each row states an activity, rather than substituting a financial-statement line item for work performed.
| Lane | Microsoft activities evidenced in the annual report | Strategic question raised |
|---|---|---|
| Product | Develop commercial productivity software, Azure services, and operating systems; invest in research and product improvements | Which capabilities should be integrated or developed across businesses? |
| Growth | Reach new commercial users; expand average revenue per user; encourage adoption of cloud services and workloads | Which mechanism is driving incremental customer spending in each business? |
| Distribution | Sell directly and through resellers and cloud partners; use OEMs for pre-installed software; operate infrastructure that delivers cloud services | Does the relevant business have effective customer access and sufficient delivery capacity? |
| People | Deploy R&D, sales and marketing, operations, support, and administrative capabilities | Where might skills, staffing, or coordination constrain execution? |
| Enabling Functions | Process contracts and orders, bill and collect, manage vendors, and coordinate operational capacity | Can the company support growth with reliable processes and timely inputs? |
Two safeguards make this map credible.
First, separate reported facts from hypotheses. The report describes Microsoft 365 Commercial’s revenue drivers and Microsoft’s channels. A claim that a particular channel is its best-performing one, or that a specific skill shortage is holding back Azure, would require additional evidence. The right-hand column raises questions; it does not answer them by assertion.
Second, do not confuse the map with a profit-and-loss breakdown. R&D expense can help identify investment in Product, and sales and marketing expense can signal spending associated with Growth. Neither expense line proves which activities create value, which are bottlenecks, or how work is organized. Likewise, reporting segments are useful for financial analysis but cut across the five activity lanes.
The map now gives you a practical starting point for an unfamiliar company: define the scope, place its consequential activities in the five lanes, identify important cross-lane dependencies, and mark what remains unverified. It also helps frame potential interventions. A problem in product adoption may call for a Product or Growth response; unreliable cloud capacity may require coordinated delivery, workforce, and enabling-function changes. Diagnosis comes before choosing an intervention.
Key takeaways
Product defines and improves the offering. Growth changes adoption and customer spending. Distribution covers routes to customers and the means of delivering what they buy. People identifies the capabilities needed to execute; Enabling Functions keep execution coordinated and controlled. For a diversified company, always specify which business an observation applies to and distinguish evidence from inference.
In the next lesson, we will look outside the company boundary to identify customers, complementors, suppliers, channels, and competitors in its ecosystem.