Microsoft EA true-up: cutting annual reconciliation liability.
Every year, tens of thousands of enterprise Microsoft customers receive a true-up invoice larger than expected — often significantly. This note explains how EA annual reconciliation is calculated, the triggers that inflate it, and the pre-true-up process that reduces liability by 25–45% before Microsoft counts your seats.
The Microsoft EA true-up is retrospective, not prospective — you pay for a year of unlicensed growth at full list, without your EA discount. Organisations that run a self-count 90 days before the anniversary date and deprovision, reallocate, and pre-negotiate consistently pay 25–45% less than those who wait for Microsoft's count.
01 Key findings
True-up is retrospective. If you deployed 500 extra Microsoft 365 E3 seats in July and only find them at your December true-up, you owe from July at full list price — typically without the discount your EA would normally provide.
The counting methodology decides the bill. Microsoft uses one of three approaches — your self-reported count, its own System Center tooling, or an independent SAM assessment. Buyers who negotiate the method before signing consistently achieve better outcomes.
Five triggers drive most surprise invoices. Untracked M&A, Azure BYOL miscounting, uncounted Teams Rooms devices, new products consuming existing entitlements, and contractor / guest access account for the majority of oversized true-ups.
Shelfware hides inside the count. Seats assigned to departed staff, inactive accounts and decommissioned devices still count. A systematic deprovisioning run typically removes 3–8% of licensed seats before Microsoft ever tallies them.
The pre-true-up window is the leverage. Price caps and step-up rates must be written in at EA signature, not at true-up. Run 90 days early and the reconciliation becomes a renewal negotiation — where 15–30% discounts on additions are routine.
02 How the true-up works
A Microsoft Enterprise Agreement typically runs three years. Within each year, an anniversary date requires you to true-up: to pay for any consumption that has grown beyond your originally purchased quantities. At that date, your SAM team or Microsoft's assessment counts qualified devices, users and processors per product; if the count exceeds your licensed quantity, you pay the difference retroactively for the whole preceding year, not just from the point of discovery.
The count covers every product category in the EA. Azure consumption is tracked through your commitment but frequently intersects with true-up calculations.
| Product category | Licensing basis | Examples | Counted at true-up |
|---|---|---|---|
| User subscriptions | Per named user | Microsoft 365 suites, Office, Exchange, Teams | Active assigned users vs purchased |
| Device licences | Per device | Windows, System Center, Teams Rooms | Qualified devices in scope |
| Server licences | Per core / processor | SQL Server, Exchange Server, SharePoint | Cores + virtualisation rules |
| Azure / hybrid | Consumption + BYOL | Azure Hybrid Benefit, reserved capacity | Tracked separately; often intersects |
Negotiate the method before you sign. An EA that specifies self-reported counting gives you control of timing and remediation; one that defaults to a Microsoft-run or third-party SAM assessment surrenders it. The counting clause is worth more than most buyers realise — settle it at signature, not at reconciliation.
03 Expensive true-up triggers
Across more than 200 EA engagements, five situations account for the majority of unexpectedly large invoices.
Untracked M&A activity. Acquired users onboard faster than licensing teams track. Within 90 days we see 15–40% of an acquired workforce on Microsoft 365 against your agreement — counted at list unless you pre-negotiated acquisition provisions.
Azure BYOL miscounting. Azure Hybrid Benefit mobility rules require careful tracking of on-premises versus in-Azure licences. Hybrid estates routinely under-count or mis-categorise, creating apparent gaps that generate liability.
Teams Rooms devices. Conference-room hardware deployed without systematically purchasing Teams Rooms Pro or Basic licences accumulates in the count and can be material at scale.
New products consuming existing entitlements. Copilot, Defender for Endpoint and Purview can silently trigger higher entitlements — a Defender deployment tripping an E5 Compliance requirement cascades into liability.
Contractor and guest access. B2B guests in Entra ID and contractor accounts are frequently miscounted. Premium features accessed by guests — Conditional Access, Entra ID P1/P2 — may require licensing the guest user.
04 Calculating exposure
Before you can manage a true-up you must size it. A structured inventory examines three things at once: your entitlement position (what you own and the rights included), your consumption reality (what users and devices actually use, from the Microsoft 365 admin centre, Entra ID and SAM data), and the price differential (what a gap costs at your negotiated rate plus any mid-term uplift). Older EAs often price newly added products well above market.
| Licence category | Typical true-up risk | Mitigation window |
|---|---|---|
| Microsoft 365 E3/E5 users | High — headcount-driven | 90 days pre-anniversary |
| Azure Hybrid Benefit | Medium — tracking gaps | Continuous monitoring |
| Teams Rooms devices | Medium — often uncounted | 60 days pre-anniversary |
| Windows Server (CALs) | Low — well understood | 30 days pre-anniversary |
| SQL Server | High — virtualisation rules | 90 days pre-anniversary |
| Power Platform | Growing — rapid adoption | 60 days pre-anniversary |
Count your unused rights first. Many Microsoft 365 E3 customers pay true-up on features they already own but never activated — Intune, Entra ID P1. Reconciling entitlements against consumption converts apparent gaps into free capacity, and every inactive seat you deprovision before the count saves money at full per-seat rate.
05 Pre-true-up checklist
Four actions, run in the 90 days before the anniversary date, do most of the work.
Run a self-assessment
Count current headcount and devices against purchased quantities 90–120 days out — early enough to remediate rather than simply pay Microsoft's tally.
Reconcile entitlement vs usage
Cross-reference Microsoft 365 admin-centre usage reports against your licence roster to surface both gaps and unactivated rights you already own.
Deprovision inactive seats
Remove licences on departed employees, dormant accounts and decommissioned devices. A systematic cleanup typically cuts the count by 3–8%.
Verify Hybrid Benefit
Confirm on-premises versus in-Azure licence allocation is tracked accurately so mobility rules do not manufacture a phantom compliance gap.
06 Reduce your liability
The highest-leverage moves happen before the anniversary date — and, for pricing, before signature.
Write in provisions that cap true-up pricing at your EA discount, add mid-term products at negotiated rather than list rates, and fix a step-up price from E3 to E5. These cannot be negotiated retroactively.
Execute the full position assessment, deprovision inactive seats, and reallocate unused entitlements. For fluctuating headcounts, negotiate a licence-pool provision so reserve seats can be assigned and returned without triggering liability.
Microsoft's team treats the true-up as an expansion conversation. Framing genuine gaps as an early renewal discussion routinely yields 15–30% discounts on additions — a lock-in is preferable to a one-off bill.
07 Pre-true-up timeline
The single highest-value process choice is when you start. The final-year true-up sets the baseline for your renewal — over-true-up and you inflate the next three-year commitment.
Proactive Recommended
90 days out: self-count, reconcile entitlements, deprovision, verify Hybrid Benefit. 60 days out: resolve Teams Rooms and Power Platform gaps. At the count: negotiate additions as an early renewal. Liability lands 25–45% lower.
Reactive Weaker
Wait for Microsoft's count. A year of unlicensed growth is billed retroactively at list, shelfware is paid for, and the inflated figure becomes the renewal baseline — with no remediation window left.
Plan your true-up before Microsoft counts
Our licensing advisory practice runs the 90-day protocol, sizes exposure, and negotiates true-up caps and additions on your behalf.
The Licensing Edge
Weekly Microsoft and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.