What Is a Microsoft EA True-Up — and Why Does It Matter?
A Microsoft Enterprise Agreement True-Up is the annual reconciliation process in which your organisation reports any increase in Microsoft software usage — additional users, new Azure consumption above your committed level, Copilot deployments — since your last reporting period. In a standard three-year EA, you perform a True-Up before each anniversary date, typically 30 days in advance.
In one engagement, a global financial services firm used their True-Up data to identify 23% over-deployment on Microsoft 365 E3. Rather than paying back-charges, Redress structured a right-sizing plan that reduced the True-Up liability to zero and locked in a 14% discount at renewal. The engagement fee was less than 3% of the documented saving.
The mechanics are straightforward: you count your current qualified user devices and additional licences, compare them to your original commitment quantities, and report the delta to Microsoft. Microsoft then charges you for the difference, usually at your pre-agreed EA pricing. At the end of the three-year term, the True-Up also rolls into the renewal negotiation.
What most enterprises get wrong is treating this as a passive process. The True-Up is actually your most powerful window for proactive cost management. Done correctly, it is the event that: validates or corrects your licence consumption data; provides three years of usage trends that inform the renewal negotiation; surfaces shelfware and over-licensed products that create renewal cost-reduction arguments; and establishes your credibility as a disciplined buyer — which materially affects how Microsoft's field team interacts with you at renewal.
The True-Up Trap
The most common True-Up mistake is over-reporting. This happens when organisations submit True-Up counts based on provisioned accounts rather than active users, or when they include test and development environments that do not qualify as production use under the EA licensing terms. Over-reporting means you pay for more licences than you owe — and because True-Up charges are carried forward into the EA baseline at renewal, you bake the overpayment into every future renewal cycle.
We have seen enterprises overpay by £50,000–£300,000 per True-Up cycle through avoidable over-reporting. At renewal, this overpayment becomes the baseline from which Microsoft calculates its standard 10–20% uplift — compounding the original error across the next three-year term.