Microsoft EA  |  Annual True Up White Paper

Microsoft EA true up 2026: control the count, hold the floor

The annual order, not the renewal, sets the price floor you carry for the rest of the term. In a representative 10,000 seat estate, reconciling one true up order recovered $453,600, or 42.9 percent, of the proposed bill.

Prepared by Redress Compliance · June 2026 · Representative Microsoft estate scenario (benchmark scenario, not a quote)

Executive summary

A Microsoft EA true up reconciles your enrolled count to your deployed count once a year. You report added users and added products, you pay for the increase, and you get nothing back for reductions until renewal. The count you submit becomes the new floor for every remaining year of the term.

Three things inflate the order above forecast: seats that were assigned but never used, suite step ups billed at the full price of the higher edition instead of the price difference, and retired licenses that are never netted against new demand. In the engagements behind this paper, those three drivers ran 15 to 30 percent above the seats actually in use at submission.

Two contract features cut the cost if you use them. Price protection holds your ordered prices flat for the full term, which matters more than ever with the July 1, 2026 list increases. Edition downgrade and renewal reduction rights let you shed unused capacity, but most customers never exercise them. The buyer side move is to reconcile to active use before you sign the order, and to stage suite step ups for the renewal where you hold the leverage.

$1.06M
Reseller proposed annual true up order, 10,000 seat estate
42.9%
Recoverable from one order through reconciliation
$453.6K
Overcount in a single annual order, locked into the floor
1,050
Defensible new seats versus 1,500 proposed
1.

How a Microsoft EA true up actually works

The true up is an annual reconciliation that compares your deployed count to the baseline you committed at signing. It captures growth above that baseline, prices it at your protected unit rates, and bills the increase. It runs at the contract anniversary, on a true up order that is separate from the three year renewal.

The mechanic that costs buyers money is direction. The EA only adds. It never subtracts before renewal. Each annual order resets the minimum you carry forward, so a number reported high in Year 1 is paid again in Year 2 and Year 3.

What gets counted in the annual order

The order counts net new users and net new product adoption since the last reconciliation. Step ups from a lower suite to a higher one are priced changes, not free upgrades. The published unit price is rarely the driver on its own; the count is.

Order eventCounted asReduces later?
Net new usersAdded seats at your protected rateRenewal only
Suite step upPriced change to the higher editionRenewal only
New product adoptionAdded licenses for the new workloadRenewal only
Decommissioned seatsNot netted unless you raise itRenewal only
Non obvious mechanic. The true up order is the moment your floor moves, not the renewal. Whoever controls the deployment number controls the quote, and by default that number comes from the reseller, not from your own sign in data.
2.

How license adds during the year compound exposure

A single inflated order is not a one year problem. Because the order resets the floor, every phantom seat is paid again in each remaining year of the term. A 300 seat overcount at the first anniversary is paid in Year 2 and Year 3 before you reach the only exit, the renewal.

The compounding is linear and easy to model. Take 300 E3 seats assigned but never used, added at the first anniversary at the protected rate of $432 per user per year. That is $129,600 a year, carried for the two remaining years of a three year term.

Term yearPhantom carry costCumulative locked
Year 1 (baseline)$0$0
Year 2 (after first true up)$129,600$129,600
Year 3$129,600$259,200
Total locked before renewal$259,200$259,200
Cumulative locked cost of a 300 seat phantom add $0 $130K $260K Year 1 Year 2 Year 3 $259,200 Reported count (locked) Reconciled count ($0)

Reported figures match the table above. Benchmark scenario, not a quote.

Why you cannot true down mid term

3.

What inflates a true up bill above the forecast

Over reported headcount, full price step ups, and uncredited decommissions inflate the bill. In a representative 10,000 seat estate the reseller proposed a $1,058,400 annual order. After reconciliation the defensible order was $604,800.

Order lineQuantityUnit per yearCost
New E3 users, as proposed1,500$432$648,000
E3 to E5 step ups, billed at full E5600$684$410,400
Proposed annual order2,100$1,058,400
New E3 users, active after reassigning retired seats1,050$432$453,600
E3 to E5 step ups, priced as the difference600$252$151,200
Defensible annual order1,650$604,800

The step up line is the quiet one. The E5 add on over E3 is $21 per user per month, which is $252 per year, not the full E5 rate of $684. Billing 600 step ups at full E5 overcharges $432 per user, the same as a net new seat.

Where the $453,600 overcount comes from $0 $150K $300K $129,600 Phantom seats $64,800 Retired not netted $259,200 Full price step ups Total $453,600

Three drivers sum to $453,600, matching the proposed less defensible order. Benchmark scenario, not a quote.

15 to 30%

Count above active use at submission

True up counts in the engagements behind this paper ran 15 to 30 percent above the seats actually in use when the order was proposed.

42.9%

Recovered in one order

Reconciling the proposed $1,058,400 order to a defensible $604,800 returned $453,600, then held for every remaining term year.

How do you build a clean count before submission

Pull the live directory, remove leavers, and reconcile assigned licenses against real sign in data. Net out reserved and decommissioned accounts. The count you can defend, not the count the reseller proposes, is the one to submit.

Which primary sources set the rules

The reconciliation rules sit in the Microsoft licensing terms, not in the reseller quote. Confirm them on the Microsoft Product Terms and the Microsoft Enterprise Agreement program page before you sign the order.

4.

The downgrade rights few customers exercise

Buyers treat the EA as a one way ratchet because the reseller frames it that way. Several rights cut the count, but they sit in the Product Terms or apply only at renewal, so most customers never use them.

RightWhat it allowsWhen usableWhy it is missed
Edition downgradeMove E5 seats to E3 to drop the suite tierRenewalSuites are framed as sticky
Down edition use rightsRun a lower version on premises for Windows Server and SQL ServerAnytimeBuried in the Product Terms
Reservation nettingRemove reserved and unassigned licenses before the countBefore the orderNot offered by default
Quantity reductionLower the committed seat countRenewalThe count is carried forward unchallenged

The single most valuable of these is edition downgrade at renewal. A seat stepped up to E5 mid term for one feature can return to E3 at renewal, but only if you raise it. The default renewal carries the higher edition forward at the new price.

5.

How price protection holds your cost against fiscal year increases

Price protection holds your ordered unit prices flat for the full term of the EA. True up adds during the term are billed at those protected rates, not at the current list. With Microsoft raising suite list prices on July 1, 2026, that hold is worth real money on every seat you add.

Microsoft 365 E3 rises from $36 to $39 per user per month, and E5 rises from $57 to $60. On an EA signed before the increase, your protected E3 rate stays at $432 per year while the new list reaches $468.

SuiteProtected EA rate per yearJuly 2026 list per yearHold value per seat
Microsoft 365 E3$432$468$36
Microsoft 365 E5$684$720$36
Protected EA rate versus July 2026 list, per user per year $0 $400 $800 $432 $468 Microsoft 365 E3 $684 $720 Microsoft 365 E5 Protected EA rate July 2026 list

Figures match the table above. List rates per Directions on Microsoft, July 2026 increase.

Non obvious mechanic. Price protection is not automatic on every line. Confirm it covers the products you expect to add later, and hold any prospective commitment until the protection language is agreed. The November 2025 removal of EA volume discount levels makes the protected baseline the real prize, not the headline discount.
6.

Where the common advice on EA true ups is wrong

The standard reseller line is to true up everything in one clean annual order so the paperwork stays simple. We disagree. In the true ups Fredrik Filipsson ran across 2024 and 2025, bundling every add into one order counted 15 to 30 percent of seats that were assigned but never used, and those seats locked into the floor for the rest of the term.

The buyer side move is to make active use, not assignment, the basis of the count. Reconcile assignments to real sign in data first, net out leavers and retired seats, and stage suite step ups for the renewal rather than the mid term order. Clean paperwork is not the goal. A defensible floor is.

Procurement and IT finance leads reviewing license assignment data against sign in activity before a Microsoft true up order
The reconciliation happens before the order is placed; once submitted, the count is the floor for the remaining term.
7.

Renewal positioning through true up management

Every true up is a rehearsal for the renewal. A clean, defensible count through the term is the evidence you bring to the renewal table, and it is what lets you reduce. A count inflated by phantom seats hands Microsoft a higher anchor and removes your room to cut.

12 months out

Build the count of record

Stand up the sign in baseline. Reconcile assignments to activity each quarter so the true up count is yours, not the reseller proposal.

Anniversary order

Report the defensible number

Submit active use, net out leavers and retired seats, and hold suite step ups out of the mid term order where you can.

Renewal

Reduce and re base

Use the one window where the count can drop. Move unused E5 seats to E3, lower committed quantities, and re base the floor.

What should you do before your next true up

  1. Pull the live directory and remove all leavers.
  2. Match assigned licenses to real sign in activity.
  3. Net out reservations and decommissioned accounts.
  4. Price every suite step up as the difference, not the full edition.
  5. Stage suite step ups for the renewal, not the mid term order.
  6. Confirm price protection covers the products you plan to add.
  7. Document the defensible count and the terms before submission.

Recommendation: reconcile to active use before you sign the true up order, then stage reductions for the renewal.

  • Before the order: submit a count built from sign in data, net of leavers, reservations, and retired seats, with step ups priced as the difference.
  • At renewal: exercise edition downgrade and quantity reduction rights to re base the floor, and lock price protection on the products you will add next.

Our fee is modest against a single reconciled order. We are glad to tie a meaningful part of the fee to delivered value.

Prepared by Redress Complianceredresscompliance.com

Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.

Procurement and IT leaders reviewing a Microsoft EA true up count against sign in data before the annual order

Facing a 2026 Microsoft EA true up?

Talk to a buyer side advisor. Thirty minutes, your add count, your timing, and your three biggest levers before you submit the annual order.

Buyer side intelligence, monthly

One letter a month. Negotiation moves, audit signals, and price book shifts.