Microsoft Organizational Structure

About the company

Microsoft Corporation sells cloud infrastructure and platform services, productivity software, security, developer tools, devices and games. It recorded USD 331.8 billion of revenue in the fiscal year that ended on 30 June 2026 and employed roughly 223,000 people at that date, about 5,000 fewer than a year earlier, run from a campus in Redmond, Washington.

The structure is worth studying because Microsoft is one of the largest companies in the world still organised as a single unitary company rather than as a portfolio of divisions. LinkedIn, GitHub, Nuance and Activision Blizzard King are wholly owned businesses folded into Microsoft's own management lines rather than separately governed subsidiaries, so the chart below is the corporation itself and not a holding group.

The financial reporting deepens the confusion rather than resolving it. Productivity and Business Processes, Intelligent Cloud and More Personal Computing were sized at USD 140.0 billion, USD 137.8 billion and USD 54.1 billion in fiscal 2026, but they are disclosure constructs: no executive carries a segment title, and the engineering organisation cuts across all three.

Microsoft Corporation organizational chart

Microsoft Corporation's reporting structure as of 2026-08. Drag to pan, scroll to zoom — or open it in QueryChart and edit it as your own.

One functional company, a separate commercial organization, and internal CEOs

The chart has an unusually wide first level. Corporate functions each report to the CEO as single company-wide organisations — legal and corporate affairs under Brad Smith, finance under Amy Hood, people under Amy Coleman, marketing under Takeshi Numoto and strategy under Kathleen Hogan. Alongside them, on the same line, sit the commercial organisation and roughly a dozen product and engineering leaders.

During fiscal 2026 Microsoft retired the Senior Leadership Team, the standing body of business-unit chiefs that had governed the company for decades. Press reporting describes what replaced it: a five-person corporate leadership group of Satya Nadella, Brad Smith, Amy Hood, Amy Coleman and Judson Althoff meeting weekly on governance, and an engineering leadership group of about 35 product and engineering leaders who coordinate laterally rather than through an intervening layer. Microsoft has not confirmed either body in an official post, and the membership of the engineering group is not public.

Go-to-market is pulled out of the product organisations entirely. Judson Althoff holds the title Chief Executive Officer, Microsoft Commercial Business and runs sales, services, support, operations and commercial marketing across more than 120 country and regional subsidiaries. In February 2026 four of his chief-officer roles were elevated to executive vice president: Deb Cupp on global enterprise sales, Nick Parker on worldwide sales and solutions, Ralph Haupter on the small and medium segment and the channel, and Mala Anand on customer experience.

On the engineering side, Scott Guthrie's Cloud + AI group carries infrastructure and the data platform, with Arun Ulag running Azure Data beneath him. Pavan Davuluri, Perry Clarke and Hayete Gallot own Windows and devices, Microsoft 365 Core and Security; Kevin Scott, Mustafa Suleyman and Jacob Andreou cover technology strategy, frontier AI and Copilot; Ryan Roslansky, Charles Lamanna and Asha Sharma run the apps, business-copilot and gaming businesses, with Matt Booty on game content beneath Sharma. Four of those roles were created in March 2026, when Rajesh Jha retired as EVP of Experiences and Devices and his organisation was divided four ways instead of being handed to a successor.

Key leadership roles

1. Satya Nadella

   Chairman and Chief Executive Officer — Chairs the board and carries roughly sixteen direct reports spanning corporate functions, commercial and engineering.

2. Brad Smith

   Vice Chair and President — Corporate, external and legal affairs; one of the five in the corporate leadership group that replaced the SLT.

3. Amy Hood

   Executive Vice President and Chief Financial Officer — One of only six people named as executive officers in Microsoft's fiscal 2026 Form 10-K.

4. Amy Coleman

   Executive Vice President and Chief People Officer

5. Takeshi Numoto

   Executive Vice President and Chief Marketing Officer

6. Kathleen Hogan

   Executive Vice President, Office of Strategy and Transformation — Role announced in March 2025; her own profile renders the title differently, and the 2026 wording could not be confirmed.

7. Judson Althoff

   Chief Executive Officer, Microsoft Commercial Business — Runs worldwide sales, services and support as one organisation across 120+ subsidiaries.

8. Kevin Scott

   Executive Vice President and Chief Technology Officer — The reporting line to the CEO is long-standing and conventional but was not restated in any 2026 announcement.

9. Scott Guthrie

   Executive Vice President, Cloud + AI Group — Same caveat as the CTO line; the Cloud + AI remit description predates the 2026 reorganisations and may be narrower now.

10. Mustafa Suleyman

    Executive Vice President and Chief Executive Officer, Microsoft AI — Remit narrowed to frontier models in March 2026, when Copilot moved to a separate EVP.

11. Jacob Andreou

    Executive Vice President, Copilot

12. Ryan Roslansky

    Executive Vice President, Microsoft 365 Apps and Copilot Platform; Chief Executive Officer, LinkedIn — Holds a Microsoft engineering EVP role and the LinkedIn CEO title at the same time.

13. Pavan Davuluri

    Executive Vice President, Windows + Devices — One of the four leaders promoted onto the CEO's line when Experiences and Devices was split in March 2026.

14. Asha Sharma

    Executive Vice President and Chief Executive Officer, Microsoft Gaming — Took the gaming CEO title in February 2026 after Phil Spencer's retirement.

How this structure supports the business

A functional organisation lets Microsoft point one engineering system at a single company-wide bet. Copilot and Azure AI cut across productivity, cloud, security, devices and gaming, and there are no divisional profit-and-loss boundaries to renegotiate before a shared model, a shared inference fleet or a shared agent platform is adopted everywhere.

One worldwide commercial organisation gives an enterprise buyer a single relationship and a single contract across Azure, Microsoft 365, Dynamics, Security and gaming. That is a real advantage in the large multi-product agreements Microsoft's growth depends on, and it lets the company shift field capacity between products without reorganising anyone's sales team.

The flat top removes a translation layer between the person setting strategy and the people shipping code, and Microsoft substitutes operating cadence for the hierarchy it removed: a weekly Copilot leadership standup with Jacob Andreou, Charles Lamanna and Ryan Roslansky, weekly AI metrics reviews, and biweekly sessions with the Azure infrastructure team.

Advantages and disadvantages

One engineering system can be aimed at a single company-wide bet without renegotiating boundaries between divisional roadmaps that each own their own P&L.

Nothing below the CEO is accountable end to end for a product. Cost, revenue and customer outcome are split across an engineering EVP, the commercial organisation and central finance, so escalation to Nadella becomes the normal way to settle a conflict rather than the exception.

Dissolving the SLT and moving a dozen product and engineering leaders onto the CEO's line removed a layer of translation and made reorganisation cheap — Rajesh Jha's organisation was redistributed in a single memo.

It gives one person an implausibly wide span of control on top of chairing the board, and concentrates arbitration and institutional memory in a group of five. Attention becomes the scarce resource, and a leader outside the weekly cadences loses visibility no matter how large their business is.

Running all sales as one global organisation under a single commercial CEO gives customers one contract and one account team across every Microsoft product.

It puts a long distance between the engineers who build a feature and the field that hears the objection to it. Althoff's stated reason for expanding his lieutenants' remits in 2026 was to shorten exactly that feedback loop.

Internal CEO titles for AI, Gaming and LinkedIn let genuinely different businesses keep their own talent markets, release cadence and culture without being forced into the core engineering rhythm.

Those boundaries are drawn by memo and redrawn often. Microsoft AI was narrowed to frontier models in March 2026 while Copilot went to a separate EVP, leaving two AI organisations with solid lines to the CEO and only a dotted line to each other while shipping one product.

Interesting facts

• Microsoft retired the Senior Leadership Team during fiscal 2026 and replaced it, according to press reporting, with a five-person corporate leadership group and an engineering leadership group of about 35 leaders who coordinate laterally.
• The segments Microsoft reports to investors are not the segments it manages by: no executive holds a segment title, and the engineering organisation cuts across all three.
• When Rajesh Jha retired as EVP of Experiences and Devices in March 2026, Microsoft appointed no successor and split his organisation four ways, promoting each leader to EVP on the CEO's own line.
• Four people inside Microsoft hold a CEO title — for the commercial business, for Microsoft AI, for Microsoft Gaming and for LinkedIn — and all four report to the single Chairman and CEO of the corporation.
• In February 2026 Charlie Bell moved from EVP of Security to an individual-contributor role on engineering quality with no direct reports but a continuing line to the CEO; he is not on this chart because he heads no organisation.
• Sales, services, support and commercial marketing are decoupled from product entirely, so an EVP running a business the size of a large public company does not own the field organisation that sells it.

Frequently asked questions

What type of organizational structure does Microsoft use?

A functional one, not a divisional one. Engineering leaders own capabilities and product areas across the whole company, corporate functions such as finance, legal, people and marketing are single centralised organisations, and sales is a separate worldwide commercial organisation. The only complication is a small number of internal businesses that carry their own CEO title while still reporting to Satya Nadella.

Do Microsoft's reporting segments match its organizational chart?

No, and that is deliberate. Productivity and Business Processes, Intelligent Cloud and More Personal Computing exist for the Form 10-K, and no executive is in charge of one. The management organisation has cut across the segments since the One Microsoft functional reorganisation of 2013.

Who reports directly to Satya Nadella?

Roughly sixteen people as of August 2026: the corporate functions under Brad Smith, Amy Hood, Amy Coleman, Takeshi Numoto and Kathleen Hogan; the commercial business under Judson Althoff; and about a dozen product and engineering leaders including Scott Guthrie, Kevin Scott, Mustafa Suleyman, Jacob Andreou, Pavan Davuluri, Perry Clarke, Hayete Gallot, Ryan Roslansky, Charles Lamanna and Asha Sharma. The span widened in 2026 rather than narrowing.

Why do several Microsoft executives have CEO in their title?

The title marks a business run with P&L-like autonomy inside the corporation, not a separate legal entity. Judson Althoff is CEO of the commercial business, Mustafa Suleyman of Microsoft AI, Asha Sharma of Microsoft Gaming and Ryan Roslansky of LinkedIn, and each reports to Satya Nadella, who remains the only Chairman and CEO of Microsoft Corporation.

Can I edit this Microsoft org chart?

Yes. Open it as your own chart and it becomes an ordinary QueryChart org chart — rename people, move reporting lines, add levels. It is a useful starting point if you are modelling a wide CEO span, a shared services layer or a go-to-market organisation kept separate from product.

Use this org chart template

Open Microsoft's structure as an editable org chart, then reshape it into your own — a wide executive line, a separate go-to-market organisation, or both.

Open this org chart as your own