How the EA True-Up Works
The Microsoft Enterprise Agreement true-up is an annual reconciliation mechanism built into every EA enrolment. It operates on a straightforward principle: when you enrol in an EA, you commit to a baseline quantity of licences. If your actual deployments exceed that baseline at any point during the following 12 months, you owe Microsoft for the overage — billed at your contracted EA rates for the full annual period.
The true-up occurs at each EA anniversary date (the 12-month mark from the original enrolment date, and each subsequent 12-month interval). Microsoft requires the enterprise to submit a True-Up Order — a formal statement of deployed licence quantities — within 30 days of the anniversary date. The True-Up Order is then compared to the enrolled baseline, and any increase triggers an order for the difference, billed for the remaining EA period.
A critical point that many enterprises misunderstand: the true-up captures the maximum quantity deployed at any point during the 12-month period — not the quantity at the anniversary date. If your M365 user count peaked at 5,200 during a brief project expansion and returned to 4,800 before the anniversary, you still owe for 200 additional licences for the full year based on that peak. This "peak-count" mechanism is the most common source of true-up surprises in our client engagements.
In our Microsoft EA review engagements, we find that 60% of enterprises have no systematic process for tracking licence peak counts during the EA year. They discover their true-up liability only at the anniversary date — often weeks after the maximum count was reached and the window to manage it had passed.
What Triggers a True-Up Charge
Understanding the specific events that increase your qualifying user or device count is the foundation of true-up management. Microsoft's true-up scope is broader than most enterprise buyers initially assume.
New User Onboarding
Every new employee or contractor assigned a Microsoft 365 licence, a Windows device, or access to server products covered by the EA increases the qualifying count. The relevant date is the licence assignment date — not the hire date, and not the date the user first logs in. Licence provisioning processes that assign licences to users days or weeks before onboarding systematically inflate peak counts. A discipline of same-day or just-in-time licence assignment is the first element of true-up management.
M&A and Organisational Change
Acquisitions, mergers, and business combinations that bring new employees within the enterprise perimeter trigger true-up obligations for any Microsoft products they are assigned. Outsourcing arrangements that move employees to a third-party provider but retain Microsoft licence responsibility within the EA are a particularly common source of true-up disputes — the obligation does not automatically transfer with the headcount. Any M&A activity should trigger an immediate true-up impact assessment before licence assignment decisions are made.
Product Deployments and Upgrades
Deploying new Microsoft products covered by the EA — server products, additional M365 features, Dynamics 365 applications — increases the qualifying count for those products. Upgrading users from E3 to E5, or from basic to premium licensing tiers, changes the product-specific count even if total user numbers are unchanged. Each EA-covered product is tracked separately; a true-up that looks modest in total user count may still trigger material charges if product-mix changes have occurred.
Cloud Service Consumption
For Azure and other consumption-based Microsoft services covered by the EA (rather than by MACC), consumption above the enrolled baseline may trigger true-up charges. This is separate from the MACC mechanism and applies to specific EA-covered cloud services where the enterprise enrolled a baseline commitment at the start of the term.
| True-Up Trigger | Typical Financial Impact | Management Control |
|---|---|---|
| Net new user hires | Per-licence annual cost × overage | JIT licence provisioning process |
| Contractor licence assignment | Per-licence annual cost × overage | Contractor licence policy; BYOD where permitted |
| M&A - acquired entity | Per-licence cost × acquired headcount | Pre-acquisition true-up impact analysis |
| E3-to-E5 upgrade | E5 premium × upgraded seat count | Targeted E5 deployment (see E3/E5 guide) |
| New EA-covered product deployment | New product annual cost × deployment | Product deployment review against EA baseline |
| Temporary project peak | Per-licence cost × peak overage | Temporary licence management; NCE flexibility |
Understanding "Qualifying Users" — Microsoft's Definition
Microsoft's definition of "qualifying users" for EA true-up purposes is broader than most enterprise procurement teams assume — and Microsoft's interpretation of this definition has been a consistent source of dispute in our client engagements.
For M365 purposes, a qualifying user is any individual who accesses Microsoft 365 services covered by the EA — including employees, contractors, temporary staff, and in some configurations, external partners granted guest access with specific capabilities. The EA policy language typically defines this as "any person who accesses or uses the Products or Qualified Devices," which Microsoft interprets broadly.
Common qualifying-user disputes arise from: contractors on client premises using client Microsoft infrastructure; guest users in Microsoft Teams with elevated permissions; shared device users where individual identification is not maintained; and service accounts assigned individual licences rather than device licences. Each of these scenarios has a defensible licensing interpretation — but the defence requires documentation and a clear organisational policy established before Microsoft raises the issue, not in response to a true-up challenge.
Proactive True-Up Management: The Quarterly Review
The most effective true-up management approach is a structured quarterly licence review — tracking current licence assignments, peak counts since the last review, and projected changes in the next quarter against the EA baseline. This review should be owned by a named individual in IT operations with input from HR (headcount changes), legal/procurement (M&A and contractor agreements), and IT project managers (planned product deployments).
The Quarterly Review Template
For each EA-covered product, the quarterly review should capture: the enrolled baseline quantity; the current assigned quantity; the peak assigned quantity since the previous quarterly review; the projected quantity in the next 90 days based on known changes; and the true-up exposure (maximum of peak and projected, minus baseline). Products where peak or projected quantity exceeds the baseline by more than 5% should trigger immediate review — can any of the overage be addressed through licence reclamation (removing assignments from inactive users), before the peak count is crystallised?
Licence Reclamation Programme
A standing licence reclamation programme — systematically identifying and removing licence assignments from users who have left the organisation, been inactive for 90+ days, or no longer need specific product access — is the most direct mechanism for managing true-up exposure. In most enterprises without a formal reclamation programme, 10–20% of assigned licences at any given time are recoverable — users who have departed, contractors who have finished engagements, or project licences that were never removed at project completion. A monthly reclamation review, combined with automated de-provisioning integrated with HR systems, typically maintains a baseline 10–15% below what an unmanaged deployment would show at the anniversary date.
Disputing an Inflated True-Up Claim
Microsoft's true-up process is not purely mechanical — it involves Microsoft's licensing team reviewing your True-Up Order submission and potentially raising additional questions or claims. In some cases, Microsoft may assert that the enterprise's submitted count understates actual deployments, or that certain users or deployments were not included in the True-Up Order as submitted.
If Microsoft raises a dispute about your True-Up Order, the resolution process depends on the quality of your internal documentation. The starting position should always be your own deployment data — produced from your licence management systems, not from Microsoft's reporting. Microsoft's deployment reports (available through the Microsoft 365 Admin Center and Entra ID) are useful references but should not be treated as authoritative — they can include stale data, miscategorised accounts, and users who have already been de-provisioned.
Effective dispute management requires: a clear policy document defining how qualifying users are defined in your organisation; a documented methodology for counting deployments; evidence from your Active Directory or Entra ID showing actual user counts at the relevant dates; and a written response to Microsoft's challenge that presents your position with supporting data. Disputes resolved with strong documentation consistently achieve materially better outcomes than those resolved through unstructured account team discussions.
For broader guidance on Microsoft EA negotiation context: Microsoft EA Negotiation: The Complete Guide for 2026. For information on potential Microsoft audit processes: Vendor Audit Defence Handbook.
M&A Activity and True-Up Implications
Mergers, acquisitions, and divestitures are among the most complex scenarios in Microsoft EA true-up management. Each scenario has different implications that must be assessed before any licence assignment decisions are made.
Acquisitions: New Entity Joins EA
When an enterprise acquires a new business entity and brings its employees within the EA, the acquired employees become qualifying users for all EA-covered products they are assigned. This can trigger a material true-up depending on the timing relative to the anniversary date. Best practice: negotiate a written "acquisition addendum" with Microsoft before licence assignments are made to the acquired population, establishing the terms on which the new entity will be incorporated into the EA — including any step-up period before true-up obligations begin.
Divestitures: Entity Leaves EA
When an enterprise divests a business unit and the employees transfer to the acquirer, the divested employees should be removed from the EA qualifying user count. This requires a documented transition plan — including an agreed date on which the divested entity's users are removed from the EA baseline — and a formal notification to Microsoft's licensing team. Without documented process, divested employees may remain in Microsoft's systems as EA users, generating ongoing true-up obligations for the divesting enterprise.
The 90-Day Pre-Anniversary Self-Assessment
Ninety days before each EA anniversary date, the enterprise should conduct a comprehensive self-assessment covering: the current licence count versus enrolled baseline for every EA-covered product; the peak count since the previous anniversary for each product; the expected count at the anniversary date based on known changes in the next 90 days; and the resulting true-up financial exposure at contracted EA rates. This self-assessment serves two purposes: it prepares an accurate True-Up Order submission, and it identifies any remaining opportunities to reduce peak exposure before the anniversary window closes.
Specifically: in the 90-day window before anniversary, any licence reclamation that reduces the current count will not change the historical peak — but will reduce the going-forward baseline and may influence how Microsoft interprets the overall compliance picture. Licence reclamation conducted in the 90-day pre-anniversary window is also the appropriate time to right-size product assignments — removing E5 licences from users who should be on E3, removing premium product access from users who have moved roles, and cleaning up ghost accounts from departed employees or contractors.
For the full Microsoft licensing framework: The Complete Guide to Microsoft Enterprise Agreement Negotiation. For M365 licence right-sizing: Microsoft 365 E5 vs E3: Cost Optimization Guide. For a comprehensive audit checklist: Microsoft 365 License Audit: Self-Assessment Checklist.