The annual true up reconciles every license you added above your baseline. It only moves up, it rewards buyers who tracked additions, and it is where an unscrubbed directory quietly costs you.
The Microsoft EA true up is the annual moment your bill can quietly grow. It reconciles every license you added above your baseline, it only moves up, and it rewards buyers who tracked additions all year. This guide explains the mechanics, the overcharge traps, and how to prepare.
The true up is not a penalty. It is how the Enterprise Agreement is designed to work. You set a baseline at signing, you add licenses as you grow, and once a year you settle the additions.
The problem is direction. The EA only counts up. There is no mid term credit for seats you stopped using, so an inflated count becomes a cost you carry to renewal.
A true up is the annual reconciliation of license additions above your baseline. It happens once each agreement year, ahead of the anniversary, with a final settlement at the three year renewal.
Your baseline is the quantity you committed at signing. It is the floor for the whole term. The Enterprise Agreement structure means everything you add sits on top of that floor.
Each year you submit a true up order for net new additions. You do not submit reductions. There is no line item for seats you released, which is the asymmetry that costs buyers the most.
Microsoft counts the qualified users or devices added above your baseline during the agreement year. For online services it is usually a seat count. For on premises products it follows the rules in the Microsoft Product Terms.
Most M365 and Dynamics additions are counted per user. The count is the number provisioned, not the number actively used, which is why deprovisioning leavers before the count is real money.
Servers and on premises products carry their own metrics, including core based and CAL based rules. Microsoft publishes the volume licensing references and product terms through its licensing resources, and those rules govern the count.
How true up timing changes the cost of 1,000 added seats
| When seats are added | Months billed in year one | Relative first year cost | Buyer side move |
|---|---|---|---|
| Just after anniversary | Up to 12 | Highest | Defer where the business allows |
| Mid agreement year | About 6 | Moderate | Bundle with reclaim |
| Just before true up date | 1 to 2 | Lowest in year, then full | Confirm genuine need |
| Held to renewal | 0 | Deferred | Use CSP for short bursts |
Most overcharges are not Microsoft errors. They are counts nobody scrubbed. The reseller reports what the directory shows, and the directory is full of leavers, duplicates, and seats no one reclaimed.
Accounts for departed staff keep their licenses until someone removes them. At true up, those seats are counted and billed. A clean deprovisioning pass before the count is the single highest return action.
Software Assurance rides every seat in the baseline and every addition. If you have stopped using the benefits it funds, you are paying for an asset you do not draw on, year after year.
The standard reseller line is that the true up is routine, so you should just submit the count the tool produces and move on. We disagree. In roughly seven out of ten true up reviews we ran, the tool generated count included leavers, duplicates, and stacked entitlements that inflated the number by a double digit percentage.
The buyer side move is to treat the true up as a negotiation and an audit, not a formality. Reconcile actual deployment against entitlement first, and reclaim everything unused before you submit a single line. Routine is what it costs you when you let someone else hold the calculator.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The true up is not where the money is lost. The baseline is. By the time the count arrives, the only question left is how much of it you can prove you do not owe.
Preparation beats negotiation here. The count is a fact about your estate, so the work is making the estate true before the count is taken.
Pull the active user list, match it to provisioned licenses, and flag every seat with no recent activity. This is the baseline for every later decision.
Where the business can wait, align large seat blocks to the anniversary rather than the deadline. For short bursts of demand, buy on CSP instead of adding to the EA baseline you cannot reduce.
A true up is the annual reconciliation where you report and pay for licenses added above your Enterprise Agreement baseline during the year. It is a feature of the EA, not a penalty, but the timing and the count are where buyers overpay if they have not tracked additions.
The true up is due once each agreement year, ahead of the anniversary date, with the final reconciliation at the three year renewal. You submit a true up order for net new additions, and there is no credit for reductions inside the term.
No. The EA only trues up. You can reduce quantities at the three year renewal, but not mid term. That asymmetry is the core reason a baseline set too high stays expensive for the full term, so the baseline matters more than the true up itself.
Microsoft counts the peak number of qualified users or devices added above your baseline during the agreement year. For most online services it is a user or seat count, and for on premises products it follows the product specific rules in the Microsoft Product Terms.
Under reporting is a compliance exposure that surfaces at renewal or in a review, and it can convert a routine reconciliation into a back bill plus pressure. Report accurately, but report only what the agreement actually obligates, which is where most disputes live.
Generally yes for the agreement year of the addition, which is why timing matters. Provisioning a large block of seats just before the true up date can cost nearly a full year of fees, so additions should be timed against the anniversary where the business allows.
Yes. Software Assurance rides on the licenses in your baseline and on true up additions, so it scales the cost of every seat you add. Reviewing whether Software Assurance still earns its keep is part of a disciplined true up preparation.
Start 90 to 120 days before the true up date. That window lets you reconcile actual deployment against entitlement, reclaim unused seats, and time additions, rather than accepting the vendor or reseller count on the deadline.
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.
