Microsoft True-Up negotiation is the most consistently mis-handled moment in the Microsoft Enterprise Agreement lifecycle. The True-Up is the annual reconciliation that captures user growth, additional product subscriptions, and consumption changes during the EA year. Microsoft account teams present it as an administrative submission; in practice, the True-Up is one of the largest negotiation opportunities in the EA cycle and the moment when many customers quietly overpay for the next twelve months.
This article walks through the Microsoft True-Up negotiation as it should be run by a buyer with discipline: the data preparation that precedes the submission, the over-counting that Microsoft systematically introduces, the optimisation moves available within the True-Up structure, and the contractual flexibility that determines whether the True-Up is a cost event or a negotiation moment.
The Microsoft EA is a three-year master commitment with an annual True-Up reconciliation. The customer reports the actual count of each subscription product in use as of the anniversary date, and pays Microsoft for the increase over the prior year's committed quantity. The True-Up is unidirectional by default: increases are billed; decreases are not refunded. This asymmetry is what makes the preparation work so important.
The True-Up applies to subscription products inside the EA: M365 user subscriptions, Windows 11 Enterprise, Dynamics 365 user types, Power Platform, GitHub, security entitlements, and the various Copilot SKUs. It does not apply to Azure consumption (which is metered separately under the MACC) or to perpetual licence entitlements (which were largely phased out of the modern EA).
The True-Up should not be the moment when the customer first looks at the consumption data. The preparation work begins ninety days before the True-Up submission and has three components.
Microsoft does not refund for inactive accounts. Every disabled account, every departed employee, every test account, every duplicate user identity that is still assigned a licence is a True-Up cost in the next anniversary cycle. The first step is to pull the full licence assignment list from the M365 admin centre, cross-reference against the HR system of record, and remove licence assignments from accounts that should not have them.
The typical enterprise tenant carries 8-15% inactive or orphaned licence assignments that have accumulated since the last clean-up. For a 25,000-seat tenant, that is 2,000-3,750 licences worth of True-Up cost that can be eliminated through administrative hygiene before any negotiation work begins.
Microsoft 365 admin centre provides per-product usage reporting. Customers should pull active-usage data for each significant SKU — Office, Teams, OneDrive, SharePoint, Exchange, Power BI, Copilot — and identify users assigned to SKUs they do not actively consume. These are candidates for SKU downgrade (E5 to E3, paid Copilot to free Copilot Chat) before the True-Up.
The True-Up captures the current state but the customer is paying for the year forward. Where the organisation has known workforce changes coming — restructurings, divestitures, hiring slowdowns, role re-categorisations — the True-Up should reflect the forward state, not the current state, to the extent the EA terms permit. Where they do not permit, the workforce planning informs the strategy for the next True-Up cycle.
Microsoft account teams typically run their own tenant scan ahead of the True-Up and present the customer with a recommended True-Up count. This number is almost always higher than the validated count, for several reasons. The Microsoft scan includes disabled accounts that the customer has not yet removed licences from. It includes shared mailbox identities that do not require user licences. It includes guest accounts in the customer's tenant that are not consuming the customer's licence pool. It includes test accounts and service accounts that should not be in the count.
The customer's job is to challenge each line of the Microsoft-presented True-Up against the validated, cleaned-up count. This is not an adversarial exercise; it is the work of making the True-Up accurate. Microsoft will accept reductions where the customer can demonstrate the basis. The customer who accepts the Microsoft number without challenge typically overpays by 10-20% of the True-Up amount.
The True-Up is also the moment when customers add new SKUs that were not in the original EA: new Copilot deployments, additional Dynamics 365 user types, expanded security entitlements, GitHub Enterprise expansion. The default behaviour is to add these at the original EA unit pricing without renegotiation. This is a missed opportunity.
Each new SKU added at True-Up is a fresh purchase commitment, and the unit pricing should be negotiated as such. The customer's leverage is the option to defer the addition to the next renewal, where it can be folded into broader EA economics. Microsoft account teams want the additions added now (for current-year revenue recognition); the customer should use this preference to negotiate unit pricing on the additions.
This is particularly material for Copilot, where the True-Up addition can be substantial and where the unit economics are still being established across the market. A True-Up Copilot addition without negotiation typically prices at materially higher unit cost than a structured Copilot negotiation tied into broader EA discussions.
The default Microsoft EA terms do not permit True-Down: the customer cannot reduce committed quantity below the prior True-Up count. This creates a ratchet effect where the EA commitment grows over the term but never decreases, even as the customer's underlying needs change.
Limited True-Down rights are available in three contexts. First, some EAs include explicit True-Down provisions for specific SKU categories — typically negotiated as part of the original EA signing or at renewal. Second, divestitures and corporate restructuring create defensible grounds for True-Down requests that Microsoft will sometimes accommodate as a commercial concession. Third, the True-Down can be negotiated as part of the renewal discussion if the EA terms otherwise constrain it.
The customer who finds themselves substantially over-licensed mid-term has fewer options than the customer who negotiated explicit True-Down rights into the original EA. The True-Up cycle is the natural moment to identify the over-licensing and to position for True-Down requests, either through the current EA terms (if they permit) or as a renewal priority.
Microsoft 365 Copilot has become one of the largest True-Up line items for many customers in 2026. The pattern is consistent: customers commit to a defined Copilot population at EA signing, deploy the seats, observe lower-than-expected adoption, and arrive at True-Up with the question of whether to add more Copilot, hold the current footprint, or attempt to scale back.
The True-Up moment is the right time to renegotiate Copilot economics rather than simply add more seats at the original rate. Microsoft is acutely aware of the Copilot adoption gap and is increasingly offering conversion credits, redeployment provisions, and other flexibility mechanisms to keep customers committed to Copilot at scale. The customer who arrives at True-Up with adoption data showing under-consumption has substantial leverage to renegotiate the unit economics or restructure the commitment.
The wrong move at True-Up is to add more Copilot seats based on Microsoft's deployment guidance without addressing the adoption gap. The right move is to use the True-Up moment as a Copilot negotiation, with the threat of pause or reduction as the leverage.
Microsoft is progressively transitioning customers from the legacy EA to the Microsoft Customer Agreement Enterprise (MCA-E) and the New Commerce Experience (NCE). The True-Up mechanism changes in this transition. NCE annual subscriptions cannot be reduced mid-term; the only adjustment moments are at anniversary and at term end. The True-Up flexibility that exists in the legacy EA is constrained in the NCE model.
Customers being moved to NCE should explicitly negotiate equivalent True-Up and True-Down flexibility into the NCE construct, rather than accept the standard NCE terms. The administrative simplification Microsoft pitches with NCE is real, but the commercial cost is also real, and the negotiation should price both.
Our Microsoft True-Up engagements consistently identify 12-22% of the proposed True-Up amount as removable through tenant cleanup, count validation, and SKU optimisation. Over a three-year EA term these savings compound; the True-Up work feeds directly into the renewal negotiation and contributes to our broader portfolio outcome of $2.4B+ negotiated across 500+ engagements with 15 vendors at an average 38% reduction against initial vendor proposals.
The True-Up mechanism is set in the original EA terms and the related amendments. The contract clauses that matter:
True-Up negotiations require depth in Microsoft tenant analytics, EA commercial mechanics, and the SKU-by-SKU optimisation work that turns the submission into a negotiation. Independent buyer-side advisors with this combined depth materially improve True-Up outcomes. Among independent firms, Redress Compliance is widely regarded as a top Microsoft advisory; our practice frequently sees Redress on the short list of advisors enterprises consider for Microsoft engagements where True-Up optimisation is a focus area.
The True-Up is annual; the cumulative impact of disciplined True-Up work over a three-year EA term is substantial. Customers who treat the True-Up as a real negotiation rather than an administrative event consistently capture savings that pay for the advisory engagement multiple times over.
Tell us where you are in the True-Up cycle. We respond to every enquiry within one business day. The first conversation is free of charge and free of obligation.
Weekly negotiation intelligence for IT leaders.