A buyer side guide to the Microsoft EA true up in 2026. How the annual count works, why it only adds licenses, and how to control the bill before the order.
A Microsoft EA true up is the annual count where you report and pay for licenses added above your baseline, and because the standard process only adds and never removes, the real control sits in the year before the count, not on the day you submit the order.
This guide is for IT and procurement leaders running an EA true up in 2026. Read it with the Enterprise Agreement guide and the EA renewal playbook so the annual count and the renewal stay aligned.
An Enterprise Agreement lets you deploy now and reconcile later. The true up is that reconciliation, run once a year so Microsoft captures the growth in your estate above the agreed baseline.
The mechanics sit in the agreement itself. Microsoft documents the Enterprise Agreement program and its annual order requirement, which is what the true up satisfies.
Your EA sets a baseline count at signing. Through the year you add users, devices, and products, and the true up reports the increase above that baseline at your agreed price level.
The true up falls on the EA anniversary, with the order usually submitted shortly before. The final year true up also closes out the full term before renewal.
You count the net increase in licensed quantities and any new products, then order the difference at your agreed price level for the remaining term. The Microsoft Product Terms define how each product is counted.
EA true up versus renewal at a glance
| Action | At true up | At renewal |
|---|---|---|
| Add licenses | Yes, reported annually | Yes |
| Remove licenses | No, not in standard true up | Yes, reset the baseline |
| Change products | Add new, keep existing | Restructure the whole mix |
The standard true up adds only. You cannot drop licenses you over deployed, which is why uncontrolled growth through the year converts straight into recurring cost.
Use the admin reporting to compare assigned licenses against active users through the year. Microsoft documents how subscriptions and license assignment are managed, which is the data you reconcile against.
Preparation is a year long discipline. The count on anniversary day simply photographs whatever state your estate is in, so the work happens before the shutter.
The common advice is to treat the true up as a routine annual order and simply pay for whatever the tools report. We disagree. In roughly 6 of 10 true ups we reviewed, the reported count included seats from projects that had already closed and users who had already left. The buyer side move is to run a reclaim sweep in the weeks before the count, then reconcile the numbers before the order is placed. The true up should record deliberate growth, not the sprawl the year happened to leave behind.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The true up reflects whatever sprawl the year produced unless someone trims it first. Reclaiming unused seats before the count cuts the addition.
The true up only adds, so reductions wait for renewal. That makes the annual count a planning signal, not just a payment.
Run the count and the renewal as one motion. The numbers you gather at true up are the evidence you carry into the renewal negotiation. Align the timing with the Enterprise Agreement renewal terms.
A Microsoft EA true up is the annual process where you report and pay for licenses added above your baseline during the year. Under an Enterprise Agreement you deploy first and reconcile once a year on the agreement anniversary, ordering the net increase at your agreed price level.
The true up is due each year on the EA anniversary, with the order typically submitted shortly before that date. The final true up of a three year term also reconciles the whole period before the agreement renews.
You count the increase in licensed users or devices and any added products since the last reconciliation, then order the difference at your agreed price level for the remaining term. The Microsoft Product Terms define how each product is counted.
Generally no. The standard EA true up only adds licenses, it does not remove them. Reductions usually wait until renewal, which is why right sizing through the year and before you renew matters more than the annual count itself.
Missing or under reporting a true up is a compliance gap that surfaces in an audit or at renewal. Microsoft can require the back order plus the new additions, so accurate annual reporting protects you from a larger and costlier reconciliation later.
Buyers lower the bill by reclaiming licenses from leavers and dormant accounts before the count and validating that every addition meets a real need. A reclaim sweep in the weeks before the count commonly cuts the reported addition by 8 to 18 percent.
Track deployment against entitlement throughout the year, run a reclaim sweep before the count, and reconcile your numbers before placing the order. The count is a snapshot of your estate, so the preparation that lowers cost happens in the months leading up to it.
The true up only adds licenses, so any reductions wait for renewal. That makes the annual count a planning signal, and the deployment data you gather at true up becomes the evidence you use to reset the baseline at the next renewal.
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.
The true up reflects whatever sprawl the year produced unless someone trims it first. Reclaiming unused seats before the count cuts the addition.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on the Microsoft EA, true up reconciliation, seat optimization, and the buyer side moves we are running in client engagements.