What the True-Up Is — and What Most Buyers Think It Is
The Microsoft Enterprise Agreement true-up is the annual mechanism by which your organisation's licence count is reconciled with your actual deployment. Once per year, you submit a report to Microsoft detailing the number of users and devices running each covered product across your organisation. If that count exceeds your EA baseline, you pay for the additional licences at the terms set in your agreement. If it is below your baseline, you generally do not receive a credit — you are simply paying for licences you are not fully using.
Most enterprise procurement teams treat the true-up as an administrative process. They receive a request from their LAR or Microsoft account team, their IT department runs a report, they sign an order form, and they pay the difference. The entire cycle takes a few weeks and is often handled below the level of serious commercial scrutiny.
This is a mistake that costs enterprises significant money. The true-up is not an administrative event. It is a commercial event — one where the terms and conditions you agreed to at EA signature directly determine your financial exposure, your ability to dispute Microsoft's count, and the pricing at which any growth is billed. Understanding the specific clauses that govern your true-up is essential before you sign your EA — because once it is signed, those terms are fixed for three years.
in true-up compliance reviews conducted for clients in 2025 — the difference between what clients expected to pay and what Microsoft's calculations indicated was owed under standard EA terms.
How the True-Up Mechanism Actually Works
Your EA establishes a baseline — the number of licences you commit to at the agreement's start. This baseline locks in your per-unit pricing for the agreement term. At each anniversary, you reconcile actual deployment against that baseline and pay for any growth at the rates specified in your agreement. In theory, the true-up ensures you only pay for what you use. In practice, the mechanism has several structural features that systematically favour Microsoft.
The Counting Definition Problem
The most consequential clause in your true-up framework is the definition of a "qualifying user" or "qualifying device" for licence count purposes. Microsoft's standard EA language counts a user as qualifying if they have been assigned a licence, regardless of whether they are actively using the software. Your IT department may report active users. Microsoft may count assigned licences. The gap between these two numbers — particularly in large enterprises with high contractor turnover, legacy accounts, and seasonal workforce fluctuations — can represent tens of thousands of licence discrepancies.
Negotiating a clear, agreed definition of what constitutes a countable user or device — one that references active use rather than mere assignment — is one of the highest-value contract modifications buyers can make at EA signature. Microsoft resists this language, precisely because the standard definition protects their revenue from licensing inactive accounts.
The Proration Structure
When your licence count increases during the year — from hiring, acquisition, or deployment expansion — the true-up bills you for the additional licences from the month of deployment to the EA anniversary date. The proration calculation seems straightforward. The complexity emerges in how Microsoft counts the "month of deployment": whether it uses the first day a licence was assigned, the date it was activated, or the date it appeared in Microsoft's telemetry. These dates frequently differ, and the difference has a direct financial consequence in large deployments.
The "Deployment Date" Definition
Microsoft's standard EA language defines deployment as the date a product is "made available to a user or device." This language is deliberately broad. In cloud deployments, Microsoft's telemetry captures the date a licence is assigned in the tenant — which may precede the date a user actually activates or uses the product by weeks or months. In on-premises deployments, the date of installation and the date of use may differ significantly.
The practical effect: Microsoft can legitimately bill for full-month proration from the date of licence assignment, even if the user never activated the product. For large cohorts of users who are assigned licences in batch processes (common in major M365 deployments), this can add up to multiple months of billing for products that were not in active use.
How Additional Licences Are Priced
The true-up prices growth licences at the per-unit rate established in your EA, prorated for the remaining months of the agreement. The rate is locked at EA signature. This is one of the EA's most valuable protections — your growth pricing is not subject to Microsoft's annual price increases during the agreement term.
However, the growth pricing only applies to products covered under your EA. Products not covered at EA signature — new Microsoft products, upgraded SKUs, or add-ons added after signature — are priced at then-current list rates unless you negotiate explicit pricing provisions for anticipated additions.
True-Up vs. Formal Audit: Understanding the Difference
A true-up is not an audit. This distinction is commercially important — and one that Microsoft's account teams sometimes obscure in their communications.
The true-up is a self-reporting mechanism: your organisation reports its deployment count to Microsoft. You control what you report, within the bounds of contractual honesty. A formal audit is a separate process in which Microsoft (or a designated third party) has the right to examine your deployment directly, without relying on your self-reported count. The audit rights in your EA govern what Microsoft can do and when.
If your account team suggests that the annual true-up gives Microsoft the right to independently verify your deployment, they are conflating two different processes. Review your EA's specific audit rights clause. In most standard EAs, Microsoft's formal audit rights are constrained — they typically require notice, must be conducted by a qualified third party, and are limited in frequency. The true-up is a separate, self-reported process.
What Microsoft Can Do and When
Microsoft's standard EA audit rights allow Microsoft or its designated representative to audit your deployment once per year, with 30 days written notice, during normal business hours, using non-intrusive means. These are the standard terms. They are negotiable at EA signature.
Buyers with significant negotiating leverage have successfully modified audit rights clauses to: extend the notice period from 30 to 60 days; restrict audits to one occurrence per two-year period; require that any audit third party be agreed by both parties; and cap the look-back period for retroactive licence obligations at 12 months. Each of these modifications reduces Microsoft's ability to conduct surprise audits or assess retroactive liability for historical deployments.
Can You Reduce Licences at True-Up?
This is one of the most frequently misunderstood aspects of the EA true-up. The answer, under standard EA terms, is generally no — not at the annual true-up. Your EA baseline is a minimum commitment for the three-year term. If your deployment falls below the baseline, you continue to pay for the committed licences.
The only mechanism to reduce your baseline — reducing the licence count below your committed minimum — is at EA renewal, not at the annual true-up. This is why a thorough licence inventory before renewal is so important. The inventory evidence you build determines whether you can argue for a reduced baseline at the start of the new agreement. Once you sign the new EA, you are committed to that baseline for another three years.
There is one partial exception: some EAs include a step-down provision that allows a limited reduction in licence count at the second anniversary of the agreement (Year 2 true-up). These provisions are not standard — they must be explicitly negotiated at EA signature. For organisations that anticipate workforce reduction, cloud migration, or SKU rationalisation during the agreement term, negotiating a step-down provision at EA signature is high-value preparation work.
The Year 2 Reduction Option
A step-down provision gives your organisation the right to reduce your licence baseline at the second anniversary of the EA, subject to a defined maximum reduction (typically 10–20% of the original baseline, negotiated at signature). This provision acknowledges that enterprise licence needs may contract as well as grow during a three-year commitment, and provides a structured mechanism for managing that contraction without waiting for renewal.
Microsoft resists step-down provisions because they reduce revenue predictability. Buyers who successfully negotiate them typically do so by demonstrating a credible case for workforce or footprint change during the agreement term — M&A activity, geographic consolidation, or documented migration plans.
True-Up Is Negotiated at Signature — Not at True-Up Time
The most important thing to understand about EA true-up clauses is that they are contractual terms negotiated at agreement signature. By the time your first annual true-up arrives, the commercial terms governing that event are locked. You can dispute Microsoft's counting methodology if you have contractual basis — but you cannot renegotiate the underlying clauses.
This is why including true-up terms in your EA negotiation preparation is not optional. The EA renewal preparation framework covers the full sequence of preparation activities. The True-Up Survival Guide provides a 28-page treatment of true-up mechanics, exposure categories, and pre-audit frameworks. Our True-Up and Compliance service covers both pre-signature term negotiation and post-signature compliance management.
Buyers who approach true-up clauses as boilerplate — as standard terms to be accepted rather than commercial positions to be negotiated — systematically overpay. The gap between standard true-up terms and buyer-optimised true-up terms is not cosmetic. Across our client base, negotiated true-up protections have prevented millions in avoidable overpayments.
In a 2025 engagement for a European healthcare organisation, we identified $2.7M in true-up exposure that had accumulated over two annual cycles due to Microsoft's interpretation of their standard counting clause. The buyer's IT team had been reporting active users; Microsoft's system counted assigned licences. The contractual language — which neither the buyer's procurement nor legal team had scrutinised at EA signature — supported Microsoft's position. The dispute was resolved commercially, but not without significant cost and management time. Proper clause negotiation at EA signature would have prevented it entirely.
True-Up Clause Negotiation Checklist
Before signing your EA renewal, ensure your legal and procurement teams have reviewed and addressed each of the following true-up-related positions. This list is not exhaustive — specific agreement structures may require additional review — but it covers the clauses that create the most frequent and significant commercial issues.
The definition of "qualified user" or "qualified device" for counting purposes should reference active use or authenticated sign-in, not licence assignment. The definition of "deployment date" for proration purposes should reference activation, not licence assignment. Growth pricing provisions should be included for all Microsoft products you anticipate adding during the agreement term. Audit rights should include reasonable notice periods, frequency limits, and third-party auditor qualification requirements. A step-down provision for Year 2 should be included if your organisation anticipates any potential licence reduction during the term. The look-back period for retroactive licence obligations should be contractually capped. The dispute resolution mechanism for count discrepancies should be clearly specified.
For the full legal and commercial treatment, our True-Up Survival Guide includes template clause language and a complete exposure framework. The Complete Guide to Microsoft EA Negotiation covers true-up terms within the full context of agreement preparation and live negotiation.