The Microsoft true up, counted and priced correctly. Clean the count, then claim the discount.

The Microsoft EA true up is an annual reconciliation of what you added during the year. What it costs depends on how you count users and whether the additions are priced at list or at your enrolled discount.

What is a Microsoft EA true up?

The true up is the annual reconciliation in a Microsoft Enterprise Agreement. Once a year you report the users, devices and subscriptions added since the last reconciliation, and Microsoft bills them in arrears at your enrollment prices.

The mechanics sit in your enrollment terms and the Microsoft Product Terms. Microsoft describes the overall structure, a minimum three year term aimed at organizations with 500 or more users or devices, on its Enterprise Agreement page.

• Cadence. Once per enrollment year, at the anniversary. Microsoft must receive the true up order between 60 and 30 days before the anniversary date.
• Scope. Enterprise products, Additional Products and added online services.
• No growth. If nothing was added, you still file an update statement in the same window.
• Direction. You can add at any time. You cannot reduce mid term, and most reductions wait for renewal.

Why do true ups feel one sided?

You cannot true down mid term. On premises licenses never come down, and your enterprise wide commitment stays where it is until renewal. The exception is Additional Products bought as subscriptions and marked reduction eligible in the Product Terms, which can be reduced at the anniversary for the year ahead.

That asymmetry is why an accurate count and a renewal plan matter. A seat added by mistake usually stays on the invoice for the rest of the term.

Is the true up count an average or a peak?

It is never an average, and the rule depends on the product. Enterprise products count qualified users and devices at the time you place the true up order. Additional Products count the maximum number used since the initial order, the last true up or the prior anniversary, whichever is latest.

Microsoft's own true up guide spells out the second rule: a license counts if the product was used or installed at any time since the last true up, even if it is idle on the day you report. The peak seat count from a two month Visio pilot goes on the order.

What have we seen in recent Microsoft true up reviews?

Across roughly 30 to 40 Microsoft EA true ups I reviewed for clients in 2024 and 2025, the first quote overstated the obligation in most cases. The errors were rarely exotic. They came from the directory, the price column and the date the count was taken.

• Directory overcount. Disabled and duplicate accounts inflated the user count by 8 to 18 percent.
• List price creep. True up lines were quoted at list rather than the enrolled discount, an overcharge of 15 to 30 percent on those lines.
• Wrong count date. Peak headcount from earlier in the year was used for enterprise products, where the enrollment counts qualified users on the day the order is placed.

Each of these is easy to correct before the order is signed. After signature, the quantities are on your enrollment and the invoice has been raised, so the correction becomes a negotiation.

How do you count users for a true up correctly?

Count from a clean source of truth, not the raw directory. Disabled, duplicate and service accounts should never reach the true up line. Reconcile the directory against HR records and your identity platform, which Microsoft documents on Microsoft Learn.

How do you build the clean count?

1. Reconcile. Match the directory to HR active records, including contractors who use company devices or online services.
2. Exclude. Remove disabled accounts, duplicates, service accounts, room and equipment resources, and shared mailboxes that need no license.
3. Check activity. Flag enabled accounts with no recent sign in and confirm each one with its manager before you drop it.
4. Evidence. Keep the query, the date you ran it and the HR extract you matched it against.

Which reports show your real position?

• Microsoft Entra admin center. Filter users by whether the account is enabled and export the list. Microsoft Graph returns the last sign in date for each user.
• Microsoft 365 admin center. Billing, then Licenses, shows purchased against assigned seats for each product. The usage reports show active users per workload.
• Microsoft Configuration Manager or Intune. Software inventory shows where Visio, Project, SQL Server and other Additional Products are installed. Keep snapshots from across the year, because Additional Products are counted at their peak.
• Volume licensing in the Microsoft 365 admin center. Your agreement, prior orders and license summary, so the baseline you reconcile against is Microsoft's own record.

Our license reclamation guide covers how to recover seats from leavers and inactive accounts during the year, so the cleanup is not all left to the weeks before the order.

How much can a stale count add to a true up?

A stale count combined with list pricing can multiply the true up several times over. Say a company enrolled 4,000 Microsoft 365 E3 users and its directory now shows 4,700 accounts. Microsoft's published list price for E3 is $39 per user per month on annual commitment, or $468 a year.

Assume the enrolled price is 15 percent below list: $33.15 a month, or $397.80 a year. The cleanup removes 5 percent of the 4,700 accounts as disabled (235), 3 percent as duplicates (141) and 2 percent as service accounts (94). That is 470 accounts, leaving 4,230 real users and 230 genuine additions.

The first quote is $236,106 higher than the correct line, about 3.6 times the right answer. The table prices each line for 12 months to keep the arithmetic visible, so check how your price sheet bills the year of addition.

The overcount also repeats. At the enrolled price, the 470 surplus seats cost $186,966 for every remaining year of the term. Enterprise wide online services such as E3 are rarely reduced before renewal in practice, so treat each added seat as permanent.

Why does a Microsoft true up cost more than it should?

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. The first is a data problem inside your company, and the second is a commercial one you fix with Microsoft before signing.

EA enrollments carry negotiated pricing that should flow to true up quantities. The Microsoft Customer Agreement has no annual true up, since subscriptions are added as you go, but its negotiated discounts should cover additions in the same way. Confirm the route on the Microsoft licensing documents library.

How do you spot the list price trap?

Compare the true up quote with your price sheet line by line. If a quantity arrives at list, push back, because added quantities belong at the level you negotiated for the base. The usual causes are a product missing from the original price sheet or a SKU replaced mid term.

What changed for online services pricing in November 2025?

From November 1, 2025, Microsoft moved online services in the EA and MPSA to consistent pricing across price Levels A to D, aligned with its public price list. The change applies at your next renewal, or when you buy an online service that is not already on your price sheet.

For the true up, online services already on your price sheet keep their enrollment price until renewal. A new online service added mid term comes in at the public price, so any discount on it has to be agreed before you deploy. Our analysis of the online services list price shift covers the renewal impact.

How do you avoid the retroactive uplift?

The retroactive uplift happens when a mid year price change is applied to your whole added quantity. You avoid it by locking pricing terms for added quantities and timing additions deliberately.

A second retroactive charge sits in the enrollment itself. Online services can be reserved before use with payment deferred to the true up, but reserved licenses are invoiced back to the month they were reserved. If you reserve early for a rollout that then slips, you pay for months of seats that sat unused.

1. Lock price protection for added quantities in the enrollment, including products you expect to add later.
2. Time large additions close to the anniversary where it helps.
3. Confirm discount flow to every true up line.
4. Reconcile the count before you accept the quote.

Does the order of additions matter?

Yes. The order you add products can trip a step price or a tier change, so model the sequence before you deploy at scale.

Sequence also creates overlap. If you buy the E5 Security add on for E3 users and move the same users to Microsoft 365 E5 a year later, you have paid twice for capability that E5 already includes.

What contract wording should you ask for?

• Price hold on additions. Enrollment prices apply to all true up quantities for the full term. This keeps mid term price changes out of the true up.
• Named future products. Put products you expect to add, such as Copilot or E5, on the price sheet at signing with a stated discount. Otherwise they arrive at the public price.
• Count definition. A written definition of qualified user that excludes service, shared and disabled accounts, which settles the directory argument before it starts.
• Reduction rights. The right to reduce named subscriptions at each anniversary. Without it, only products the Product Terms mark reduction eligible can come down.
• Quote timing. A commitment that the true up quote arrives before the ordering window opens, so you have time to check it.

What discount applies to true up quantities?

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, plus any additional discount negotiated at signing.

• Same level. Additions match the base discount.
• Tier crossing. Large additions may improve the level for on premises products. Since the November 2025 change, growth in online services no longer earns a better level on its own.
• Renewal evidence. A big, clean true up strengthens your position in renewal talks.

Every added line inherits the base discount, so it pays to benchmark your EA discount before the true up rather than after it.

Why we advise against holding back deployment to shrink the true up

The standard advice is to minimize the true up by deploying as little as possible during the year. We disagree. In those reviews, buyers who throttled deployment to shrink the count often paid more at renewal, because they arrived with a small, weak baseline and little to bargain with.

Count accurately, claim the discount on every added line, and use a healthy true up as evidence of committed spend at renewal. A clean, larger true up at your enrolled discount serves you better than a suppressed one that hands Microsoft the renewal conversation. Control the price on each line and let deployment follow the business.

A true up is a count and a price. Get the count clean and the discount applied, and the surprise disappears.

What will the Microsoft account team say about your true up?

Most true up discussions run through a handful of familiar lines. These are the ones we hear most often, with the reply that holds up.

• "The count comes straight from your tenant." The tenant shows accounts, while the enrollment bills qualified users. Send your reconciled count with the HR match and the exclusion list, and ask for that number to be priced.
• "That product is not on your price sheet, so it is at list." Ask for it to be added at your enrollment discount before the order is signed. If the enrollment named it, point to the clause.
• "Place the order now and we will fix the discount at renewal." Decline. Once you sign a true up order at list, you have agreed that price, and the enrollment gives you no route to a refund later.
• "The order has to be in this week." The deadline is fixed in the enrollment and you know it months ahead. Start the count early and the calendar never becomes the reason you accept a quote.

When should you start preparing for the true up?

Start four months before the anniversary. Microsoft's own guidance sets checkpoints at 120, 90, 60 and 30 days, with the order due inside the last of those windows.

If the true up falls in the last year of the enrollment, the renewal runs alongside it. Our 12 month EA renewal plan sets out that calendar, and the complete EA true up guide covers the order forms themselves.

How does enrollment size change the work?

At 600 users, close to the EA minimum, a small directory error is a large share of the year's growth, and one licensing owner can run the reconciliation. At 20,000 users the count spans several HR systems, regions and often acquired tenants. It needs an owner in IT and one in HR, and 120 days becomes the minimum.

What to do next

1. Reconcile early. Match your directory against HR active records before the anniversary, starting four months out.
2. Clean the count. Exclude disabled, duplicate and service accounts, and shared mailboxes that need no license.
3. Check the price column. Demand your enrolled discount on every true up line.
4. Check the count rule. Confirm which applies to each product: qualified users when the order is placed, or the highest use since the last true up.
5. Confirm price protection. Check the terms that cover added quantities and products not yet on your price sheet.
6. Model the sequence. Test the order of large additions for step price effects and overlapping add ons.
7. Keep the evidence. File the clean count and the priced order, and bring both to the renewal negotiation.

Frequently asked questions