Microsoft Enterprise Agreement Guide 2026
How to structure, true-up, and renew a Microsoft Enterprise Agreement without overbuying — covering EA thresholds, Azure commitments, Microsoft 365 right-sizing, and the Copilot pricing question every CIO now faces.
Executive Summary
The Microsoft Enterprise Agreement is the most consequential software contract most enterprises sign, bundling Microsoft 365, Windows, server products, and Azure into a three-year commitment that quietly shapes IT spend for the rest of the decade. Its complexity is commercial: bundling and "future-proofing" suites push customers toward higher editions and larger commitments than usage justifies.
This guide explains how the EA is constructed, how true-ups and the annual order really work, how Azure Monetary Commitments (MACC) are discounted, and where Microsoft 365 and Copilot spend can be right-sized. The recurring theme for buyers: Microsoft's proposal is built around its sales targets, not your utilization — and the difference between the two is typically 15–30% of the contract value.
1. How the Enterprise Agreement Is Structured
An EA is a three-year commitment available to organizations above roughly 500 users or devices. It is built from "enrollments" — most commonly the Enterprise Enrollment for organization-wide products (Microsoft 365, Windows, Office) and the Server and Cloud Enrollment (SCE) for server workloads and Azure. The defining feature is the organization-wide commitment: certain products must be licensed across the entire qualified user or device base, which is exactly the mechanism that pushes spend upward when Microsoft proposes a higher edition "for consistency."
Pricing is set by a "level" tier based on size, and discounts are layered on top through negotiation. The critical insight is that the price level is far less negotiable than the edition mix and the commitment quantities. Most overspend is not a failure to win another discount point; it is agreeing to license E5 organization-wide when a segmented mix of E3 and E5 matches actual need.
Microsoft sellers are measured heavily on cloud and premium-suite growth. A proposal that moves your whole estate to E5 and adds an Azure commitment is optimized for the seller's compensation plan. That does not make it wrong — but it should be tested against your usage data before signing, not after.
2. True-Ups and the Annual Order
The EA's signature mechanic is the annual "true-up." Throughout the year you deploy what you need; once a year you report the net increase and pay for it. There is no true-down within the term — quantities can only ratchet up — which is why the initial baseline and the edition mix matter so much. Over-commit at signing and you carry that cost for three years; under-baseline and you simply true-up to reality without penalty.
This asymmetry is a planning tool, not a trap, once understood. Baseline conservatively to genuine current need, deploy growth as it actually occurs, and reconcile annually. The table below shows the cost difference between an aggressive baseline and a usage-led one for a 5,000-seat estate.
| Approach | Year 1 licensed | 3-year cost (indicative) | Outcome |
|---|---|---|---|
| Aggressive: 5,000 × E5 day one | 5,000 E5 | $9.5M | Locked in; pays for unused premium features |
| Usage-led: 3,500 E3 + 1,500 E5, true-up growth | Segmented | $6.8M | Matches need; true-ups add only real growth |
3. Microsoft 365 Right-Sizing
The single largest recurring saving in most EAs is matching the M365 edition to the role. Microsoft markets E5 as the default, but its premium value — advanced security, compliance, analytics, and voice — is genuinely consumed by a minority of users in most organizations. Frontline and task workers are frequently over-licensed on E3 when an F-series license fits, and knowledge workers are placed on E5 when E3 plus a targeted security add-on delivers the same protection at lower cost.
Right-sizing is a data exercise: pull actual feature usage from the Microsoft 365 admin and security centers, segment users by role, and license to the role rather than to the org-wide default. The savings are durable because they reduce the committed baseline, not just a one-year order.
We model your actual M365 usage against Microsoft's proposed mix before you sit down — clients routinely recover 15–30% of the proposed contract value. Start with a confidential baseline review.
4. Azure: MACC, Discounting, and Consumption Risk
Azure is typically committed through a Microsoft Azure Consumption Commitment (MACC) — a dollar amount you agree to consume over the term in exchange for discounting and access to Marketplace benefits. The leverage is real: Microsoft discounts committed Azure aggressively, and eligible Marketplace purchases can count toward the MACC. The risk is equally real: an oversized MACC that you cannot consume becomes shelf-dollars, and aggressive ramp assumptions in year one create a shortfall scramble later.
| Lever | Effect | Watch-out |
|---|---|---|
| MACC (consumption commitment) | Unlocks discount & Marketplace credit | Size to a credible forecast, not the discount offered |