Microsoft Enterprise Agreement Guide: Structure, Components & Buyer Strategy 2026

What Is the Microsoft Enterprise Agreement?

The Microsoft Enterprise Agreement (EA) is a volume licensing contract designed for organisations with 500 or more users or devices. It provides a single agreement framework under which the organisation can acquire Microsoft 365 (E1, E3, E5, E7), Azure services, Dynamics 365, and on-premises server software at negotiated rates over a three-year term.

The EA is not a single document. It is a structured collection of agreements — the master Enterprise Agreement, one or more Enrollments that specify products and quantities, and any applicable Product Terms that govern usage rights. An EA without at least one active Enrollment is legally incomplete and provides no licensing rights. This layered structure is frequently misunderstood by procurement teams who treat the EA as a single signed contract.

Organisations sign directly with Microsoft (EA Direct) or through a Microsoft-authorised reseller or distributor (EA Indirect). In both cases, the commercial terms — discounts, True-Up mechanics, payment schedules — are negotiated against the same Microsoft price list, but the billing and relationship management flows through the reseller in indirect scenarios.

Who Qualifies for an EA?

The EA requires a minimum of 500 qualifying users or devices at the enterprise level. Microsoft defines "qualifying users" broadly to include full-time employees, part-time employees, and contractors who regularly use Microsoft software. The 500-seat threshold applies to the entire qualifying entity, not a single legal entity within a group, which creates complexity for organisations with subsidiaries in multiple geographies.

Organisations below 500 seats are typically directed toward the Microsoft Customer Agreement (MCA) or Cloud Solution Provider (CSP) programs. Organisations above 500 but below 1,000 seats often have less negotiation leverage than Microsoft's field team implies — the EA economics for small-to-mid-size enterprises are less favourable than Microsoft's commercial materials suggest.

EA Anatomy: The Four Core Components

1. The Enterprise Agreement Master Document

The master EA document governs the overall commercial relationship. It defines licensing rights and restrictions, transfer rights for mergers and acquisitions, termination clauses and ramp-down provisions, audit rights and compliance obligations, and the governing law and dispute resolution framework. The master document changes relatively infrequently, but Microsoft has updated key provisions around data processing and AI workloads in recent years that warrant careful review by legal counsel before signing.

2. Enterprise Enrollment

The Enterprise Enrollment is the most common enrollment type. It specifies the products the organisation is committing to purchase, the licensed quantities at the start of the term, the pricing tier, and the payment schedule. Every EA must include at least one Enrollment to be operative.

The Enterprise Enrollment locks in the product commitment for the three-year term. Quantities can be increased at any anniversary through the True-Up process. Reductions are not permitted mid-term without special contractual provisions — this asymmetry is one of the most important commercial dynamics in any EA negotiation.

3. Server and Cloud Enrollment (SCE)

The Server and Cloud Enrollment covers on-premises server products (Windows Server, SQL Server, System Center) and Azure commitments. Organisations that commit to an Azure monetary commitment within the SCE typically receive better Azure pricing and access to Azure Hybrid Benefit rights that reduce the effective licensing cost of workloads migrated from on-premises to Azure.

SCE pricing for server products is volume-sensitive and negotiated separately from the M365 Enrollment. Organisations with significant on-premises server estates should model SCE economics independently, as the Azure commitment thresholds required for optimal SCE pricing are often structured to create Azure adoption incentives rather than reflect actual workload economics.

4. Subscription Enrollment

The Subscription Enrollment provides similar commercial terms to the Enterprise Enrollment but treats licenses as subscriptions rather than perpetual rights with Software Assurance. Subscription Enrollments typically have lower upfront cost but no perpetual fallback rights on expiry. For organisations that have fully migrated to cloud services and have no on-premises footprint to protect, the Subscription Enrollment can represent better economics — but the loss of perpetual rights requires careful assessment.

The Microsoft 365 SKU Stack: E1, E3, E5, E7

The Microsoft 365 product stack has four enterprise SKU tiers in 2026: E1, E3, E5, and E7. E7 is the new top SKU, released above E5, and Microsoft's field teams are actively moving E5 customers to E7 at renewal. Any procurement team still treating E5 as the ceiling of the M365 stack is operating on outdated information.

E1: Entry-Level Cloud Productivity

Microsoft 365 E1 provides core cloud productivity — Exchange Online, SharePoint Online, Teams, and Office web apps — at approximately $10 per user per month. E1 does not include desktop Office applications, advanced security features, or compliance tools. E1 is appropriate for task workers, frontline workers with limited computing needs, or as a base licence for users with specific application requirements that are supplemented by targeted add-ons.

E3: The Enterprise Baseline

Microsoft 365 E3 at approximately $36 per user per month includes desktop Office apps, Exchange Online, SharePoint, Teams, Entra ID P1, Intune Plan 1, and basic compliance tools. E3 is the most widely deployed SKU in enterprise environments and represents the appropriate baseline for knowledge workers who do not require advanced security, AI, or extended compliance capabilities. Entra ID P1 inclusion provides Conditional Access and dynamic group management, which satisfies most enterprise identity requirements without the E5 premium.

E5: Advanced Security and Compliance

Microsoft 365 E5 at approximately $57 per user per month adds E5 Security (Defender for Endpoint P2, Defender for Identity, Defender for Cloud Apps, Entra ID P2), E5 Compliance (Advanced eDiscovery, Insider Risk Management, Communication Compliance), and Microsoft Teams Phone System. E5 is appropriate for users who genuinely require advanced threat protection, privileged identity management, or regulatory compliance tooling — but the E5 shelfware rate across enterprise deployments is consistently 30 to 50 percent. Most organisations should apply E5 selectively to high-risk roles, security personnel, and regulated users rather than deploying it organisation-wide.

E7: The New Top SKU

Microsoft 365 E7 is the newest and highest tier in the M365 SKU stack, released above E5. E7 bundles advanced AI capabilities — including Microsoft 365 Copilot — security features previously sold as E5 add-ons, and next-generation compliance tools into a single per-user SKU. Microsoft's field teams are actively pushing E5 customers to upgrade to E7 at renewal, positioning it as the logical next step in the M365 journey. Microsoft 365 Copilot was previously sold as a $30 per user per month add-on; E7 includes Copilot within the base SKU, making the upgrade economics appear favourable when presented by Microsoft's account team. Independent TCO analysis before accepting E7 upgrade proposals is essential.

The True-Up Mechanism: How Annual Reconciliation Works

The True-Up is one of the most commercially significant — and most mismanaged — aspects of the Microsoft Enterprise Agreement. Understanding it precisely is the prerequisite for avoiding unnecessary spend.

What the True-Up Is

At each anniversary of the EA start date (not at Microsoft's fiscal year end), organisations must reconcile their actual deployed user and device counts against the quantities committed at EA signing. Any increase in deployed users above the committed quantity must be reported and invoiced at the contracted rate. True-Up is a one-way ratchet: organisations must pay for growth, but cannot reduce their committed quantities mid-term without special provisions.

True-Up Timing and Process

The True-Up window typically opens 60 to 90 days before the anniversary date. Microsoft sends a True-Up order form listing the enrolled products and committed quantities. The organisation must complete an inventory of deployed users, compare against committed quantities, and submit the True-Up order for any increases. Failure to submit a True-Up is a compliance breach — Microsoft interprets deployed-but-unlicensed usage as a licensing gap, which creates audit exposure.

Microsoft's account teams use the True-Up as a commercial touchpoint. True-Up meetings frequently become upsell conversations where account teams introduce new products, propose SKU upgrades, and present Azure consumption analyses. Organisations should prepare for True-Up meetings with independent licence data rather than relying on Microsoft's usage reports, which are designed to identify under-licensing rather than over-licensing.

True-Up Strategy: Avoiding Overpayment

Three years of True-Up data tells the complete story of your Microsoft deployment. Organisations that conduct an independent licence audit before the True-Up deadline consistently identify 15 to 30 percent of reported True-Up spend that can be avoided through unused licence reclamation, accurate headcount reporting, and product rationalisation. Key actions before any True-Up include conducting a proper licence inventory across all enrolled products, reclaiming licences from leavers and inactive accounts before the True-Up snapshot date, reviewing whether product mix is still appropriate (E5 users who do not use E5 features should be downgraded to E3 at the next available opportunity), and challenging Microsoft's usage data with your own infrastructure-sourced counts.

Discount Structure: What's Changed in 2025–2026

The EA discount landscape has changed materially in the last 18 months, and many procurement teams are still operating on assumptions that reflect the pre-2024 pricing environment.

Volume Discount Tier Collapse

Microsoft eliminated volume-based Level A–D pricing tiers for online services effective November 2025. Under the previous structure, organisations with large seat counts qualified for Level B, C, or D pricing at 6 to 12 percent below Level A list price. From November 2025, online services — Microsoft 365, Dynamics 365, Power Platform — are priced at Level A list for all customers regardless of seat count. Organisations at former Level D pricing face an effective pricing reset of 8 to 12 percent. On-premises licence Level discounts remain, but the cloud services that constitute the majority of modern EA spend have moved to flat pricing.

Current Discount Benchmarks

Standard EA discounts in 2026 are 10 to 20 percent off list price, down from the historical 15 to 25 percent range that most procurement benchmarks were built against. These discounts now require active negotiation and are not automatically applied based on volume. NCE (New Commerce Experience) monthly commit products are priced at list with no discount. NCE annual commit products carry up to 5 percent discount versus monthly pricing. Three-year commit terms provide better discounts but significantly reduce flexibility to adjust quantities downward.

What Moves Discounts in 2026

Despite the tier collapse, custom discounts remain negotiable through several levers. Total contract value — the larger the overall EA commit, the more room Microsoft's field teams have to apply additional discount. Azure commitment — organisations willing to commit to a meaningful Azure monetary commitment within the SCE unlock better M365 pricing through the bundled commercial relationship. Competitive positioning — credible evidence that the organisation is evaluating Google Workspace, Zoom, or AWS-based alternatives for specific workloads creates leverage. Microsoft fiscal year timing — signing or renewing in Microsoft's Q4 (April through June) gives buyers the highest leverage, as Microsoft field representatives have maximum incentive to close deals and discount before June 30. And multi-year lock-in trade-offs — Microsoft will apply larger discounts in exchange for longer commitment terms, but this reduces the buyer's flexibility and should only be accepted when future headcount and product mix are predictable.

EA vs MCA: Microsoft's Commercial Program Shift

Microsoft has been actively steering enterprise customers toward the Microsoft Customer Agreement (MCA) since 2022, and this trend has accelerated. Understanding why Microsoft prefers MCA — and what buyers lose in the transition — is critical context for any EA renewal decision.

What the MCA Changes

The MCA is a transactional agreement that replaces the EA's structured three-year commitment with a more flexible monthly or annual subscription framework. Microsoft's field teams present MCA as a simplification — fewer documents, faster signing, and more flexible terms. The commercial reality is that MCA moves buyers from a negotiated-price environment with established discounts to a consumption-based environment where Microsoft's list price is the default and discount leverage is structurally lower.

Under the EA, organisations lock in pricing at signing for the three-year term. Under MCA, Microsoft can adjust pricing on NCE products with 30 days' notice. The EA includes committed quantities that Microsoft must honour. MCA pricing is predominantly at NCE list. EA negotiations happen once every three years with significant preparation and leverage. MCA negotiations happen continuously through Microsoft's account team relationship, where organisational buying power is diluted.

When EA Remains the Better Choice

The EA remains the better commercial framework for organisations with 500 or more users when headcount is stable and predictable, when the organisation has significant on-premises infrastructure requiring perpetual licences and Software Assurance, when the volume and complexity of Microsoft products warrants a single negotiated master agreement with locked pricing, and when the organisation has sufficient internal or advisory expertise to manage a three-year structured commercial relationship.

MCA may be appropriate when the organisation is growing rapidly and needs the flexibility to add users without True-Up penalties, when the Microsoft footprint is predominantly Azure and cloud-native with minimal M365 complexity, or when the organisation has deliberately chosen to reduce Microsoft dependency and wants flexibility to exit over a 12-month window.

EA Renewal: The Critical 18-Month Window

EA renewal preparation should begin 18 months before the EA expiry date — not 90 days, as Microsoft's standard renewal process implies. The 18-month window provides sufficient time for the activities that determine whether an organisation enters renewal with leverage or without it.

Months 18–12 Before Expiry: Data and Baseline

Conduct a comprehensive licence inventory across all enrolled products. Identify E5 shelfware (users with E5 licences who do not use E5 features), unused add-ons, and products that can be eliminated or renegotiated. Generate three years of True-Up data analysis. Build an independent view of your Microsoft total cost of ownership — not from Microsoft's ECIF or account team tools, but from your own procurement and finance systems. This baseline is the foundation of every subsequent negotiation move.

Months 12–6 Before Expiry: Leverage Creation

Develop credible alternatives to Microsoft's renewal proposal. This does not require committing to a migration — it requires building a documented business case that demonstrates the organisation has evaluated Google Workspace for specific workloads, that Azure cost has been benchmarked against AWS and Google Cloud, and that the total cost of maintaining Microsoft's full stack at current pricing has been compared against a selective-deployment model. Microsoft's account teams respond to evidence of evaluation — vague dissatisfaction does not create discount leverage, but a documented alternative scenario does.

Months 6–0 Before Expiry: Active Negotiation

Enter the formal negotiation with a written proposal — not a verbal conversation. Present your licence inventory, your rationalised product mix, your proposed quantities and pricing targets, and the conditions under which you will sign. Avoid signing in Microsoft's Q1 (July–September), when Microsoft's field teams have minimal incentive to close. Sign in Q4 (April–June) or use an approaching Microsoft fiscal quarter end to create urgency on Microsoft's side. Lock pricing for the full three-year term and negotiate caps on any variable components — Azure consumption, Copilot seats, and add-on products — that Microsoft may attempt to adjust at annual commitment points.

Common EA Mistakes and How to Avoid Them

Accepting Microsoft's product mix without independent analysis: Microsoft's renewal proposals are designed around Microsoft's revenue objectives, not your organisational requirements. Every product in a renewal proposal should be justified by actual usage data before being accepted.

Treating E5 as the default premium tier: E5 shelfware is one of the largest sources of avoidable Microsoft spend. Organisations should audit E5 feature adoption before every renewal and right-size to E3 for users who do not require E5 capabilities. And remember — E7 is now the new top SKU above E5, so any discussion of the M365 ceiling needs to account for the E5-to-E7 upsell motion.

Signing without True-Down provisions: Standard EAs do not permit quantity reductions mid-term. If your headcount is volatile, negotiate explicit True-Down rights at each anniversary or EAS provisions that protect against overpayment if the workforce shrinks.

Ignoring the Microsoft fiscal calendar: Microsoft's Q4 (April through June) is the optimal signing window. Microsoft's field representatives have maximum close incentive in this period and significantly more discretionary discount authority than in Q1 or Q2.

Starting renewal negotiations too late: Organisations that begin EA renewal discussions six months before expiry consistently achieve worse outcomes than those that start 18 months out. Late negotiation creates time pressure that Microsoft's account teams exploit.

Using Microsoft-provided ROI tools for decision-making: Microsoft's licensing calculators, TCO tools, and ECIF credits are designed to justify purchasing more Microsoft products, not to help you identify the optimal spend level. Independent analysis of the same data consistently produces different conclusions.

Software Assurance: What You Actually Get

Software Assurance (SA) is included with EA licences and provides version upgrade rights, training vouchers, deployment planning services, and License Mobility rights. SA is frequently cited by Microsoft's account teams as a significant value component of the EA premium over SPLA or OEM pricing. The practical value of SA depends almost entirely on whether the organisation deploys SA benefits systematically.

Organisations that audit their SA benefit consumption consistently find that 40 to 60 percent of SA benefits go unclaimed. Training vouchers expire. Deployment planning services are never scheduled. License Mobility rights for Azure hybrid workloads — potentially the most valuable SA benefit — are often not activated. If you are paying the EA premium that includes SA, you should be consuming SA benefits. An annual SA benefit audit is a standard component of Redress Compliance's EA management engagements.

Azure Within the EA: Committed vs Consumed

Azure is increasingly a significant component of EA spend, but the mechanics of Azure within an EA are different from M365. Azure is a consumption-based service — you commit to an Azure monetary amount (MACC) and Microsoft draws down against that commitment as you consume Azure resources. The commitment level determines your Azure pricing tier.

Azure Reserved Instances (RI) and Azure Savings Plans represent the two primary cost optimisation mechanisms within Azure. Reserved Instances commit to specific VM types and sizes for one or three years in exchange for 30 to 60 percent savings versus pay-as-you-go. Savings Plans provide flexible compute savings at 17 to 37 percent below pay-as-you-go without the rigidity of Reserved Instance commitments. Both mechanisms should be modelled against actual Azure workload patterns before committing — over-provisioning Reserved Instances creates stranded spend that is difficult to recover.