What the True-Up Actually Is — and Why It Feels Like a Trap
The Microsoft Enterprise Agreement True-Up is an annual reconciliation event built into every EA. Once per year — typically between 30 and 60 days before your enrollment anniversary date — your organisation is required to review all product deployments and report any additions above your original baseline. Microsoft then invoices the difference for the remainder of the term, usually on a pro-rated basis.
On paper, this sounds fair. In practice, it consistently generates unbudgeted invoices of six figures or more, for three structural reasons that Microsoft has never fixed because they work in its favour.
First, the True-Up is upward-only by design. You must report every addition — new users, new workloads, new server licences added at any point during the year. You cannot reduce. If your headcount grew by 200 people and then fell back to baseline, you still owe Microsoft for those 200 seat-months. There is no mechanism in a standard EA to reflect genuine reductions mid-term for on-premises products. For cloud subscriptions under M365, even the limited "True-Down" that exists is restricted, conditional, and frequently unavailable at the time of year when it would matter most.
Second, costs are cumulative and invisible until they arrive. A deployment of 50 additional M365 E3 seats in March, 30 more in July, and a new Azure SQL workload in October generates a True-Up order that combines all three additions in a single invoice. Each addition looks trivial at deployment time. The combined bill at reconciliation can reach seven figures across a 10,000-seat estate, and it arrives on a fixed calendar that waits for no budget cycle.
Third, Microsoft's field team is incentivised to sell into the gap. Your account team knows your deployment data from telemetry and the Microsoft 365 admin portal. They can see exactly where you are over-deployed before you can. The True-Up window — 30 to 60 days before anniversary — is precisely when Microsoft sales representatives begin conversations about upgrading your baseline to E5 or, increasingly in 2025 and 2026, to the new E7 tier. What looks like a helpful "we can tidy this up at renewal" conversation is in fact a structured upsell motion anchored in your compliance exposure.
How the True-Up Mechanics Work in Detail
Understanding the mechanics precisely is the first step to avoiding the trap. An EA True-Up order covers all qualified users, qualified devices, and processor or core units added above the baseline quantities stated in your original Enrollment or Product Selection Form. The order must be submitted between 60 and 30 days prior to each annual anniversary date — with the Year 3 order due within 30 days before expiry, after which no additions will be accepted for that term.
For on-premises products such as Windows Server, SQL Server, and Office on-premises, True-Up pricing is set in the Customer Price Sheet at signing and covers the remaining years of the term. Adding 100 SQL Server Standard licences in Year 2 means you pay for those licences for Years 2 and 3 in a single order — two years' payment in one invoice. Adding in Year 3 means one year's payment only, which creates a perverse incentive to delay reporting, but doing so puts you in audit-risk territory.
For Microsoft 365 cloud subscriptions — M365 E3, E5, E7, Teams, Copilot add-ons — the True-Up mechanism is slightly different. Additions reported at True-Up are often billed pro-rated for the months remaining in the subscription year, not the full agreement term. This means the pro-rata calculation can dampen the cost of additions reported close to the anniversary date, but it also means additions made early in the year carry nearly a full year's cost at True-Up.
Microsoft 365 Copilot at $30 per user per month is now one of the largest surprise line items on True-Up invoices. Pilot deployments that were never formally decommissioned, or test tenants where Copilot was enabled broadly without proper licence controls, routinely appear in True-Up submissions with six-figure bills attached. For organisations evaluating E7 — which bundles Copilot, Agent 365, and Work IQ into a single per-user price — the True-Up for unreported E7 licences will be even more acute.
Need to prepare your True-Up submission — or challenge a bill that arrived?
Our Microsoft EA negotiation specialists →The Five Biggest True-Up Traps
After reviewing hundreds of EA True-Up submissions across EMEA and North America, the same five failure patterns repeat. Each one is avoidable with the right governance — but each one is also exploited by Microsoft's field team if you let it materialise.
The most expensive mistake is the most common: delegating the True-Up to procurement or finance, running a single data pull 45 days before the anniversary, and treating the result as the definitive number. By that point, the deployments are done and the cost is locked. There is no room to optimise, reclaim unused licences, or rebalance SKUs. The only options are pay the invoice, dispute the data, or use the bill as a lever — but without independent data, you have no credible lever.
The fix is continuous tracking. Quarterly internal reconciliations, ideally using your own SAM tooling against Microsoft's admin portal data, give you three or four opportunities per year to identify over-deployment and take corrective action before it compounds.
Industry data consistently shows that 15 to 30 percent of Microsoft licences in large enterprises are assigned to users who no longer actively use them — former employees, contractors, project staff, or users who were upgraded and then moved to a lower-tier role. These accounts inflate the True-Up baseline and accumulate cost silently.
A 12,000-seat estate where 15 percent of accounts are inactive represents roughly 1,800 redundant licences. At E3 pricing of approximately $36 per user per month, that is over $775,000 per year in wasted spend that compounds at each True-Up. Reclaiming those licences before the anniversary date reduces your True-Up obligation directly and creates a licence pool for new hires, eliminating future True-Up additions for up to a year or more.
The action is to build licence reclamation into your IT offboarding process: when an employee departs, their licence returns to a reallocation pool within 30 days. Automate this through Microsoft Entra lifecycle workflows or your ITSM platform. This single process change saves most enterprises more than the cost of implementing it within the first quarter.
Microsoft 365 administrators have broad ability to assign licences from the admin portal, and in most enterprises, this power is distributed across multiple IT teams, regional administrators, and project managers. Without centralised licence governance, individual admins routinely assign E5 or Copilot licences to users who request additional features, without reference to the EA baseline or the True-Up implications.
The problem accelerates when Microsoft pushes capability rollouts. When Microsoft Copilot was enabled across tenants as a trial feature during 2024 and 2025, many organisations saw their Copilot seat counts jump without a formal procurement decision. At True-Up time, those "trial" seats appeared as payable additions — at full $30 per user per month. The fix is licence assignment governance: all licence assignments above baseline require an approval workflow that includes a cost acknowledgement based on True-Up impact. This does not require complex tooling — a Power Automate flow that emails the IT manager and finance for any licence assignment above a defined baseline threshold is sufficient.
Many procurement managers believe that deploying additional licences just before the True-Up date is a cost-saving tactic — since the pro-rata bill for a deployment made one month before anniversary is only one month's cost, versus a full year for a deployment made at the start. This logic is correct but creates a dangerous incentive.
Organisations that intentionally delay reporting additions to reduce their True-Up bill are taking a compliance risk. Under the EA terms, you are required to report all additions at the annual True-Up. Deliberate under-reporting is non-compliance, and Microsoft's audit programme — which is active and increasing — looks specifically for patterns where deployment telemetry exceeds reported True-Up quantities. The back-charge and penalty exposure from an audit finding is typically three to five times the original True-Up cost, and it removes your negotiating leverage completely.
The correct tactic is not to delay reporting, but to delay deployment. If a new workload can wait two months, deploy it after the anniversary date and it falls into the next True-Up cycle. This is legitimate planning, not evasion, and it is the kind of timing management that experienced Microsoft licensing advisors build into deployment calendars.
Perhaps the most sophisticated trap is the assumption that there is nothing to negotiate once the True-Up order is submitted. This is false. The True-Up is one of the highest-leverage moments in your Microsoft relationship — if you arrive with independent data, a clear position on future consumption, and knowledge of Microsoft's own fiscal calendar.
Microsoft's fiscal year ends on 30 June. The Q4 pressure window from April through June is when Microsoft account teams have maximum incentive to close volume. If your True-Up date falls in this window, or if your renewal follows the True-Up by less than six months, you have genuine leverage. Microsoft field reps are measured on new E5-to-E7 transitions, Azure committed spend, and Copilot seat expansion. Offering to formalise growth — locking in E7 or Copilot deployment commitments for Year 2 and Year 3 — in exchange for a discount on the True-Up order or a cap on future True-Up pricing is a commercially rational conversation that Microsoft will engage with far more readily than most customers expect.
The True-Down Myth: Why You Cannot Simply Reduce
No discussion of the True-Up trap is complete without addressing the True-Down — and specifically, why it almost never works the way organisations hope. The True-Down is the theoretical ability to reduce licence quantities at True-Up time. In practice, it is severely constrained by the EA terms, and most organisations discover this only when they need it.
For on-premises products enrolled as Enterprise-wide purchases — including on-prem Office, Windows Client, and Client Access Licences — there is no True-Down right under a standard EA. The licence count cannot be reduced below the original baseline for the term. Period. If your organisation contracted for 10,000 Windows licences and then reduced headcount to 8,000, you continue paying for 10,000 until the agreement expires.
For M365 cloud subscriptions, a limited True-Down is technically possible, but the conditions are restrictive. The quantity after reduction must still meet or exceed the number of Qualified Users shown on the Product Selection Form. Step-up licences and add-on subscription licences do not count toward this threshold. In practical terms, for an organisation with an Enterprise-wide commitment across all users, the True-Down right often yields zero reduction because the committed quantity is the user count itself.
The structural asymmetry — True-Up is mandatory and unlimited upward; True-Down is optional, conditional, and frequently unavailable — is not an oversight. It is the architecture of Microsoft's enterprise licensing model, designed to ensure that any deployment decision results in a permanent revenue floor. Understanding this before you negotiate your next EA is essential: the ability to reduce is a contractual right that must be explicitly negotiated at signing, not assumed from the product documentation.
The SKU Dimension: E7 and the New True-Up Maths
Microsoft's introduction of M365 E7 as the new top SKU — above E5 — changes the True-Up calculus for 2025 and 2026. E7 at approximately $99 per user per month bundles Copilot, Agent 365, advanced security previously sold as E5 add-ons, and Work IQ analytics into a single per-user price.
For organisations currently on E3 or E5 with separate Copilot add-ons, the True-Up exposure is compound: you must report base SKU additions, Copilot seat additions, and any security add-ons separately. Microsoft's field team is acutely aware that this complexity makes the True-Up painful for E3 and E5 customers — and they will use that pain as a reason to recommend upgrading to E7, where all those add-ons are consolidated and the True-Up is a single line item.
This is not inherently a bad outcome. If your organisation genuinely uses Copilot broadly and needs the E5 security features, E7 can represent a lower total cost of ownership than the sum of E5 plus add-ons — particularly if Microsoft offers a transition discount during the Q4 window. But it is only a good deal if you negotiate the price of E7 against independent benchmarks, not against Microsoft's list price.
Our EA benchmarking data shows that standard EA discounts in 2025 and 2026 are running at 10 to 20 percent off list price — down from the historical 15 to 25 percent that organisations achieved three to five years ago. The reduction in discount range reflects Microsoft's tighter control of the MCA channel, where buyer leverage is structurally lower than under a traditional EA. If your account team recommends moving to E7 via an MCA rather than a new EA, you are likely leaving money on the table.
What Best-in-Class True-Up Management Looks Like
The organisations that consistently navigate True-Ups without surprise bills share four structural practices that are independent of tooling sophistication. They do not require a SAM platform or a dedicated licensing team — though both help. They require governance.
Quarterly internal reconciliations. At the end of each fiscal quarter, IT runs a licence assignment report against the EA baseline and identifies any additions. The report goes to the procurement or vendor management team, who categorise each addition as planned, unplanned, or recyclable. Unplanned additions trigger a budget check. Recyclable licences — from departures or role changes — are reclaimed immediately. This single practice eliminates most True-Up surprises.
Deployment calendars aligned to the EA anniversary. Any new workload with a planned deployment date within 90 days of the anniversary is evaluated for timing. If the deployment can be deferred by 30 to 60 days, it falls into the next True-Up cycle, reducing the current year's bill. This is not evasion — it is deployment planning. The deployment still happens; it just happens at the optimal point in the licensing calendar.
Independent data before the True-Up submission. Microsoft's admin portal data and your own IT asset records will not always agree. Before submitting your True-Up order, run your own count from your directory, your SCCM or Intune data, and your HR system for headcount. Discrepancies — which are common — almost always resolve in your favour when you have independent evidence. Submitting Microsoft's number without cross-checking it first is unnecessarily risky.
Negotiating True-Up pricing at EA signing, not at True-Up time. The most powerful lever is the one that no longer exists once the True-Up arrives: the pricing terms for additions. At EA signing, you can negotiate a "future pricing" annex that fixes the per-unit cost for any True-Up additions across all three years of the term. Without this, Microsoft can apply list price or eroded discount rates to additions. With it, you lock in the same commercial terms for growth as for the baseline. This is standard practice for sophisticated buyers and is consistently achievable during Q4 negotiations.
Working through a True-Up submission or negotiating EA renewal terms?
Redress Compliance provides independent Microsoft licensing advisory — buyer-side only, 500+ engagements, Gartner recognised.The Q4 Window: When Leverage Is Highest
Microsoft's fiscal year ends on 30 June. The 13 weeks from 1 April to 30 June represent the highest-leverage period for buyers — both for True-Up negotiations and for EA renewals. Microsoft account teams face maximum quota pressure in this window, and the combination of end-of-quarter incentives and end-of-year recognition drives deal velocity that works in the buyer's favour.
If your True-Up date falls between April and June, do not treat it as an administrative event. Treat it as a negotiation. Come prepared with your own licence count data, a view on three-year growth projections, and a proposal that packages the True-Up order with a forward commitment — whether that is a move to E7, an Azure Reserved Instance block, or a Copilot expansion commitment. Microsoft's field team will have deal approval authority in Q4 that simply does not exist in Q1 or Q2. The discount that is "not possible" in October is frequently available in May.
Organisations that engage a specialist Microsoft EA negotiation specialist for their True-Up submission consistently achieve better outcomes than those that handle the process internally — not because the internal team lacks skill, but because the information asymmetry between Microsoft's account team and an internal buyer is substantial. An external adviser who works on Microsoft negotiations exclusively brings benchmark data, a knowledge of what other organisations at similar scale have achieved, and an understanding of the deal structures that Microsoft's approval systems can accommodate.
Key Takeaways
The True-Up trap is not an accident of design. It is a structural feature of the EA that compounds cost through information asymmetry, upward-only reconciliation mechanics, and a deployment-time decision culture that is disconnected from licensing governance. The organisations that avoid the trap share one characteristic: they treat licence management as a continuous operational discipline rather than a once-a-year compliance event.
Before your next True-Up submission, confirm the following. Do you have an independent licence count from your own systems that you can cross-check against Microsoft's admin portal data? Have you reclaimed all licences from departed employees and inactive accounts? Have you identified any deployments that could be deferred past the anniversary date without operational impact? And critically — did you negotiate future pricing terms at EA signing that fix the per-unit cost of True-Up additions for the entire term?
If the answer to any of those questions is no, the True-Up trap is still open. The right time to close it is now — before the invoice arrives.