Thank you for registering. Your copy of the Microsoft True-Up Survival Guide has been prepared for immediate access. 28 pages on true-up exposure categories, the pre-audit preparation framework, and the settlement negotiation tactics that determine whether your true-up event costs you what it should — or significantly more.
A confirmation has also been sent to your registered email address. If you don't receive it within 10 minutes, check your spam folder.
The Microsoft Enterprise Agreement true-up is an annual event — but its commercial consequences are determined in the months before the anniversary date, not during the counting exercise itself. Organisations that treat the true-up as an administrative task rather than a commercial negotiation routinely pay 20–40% more than their actual licence exposure requires. This guide maps the four exposure categories that drive the majority of unexpected true-up costs, and the preparation framework that eliminates most of the surprise.
The EA true-up requires you to report the highest peak user count during the prior 12 months for user-based products — M365, Dynamics 365, and related workloads. Organisations that have had personnel changes, office closures, or M&A activity frequently carry stale Active Directory accounts that inflate reported user counts by 8–25%. Each inflated user adds a full annual licence cost to the true-up invoice. A 10,000-user organisation with 15% stale account inflation is paying for 1,500 licences that nobody is using.
Windows Server, SQL Server, and System Center remain the largest source of true-up surprises for organisations with hybrid or on-premises infrastructure. The per-core licensing model, virtualisation rules, and the distinction between Standard and Datacenter editions create complexity that most IT teams track imprecisely. The most common scenario: a virtualisation platform running more SQL Server instances than initially licensed, or Windows Server Datacenter licences applied to physical hosts where the virtualisation rights don't cover the actual VM density. Microsoft's Software Asset Management (SAM) teams will find these gaps.
Organisations with Microsoft Azure Consumption Commitment (MACC) as part of their EA face a dual exposure risk at true-up: under-consumption against committed MACC amounts (which cannot be recovered after the period closes) and over-consumption in categories not covered by MACC credits. The combination of MACC credits expiring unused while unrelated Azure charges accumulate at list price is one of the most costly true-up scenarios we see. The second: organisations that haven't activated Azure Hybrid Use Benefit (AHUB) on eligible workloads and are paying full Azure pricing for Windows Server and SQL Server that their SA entitlements cover.
Software Assurance (SA) is renewed as part of the EA — but organisations that have reduced their EA scope, discontinued specific product lines, or restructured agreements mid-term sometimes carry SA entitlements that have lapsed without replacement. Lapsed SA eliminates upgrade rights, Licence Mobility, and AHUB eligibility for the affected product families. The commercial consequence shows up at true-up when the organisation attempts to use benefits against entitlements that are no longer active. SA lapse is also a common audit trigger for Microsoft's SAM programme.
The True-Up Survival Guide follows the complete arc of a true-up event — from the 90-day preparation window through the counting process, exposure quantification, Microsoft's pricing presentation, and the settlement negotiation. Most guides cover the compliance counting methodology. This one covers the commercial mechanics that determine what you actually pay.
The Enterprise Agreement requires an annual true-up of all user-based and device-based licences, with a final true-up at agreement expiry covering all products. The counting methodology differs by product family: user-based products (M365, Dynamics 365) use peak count during the period; server products use point-in-time counts at the true-up date or the highest deployment level, depending on the product. Understanding which counting methodology applies to which product — and in which situations Microsoft will use SAM tools to validate your self-reported counts — determines the risk profile of your true-up event.
Key finding: 67% of organisations that self-report true-up data without a pre-event audit subsequently receive a revised invoice from Microsoft's SAM team — at an average upward adjustment of 23%.The most powerful position in a true-up event is to have completed your own licence count before Microsoft begins theirs. A self-conducted audit 90 days before anniversary gives you three advantages: time to remediate stale accounts and unused assignments before the counting date, the ability to quantify your actual exposure and budget for it, and a defensible position in any subsequent SAM conversation. The preparation framework covers the tools, queries, and workflows for completing a credible self-audit across all EA product families — M365, Windows Server, SQL Server, Dynamics 365, Azure, and the full Office server stack.
Key finding: Organisations that complete a self-audit before true-up pay on average 18% less in true-up costs than those that rely on Microsoft's counting methodology — even when the underlying licence position is identical.Before engaging with Microsoft's true-up pricing presentation, you need your own financial model of the exposure. The model has three components: the licence delta (what you owe in units), the pricing that applies to those units (EA pricing, not list price), and the SA cost that Microsoft will attach to additional licences for the remaining term of the agreement. The pricing calculation is where most organisations make costly errors — accepting Microsoft's initial true-up invoice as the correct starting point rather than verifying the unit price against their EA schedule and the specific product version being invoiced.
Key finding: In 34% of true-up invoices reviewed, at least one line item contains a pricing error — wrong version, wrong SA inclusion, wrong edition — that the organisation would not have detected without an independent price verification.True-up events are not purely mechanical invoicing exercises. The pricing Microsoft applies to additional licences, the SA attachment decisions, the treatment of borderline deployment scenarios, and the resolution of ambiguous counting situations all involve commercial judgement. Microsoft account teams have pricing flexibility — the extent of that flexibility depends on the strategic relationship, the licence volumes involved, and the buyer's position in the renewal cycle. The guide maps which elements of a true-up invoice are negotiable, what leverage exists, and the specific positions that generate the best outcomes without damaging the broader commercial relationship.
Key finding: Organisations that engage an independent adviser for true-up settlement achieve an average of 14% reduction in final invoice value versus the initial Microsoft presentation — primarily through pricing corrections and SA structure optimisation.A formal SAM (Software Asset Management) review initiated by Microsoft is a different process from a routine true-up — it carries different contractual rights, different timelines, and different financial stakes. The guide covers the SAM review process from the initial contact letter through data collection, analysis, and settlement. The critical distinction: a SAM review initiated by Microsoft gives them the right to request specific data and to use their own counting tools. Understanding what you are contractually required to provide — and what you are not — determines the risk profile of the SAM outcome.
Key finding: 82% of Microsoft-initiated SAM reviews result in a financial settlement — but the median settlement amount is 40% lower when the organisation has independent legal and commercial representation engaged before responding to the initial letter.The period immediately following a true-up is the optimal time to restructure the EA to reduce future true-up exposure. New licence entitlements are fresh in the record, SA is current, and the Microsoft account team is receptive to constructive conversations about agreement structure. The guide covers the post-true-up restructuring review — identifying over-committed products for down-size at the next renewal, activating under-used SA benefits, restructuring the MACC commitment to match actual Azure consumption trajectory, and establishing the quarterly licence review cadence that prevents the next true-up from being a surprise.
Key finding: Organisations that conduct a formal post-true-up restructuring review reduce their subsequent true-up costs by an average of 31% compared to organisations that treat the true-up as a closed event.The true-up conversation with Microsoft's account team is a commercial negotiation, not an administrative process. Our advisory service delivers an independent licence count, exposure quantification, and settlement negotiation support — so you enter the conversation with your own data, not Microsoft's.
18 pages on audit triggers, contractual rights during a SAM review, exposure quantification methodology, and the settlement negotiation framework that controls your final liability.
Download Free →The complete 24-page guide to Microsoft Software Assurance — benefit catalogue, upgrade rights, Licence Mobility, AHUB activation, and SA renewal negotiation tactics.
Download Free →The 40-page framework for approaching EA negotiations — pricing mechanics, leverage points, timing strategy, and the positions that consistently reduce renewal costs by 25–40%.
Download Free →The frameworks in this guide work. They work better with 20 years of deal data behind them. If you have an upcoming EA renewal, true-up, or Microsoft audit — a 20-minute call with a senior advisor will tell you exactly where your exposure is and what you can negotiate.