An annual reconciliation that overcharges when the count is stale and the price is list. Here is how to get both right.
The Microsoft EA true up is an annual reconciliation, and the cost lives in how you count users and whether you let Microsoft apply the increase at full list.
The true up is the annual reconciliation in an Enterprise Agreement. It captures the users, devices, and subscriptions you added during the year and bills them in arrears.
The mechanics sit in your enrollment terms and the Microsoft Product Terms. Microsoft describes the EA structure on its Enterprise Agreement page.
You cannot true down mid term. Reductions wait for renewal, which is exactly why an accurate count and a renewal plan matter.
Count from a clean source of truth, not the raw directory. Disabled, duplicate, and service accounts should never reach the true up line. Reconcile against your identity platform, which Microsoft documents on Microsoft Learn.
True up count, common error versus correct method
| Item | Common error | Correct method | Typical impact |
|---|---|---|---|
| Disabled users | Counted | Excluded | 5 to 12 percent |
| Duplicate accounts | Counted twice | Deduplicated | 3 to 8 percent |
| Service accounts | Counted as users | Excluded | 2 to 6 percent |
| Baseline | Peak headcount | Average added | Varies |
True ups cost too much for two reasons. The count is inflated by stale data, and the price is quoted at list rather than your enrolled discount.
Microsoft Customer Agreement and EA enrollments both carry negotiated discounts that should flow to true up quantities. Confirm the route on the Microsoft licensing documents library.
If the true up arrives at list, push back. Added quantities belong at the same level you negotiated for the base.
The retroactive uplift happens when a mid year price change is applied to your whole added quantity. You avoid it by locking pricing terms and timing additions deliberately.
The order you add products can trip a step price or a tier change. Model the sequence before you deploy at scale.
True up quantities should carry the same discount as your base enrollment. The starting point is your price level, which depends on enrollment size and tier.
The standard advice is to minimize the true up by deploying as little as possible during the year. We disagree. Across the true ups we reviewed, the buyers who throttled deployment to shrink the count often paid more at renewal, because they entered the renewal with a small, weak baseline and no leverage. The buyer side move is to count honestly, claim the discount on every added line, and use a healthy true up as evidence of committed spend when you negotiate the renewal. A clean, larger true up at your enrolled discount beats a suppressed one that hands Microsoft the renewal narrative. Manage the price, not the deployment.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A true up is a count and a price. Get the count clean and the discount applied, and the surprise disappears.
A Microsoft EA true up is the annual reconciliation in an Enterprise Agreement that captures users, devices, and subscriptions added during the year and bills them in arrears. It runs once per enrollment year at the anniversary.
No, you cannot reduce quantities mid term. Reductions wait until renewal, which is why an accurate count and a renewal plan matter so much.
Count from a clean source of truth reconciled against HR active records, excluding disabled, duplicate, and service accounts. Raw directory counts typically overstate the obligation by 8 to 18 percent.
No, true up quantities should carry the same discount as your base enrollment. A true up quoted at list price is a 15 to 30 percent overcharge that you should push back on.
The retroactive uplift is when a mid year price change is applied to your whole added quantity. You avoid it by locking price protection for additions in the enrollment terms.
Yes, the sequence of additions can trip a step price or tier change. Model the order before deploying at scale so you do not cross a threshold unintentionally.
Yes, a clean and healthy true up is evidence of committed spend that strengthens your renewal position. Suppressing deployment to shrink the count often weakens your baseline and your leverage.
The true up is due once per year at your enrollment anniversary, reconciling everything added since the last reconciliation. Prepare the clean count in the weeks before that date.
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.
A true up is a count and a price. Get the count clean and the discount applied, and the surprise disappears.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side brief a week on Microsoft pricing, audit posture, and the levers that hold a discount. No vendor spin.