The Microsoft Enterprise Agreement in Plain English
A Microsoft Enterprise Agreement is a fixed three-year volume licensing contract under which an organisation commits to licensing Microsoft products and cloud services at a defined volume and a locked price for the duration of the agreement. In exchange for that volume commitment and three-year term, Microsoft provides access to its full product catalogue, Software Assurance benefits, and — historically — meaningful discounts off list price.
The EA was introduced as Microsoft's flagship programme for large organisations, and it remains the dominant licensing vehicle for enterprises with complex Microsoft environments. As of 2026, the majority of organisations with more than 2,400 users still renew under the EA framework, though Microsoft is actively steering mid-market organisations with 500 to 2,400 users toward the Microsoft Customer Agreement for Enterprise (MCA-E) instead.
The EA is administered through Microsoft's Volume Licensing platform and typically involves a Microsoft account team, a Licensing Solution Provider (LSP) or reseller, and — for larger organisations — a direct relationship with Microsoft's enterprise field sales organisation. Redress Compliance works exclusively on the buyer side of these negotiations, ensuring our clients extract maximum value from every EA they sign.
Who Is the EA Designed For?
The EA is available to commercial organisations with a minimum of 500 users or devices, and to public sector organisations with a minimum of 250 users or devices. Historically Microsoft applied this threshold uniformly, but the commercial landscape in 2026 is more nuanced.
Microsoft's internal guidance now directs organisations with fewer than 2,400 users toward CSP or MCA-E rather than EA. Organisations in the 500 to 2,400 user band may still access an EA, but Microsoft field teams are less likely to initiate the conversation and may actively promote alternative agreements. Above 2,400 users, the EA remains the default enterprise licensing vehicle, though the MCA-E transition is underway for many Azure-heavy organisations regardless of seat count.
For organisations weighing their options, the EA's three-year price lock is its most significant differentiator. With Microsoft announcing pricing increases effective July 1, 2026 — including SKU-level adjustments across M365 suites — organisations that sign or renew EA agreements before that date will shield their budgets from those increases for the full three-year term.
What Does the EA Cover?
The EA covers Microsoft's entire commercial product catalogue, which means almost any Microsoft software or cloud service can be included. The specific structure depends on the enrollment type chosen within the EA framework.
Enterprise Enrollment (EE)
The Enterprise Enrollment is the most common component, primarily used for Microsoft 365 (formerly Office 365), Windows, and other desktop productivity products. Under EE, organisations select a core desktop platform — typically M365 E3, E5, or the newer E7 tier — and commit to deploying that platform across all qualifying users organisation-wide. The M365 SKU stack runs E1, E3, E5, and E7, with E7 the current top tier, bundling advanced AI capabilities, Microsoft 365 Copilot, and enhanced security features previously sold as separate add-ons. Microsoft field teams are actively promoting E7 upgrades at renewal for organisations currently on E5.
Server and Cloud Enrollment (SCE)
The Server and Cloud Enrollment covers Microsoft's server infrastructure products including Windows Server, SQL Server, SharePoint Server, Exchange Server, and System Center. The SCE also includes access to Azure as part of a unified commitment. For organisations running hybrid environments — on-premises infrastructure alongside Azure cloud — the SCE provides the licensing mechanism to manage both under a single agreement with Azure Hybrid Benefit rights.
Azure Commitment
Azure consumption is handled separately from the EE, typically through a Microsoft Azure Consumption Commitment (MACC). Azure pricing under an EA can follow Reserved Instances (RI) or Azure Savings Plans for compute workloads, providing 30 to 65 percent savings over pay-as-you-go rates in exchange for one-year or three-year commitments. Azure is automatically accessible when you enrol in any EA component; it can also be licensed as a standalone commitment.
Dynamics 365 and Power Platform
Dynamics 365 CRM and ERP applications, along with Power Platform (Power Apps, Power Automate, Power BI), can be added to the EA as line items. Dynamics 365 has specific attach licence rules: qualifying base licences are required before attaching certain application licences, and Microsoft has tightened enforcement of these rules from January 2026 onwards.
Preparing for your EA renewal or first-time negotiation?
Our Microsoft licensing advisory team has completed 200+ EA engagements across EMEA and North America.How the Annual True-Up Works
The True-Up is one of the most misunderstood — and most financially consequential — elements of the Microsoft Enterprise Agreement. Every EA includes an annual True-Up obligation: once per year, on or before the anniversary of your enrollment, you are required to report any increase in the number of users or devices covered by the agreement and pay for those additions at your contracted per-unit price.
The True-Up is a self-reported process. Microsoft does not automatically audit you at True-Up time, but the contractual obligation to report accurately exists. Organisations that consistently under-report at True-Up accumulate a compliance exposure that becomes a liability at renewal or audit. The True-Up date falls on the anniversary of your enrollment start — not Microsoft's fiscal year end — so it is independent of Microsoft's June 30 year-end calendar.
What the True-Up Covers
The True-Up covers all increases in licensed quantities since the previous anniversary. If your organisation has grown by 200 users since your last True-Up and those users are using M365 E3, you must report and pay for those 200 seat additions at your contracted E3 rate for the remaining months of the current year.
The True-Up does not allow reductions. If you have over-licensed — deployed fewer users than contracted — you cannot reduce your committed quantity mid-term. True-Down is only possible at renewal, not during the term. This asymmetry is a significant risk for organisations that over-commit at the start of an EA term, which is why right-sizing the initial commitment is one of the most important decisions in any EA negotiation.
True-Up as a Negotiation Opportunity
Experienced buyers treat the annual True-Up not merely as a compliance obligation but as a negotiation touchpoint. The True-Up order is placed through your LSP and creates a commercial conversation with Microsoft. Organisations that plan ahead — identifying product mix changes, licence transitions, and new requirements several months before the True-Up date — can use the True-Up to add products at contracted rates, transition from one SKU to another, and document their consumption profile ahead of renewal.
Software Assurance: What You Are Paying For
Software Assurance (SA) is mandatory under the EA and is embedded in the per-unit pricing for all perpetual licences and most subscription products. SA is not a separate line item; it is built into the EA pricing structure. Understanding what SA provides is important because it forms part of the value justification for EA pricing versus alternative programmes.
SA provides upgrade rights — the right to deploy new product versions released during the EA term at no additional licence cost. For organisations running Windows Server and SQL Server, SA provides the Azure Hybrid Benefit, allowing on-premises licences to be used in Azure without paying Azure's full compute rate. SA also provides step-up licence rights, training vouchers, Home Use Programme entitlements, and access to Microsoft's Customer Success team for deployment planning.
For cloud-only products like M365 and Dynamics 365, SA is less directly relevant because subscription products are inherently evergreen. The SA value in an EA context for cloud products is primarily the training entitlements and the Customer Success resources, not the upgrade rights that drive SA value for on-premises software.
EA Discounting in 2026: What to Expect
The discount landscape for Microsoft EA negotiations has shifted significantly over the past three years. Historically, large enterprises could achieve discounts of 15 to 25 percent off Microsoft's list price under an EA, driven by volume tiers and competitive pressure. The current reality is different: standard EA discounts now land in the 10 to 20 percent range, reflecting Microsoft's stronger market position and the deliberate collapse of volume-based discount tiers.
From November 2025, Microsoft eliminated volume-based pricing tiers for online services including M365, Dynamics 365, and Power Platform under EA. This change means that an organisation with 30,000 users pays the same unit price as one with 3,000 — what Microsoft called a move to pricing consistency. The practical effect for large enterprises was a meaningful reduction in achievable discount depth, as volume leverage was removed from the pricing model.
Discounts are still available, but they must be actively negotiated rather than assumed. The strongest leverage points in 2026 are competitive alternatives (demonstrating genuine evaluation of Google Workspace or other substitutes), timing (Microsoft's Q4 runs April 1 to June 30 and represents the highest-leverage window as field teams work to close before fiscal year end on June 30), and deal size. Organisations that engage specialist Microsoft EA negotiation specialists consistently achieve better outcomes than those that negotiate directly without independent benchmarking.
EA vs MCA-E: The Critical Difference
The Microsoft Customer Agreement for Enterprise (MCA-E) is the agreement type Microsoft is actively promoting as an alternative or successor to the traditional EA. Understanding the difference is essential for any organisation approaching renewal in 2026.
The EA is a fixed three-year contract with committed volumes and price lock. The MCA-E is an evergreen agreement with no fixed term — it renews annually, and Microsoft can adjust pricing at each renewal. This distinction has major financial consequences. An EA signed before Microsoft's July 2026 price increase locks pricing for three years. An MCA-E renewing after July 2026 resets to new pricing automatically.
Beyond pricing, EA provides stronger negotiation leverage for custom terms including audit protections, jurisdiction clauses, and indemnity provisions. MCA-E uses standardised legal terms with limited customisation. Under the EA, compliance gaps identified at True-Up are corrected annually on a self-reported basis. Under MCA-E, Microsoft retains stronger real-time audit and verification rights, and compliance is assessed continuously rather than annually.
Organisations that transition from EA to MCA-E without independent advice are reporting cost increases of 10 to 30 percent, driven by the loss of price lock combined with Microsoft's recent pricing adjustments. Our Microsoft licensing advisory practice includes EA-to-MCA-E transition analysis as a standard service for renewing clients.
Five Things That Catch EA Customers Off Guard
1. Over-committing at signing: Microsoft's field team has an incentive to maximise the contracted volume at the start of the EA term. Organisations frequently commit to more licences than they will deploy, creating shelfware that inflates cost without delivering value. Right-sizing the initial commitment — even if it means a lower starting volume — is consistently the better strategy. You can True-Up upward; you cannot True-Down mid-term.
2. Missing the True-Up deadline: The True-Up must be submitted 30 to 60 days before your anniversary date. Missing the window creates administrative complications and can result in delayed invoicing that compounds with the next cycle. Calendar the True-Up deadline the moment you sign an EA.
3. Bundling support with the EA: Microsoft Unified Support renewal is often co-timed with the EA renewal by Microsoft's account team. This bundling benefits Microsoft because it limits your ability to negotiate support independently. Decoupling the support renewal date from the EA renewal date gives you the leverage to evaluate alternatives — including third-party Microsoft support providers — without timing pressure.
4. Assuming the LSP is negotiating for you: Licensing Solution Providers are resellers compensated by Microsoft on transaction volume. Their incentive is to close deals, not to optimise your commercial position. Independent Microsoft licensing advisory provides the benchmarking and negotiation support that LSPs structurally cannot offer.
5. Not benchmarking before renewal: Microsoft's account team will present a renewal proposal benchmarked against your current spend trajectory. Without independent benchmarking data — what comparable organisations are actually paying — you have no objective basis for evaluating whether the proposal is competitive. Redress Compliance provides independent EA benchmarking as part of our renewal advisory service.
Stay Ahead of Microsoft Licensing Changes
EA terms, discount dynamics, and Microsoft's product strategy shift regularly. Subscribe to our Microsoft knowledge hub for quarterly updates on EA negotiation strategy and licensing changes.