The complete Microsoft Enterprise Agreement guide.
A Microsoft Enterprise Agreement locks 500+ seat organisations into a fixed annual commitment governed by true-up, price protection and exit terms that quietly favour the vendor. This note breaks down EA structure, the E3/E5 mix, Azure MACC, NCE and the negotiation levers that recover 15–30% at renewal.
Treat the EA as a negotiation, not a renewal form. The default path — auto-renew at a 10–15% uplift, license E5 across the board, over-commit on Azure MACC — leaves 15–30% on the table. Right-size the commitment, blend E3 with selective E5 plus Defender, layer Hybrid Benefit onto Reserved Instances, and open renewal talks 90 days out against Microsoft's June fiscal year-end.
01 Key findings
Highest point of use is the trap. True-up counts your peak, not your average — temporary project VMs or pre-audit seat counts get billed at your 12-month ceiling.
E5-for-everyone is the most common overspend. Selective E5 for executives and high-risk teams, E3 for the rest, plus Defender for Office 365 as an add-on, matches the security posture at 20–30% lower cost.
Azure value leaks without Hybrid Benefit and RIs. Reserved Instances (30–65% off) stack with Azure Hybrid Benefit against your MACC commitment — most buyers skip one or both.
Commitment sizing beats discount hunting. Over-committing triggers non-refundable true-ups; Microsoft credits future months rather than refunding underspend, so cash left on the table rarely comes back.
Timing is leverage. Renewals landing April–June hit Microsoft's Q4 close and reliably earn 3–5 additional discount points for no concession.
NCE is flexibility, not savings. Monthly NCE costs slightly more per unit; use it for volatile or temporary users and keep the stable core on EA pricing.
02 EA structure & pricing
An EA is a volume programme for organisations with 500+ eligible licenses, running 1–3 years. Four interdependent components decide your price, flexibility and exposure — and each is where money leaks.
| Component | What it governs | Where the money leaks |
|---|---|---|
| Commitment level | Fixed annual dollar amount, billed in 12 monthly instalments, drawn down as you buy | Set too high on the first term — underspend is credited, not refunded |
| Products & price curve | Per-family pricing (M365, EMS, Server & CAL, Azure, Dynamics 365, Power Platform) | Fragmented buying misses volume tiers — E3 can fall from ~$11 to ~$8.50/user as seats rise |
| Software Assurance & add-ons | On-prem/cloud use rights, Hybrid Benefit eligibility, Copilot and security add-ons | Add-ons priced off-discount; SA lapses forfeit Hybrid Benefit |
| Term length | 1, 2 or 3-year terms | 3-year lock now only ~3–5% cheaper than 1-year, but sacrifices flexibility |
Model current state, then commit to 90% of projected need, not 110%. Microsoft's own guidance adds 10–15% for growth, which routinely produces annual overpayment. A modest under-commitment captures the EA discount while leaving headroom for variance, without stranding cash in non-refundable credits.
03 Microsoft 365: E3 vs E5
Microsoft 365 is the bulk of EA spend, and the E3/E5 mix is where the largest savings emerge. The list gap between E3 and E5 is 40–50%; EA pricing compresses it, but blanket E5 still overpays.
- Office apps, Exchange, Teams, SharePoint, OneDrive
- Baseline security and device management
- Add Defender for Office 365 at ~$5–6/user vs full E5 upgrade
- No advanced threat protection out of the box
- No Advanced eDiscovery or Azure AD P2
- No Teams Phone / voice
- Defender for Office 365 advanced threat protection
- Advanced compliance & eDiscovery, Azure AD P2
- Voice capabilities and advanced analytics
- Licensing all users overpays where few need the features
- Full upgrade ~$8–10/user vs a targeted add-on
- Feature adoption often lags the spend
- 20–30% lower cost at equal security posture
- E3 + Defender for Office 365 for at-risk users
- Teams Premium reserved for genuine power users
- Requires an accurate user-risk segmentation
- Needs annual audit to prevent licence creep
- Business Standard/Premium rarely justified at EA scale
Model E3 + Defender for Office 365 before accepting blanket E5. For E3 organisations, adding Defender as a standalone licence (~$5–6/user/month) is more cost-effective than upgrading everyone to E5 (~$8–10/user). Bring this proposed mix to renewal — it commonly lands 20–30% below full E5 while holding the same posture.
04 Azure in the EA
Azure grows faster than any other Microsoft product, and its pricing model differs from the per-user predictability of Microsoft 365. Most buyers leave 15–30% of Azure value unclaimed by not layering the three levers below.
MACC commitment
The Microsoft Azure Consumption Commitment applies credits monthly against a committed dollar amount. Model the trailing 12 months, adjust for growth, and set MACC to 85–90% of projected spend to avoid overage true-ups and stranded refunds.
Reserved Instances
1- or 3-year prepaid compute commitments deliver 30–65% off on-demand. Purchase RIs inside the EA so they draw down against MACC — a stable, predictable base beneath variable consumption.
Azure Hybrid Benefit
Windows Server and SQL Server licences with active Software Assurance run in Azure without double-paying for the licence; SQL saves ~$3–4 per core/month. Confirm SA is active before renewal.
Stack them
The levers compound: the EA discount on compute, plus RI prepayment savings, plus Hybrid Benefit licence savings on top. Layered correctly they recover the 15–30% most estates leave behind.
05 New Commerce Experience
NCE offers monthly flexibility and mid-contract upgrades without waiting for annual true-up. It coexists with EA pricing rather than replacing it — the question is which products sit where. Five dots = strongest fit.
Leaving an active EA for NCE can trigger true-up or charge-back provisions. Read your termination terms first, and at renewal decide explicitly which products stay on EA pricing, which move to NCE, how blended discounts apply, and whether MACC covers NCE-purchased Azure.
06 True-up mechanics
True-up is the annual reconciliation of commitment against actual usage. On your anniversary, Microsoft measures 12-month usage, prices it at your per-unit rate, subtracts your commitment, and invoices the difference — underspend is credited forward, not refunded.
Microsoft counts your peak, not your average. Drop from 2,000 to 1,800 E3 users over the year and you are still billed for 2,000. Spin up 500 VMs for a 30-day project and that peak sets your count. If your business is seasonal, negotiate a quarterly average or 90th-percentile methodology instead of raw HPU.
| Pitfall | What triggers it | Fix |
|---|---|---|
| Unused licences | 5,000 seats assigned, 4,000 active — the extra 1,000 (~$120k/yr) still counted | Count only activated licences; reclaim unassigned seats before true-up |
| Shared mailbox overage | Service and resource mailboxes silently trigger extra E3 counts | Negotiate shared-mailbox exclusions in EA terms |
| Azure over-commitment | $500k MACC against $650k consumption — a $150k true-up charge | Right-size MACC and buy RIs earlier to lock consumption |
Negotiable true-up terms include decline limits (max 15% annual decrease), partial credits for underspend, fiscal-year rather than calendar measurement, and exclusion of dev/test or service-account categories.
07 Negotiation levers
EA negotiation is not a fair fight if you walk in unprepared. Microsoft's account teams carry sophisticated models and quota incentives. These levers level the field — illustrative ceilings on additional discount:
Renewal timing
Microsoft's fiscal year ends in June. Renewals landing April–June meet Q4 quota pressure and capture 3–5% simply on timing. December renewals carry the least leverage.
Commitment reduction threat
If you are chronically over-committed and your agreement allows a 10–20% annual decline, a credible reduction threat forces better pricing to preserve the commitment level.
Competitive alternative
A genuine Google Workspace pilot for selected teams — not a bluff — typically unlocks 10–15% to prevent it. A CTO willing to evaluate carries real weight.
Licensing-mix reframe
Frame it as “same commitment level, better product mix.” Shifting full E5 to blended E3 + selective E5 + Defender preserves Microsoft's revenue while capturing pricing flexibility.
08 Copilot licensing
Copilot is Microsoft's fastest-growing product and its EA treatment is still evolving. Pricing is fluid as Microsoft calibrates enterprise willingness-to-pay; expect it to stabilise by 2027.
| SKU | Indicative price | What it covers |
|---|---|---|
| Copilot for Microsoft 365 | $30/user/month | AI in Office, Teams analysis, Outlook summarisation (enterprise; requires E5 + add-on) |
| Copilot Studio | ~$25/month per environment | Custom Copilot creation and agents |
| GitHub Copilot for Business | $21/user/month | Enterprise code generation |
| Azure OpenAI Service | Pay-per-token | Custom applications — often 10–100x cheaper than Copilot Pro at scale |
Negotiate Copilot as a separate bundle, not folded into your baseline. Request 25–40% pilot pricing for a 6-month evaluation, keep Copilot out of your MACC commitment so pilot cost does not inflate your true-up baseline, clarify data residency, and model it as an 18–24 month ROI play concentrated on executives, sales and R&D.
09 Common EA traps
The most expensive mistakes across 500+ engagements — and how to avoid each.
Over-licensing users
E5 for all when only a fraction need it can waste $840k/yr at 10,000 seats. Run an annual audit and reclaim or remove unassigned licences.
Allowing auto-renewal
Auto-renewal defaults to a 10–15% uplift. Diarise renewal 90 days before expiry and run a competitive process to recover 10–20%.
Mixing EA and NCE blindly
NCE add-ons bought without a stated blended discount often land at list. Fix the discount structure in writing before purchasing.
Untracked Azure commitments
Under- or over-consuming MACC both cost money. Track monthly consumption against commitment and hold 90–100% via RI adjustment.
Ignoring Hybrid Benefit
On-prem Windows/SQL with SA can cut Azure cost 20–30%. Keep a central licence registry and configure VMs to claim it.
Unvalidated true-up
Complex methodology produces errors — miscounted mailboxes, test users, double-counted devices. Request documentation and dispute in writing.
10 Recommendation
Take the ~3–5% premium over a 3-year term when M&A, reorganisation or vendor evaluation is plausible. You keep the right to re-optimise commitment, mix and term every year without penalty.
Lock the deeper discount only with a stable 5-year cloud roadmap and predictable headcount. Pair it with negotiated decline limits so a fixed term does not become a fixed overpayment.
Keep the stable core on EA pricing and route new projects, temporary and seasonal users to NCE. Confirm how MACC applies to NCE-purchased Azure so overlapping capabilities are not paid for twice.
Model your EA before you sign
We audit your current agreement, build the optimal commitment and mix, and negotiate the renewal directly with Microsoft.
11 Frequently asked questions
What is a Microsoft Enterprise Agreement?
A volume licensing programme for organisations with 500+ eligible licenses. It provides standardised pricing with a fixed annual commitment, true-up provisions, and coverage across Microsoft 365, Azure, Windows Server, SQL Server, Dynamics 365 and Power Platform. EAs typically run 1–3 years.
How does the Microsoft EA true-up work?
An annual reconciliation: Microsoft counts the highest point of use for users or devices over 12 months, multiplies by your per-unit price, and subtracts your commitment. If consumption exceeds commitment you owe the difference; if it is lower, credits apply to future months rather than a refund.
Should we choose E3 or E5 licensing?
E3 covers core productivity; E5 adds advanced security, compliance, voice and analytics. Most organisations save 20–30% with a selective mix — E5 for executives and high-risk teams, E3 plus targeted add-ons such as Defender for Office 365 for everyone else. Validate actual requirements before licensing E5 broadly.
How do we negotiate a better Microsoft EA?
Time renewals to Microsoft's June Q4, threaten credible commitment reductions, present a genuine competitive alternative, optimise the product mix, and choose shorter terms for flexibility. Engaging an advisory firm typically captures 15–30% savings. Start 90 days before expiry.
What is Microsoft NCE and how does it affect our EA?
The New Commerce Experience offers monthly flexibility and mid-contract upgrades without waiting for true-up, usually at a slightly higher unit price. Many organisations run a hybrid model — stable users on EA, volatile or temporary licenses on NCE — and confirm how MACC applies to NCE-purchased Azure.
Can we reduce our Microsoft EA commitment mid-term?
Most agreements allow reductions during annual true-up periods, subject to decline limits (typically 10–25%). Mid-term reductions outside true-up require negotiation with your Microsoft Account Executive and may carry financial adjustments. Review your specific decline provisions.
The Licensing Edge
Weekly Microsoft and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.