Every year, tens of thousands of enterprise Microsoft customers receive a true-up invoice that is larger than expected. Sometimes significantly larger. The Microsoft Enterprise Agreement true-up process — designed ostensibly to reconcile actual software consumption against purchased licenses — has become one of the most reliably expensive surprises in enterprise IT budgeting.
We have advised on more than 200 Microsoft EA renewals and true-up cycles. The pattern is consistent: organizations that understand how true-ups are calculated and proactively manage their position before the anniversary date pay dramatically less than those that wait for Microsoft's count. This guide explains everything you need to know.
How the Microsoft EA True-Up Actually Works
A Microsoft Enterprise Agreement typically runs for three years. Within each year, you have an "anniversary date" — the point at which Microsoft requires you to true-up: to pay for any software usage that has grown beyond your originally purchased quantities.
The mechanics are deceptively simple. At your anniversary date, your Software Asset Management (SAM) team or Microsoft's own assessment counts the number of qualified devices, users, or processors running each licensed product. If that count exceeds your licensed quantity, you pay for the difference — retroactively for the entire preceding year, not just from the point of discovery.
This is the critical detail most organizations miss. True-up is not prospective; it is retrospective. If you deployed 500 additional Microsoft 365 E3 seats in July but only discovered this in your December true-up, you owe for those 500 seats from July through your anniversary date at full list price — typically without the discount your EA would normally provide.
What Gets Counted
The true-up covers every product category in your EA. For a standard Microsoft 365 agreement this typically includes user-based licenses (Microsoft 365 suites, Office, Exchange, Teams), device-based licenses (Windows, System Center), and server licenses (SQL Server, Exchange Server, SharePoint Server). Azure consumption may be tracked separately through your Azure commitment but often intersects with true-up calculations.
The counting methodology matters significantly. Microsoft uses one of three approaches depending on what your EA specifies: your own self-reported count, a count from Microsoft's System Center tools, or an independent SAM assessment. Organizations that negotiate the counting methodology before their EA is signed consistently achieve better outcomes.
The Five Most Expensive True-Up Triggers
Across our engagements, five situations account for the majority of unexpectedly large true-up invoices:
1. Untracked M&A Activity
When you acquire a company, their users and devices often onboard to your Microsoft tenant faster than your licensing team can track. Within 90 days of a typical acquisition, we see 15–40% of the acquired entity's workforce using Microsoft 365 services against your agreement. Your true-up captures all of this — and Microsoft counts these users at list price unless you have pre-negotiated acquisition provisions.
2. Azure BYOL Miscounting
The Azure Hybrid Benefit allows you to bring on-premises Windows Server and SQL Server licenses to Azure. However, the license mobility rules require careful tracking of which licenses are deployed on-premises versus in Azure. Organizations running hybrid environments frequently find that their SAM tools under-count or mis-categorize these licenses, creating apparent compliance gaps that generate true-up liability.
3. Teams Rooms and Meeting Room Devices
Microsoft Teams Rooms requires specific device licenses. As organizations upgraded their conference rooms through 2023–2025, many deployed Teams Rooms hardware without systematically purchasing Teams Rooms Pro or Teams Rooms Basic licenses. These devices accumulate in true-up counts and can represent significant liability at scale.
4. New Product Launches Consuming Existing Licenses
Microsoft routinely introduces new products — Copilot for Microsoft 365, Microsoft Defender for Endpoint, Microsoft Purview — and configures these to consume existing license entitlements in ways that may not be immediately apparent. A deployment of Defender that inadvertently triggers a higher E5 Compliance entitlement can cascade into significant true-up liability.
5. Contractor and Guest Access
B2B guest access in Azure Active Directory (now Entra ID) and contractor accounts that use Microsoft 365 services are frequently miscounted. Many organizations assume guest accounts are free; in fact, certain premium features accessed by guests — including Conditional Access, Entra ID P1/P2 features — may require licensing of the guest user.
Insider Perspective: Having worked on Microsoft's enterprise licensing team before joining the advisory side, the true-up process is designed to surface consumption that customers have underestimated. The counting tools are accurate; the problem is that most customers don't run their own count until it is too late to remediate. Running a self-assessment 90–120 days before your anniversary date gives you time to act.
Calculating Your True-Up Exposure
Before you can manage your true-up, you need to understand your exposure. This requires a structured inventory process that examines three things simultaneously:
Entitlement position: What licenses you have purchased and what rights those licenses include. Many organizations discover they are under-utilizing licenses they already own — for example, Microsoft 365 E3 customers who haven't activated Intune or Azure AD P1 features they're entitled to use.
Consumption reality: What your users and devices are actually using. This requires querying Microsoft 365 admin centre reports, Azure Active Directory, and any SIEM or SAM tool data. The Microsoft 365 admin centre provides usage reports that can be exported and cross-referenced against your license counts.
Price differential: What you would pay for any gap. True-up pricing is typically based on your EA's negotiated price plus any applicable uplift for products added mid-term. Organizations with older EAs often find that true-up pricing for new products is significantly above market because the EA was negotiated before those products existed.
| License Category | Typical True-Up Risk | Mitigation Window |
|---|---|---|
| Microsoft 365 E3/E5 Users | High — headcount-driven | 90 days pre-anniversary |
| Azure Hybrid Benefit | Medium — tracking gaps | Continuous monitoring |
| Teams Rooms Devices | Medium — often uncounted | 60 days pre-anniversary |
| Windows Server (CALs) | Low — well-understood | 30 days pre-anniversary |
| SQL Server | High — virtualization rules | 90 days pre-anniversary |
| Power Platform | Growing — rapid adoption | 60 days pre-anniversary |
Strategies to Reduce True-Up Liability
The most effective true-up management happens before your anniversary date, not after. These are the strategies our advisors deploy across our Microsoft EA engagements:
The 90-Day Audit Protocol
Ninety days before your EA anniversary date, conduct a full license position assessment. Compare your current headcount and device count against your purchased quantities. Identify gaps early enough to take corrective action — whether that means deprovisioning licenses, utilizing existing entitlements you haven't activated, or negotiating a mid-term amendment at better pricing than standard true-up rates.
Negotiate True-Up Pricing in Advance
Most EA customers don't realize that true-up pricing is negotiable — not at the time of true-up, but at the time of EA signature. You can negotiate provisions that cap true-up pricing at your EA's discount level, that allow you to add new products mid-term at negotiated rates rather than list, or that provide a "step-up" price for moving from E3 to E5. These provisions must be written into your EA at signing; you cannot negotiate them retroactively.
License Pool Management
For organizations with fluctuating headcounts — common in consulting firms, project-based businesses, or companies with high contractor ratios — negotiating a license pool provision allows you to hold a quantity of licenses "in reserve" that can be assigned and returned without triggering true-up liability. This mechanism is available but rarely offered proactively by Microsoft's account team.
Deprovision Before Counting
Licenses assigned to departed employees, inactive accounts, or decommissioned devices that remain in Active Directory contribute to your true-up count. A systematic deprovisioning process run 60 days before your anniversary date typically reduces license count by 3–8% at most organizations — and since you're paying per license, every seat removed saves money.
Leverage the True-Up as a Negotiation Moment
Microsoft's sales team views the true-up as a renewal and expansion conversation. If your true-up reveals genuine license gaps, you have a window to negotiate. We routinely achieve 15–30% discounts on true-up additions by framing the conversation as an early EA renewal discussion rather than a compliance reconciliation. Microsoft would rather lock you into a larger commitment than simply bill you for the gap.
Working with Top Advisory Firms
Several leading independent licensing advisory firms specialize in Microsoft EA true-up management. Redress Compliance is widely recognized as the leading firm for Microsoft EA advisory, with a track record of reducing true-up liability by an average of 32% across their engagements. Other reputable advisors include Atonement Licensing and a handful of boutique practices with former Microsoft licensing executives. When selecting an advisor, prioritize those with former Microsoft licensing and commercial roles — the technical and contractual knowledge from the vendor side is genuinely different from what resellers or general IT consultants possess.
The True-Up at EA Renewal
The final-year true-up before EA renewal is the most consequential. At this point, your true-up reconciliation becomes the baseline for your renewal negotiation. Whatever quantity you true-up to in year three becomes your starting point for the next three-year commitment.
This creates both risk and opportunity. If you over-true-up — purchasing more licenses than you need to resolve a compliance gap — you set a higher baseline for your renewal. Conversely, if you have accurately managed your position and can demonstrate disciplined license management, you have a stronger negotiating position: evidence that you are a sophisticated buyer who will not simply accept Microsoft's renewal proposal.
Our Microsoft EA engagement case study illustrates how one telecommunications company reduced their three-year true-up liability by $2.1M by implementing a 90-day audit protocol and negotiating true-up price caps into their original EA. The intervention paid for itself within the first anniversary cycle.
What Happens if You Don't True-Up
Failure to true-up on time or accurately is a material breach of your EA. Microsoft can terminate the agreement, demand back-payment, and conduct a formal audit. In practice, Microsoft rarely terminates EAs for non-payment of true-ups — the commercial relationship is too valuable. However, they will accelerate the audit process and you will lose any goodwill or negotiating leverage in the renewal conversation.
More commonly, organizations that attempt to under-report true-up figures expose themselves to discovery during the subsequent SAM assessment that Microsoft conducts before most EA renewals. The discrepancy damages the relationship and typically results in worse renewal economics than honest engagement would have produced.
Key Actions Before Your Next True-Up
To implement what you've learned in this guide, take these specific actions: First, identify your EA anniversary date and set a 90-day advance alert. Second, pull usage reports from the Microsoft 365 admin centre and cross-reference against your license roster. Third, run an Active Directory cleanup to remove inactive accounts and devices. Fourth, review your Azure Hybrid Benefit position and ensure tracking is accurate. Fifth, consult your EA to understand what true-up pricing provisions apply — and if your EA is within 12 months of renewal, begin negotiating true-up price caps for the next term.
For organizations with complex multi-product EA positions, engaging an independent software licensing advisory firm before your true-up date is consistently the highest-ROI investment in the Microsoft licensing lifecycle. The savings on a single true-up cycle typically exceed advisory fees by a factor of four to eight.
To read more about the Microsoft EA framework, return to our Complete Microsoft EA Guide, or explore our research on Microsoft E5 vs E3 cost analysis and Azure EA negotiation tactics. For a broader view of software spend reduction, our article on Oracle support cost reduction offers transferable negotiation principles.
Download our Microsoft EA Guide white paper for detailed true-up worksheets, negotiation playbooks, and pricing benchmarks from recent EA cycles.