Every Microsoft Enterprise Agreement contains a true up. Done wrong, it produces a one shot bill that runs 12 to 35 percent above the original commitment. Done right, it is a routine annual reconciliation. This article maps the seven mistakes that cost the most and the corrections that pay back inside one renewal cycle.
A Microsoft true up is the annual reconciliation under the Enterprise Agreement that converts new user additions and product upgrades into licensed entitlement. It is not a discretionary process. Microsoft mandates it once each EA year, and the publisher's audit team validates the count.
The mistake pattern is consistent. Customers undercount in year one, then over correct in year three when the renewal arrives. The publisher captures the swing as retroactive uplift and renewal compression. The total cost can exceed the EA price by 30 percent or more across the three year cycle.
This article walks through the counting rules, the seven mistakes that drive the overrun, and the buyer side moves that bring the true up under control. Run it alongside the EA renewal playbook, the Microsoft knowledge hub, and the Microsoft services page.
Key Takeaways
What every EA holder should know before the next true up window
The count is yours. Microsoft does not produce the count. The customer submits it. Internal accuracy determines the bill.
True up is not list price. Negotiate the true up price level inside the EA, not at submission time.
User definitions matter. M365 user means active user plus shared mailbox plus admin account plus service account. Get the definition wrong and the count is wrong.
Step ups are not true ups. Edition upgrades follow a separate path with different commercial terms.
Reduction is not allowed mid term. The EA only ratchets up. Reductions land at renewal, not true up.
The audit window opens at submission. Microsoft validates the true up against tenant telemetry. Discrepancies trigger an audit.
The renewal price is set at year three. Every true up adjustment compounds into the year three baseline.
What a Microsoft EA true up actually is
The Enterprise Agreement commits the customer to a minimum quantity at year one. Each subsequent year, the customer submits a true up to reconcile the actual quantity against the commitment. Additions are billed at the EA price level. Reductions are not credited until renewal.
The true up submission window
Annual cycle. The true up is due 30 to 60 days before the EA anniversary, depending on contract paper.
Customer submitted. Microsoft does not auto calculate. The customer or Licensing Solution Partner submits the count.
Validation phase. Microsoft compares submission against tenant telemetry. Discrepancies open the audit door.
Settlement. The true up invoice clears 30 days after acceptance. The new entitlement applies retroactively to the year start.
Products in scope
The true up scope includes every product under the EA enrollment. Microsoft 365 and Office 365 user subscriptions, Windows client access, server CALs, Azure committed spend, Dynamics 365, Power Platform, and on premises server products all settle through the true up. Each product has a distinct counting rule.
Seven costly mistakes that drive the overrun
The mistakes are predictable. Each one is preventable with a process change that takes weeks, not months.
Mistake one: counting active users instead of licensed users
What goes wrong. The HR system counts active employees. The licensing rule counts assigned users, service accounts, shared mailboxes, and admin accounts.
Cost impact. Underreporting by 5 to 12 percent at submission. Retroactive uplift at audit.
Fix. Pull the count from the Microsoft 365 admin center, not from HR.
Mistake two: missing the shared mailbox rule
What goes wrong. Shared mailboxes over 50 GB or with calendar access require a license.
Cost impact. 1 to 3 percent of the user count.
Fix. Quarterly mailbox audit. Archive or right size.
Mistake three: ignoring Windows VDA
What goes wrong. Virtual desktop access requires VDA or M365 with Windows entitlement.
Cost impact. The VDA shortfall is often the single largest true up category. Up to 8 percent of the bill.
Fix. Reconcile VDI session counts against M365 entitlement quarterly.
Mistake four: Azure committed spend overrun
What goes wrong. Azure spend above the EA commit converts to overage at list price.
Cost impact. 10 to 25 percent uplift on the overage portion.
Fix. Increase the committed spend at true up to absorb the overage band.
Mistake five: step ups treated as true ups
What goes wrong. Moving users from E3 to E5 is a step up, not a true up. Different commercial rules apply.
Cost impact. Step up pricing locks in for the remaining EA term.
Fix. Run step up volume through a separate negotiation. Do not bundle with true up submission.
Mistake six: signing at list price
What goes wrong. The customer accepts the LSP quotation at EA list. No negotiation.
Cost impact. 5 to 18 percent above achievable price.
Fix. Treat the true up as a mini negotiation. Reference the EA price level, not the renewal level.
Mistake seven: missing the audit defense window
What goes wrong. Microsoft opens an audit on the strength of a true up anomaly.
Cost impact. Audit settlement averages 1.4x the true up shortfall.
Fix. Effective license position completed before submission, signed by the licensing owner.
User counting rules that matter
Microsoft has shifted toward per user counting across the M365 stack. The rule is not intuitive. Get the definition right and the count is straightforward.
Per product counting rules
Product
Counting unit
Common error
Frequency to check
Microsoft 365 E3 / E5
Assigned user
Including unassigned admin accounts
Monthly
Office 365 E1 / E3
Assigned user
Shared mailbox over 50 GB
Monthly
Dynamics 365
Named user by role
Misclassified role license
Quarterly
Power BI Pro
Per user
Workspace access without entitlement
Quarterly
Windows Server CAL
Device or user
External user access path
Annually
SQL Server
Core or Server plus CAL
Virtualization and core minimum
Quarterly
Azure committed spend
Monthly consumed
Marketplace pass through
Monthly
Tooling for the count
Microsoft 365 admin center. Authoritative source for user assignment data.
Azure cost management. Authoritative source for committed spend versus overage.
SCCM or Intune. Authoritative for device counts and Windows VDA.
LSP reporting. Cross check against publisher record. Do not rely on it as the source of truth.
Negotiation moves at the true up window
The true up is a negotiation moment, not a clerical event. Microsoft expects the customer to ask. The customer who does not ask pays full EA list.
Five negotiation moves that work
Reference the EA price level, not list. The true up clause settles at the EA price level. Confirm in writing before submission.
Bundle the true up with the next product purchase. Microsoft sells incremental Copilot, Power Platform, or Dynamics seats off the same paper. Use the true up volume as a discount lever.
Convert overage to commit. Azure overage at list converts to committed spend at 10 to 25 percent off. Settle at true up.
Park step ups separately. Negotiate edition upgrades on a separate paper with a separate price book.
Use the renewal anniversary as a deadline. The true up settlement informs the renewal baseline. Do not let it close inside Microsoft Q1 or Q2.
Anti patterns to avoid
Letting the LSP submit without sign off. The LSP submits to the publisher, not to the customer. The submission is the audit trigger.
True up signed without the renewal in view. The true up settlement becomes the renewal baseline. Negotiate both together.
Last minute true up. The 30 day window is the publisher's window. The customer needs 90 days.
True up versus renewal versus mid term reduction
Three distinct moments interact under the EA. Conflating them produces the overrun pattern.
Three moments compared
Moment
What it does
Can reduce?
Price reset?
True up (annual)
Adds new entitlement
No
No price reset
Step up (mid term)
Upgrades edition
No
Lock in remaining term
Renewal (year three)
Resets baseline and price
Yes
Full price reset and uplift
When to use each
True up. Use for organic growth and incremental seat needs.
Step up. Use only when the edition upgrade has clear ROI and a separate negotiation.
Renewal. Use to reset oversized footprints. Reductions land here.
What to do next
The checklist takes the EA holder from where they are today to a clean true up submission with negotiated pricing.
Pull the count. M365 admin center, not HR. Validate against assigned user definition.
Map the shared mailboxes. Identify mailboxes over 50 GB or with delegated access.
Reconcile Azure spend. Six month rolling consumption against committed spend. Identify the overage band.
Identify step up candidates. Separate from the true up. Negotiate independently.
Confirm EA price level. Get the LSP to confirm the price level applied at submission, in writing.
Run audit defense. ELP signed before submission. Discrepancies resolved on the customer's terms.
Submit 90 days early. Window for negotiation. Use it.
Frequently asked questions
What is the deadline for the Microsoft EA true up submission?
The standard EA paper requires the true up submission 30 to 60 days before the contract anniversary. The exact deadline is in the enrollment paperwork. The customer is responsible for the submission, not the LSP or Microsoft.
Best practice is to start the reconciliation 90 to 120 days before the anniversary. That window allows internal validation, leaver and joiner reconciliation, audit defense preparation, and a real negotiation on the true up pricing before submission.
Can the customer reduce license counts at the true up?
No. The EA only ratchets up at true up. Reductions are not credited until the renewal. The mechanic is by design. Microsoft prices the EA discount against the assumption that the customer commits to the entitlement for the full three year term.
The renewal at year three is the moment to reset oversized commitments. Customers that try to reduce at true up either receive no credit or face commercial friction with the LSP. Save the reduction conversation for the renewal cycle.
Is the true up price the same as the EA price level?
The contract says yes. In practice, the LSP will quote the true up at the EA price level only if the customer asks. Without confirmation in writing, some LSPs quote at the current renewal level, which can be 8 to 18 percent higher.
Always request the price level confirmation in writing before submission. Reference the original EA enrollment and the price level applied. The clause exists in every EA. Use it.
What happens if the true up count is wrong?
Microsoft validates the submission against tenant telemetry. If the published count is less than the tenant data, Microsoft opens an audit. Audit settlement averages 1.4x the underreported shortfall, plus interest in some cases.
The defense is an effective license position prepared before submission. The ELP reconciles tenant telemetry, HR data, and licensing records into a single signed count. The ELP is the customer's audit defense if the publisher challenges the submission.
Does the true up affect the renewal price?
Yes. The true up settlement becomes part of the year three renewal baseline. Every seat added at true up compounds into the renewal commitment. A true up that overcommits inflates the renewal. A true up that undercommits exposes the customer to audit and retroactive uplift.
Best practice is to model the renewal at the same time as the true up. The renewal forecast informs the true up volume. The two events are commercially linked.
Should Azure committed spend be increased at the true up?
Often yes. Azure overage at list is 10 to 25 percent above committed spend rates. If the overage band is stable, converting it to commit at the true up captures the price differential. The committed spend increase counts as new commitment, which can also unlock incentive funding from the LSP.
Do not convert overage to commit blindly. If the overage is one off project spend, the commitment locks in the customer at a higher baseline. Model the next 18 to 24 months of consumption before increasing the commit.
How does Redress engage on the true up?
Redress runs the true up under the Vendor Shield subscription and the Renewal Program. The work covers the count reconciliation, the LSP negotiation, the ELP build, the Azure commit modeling, the step up separation, and the submission gate.
The engagement typically delivers a 12 to 22 percent reduction against the LSP first quotation, plus a documented baseline that protects the year three renewal. Read the EA renewal playbook and the Microsoft services page for the program scope.
The playbook covers true up timing, edition step ups, the renewal baseline, the Azure committed spend conversation, and the Copilot add on negotiation. Buyer side moves only.
Independent. Written for CIOs, CFOs, and procurement leaders running an active Microsoft EA. No publisher kickback. No LSP affiliation.
EA Renewal Playbook
Open the white paper in your browser. Corporate email only.
The true up adds. The step up upgrades. The renewal resets. Three moments. Three negotiations. The customer who treats them as one event pays for all three at the publisher's rate.
Former Microsoft Enterprise Sales Lead
Now on the buyer side, 180 EA renewals over five years
True up benchmarks, EA discount bands, Copilot ROI patterns, and the audit defenses that worked. Written for buyer side teams running active Microsoft renewals.
Before you go
Get the buyer side monthly briefing.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
