Home/EA Renewal Negotiation/Microsoft Org Chart
Negotiation Tactics · Org Chart

You cannot negotiate a deal you cannot map.

The single most common buyer mistake is treating the Microsoft account rep as Microsoft, when the rep is one node in a large organization with sharply divided authority over price, product, and approval. The field sells, the deal desk approves, the licensing organization interprets the rules, and senior management owns the exceptions. Knowing which function holds which lever tells you where to push, where to escalate, and where a no is real versus a no that can be moved. The buyer who maps the Microsoft organization negotiates with the people who decide, not only the people who sell.

Contact Us EA renewal negotiation pillar →
Why the map matters

Microsoft is functions, not a face.

The rep is the buyer's only visible contact, which creates the illusion that the rep speaks for Microsoft. Behind the rep sit functions with their own authority and their own incentives.

The illusion
Single contact

The rep is one node

A buyer who knows only the account rep sees Microsoft as a single point with a single answer. Every no sounds final because there is no visible alternative. This is precisely the view Microsoft prefers the buyer to hold, because it confines the negotiation to the layer with the least authority to concede.

In reality the rep cannot set product use rights, cannot finalize nonstandard pricing, and cannot grant exceptions alone. Those powers live in other functions the buyer never sees unless they go looking.

  • The effect. Every no looks final from one contact.
  • The truth. The rep holds the least concession authority.
The reality
Divided power

Authority is distributed

Microsoft separates selling, approving, and rule interpretation across distinct functions on purpose. The field carries the relationship and the quota. The deal desk owns pricing exceptions. The licensing organization interprets product terms. Management owns strategic exceptions. Each will give a different answer to the same question.

Mapping these functions tells the buyer where a given ask actually gets decided, and therefore where to direct evidence, where to escalate, and which no is simply the wrong function answering.

  • The map. Field sells, deal desk approves, licensing rules.
  • The use. Direct each ask to the function that owns it.
The field organization

The people across the table.

The field is what the buyer sees: the team carrying the relationship and the quota. Understanding their incentives explains much of how a negotiation behaves.

Function 01
Account exec

The account executive

The account executive owns the relationship and the number. Their incentive is to close at the highest defensible value with the least risk to the account. They carry the discount band they can approve alone and act as the gateway to every function above them.

  • Owns. The relationship, the quota, the gateway.
  • Incentive. Close high, hold the account, limit risk.
Function 02
Specialists

Solution specialists

Product specialists are brought in to grow specific workloads such as Azure, security, or Copilot. Their incentive is consumption growth in their line, which can be used by a buyer to play one specialist's growth target against another's pricing.

  • Owns. Growth of a specific product line.
  • Incentive. Drive consumption in their workload.
Function 03
Field lead

The field manager

Above the account executive sits a field sales manager who owns a portfolio of accounts and a larger quota. This is the first escalation rung, with authority and motivation the individual rep lacks when the relationship or the number is genuinely at risk.

  • Owns. A portfolio and a larger quota.
  • Use. First escalation rung above the rep.
The back office

The functions that actually approve.

Behind the field sit the functions that hold the authority the field does not. Most concessions a rep claims are impossible are in fact decided here.

Function 04
Deal desk

The deal desk

The deal desk is where nonstandard pricing and structure are approved or refused. When a rep says the numbers cannot work, the deal desk is the body that would actually decide. It evaluates margin, precedent, and strategic value, and it responds to a documented buyer case far more than to a rep's relationship plea.

Understanding that the deal desk, not the rep, owns the pricing exception tells the buyer where the real decision sits and how to package the evidence that will move it.

  • Owns. Nonstandard pricing and structure approvals.
  • Moves on. Documented margin, precedent, and strategic value.
Function 05
Licensing org

The licensing organization

The licensing organization interprets product use rights and program rules. It is the authority a buyer engages when a rights question or a compliance interpretation is in dispute, and its reading can differ from whatever the rep asserted. On terms and rights, this function, not the field, holds the pen.

Knowing this lets a buyer route a rights dispute to the body that can actually rule on it, rather than accepting the field's convenient interpretation as settled.

  • Owns. Product use rights and program rule interpretation.
  • Use. Route rights disputes here, not to the field.
Reading incentives

Map the incentives, not just the boxes.

An org chart is only useful if the buyer reads the incentives behind each box. Fiscal timing, quota structure, and consumption targets shape every answer the buyer hears.

Lever 01
Fiscal pressure

The year end incentive

Microsoft's fiscal year ends in June, and the field carries quota pressure that intensifies through the fourth quarter. The same ask that meets a flat no in the second quarter can find approval in June, because the field's incentive to close has changed. The org chart tells you who feels that pressure and when.

  • The window. Field quota pressure peaks at fiscal year end.
Lever 02
Growth targets

The consumption incentive

Specialists are measured on growth in their product line. A buyer who can attach a concession to growth in a workload a specialist owns gives that specialist a reason to advocate internally. Reading these targets turns parts of the Microsoft organization into allies for the right structure.

  • The play. Attach asks to a specialist's growth target.
Our position

What we do with the Microsoft map.

We maintain a working map of the Microsoft organization for each engagement and route every ask to the function that actually owns the decision.

Our move 01
Map the account

We chart the specific organization

For each engagement we identify the account executive, the specialists, the field manager, and the deal desk and licensing contacts that govern the account, along with the fiscal and quota pressures shaping their behavior. The map is specific to the buyer's deal, not a generic diagram.

With the map in hand we know where each ask is really decided, which no is the wrong function answering, and where the fiscal calendar opens a window the rep will not mention.

Our move 02
Route the asks

We direct each ask to its owner

Pricing exceptions go to the deal desk with a documented case. Rights disputes go to the licensing organization. Strategic exceptions go executive to executive. We route each ask to the function that holds the authority, rather than letting the field answer for functions it does not control.

Clients find that simply addressing the right function with the right evidence converts answers that looked final into concessions, because the question finally reached the body that could say yes.

The Microsoft org map.

Our reference diagram of Microsoft's negotiation organization, the authority each function holds, and the incentives that shape their answers. Sent on request.

$420M+ recovered · 340+ engagements
Engage the practice

Negotiate with the people who decide.

The rep is one node in a large organization with divided authority. We map the functions, read the incentives, and route every ask to the owner who can actually approve it.

Contact Us 79% audit exposure cut · 20+ years practice depth