28 pages. The annual true-up is the moment Microsoft reconciles what you committed to against what you actually deployed — and bills you for the gap. Most enterprises walk in underprepared. This guide changes that. Know your exposure before Microsoft does, challenge what's challengeable, and negotiate the settlement.
Used by compliance and procurement teams across 40+ industries. No spam. Unsubscribe anytime.
Enter your details for immediate access. Your information is never shared or sold.
Joined 1,500+ enterprise compliance professionals who have downloaded this guide
The true-up is not a passive event. It is a negotiation. This guide gives you everything you need to prepare, challenge, and settle it on your terms.
The mechanics of the annual true-up — what Microsoft measures, how the Effective Date calculation works, what triggers a mid-year "step-up," and the three most common measurement errors Microsoft makes that cost enterprises money.
Undeployed M365 licences, unauthorised server OS installations, SQL Server virtualisation misconfigurations, Teams Phone undercounting, Azure AD Premium gaps, and Copilot shadow deployments. Ranked by average enterprise liability.
A 12-step self-assessment framework for discovering and quantifying your exposure before Microsoft's data arrives. Which tools to use, which data sources matter, and how to reconcile Active Directory counts against EA entitlement records.
Not every Microsoft invoice line is correct. We identify the most common measurement disputes — virtual machine licensing overcounting, test/dev environment inclusion, contractor seat ambiguity — and the specific contractual language that supports a challenge.
When you have genuine exposure, you still have options. How to use the true-up as a negotiation event to restructure your licence mix, activate previously unused benefits, and convert overage into a more favourable forward commitment.
The enterprises that fare best at true-up time treat it as a 12-month programme, not a 30-day scramble. Governance structures, tooling cadences, and internal stakeholder alignment that eliminate surprise liability entirely.
Across 500+ engagements, these three categories account for over 70% of unexpected true-up liability. All three are controllable with the right preparation.
Average undisclosed liability from headcount growth between annual true-up cycles. Particularly acute in organisations with distributed hiring across business units that report to IT after the fact.
Misconfigured virtualisation environments — particularly VMware clusters — routinely trigger SQL Server licence overcounting under Microsoft's per-core rules. Challengeable, but only with the right documentation.
Enterprises that deployed Teams Phone System after their last true-up consistently undercount their active users because the measurement pulls from provisioning systems that lag actual usage by 30–60 days.
The True-Up Survival Guide is structured as a pre-true-up action checklist, not a theoretical overview. Every chapter has a corresponding "what to do now" action list so you can move immediately from reading to implementation.
This 2026 edition covers the expanded Copilot measurement rules introduced in the 2025 EA revision, the new Azure Active Directory licensing categories under Entra ID, and the updated virtual machine licensing rules for Azure Stack HCI deployments.
Related reading: True-Up Defence service overview, healthcare true-up defence ($2.7M liability avoided), EA Negotiation Playbook, and EA Negotiation Advisory.
"We identified $2.1M in challengeable lines before Microsoft's invoice arrived. By the time we sat down with our account team, the conversation was entirely different. We settled at 22 cents on the dollar."
Director of IT Procurement, Regional Healthcare SystemThe time to prepare is 90 days before your anniversary date — not 30. A 30-minute consultation will identify your specific exposure categories and what's realistically challengeable in your contract.