Editorial photograph of a Microsoft Enterprise Agreement true up contract on a desk
Spoke / Microsoft EA

Microsoft true up process guide.

The annual true up is where Microsoft Enterprise Agreement spend grows. The independent guide to the order, the math, the timing, and the buyer side moves.

Contact Us Microsoft Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Every Microsoft Enterprise Agreement carries an annual true up. The order is self reported and the math compounds across the term. The buyer side moves are well known.

Key takeaways

  • The true up is a self reported annual order that captures the increase in licensed users and devices over the prior year.
  • It is not an audit. Microsoft does not arrive on site. The customer submits the order through the partner and the LSP.
  • There is no true down. License counts only increase across the EA term, even if usage falls.
  • The window is roughly sixty days from the EA anniversary. Late submissions trigger penalty pricing and partner escalation.
  • Cloud subscription quantities reconcile monthly, not annually. The true up applies only to the on prem and the legacy SKUs.
  • Most overspend comes from leavers still tagged as users in Active Directory, and from contractors counted twice across tenants.
  • An independent review before true up will usually reduce the reportable count by ten to twenty percent.

The Microsoft true up runs every year on every Enterprise Agreement. The order is self reported, the math compounds, and the timing is unforgiving.

There is no true down. Once a user or device is added to the EA, the count cannot fall during the agreement term, even if usage falls to zero.

What follows is the buyer side reference. What the true up is, how the order runs, where the risk sits, and the moves that protect spend each year.

What the true up is

The true up is the annual reconciliation that closes the gap between licensed and consumed in an Enterprise Agreement.

The definition

The customer reports the increase in user count and device count over the prior twelve months. Microsoft charges for the delta.

What it covers

On prem licenses, server licenses on the EA, and any legacy SKU still on the agreement. Cloud subscriptions reconcile monthly.

  • On prem desktop bundles. Office, Windows, Core CAL, and the like.
  • Server licenses. Windows Server, SQL Server, and System Center.
  • Legacy SKUs. Anything still on the EA that has not moved to subscription.
  • Not cloud. M365 E3 and E5 subscriptions reconcile monthly through the cloud portal.

The annual window

The true up order is due roughly sixty days before each EA anniversary. The third anniversary closes into the renewal cycle.

How the order runs

The mechanics are simple, but the prep work decides the size of the order.

Pulling the counts

The customer extracts user counts from Active Directory or Entra ID, and device counts from SCCM, Intune, or Jamf.

Partner submission

The counts go to the LSP or the partner. They build the order through Volume Licensing Service Center and pass it to Microsoft.

Pricing the order

The price comes from the EA price list at the agreement anniversary. Volume tiers carry across the term.

Microsoft true up risk pattern summary

Risk pattern Typical inflation Cleanup window Buyer side move
Leavers still in Entra ID5 to 15 percent of seats30 days pre orderRun a directory cleanup script
Double counted contractors3 to 8 percent of seats60 days pre orderNet out across tenants
M and A headcount driftVariable12 monthsStructure carve out clauses early
Shadow service accounts2 to 5 percent of seats30 days pre orderFilter UPNs against rule set
Stale device records5 to 10 percent of devices30 days pre orderRun SCCM clean sweep
Every leaver still in your directory at the anniversary is paid for as if they were active. The cleanup is mechanical and the savings are immediate.

Where the risk sits

Three patterns drive almost every true up overspend.

Leavers still in directory

Users who left the company but were never disabled in Entra ID. They still count, and they still get billed at true up.

Double counted contractors

Contractors with accounts in both customer and supplier tenants. Counted twice unless the agreement is structured to net them out.

Mergers and divestitures

Acquired entities pull headcount into the EA mid term. Divested entities cannot be removed. The asymmetry adds up.

Shadow accounts

Service accounts, test accounts, and shared mailboxes counted as licensed users. The cleanup is mechanical, the savings are real.

Buyer side moves

The true up is a self report. The buyer controls the inputs.

Pre true up cleanup

Disable leavers in Entra ID. Reconcile shared mailboxes. Net out contractors. Document the methodology.

SKU rationalization

Drop SKUs that no longer match the deployment. Move legacy SKUs to subscription where the math works.

Partner management

Hold the LSP to the agreed methodology. Push back on inflated counts. Document every assumption.

Suggested reading

What to do next

  1. Pull a fresh export of Entra ID users and tag every leaver from the last twelve months.
  2. Reconcile every shared mailbox and service account against the user list. Remove from the count.
  3. Audit contractor accounts against supplier tenants. Net out duplicates.
  4. Build the corrected count sixty days before the EA anniversary.
  5. Submit the corrected count to the LSP with documented methodology.
  6. Review the partner quote against your count. Push back on any inflation.
  7. Schedule the cleanup as a standing annual exercise inside the IT operations calendar.

Frequently asked questions

What is the difference between true up and audit?

True up is a self reported annual order. Audit is a separate compliance review run by Microsoft or a third party. The two are governed by different clauses in the EA.

Can I true down at the end of the year?

No. The EA carries forward the highest count reached during the term. Reductions only happen at renewal, when a new agreement is signed.

Do cloud subscriptions go through true up?

No. M365 and Azure subscriptions reconcile monthly through the cloud portal. True up only applies to on prem and legacy server SKUs on the EA.

What happens if I miss the true up window?

Microsoft applies penalty pricing through the partner and may escalate to compliance review. The cure is to file the order within thirty days of notification.

Are contractors counted as users?

Yes, if they have an account in your tenant. Net them out only when the master service agreement places the license cost on the supplier side.

How big is a typical first true up?

Most EAs run a first true up at five to fifteen percent of the original baseline. Cleanups before the order will land it at the low end of that range.

Microsoft EA Renewal Playbook

The full microsoft ea renewal playbook framework from the Microsoft Practice.

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.

No spam. We will only email you about this download. Privacy.
Run the Microsoft 365 license optimizer against your estate in under five minutes.
Open the Tool →
60 days
Order Window
3 year
EA Term
0 reduction
True Down
100%
Buyer Side
100%
Buyer Side

The true up is not an audit. It is an annual self report. Treat it that way and the leverage flips to the buyer side.

Fredrik Filipsson
Co Founder, Redress Compliance
Deep Library

More on this topic.

Microsoft Practice →
Microsoft EA renewal playbook overview
Microsoft
Microsoft EA renewal playbook.
Renewal moves, M365 SKU framework, Azure commitment, and the buyer side levers.
15 min read
Microsoft knowledge hub overview
Microsoft
Microsoft Knowledge Hub.
Every Microsoft framework, benchmark, and playbook in one library.
8 min read
Azure MACC negotiation overview
Microsoft
Azure MACC commit to consume negotiation.
How to size and negotiate the Microsoft Azure Consumption Commitment.
12 min read
Microsoft 365 Copilot licensing overview
Microsoft
Microsoft 365 Copilot licensing.
Enterprise licensing model, prerequisites, and rollout posture for M365 Copilot.
14 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

The Microsoft Brief.

Monthly briefings on Microsoft EA renewal, true up posture, Azure commitment, and the buyer side benchmarks.