Selling to Microsoft

Microsoft reported 331.8 billion dollars of revenue in fiscal 2026, the year ended 30 June 2026, and spent 35.6 billion dollars on research and development. It also put 115.9 billion dollars into property and equipment, most of that datacentre capacity.

A different number decides whether you have a business here. As of 30 June 2026 Microsoft employed 223,000 people full time, and 77,000 of them sat in product research and development. Your competition is usually not another vendor. It is a team down the hall that already ships in your category, or believes it could ship in two sprints.

No regulator obliges Microsoft to buy third party assurance, so the bias to build is structural rather than cultural. And across identity, endpoint security, data platforms, developer tooling and productivity software, Microsoft already sells a product that competes with yours. Work out which situation you are in before you write a single email.

How the buying process actually runs

There is no supplier application form. Microsoft's procurement site states that it is a resource, not an application process. You cannot register your way in, unlike regulated industries where a supplier database is at least a queue. Procurement begins when a Microsoft employee decides they want to buy from you and becomes your business sponsor. Everything downstream depends on that person existing first.

Paper comes before work. Where a contract is required, the Microsoft Supplier Services Agreement must be executed before any work starts, with statements of work and purchase orders following. Onboarding runs through SupplierWeb, invoicing through MS Invoice.

SSPA is the gate that surprises software vendors. The Supplier Security and Privacy Assurance programme applies globally to any supplier that processes personal data, Microsoft confidential data, or uses AI systems in its work for Microsoft. That covers almost every software product sold into the company in 2026. For new suppliers, work cannot start until the compliance cycle is complete. You enrol with your business sponsor, attest annually against the Supplier Data Protection Requirements, and may be selected to produce an independent assessment against the DPR using a firm from Microsoft's preferred assessors list. The programme guide and the DPR sit at version 12 for fiscal 2026 and are republished annually: a standing cost.

The Supplier Code of Conduct is an annual obligation, not a signature at closing. An authorised representative must acknowledge it every year and complete Microsoft's training course, attested in SupplierWeb, and you must train your own employees and subcontractors on its content annually.

There is a second door that does not exist at a bank. Microsoft runs a partner ecosystem alongside its supplier programme, and for a software company that route often matters more than procurement. Through the Microsoft AI Cloud Partner Program you can take Solutions Partner designations and specialisations, publish a transactable offer on Microsoft Marketplace, and become eligible for services co-sell, where Microsoft's own sellers work your deals alongside you. Partners holding those designations, specialisations or Azure Expert Managed Services Provider status can co-sell without publishing a Marketplace consulting services offer first. Being carried into customer accounts by Microsoft sellers is a different business from asking Microsoft to spend money on itself.

Who owns what, so you know where your deal belongs

You will not be selling to these people. Their remit tells you which part of Microsoft your deal sits in and whose priorities it has to align with.

Names and titles from Microsoft's leadership and investor pages, verified 11 September 2026. Senior roles change; verify at source.

You cannot sell into this account from the bottom

Microsoft's revenue sits in three reported segments, each a large company in its own right. In fiscal 2026, Productivity and Business Processes produced 140.0 billion dollars, Intelligent Cloud 137.8 billion dollars, and More Personal Computing 54.1 billion dollars. Commercial remaining performance obligation stood at 678 billion dollars.

A deal that justifies the cost of selling here runs to millions a year, and for infrastructure to tens of millions across a multi year term. Nobody signs that from the middle of an organisation. It is approved by someone in or reporting into the leadership of a segment, which sets the altitude your entry point has to reach.

There is a second reason to aim high, specific to a software company. The build versus buy argument is almost never held in a room you are in. Someone with 77,000 engineering colleagues says "we could do this internally" and the conversation ends quietly. A sponsor senior enough to overrule that is the only thing that keeps the deal alive.

The layer that matters is below the public names

The executives above are not who you sell to. The layer that matters sits beneath: engineering leaders and platform owners inside Cloud + AI, the programme leads running internal AI deployment, the security and identity owners, the procurement category managers paired with them, and, in the commercial business, the partner development managers who decide which independent software vendors get carried into customer accounts.

At most companies of this size that layer is thin. At Microsoft it is not. The number of people who could credibly sponsor a purchase in your category runs to dozens, possibly low hundreds, almost none of them on a leadership page. The buying committee has to be built one person at a time, and it changes as reorganisations move product groups around.

The board is a published second-degree map

Microsoft's board was expanded to 13 members in May 2026. Its directors hold senior positions across a named, checkable set of organisations: the most useful public asset here.

• Hugh Johnston, Senior Executive Vice President and Chief Financial Officer of The Walt Disney Company.
• John David Rainey, Executive Vice President and Chief Financial Officer of Walmart.
• Charles W. Scharf, Chairman and Chief Executive Officer of Wells Fargo.
• Mark Mason, Executive Vice Chair and Senior Executive Advisor to the Chair and CEO at Citi.
• Catherine MacGregor, Group Chief Executive Officer and a director of Engie.
• Reid Hoffman, a partner at Greylock Partners.
• Penny Pritzker, Founder and Chairman of PSP Partners.
• John W. Stanton, Founder and Chairman of Trilogy Partnerships.
• Sandra E. Peterson, the board's Lead Independent Director.
• Carmine Di Sibio, former Global Chairman and CEO of EY, sits on the boards of PayPal Holdings and Prudential Financial.
• Teri List, former Executive Vice President and Chief Financial Officer of Gap.
• Emma Walmsley, former Chief Executive Officer and a former director of GSK.

If anyone in your network is senior at any of those organisations, there is a published two hop path to a Microsoft director. Judson Althoff, who runs the commercial business, serves as a director at Ecolab and GE Aerospace. Almost nobody works this map, because it takes a database rather than a memory.

The other connector routes

A formal alumni network exists. The Microsoft Alumni Network is an independent nonprofit founded in 1995, open to former Microsoft employees, with thousands of members worldwide. Former colleagues are organised, findable, and still know who stayed.

Acquired company alumni are a separate pool, and Microsoft publishes the list. Microsoft maintains an acquisition history page on its investor site. Anyone who worked at GitHub, LinkedIn, Nuance, Activision Blizzard or Skype before the deal now has former colleagues inside Microsoft, and those relationships predate the integration.

Partners and systems integrators are already inside. The same firms that sell Microsoft technology into your customers can route you to the Microsoft team with the problem, and often want to, because it makes their engagement stickier.

Your own customers who run on Microsoft. A champion who has watched your product work inside a large Azure or Microsoft 365 estate is a more credible referrer than anyone on your payroll, and they often have a named Microsoft account team who can open a door.

A company of any scale is not looking at a handful of routes into Microsoft but at hundreds of thousands of relationships, any one of which might be one hop from the person who matters. That is a matching problem, and nobody solves it by thinking harder. Finding which paths exist is what a relationship intelligence platform is for.

And then you have to get to your own connector

This step fails more introductions than the external ask does. Suppose the best path runs through one of your own directors who also sits on a board with a Microsoft director. You have to get that person to prioritise it, write something credible, and spend a piece of a relationship that took years to build. Ask twice in a quarter and you will not be asked again.

The same logic holds at every level. Asking a customer champion to introduce you to their Microsoft account team is asking them to lend you their credibility. Ask badly, too often, or without giving them something forwardable, and you degrade the relationship that made it possible.

Three rules for the introduction itself

Ask for the organisation, not the company. "An introduction to whoever owns supplier security review for AI systems in Cloud + AI" is actionable. "An introduction to Microsoft" is not.

Write the blurb your connector will forward. They will not write your pitch. Give them a paragraph they can send without editing. The forwardable blurb is the whole craft.

A warm path starts the clock, it does not skip it. You still need a business sponsor, an executed Microsoft Supplier Services Agreement, and SSPA clearance before any work begins. What it buys you is a real conversation about build versus buy with someone who has a problem and a budget, months earlier, and a second person in the room when the internal team says it could build this instead. That is why multithreading matters more here than in almost any other account.

See the warm paths into Microsoft

Everything above describes the problem: an extreme build bias and a partner route that is not procurement. What it does not tell you is which of your own relationships already reaches inside. That is a question about your network, not theirs, and it is the one most teams answer from memory.

Boomerang maps the warm paths your company already has into accounts like Microsoft, across your team, your customers, your board and investors, and your partners. It then drafts the ask, routes it through the right connector and tracks it to a booked meeting. Book a 15-minute walkthrough and see it run against your own target accounts.