Microsoft / True Up
Microsoft EA True Up. The 2026 complete guide.
The annual true up settles every license you added during the year. Count it late and it overcharges you. Plan it early and it is the cheapest license event you run.
The annual true up settles every license you added during the year. Count it late and it overcharges you. Plan it early and it is the cheapest license event you run.
The Microsoft EA true up is the annual reconciliation that settles what you added during the year. Counted late, it overcharges you. Planned early, it is the cheapest license event you run. This guide covers the counting rules, the timing traps, and the moves that cut the invoice.
A true up is not a tax. It is an annual order. Microsoft lets you grow inside the enrollment and settle the additions once a year instead of at every purchase.
The mechanism is fair. The execution is where money leaks. Most overpayment comes from counting badly, not from the rules themselves.
A true up is the once a year true up order that reconciles licenses added above your baseline. You submit it before your enrollment anniversary, and it covers every net new seat and qualifying addition since the last count.
The Enterprise Agreement is built around this rhythm. You commit to a baseline at signing, deploy freely during the year, then settle the growth annually.
Your true up is due on the enrollment anniversary, not the calendar year end and not Microsoft fiscal year end. Confusing the three is the single most common timing error we see.
You are billed from when the license was first used, not when you place the true up order. Deploying in month two and counting in month eleven still means you owe from month two.
The count is a net additions count. You compare current deployment against your enrollment baseline and pay for the increase. You never get credit for a decrease at this event.
That asymmetry is the heart of the trap. Additions flow up immediately. Reductions only land at renewal, when you reset the baseline.
Step ups are additions too. Moving a seat from E3 to E5 is a priced change, not a free swap, and it lands on the true up.
Pull your own figures from the admin center and your identity provider. Microsoft license terms and product rules live in the Microsoft Product Terms, and you should reconcile against active accounts, not headcount.
The expensive traps are not pricing tricks. They are hygiene failures that turn temporary growth into a permanent baseline you carry for years.
Common true up traps and the buyer side fix
| Trap | What it costs | The fix |
|---|---|---|
| Counting leavers | Paying for inactive accounts | Reconcile to active identities |
| Emergency mid year buys | Permanent shelfware floor | Use CSP for spikes |
| Blind step ups | E5 added without a need | Map features to roles |
| Reseller count accepted | 8 to 18 percent over true | Run your own count first |
Once a seat is trued up, it joins the baseline. You cannot remove it until renewal. A panic purchase in March becomes a fixed cost until the next renewal cycle.
Per user add ons are now the fastest growing true up line. Microsoft 365 Copilot and the unbundled security stack attach quietly, and each one is a recurring per user charge once trued up.
You reduce it by counting early, counting yourself, and removing waste before the count freezes it. The work happens 60 to 90 days before the anniversary, not in the final week.
The standard reseller advice is to accept the prepared true up count and pay it on time to stay compliant. We disagree. In roughly seven out of ten true up reviews we ran, the prepared count was higher than the deployed reality, and the customer paid for inactive accounts and unused step ups. The buyer side move is to run your own reconciliation 90 days early, deactivate leavers, reclaim idle seats, and submit your own defensible count. On time is good. Correct and on time is cheaper.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A true up only adds. It never subtracts. Every seat you fail to clean before the count becomes a cost you carry until the next renewal.
Run short term and seasonal demand through CSP, not the EA. Microsoft documents the buying paths on its how to buy page. Keep the EA baseline for stable demand so spikes never freeze into it.
A true up is the annual order that reconciles licenses added above your enrollment baseline. You submit it before your enrollment anniversary and pay for net new seats and qualifying additions made during the year.
It is due on your enrollment anniversary date, not the calendar year end and not Microsoft fiscal year end. Most timing mistakes come from confusing those three dates, so confirm the anniversary in your enrollment paperwork.
No. A true up only adds licenses above the baseline. Reductions are only possible at renewal, when you reset the baseline. This asymmetry is why seats added in a panic become a fixed cost until renewal.
Microsoft counts net additions against your enrollment baseline, including new seats, step ups such as E3 to E5, and per user add ons. You should reconcile against active identities and sign in data, not raw headcount.
You are billed from when a license was first used, not when you place the true up order. Deploying in month two and counting in month eleven still means you owe from month two of usage.
Prepared counts often include leavers, idle accounts, and unused step ups. In our reviews the prepared count overstated paid additions by 8 to 18 percent, so running your own reconciliation first protects the invoice.
Start 60 to 90 days before the anniversary. That window gives you time to deactivate leavers, reclaim idle seats, right size step ups, and build a defensible count before the deadline freezes the numbers.
Clean reconciliation typically trims the true up invoice by 10 to 25 percent. The savings come from removing inactive accounts, avoiding unneeded step ups, and keeping seasonal spikes off the enrollment baseline.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
