The Intentional Opacity of EA Pricing
Microsoft's Enterprise Agreement pricing system is deliberately complex. That complexity is not accidental — it serves Microsoft's commercial interests by making it nearly impossible for buyers to independently verify whether they are receiving fair pricing. After working with 500+ enterprise customers across two decades, I can say with certainty: most organisations have no idea how their EA price was actually determined. They received a proposal, negotiated it down by some percentage, and signed. They have no baseline, no benchmark, and no framework for evaluating whether what they paid was reasonable.
This guide explains the actual mechanics of Microsoft EA pricing — the layer structure, the discount methodology, the reseller economics, and the approval processes that determine what's available to which customers. Understanding this system is a prerequisite for any meaningful EA negotiation.
Layer One: List Price (ERP)
All EA pricing starts from Microsoft's published Estimated Retail Price — the ERP or list price. This is publicly available through Microsoft's licensing documentation and changes at Microsoft's discretion, typically with 30 days' notice for existing agreements and more notice for new EA structures.
Microsoft has raised list prices materially in recent years. The 2022 M365 price increases (9–25% depending on SKU) and subsequent 2023 adjustments reset the baseline for virtually every EA. The 2025 E3/E5 restructuring changed the SKU architecture in ways that affected calculated unit economics across the board. Understanding list price movement is essential because EA discount levels are calculated against list — and list price increases directly affect your total cost even when your "discount level" holds constant.
A 15% list price increase applied to an EA where your discount level stayed flat is a 15% cost increase. Your rep may present this as "no change to your discount" — which is technically true and commercially misleading.
Layer Two: Level Discounts (The D-Level System)
Microsoft's EA pricing is structured around "discount levels" — tiered reductions from list price based primarily on total agreement value. The specific thresholds and associated percentages are not publicly disclosed, but the system functions as a step structure with meaningful jumps at volume milestones.
The D-level system has several characteristics buyers need to understand. First, discount levels are product-category specific — your D-level for Microsoft 365 is calculated separately from Azure, which is separate from Server products. A very large Azure MACC does not automatically improve your M365 discount level. Second, discount levels are applied to the base SKU price before any additional discounts, credits, or program incentives — this sequencing matters for calculating actual unit economics. Third, D-levels can be renegotiated at renewal even if your overall volume holds flat, if you can demonstrate market-competitive alternatives.
For the purposes of pricing benchmarks, the relevant comparison is not your discount level percentage — it is your net unit price after all applicable discounts, compared against what comparable organisations have closed at.
Layer Three: Additional Discounts (Non-Standard Terms)
Beyond D-level discounts, Microsoft's approval structure allows for additional non-standard discounts. These require internal approval from Microsoft's licensing desk and typically involve one or more of the following justifications: competitive displacement threat, strategic account designation, public sector or non-profit status, significant volume growth commitment, or end-of-fiscal-year incentive.
Non-standard discounts are where most of the negotiating room lives. D-level discounts are relatively mechanical — they're hard to argue with because they're tied to volume thresholds. Additional discounts require Microsoft's reps to build a business case for their internal approvals process, which is why the leverage framework from our EA negotiation leverage article is so important. The better your leverage story, the more ammunition your rep has for the internal approval process.
It is worth noting that Microsoft's approval process is tiered. A rep can approve certain additional discounts unilaterally. Regional management can approve the next tier. Microsoft's enterprise licensing desk handles the highest discount approvals. Understanding which tier you need to reach — and structuring your negotiation to escalate appropriately — is a significant part of what makes experienced negotiation advisors valuable.
Layer Four: Reseller Economics
Most enterprises buy their EA through a Microsoft Large Account Reseller (LAR) rather than directly from Microsoft. This is Microsoft's preferred channel structure and has important pricing implications that buyers frequently misunderstand.
LARs receive a margin from Microsoft — typically 2–5% of deal value depending on volume and account type. This margin is built into the price you pay. In theory, a LAR's margin is covered by Microsoft and shouldn't affect your pricing. In practice, LARs can add incremental margin on top of Microsoft's price, and buyers who don't track this carefully can end up paying above the Microsoft-set price without knowing it.
More importantly, LARs have their own incentives — Microsoft pays performance bonuses for resellers who grow assigned accounts, which creates incentive structures that don't always align with the buyer's interest in minimising cost. The LAR who maximises your EA scope is more likely to hit their Microsoft incentive targets than the LAR who right-sizes your agreement.
This is a structural reason why independent advisory creates value: an advisor who is not receiving Microsoft reseller incentives has no financial interest in the outcome except the client's cost reduction. If you are using your reseller as your primary source of EA negotiation advice, you have a fundamental conflict of interest that you need to be aware of.
Layer Five: True-Up Pricing Mechanics
The EA's annual true-up is not simply a count of additional seats multiplied by unit price. The pricing mechanics of true-up additions depend on when in the contract year the true-up is assessed, which products are included, and whether the additions trigger a change in your D-level for the remaining term.
True-up additions are priced at your current EA unit price — but that price may have changed since your original signing if Microsoft has published a price increase. Most EA agreements contain a price cap provision for the original product set, but additions made through the true-up process may be subject to current pricing. This distinction can be worth millions of dollars for large-scale deployments and is consistently misunderstood by procurement teams that are focused on seat count rather than unit economics.
For organisations with significant deployment growth between true-up cycles, understanding the true-up pricing mechanics before the true-up date is essential — not after. Our true-up compliance advisory specifically addresses pre-true-up planning to ensure there are no pricing surprises at submission. See also our detailed guide to EA true-up clauses.
Layer Six: Credits, Incentives, and SLA Credits
Microsoft offers a range of credit and incentive programs that can reduce net EA cost without changing the nominal price structure. These include Azure Hybrid Benefit credits for organisations migrating on-premises workloads, Software Assurance benefit credits for training and deployment services, and SLA credits for service disruptions above defined thresholds.
These programs are real money — Azure Hybrid Benefit alone can reduce Azure licensing costs by 40–50% for organisations running Windows Server and SQL Server workloads on Azure. But they require proactive claim and management. Microsoft does not automatically apply credits; buyers need to understand what they are entitled to and track utilisation actively.
Many organisations we assess are systematically under-claiming on Software Assurance benefits, leaving tens or hundreds of thousands of dollars in unused entitlements on the table each year. Our M365 optimization engagements routinely include a benefit utilisation audit as a first step because the findings usually justify the engagement cost before we get to any pricing work.
What Actually Determines Your EA Price
Having mapped all six pricing layers, it is worth summarising what actually drives the price a given enterprise pays. In order of impact: your negotiation preparation and leverage position (highest impact, most controllable), your product scope and volume (determines D-level, partially controllable through right-sizing), your reseller relationship and whether they have conflicting incentives (often underappreciated), your timing relative to Microsoft's fiscal calendar (significant impact, often ignored), and your claim and utilisation of available credits and programs (pure upside, consistently under-managed).
The enterprises that pay the least for equivalent Microsoft coverage are not the largest — they are the most prepared. Scale helps at the D-level threshold structure, but the non-standard discount layer and the credit utilisation layer are available to organisations of any size. The key is knowing where the money is and building a coherent strategy to capture it before the renewal conversation begins.
If your next EA renewal is within 12 months, we recommend starting with a comprehensive renewal preparation process that maps your current position across all six pricing layers. The preparation investment consistently generates returns of 8–12x in the first renewal cycle.