The Definition That Actually Matters
A Microsoft true-up is the annual licence reconciliation process built into every Microsoft Enterprise Agreement. Once per year — on the anniversary date of your EA signing — you are required to compare the number of Microsoft product licences you have deployed across your organisation against the number of licences you committed to at EA signature. If you have deployed more than you committed to, you pay for the difference. If you have deployed less, you continue paying your committed amount.
That is the textbook definition. The definition that actually matters commercially is this: the true-up is a contractually mandated self-reporting exercise that determines your annual incremental Microsoft spend, conducted under counting rules that you probably did not negotiate carefully enough at EA signature.
The gap between the textbook definition and the commercially accurate one is where most enterprise organisations lose money — not because they are unlicensed, but because the mechanism by which licence counts are determined systematically produces higher counts than most buyers expect. Understanding how the true-up actually works — not how it is described in sales materials — is the starting point for managing it effectively.
Based on our advisory work across 500+ engagements since 2016. The surprise is almost always attributable to counting methodology differences, not actual deployment growth the buyer was unaware of.
How the True-Up Process Actually Works
Every EA has an anniversary date — the date one, two, and three years from when your agreement was signed. Microsoft (through your LAR — Licensing Solution Provider) initiates the true-up process approximately 60–90 days before each anniversary. You will typically receive a "true-up order form" listing every product covered under your EA with its committed baseline quantity and a blank field for your reported quantity.
Your IT team fills in the current deployment count for each product. The completed form goes back to your LAR, who processes any additional licence quantities as an order. You pay for the incremental licences at the per-unit pricing locked in your EA, prorated to cover the remaining months of your current EA term from the date of deployment. At your third anniversary, the full-cycle true-up closes out the current EA and your renewal negotiation determines the baseline for the next three years.
What "Deployment" Means — and Why It Matters
The question of what counts as a "deployed" licence is where most true-up disputes and surprises originate. Microsoft's standard EA language defines deployment as a product being "made available to a user or device." In practice, for cloud products like Microsoft 365, this means a licence has been assigned in your tenant — regardless of whether the user has ever authenticated, activated the product, or used it once.
This is the critical distinction: your IT team likely counts active users. Microsoft's system counts assigned licences. In any large organisation, these two numbers diverge — sometimes significantly. The divergence is created by terminated employees whose accounts have not been cleaned from the directory, contractors whose projects ended but whose licences were not reclaimed, and temporary workers whose accounts persist after their assignments conclude.
5,000-User Organisation: What the Numbers Show
IT team count (active users, last 30-day sign-in): 4,847 M365 E3 users
EA baseline commitment: 5,000 M365 E3 users
IT conclusion: Under-deployed, no additional true-up payment due
Microsoft system count (all assigned licences): 5,312 M365 E3 users
True-up calculation: 312 users above baseline × £28.40/user/month × 12 months = £106,281 additional annual cost
The 465-user gap between IT's active user count and Microsoft's assigned licence count represents the accumulated effect of incomplete offboarding, contractor account residue, and temp worker licence retention — all billed at full M365 E3 rates under standard counting methodology.
What Triggers True-Up Charges
True-up charges are triggered any time your reported deployment exceeds your EA baseline. The most common triggers fall into five categories that every enterprise IT and procurement team should monitor continuously, not just at true-up time.
Headcount Growth Above Baseline
The most obvious trigger: your organisation has grown since you set the EA baseline, and new employees have been provisioned with Microsoft licences. This is expected and manageable — the EA's true-up mechanism exists specifically to handle growth. The commercial question is whether the growth rate you projected when setting the baseline was accurate, and whether the products being deployed to new users match the products covered in your EA.
Incomplete Offboarding Processes
The most frequently underestimated trigger. When an employee leaves, their Microsoft account and assigned licences typically remain active until IT processes the offboarding. In large organisations with distributed IT teams, this gap can be days to weeks. At any given moment, a 10,000-person organisation may have 200–400 former employees still holding assigned Microsoft licences — all countable under the standard true-up methodology. Multiply by the per-user annual cost and the exposure accumulates quickly.
Contractor and External User Provisioning
Contractors, consultants, temporary workers, and external collaborators often receive Microsoft licences for project access. Unlike permanent employees, these users are managed outside standard HR offboarding workflows, meaning their licences frequently persist after their engagement ends. This category is particularly problematic for organisations with high contractor utilisation — common in consulting, financial services, and project-based manufacturing environments.
Add-On Product Deployment Without EA Coverage
Microsoft's product catalogue has expanded dramatically with M365 Copilot, Viva suite, Power Platform premium add-ons, Defender components, and Purview capabilities — all separately licensed products that are not automatically included in your EA coverage unless explicitly added. When IT teams enable these products — even informally, for trials or pilots — they create true-up exposure for products outside the EA baseline. The true-up compliance guide covers this add-on exposure category in detail with product-by-product risk ratings.
Acquired Entity Deployment
If your organisation has made acquisitions during the EA term, the acquired entity's Microsoft deployment may not be covered by your existing EA unless the entity has been formally added as an enrolled affiliate. Products deployed in acquired entities outside your EA coverage create true-up exposure — and potentially formal audit liability for the period between acquisition and formal EA enrollment.
What the True-Up Is Not
Three common misconceptions about the true-up create real commercial harm when buyers act on them.
It Is Not an Opportunity to Reduce Your Licence Count
The annual true-up is a one-way ratchet under standard EA terms. You can report higher deployment (and pay more), but you cannot report lower deployment than your EA baseline and pay less. Your EA baseline is a minimum three-year commitment. If your actual deployment falls below that baseline, you continue paying for the committed quantity until renewal. The only opportunity to reduce your baseline is at EA renewal — which is why building a credible usage evidence base in the 12 months before renewal is so important. The guide to reducing EA licence counts covers the preparation methodology and renewal negotiation approach.
It Is Not the Same as a Formal Audit
The true-up is self-reported — you submit the count, Microsoft processes it. A formal Microsoft licence audit is a distinct, more adversarial process in which Microsoft (or a designated third party) has the right to independently verify your deployment. The confusion between these two processes leads some organisations to over-report in true-up submissions out of fear of audit findings. Over-reporting the true-up costs real money for no commercial benefit — Microsoft is not going to reward conservative over-reporting at renewal. For the full treatment of how Microsoft audits work and how they differ from the true-up, see the licence compliance audit guide.
It Is Not a Fixed Administrative Cost
The most expensive misconception: treating the true-up as a predictable, manageable administrative cost rather than an actively managed commercial exposure. Organisations that do not maintain continuous licence governance — monthly hygiene cycles, quarterly reconciliation, pre-true-up sprints — consistently face larger true-up bills than those that do. The true-up is not something that happens to you. It is a commercial outcome you manage or fail to manage.
The most expensive true-up we have seen in our advisory practice was a manufacturing organisation that treated its annual true-up as an administrative exercise for seven consecutive years. By the time they engaged us in advance of their most recent renewal, their deployed-to-baseline ratio across three product lines had drifted so far that their renewal negotiation was conducted under severe Microsoft pressure — Microsoft's leverage came entirely from the buyer's non-existent governance record. Had they maintained quarterly reconciliation, the renewal would have looked very different.
The True-Up as a Commercial Event
The most commercially sophisticated enterprise buyers do not manage the true-up as a compliance obligation. They manage it as an annual data-generation exercise that feeds directly into their EA renewal strategy.
Your three years of true-up submissions are the most credible evidence base you have for renewal baseline negotiations. If your data shows consistent under-deployment across any product line — even if the under-deployment is below your baseline rather than above it — you have documented evidence for a lower renewal commitment. If your data shows consistently high true-up charges driven by specific user populations (contractors, temporary workers, external collaborators), you have the basis for a structured deployment control proposal that reduces future true-up exposure while also reducing your renewal baseline.
Microsoft's renewal teams use your highest true-up deployment count as their baseline anchor. Your job — if you have managed your true-up data actively — is to present a well-evidenced counter-position that reflects your actual forward deployment needs rather than your highest historical peak. The Complete Guide to Microsoft EA Negotiation covers how true-up data integrates with the full renewal preparation framework.
What to Do Before Your Next True-Up
If your next EA anniversary date is within 12 months, there are three immediate actions to take. First, pull a current Entra ID report showing all licensed users and their last authentication date. Identify accounts with no activity in 30+ days. Initiate cleanup of stale accounts — this is your immediate exposure reduction lever. Second, review your EA order history and identify every product covered under your EA. Compare that list against every Microsoft product currently enabled in your tenant. Any products in your tenant but not in your EA coverage need immediate assessment. Third, build a simple 12-month true-up projection based on current headcount growth rates and any planned Microsoft product deployments. The projection does not need to be precise — its purpose is to surface surprises before they become bills.
For the detailed preparation framework including the full 6-week pre-true-up sprint timeline, data gathering methodology, and remediation priorities, the true-up preparation guide for 2026 is the definitive operational resource.