What triggers a Microsoft EA true-up
Every Microsoft Enterprise Agreement includes a true-up clause that requires your organization to reconcile actual license usage against the baseline commitment at least once per year. For most agreements, this happens on the anniversary date. Some contracts specify quarterly reporting, but the annual reconciliation is where the financial impact lands.
The trigger is simple: if you are using more licenses than your EA baseline covers, you owe Microsoft for the difference at the per-unit rate locked into your agreement. You cannot negotiate this rate during the true-up. It was set when the contract was signed.
What makes the Microsoft EA true-up uniquely painful is scope. It covers M365 seats, Azure consumption, Windows Server and CAL counts, and any other products on the enrollment. A company that grew from 800 to 1,100 employees over 12 months could be looking at a six-figure true-up bill across E3/E5 licenses alone.
If you have not been through a Microsoft true-up before, this overview of how true-ups work covers the fundamentals.
How to audit your M365 seat count against the EA baseline
The first step in true-up preparation is knowing your actual number. This sounds straightforward, but in practice it is where most organizations fail.
Step 1: Pull your EA baseline from the enrollment
Your Microsoft Volume Licensing Service Center (VLSC) or the Microsoft 365 Admin Center shows the license quantities on your enrollment. This is your contractual baseline. Document it by SKU: how many E3 seats, how many E5 seats, how many Power BI Pro licenses, and so on.
Step 2: Pull your actual provisioned count
Go to the Microsoft 365 Admin Center and pull the active user count for each license type. Be specific:
- Active users with licenses assigned
- Disabled accounts that still have licenses assigned (these still count)
- Shared mailboxes that have been upgraded to full licenses
- Guest accounts that consume license entitlements
Step 3: Compare the two numbers
The delta between your EA baseline and your actual provisioned count is your true-up exposure. Multiply by the per-unit rate in your agreement. That number is what your CFO needs to see.
Common traps that inflate your true-up bill
Entra ID shows the real count, but nobody looks
Microsoft Entra (formerly Azure AD) reflects your actual user count in real time. It is the source of truth. But most organizations do not compare their Entra user count to their EA baseline on a regular cadence. The gap grows silently for 12 months and surfaces as a surprise.
Disabled accounts still consuming licenses
When employees leave, IT often disables the account but does not remove the license assignment. The account is inactive, but the license is still consumed. During a true-up, Microsoft counts assigned licenses, not active usage.
Shared mailboxes converted to user mailboxes
Exchange Online shared mailboxes do not require a license. But if someone converts a shared mailbox to a regular user mailbox (sometimes to increase storage), it now requires a license and counts toward your true-up.
Acquisitions and mergers adding users in bulk
If your company acquired another organization mid-contract, those users were likely provisioned into your tenant. Depending on the timeline, you could owe for 6 to 12 months of additional licenses at the locked-in rate.
Azure consumption spikes
Azure true-ups are consumption-based, not seat-based. A development team spinning up resources for a project can create significant overage that does not show up until the reconciliation.
How to deprovision before the reconciliation date
The true-up reconciliation is based on your peak usage during the measurement period in some agreements, and point-in-time count in others. Check your specific EA terms. If your agreement uses a point-in-time count, deprovisioning before the measurement date directly reduces your bill.
Practical deprovisioning checklist:
- Remove license assignments from disabled accounts (departures, role changes)
- Audit shared mailboxes that were converted to user mailboxes and revert where possible
- Identify contractors and temporary workers whose engagements have ended
- Check for duplicate accounts (same person with two accounts in different domains post-merger)
- Review Power BI, Visio, and Project licenses assigned to users who have not opened the application in 90 days
- Remove trial licenses that auto-converted to paid assignments
Start this process at least 60 days before your true-up date. License changes in Microsoft 365 are not always immediate, and you need time to coordinate with department heads before removing access.
Negotiating with your Microsoft account team
True-ups have limited negotiation room because the rate is locked in. But "limited" does not mean "zero." Here is where you have leverage:
Unused but provisioned licenses
If you can demonstrate that licenses were assigned but never actively used (the user never signed in, never opened an application), some Microsoft account teams will consider a partial credit. This is not guaranteed and depends on your relationship with your account executive, but it is worth raising.
Growth trajectory as renewal leverage
Your true-up data tells a story about your growth. If you are consistently growing 15 to 20 percent annually, that information is valuable in the renewal negotiation. Use the true-up conversation to set up the renewal conversation. Ask your account team what the renewal pricing would look like if you committed to a higher baseline.
Timing the conversation
Do not wait for the true-up invoice to arrive. Contact your Microsoft account team 90 days before the true-up date to discuss the reconciliation proactively. Account executives respond better to proactive outreach than to disputes after the invoice is issued.
Product mix adjustments
If your true-up reveals that you are paying E5 rates for users who only need E3 functionality, use the reconciliation as an opportunity to discuss SKU adjustments for the next period. You cannot change the current true-up, but you can reduce future exposure.
Building a repeatable process
The difference between organizations that get surprised by Microsoft true-ups and those that manage them effectively comes down to one thing: a repeatable quarterly audit.
Every quarter, someone on your team should:
- Pull the current provisioned license count from the M365 Admin Center
- Compare it to the EA baseline
- Calculate the financial delta
- Report the number to finance and procurement
- Deprovision any licenses that are no longer needed
This takes about two hours per quarter when done manually. It saves tens or hundreds of thousands of dollars per year.
Key takeaways
- Microsoft EA true-ups reconcile your actual M365, Azure, and Server license usage against your contract baseline at a rate you cannot negotiate.
- The most common trap is the gap between your Entra ID user count and your EA baseline that nobody monitors.
- Deprovisioning unused licenses before the measurement date directly reduces your bill in point-in-time agreements.
- Start the conversation with your Microsoft account team 90 days before the true-up, not after the invoice arrives.
- Quarterly audits turn a painful annual surprise into a manageable, predictable process.
If your team is tracking Microsoft license counts in spreadsheets or discovering the true-up number when the invoice lands, StackIQ can help. See how StackIQ tracks renewals and true-ups on one calendar with automated seat count monitoring and financial exposure alerts.