Microsoft EA True-Up Negotiation: Strategies, Traps, and Cost Reduction Tactics

How the Microsoft EA True-Up Works

The Enterprise Agreement True-Up is the annual reconciliation mechanism built into every standard Microsoft EA. When you sign a three-year EA, you commit to an initial quantity of licences across the products in your agreement. The True-Up — conducted annually, 30 days before each EA anniversary date — requires you to report any increases in your qualifying user and device counts since the initial commitment.

The process itself is straightforward: your organisation counts the number of qualifying users and devices for each licensed product, compares that count to your original commitment quantities, and reports the delta (the additional units) to Microsoft. Microsoft then invoices you for those additional units at your pre-agreed EA pricing. At the end of the three-year term, the final True-Up count becomes the baseline for the renewal negotiation.

Three points about this mechanism are frequently misunderstood. First, the True-Up is one-directional — you can only report increases. If your user count has fallen (through redundancies, divestitures, or voluntary attrition), the EA does not automatically reduce your licence obligation. The right-sizing opportunity comes at renewal. Second, True-Up units should be priced at your negotiated EA rate, not at list. If your EA includes a 15% discount on M365 E3, your True-Up E3 units should cost 15% below list — but this is not always automatically applied unless you push for it. Third, the True-Up data you generate across the three-year EA term is the most powerful input into your renewal negotiation — far more valuable than any benchmark data Microsoft's field team will present to you.

The 10 Most Costly True-Up Mistakes

Mistake 1: Reporting Provisioned Accounts Instead of Active Users

The most expensive recurring True-Up error. Many organisations count Microsoft 365 licences by querying the number of user accounts in Azure Active Directory — including disabled accounts, service accounts, shared mailboxes, and leavers who have not been de-provisioned. The EA licensing obligation applies to qualified users and devices in active use, not to provisioned accounts. Over-reporting by 5–10% of total user count is common; at 10,000 users and E3 pricing, that over-reporting costs approximately £200,000–£400,000 over a three-year EA term.

Mistake 2: Failing to Apply the Negotiated Discount to True-Up Units

True-Up units added mid-term should be priced at your contracted EA discount rate. In practice, the pricing for True-Up units is often processed by the reseller or Microsoft at a default rate unless someone explicitly checks. This is worth validating every True-Up cycle — particularly when the additional unit volume is significant.

Mistake 3: Including Dev/Test Environments in Production Count

Development and test environments that run Microsoft software are often excluded from EA True-Up obligations under specific provisions in the Product Terms (particularly for development licences and certain Azure services). Including them in the production user count is an over-statement that creates unnecessary cost.

Mistake 4: Ignoring Shelfware When Building the True-Up Report

The True-Up is the right moment to document which products in your EA are underutilised. E5 security and compliance add-ons — Microsoft Defender for Identity, Microsoft Sentinel, Microsoft Purview advanced features — are frequently over-purchased relative to actual deployment. Documenting this formally during the True-Up creates the evidence base for right-sizing at renewal.

Mistake 5: Not Locking in True-Up Pricing for New SKUs

If your organisation adopts new Microsoft products mid-term — Microsoft 365 Copilot ($30/user/month as a standalone, or included in the new M365 E7), Microsoft Fabric, or Copilot Studio — and those SKUs are not in your original EA commitment schedule, the True-Up will likely price them at list or near-list. The correct approach is to amend the EA to include the new SKU at a negotiated rate before the True-Up, not after.

Mistake 6: Missing the True-Up Submission Deadline

The True-Up submission must be completed 30 days before the EA anniversary date. Missing this window creates a late True-Up scenario that complicates invoicing and can trigger list pricing for the delayed period. Calendar management for the True-Up cycle should be part of your standard Microsoft licence governance process.

Mistake 7: Treating the True-Up in Isolation from the Renewal

The True-Up is not an isolated compliance event — it is part of a continuous three-year data-gathering exercise that culminates in the renewal negotiation. Organisations that document their True-Up data systematically across all three cycles arrive at renewal with a complete, auditable picture of their consumption. Those that treat each True-Up in isolation arrive with nothing. The difference in renewal outcomes is significant: well-prepared buyers consistently achieve 3–8% better renewal pricing than unprepared buyers with comparable spend levels.

Mistake 8: Letting Microsoft Define the E5 to E7 Upgrade Narrative

Microsoft field teams are actively moving E5 customers to M365 E7 — the new top SKU above E5 — at renewal. E7 bundles capabilities previously sold as E5 add-ons, including Microsoft 365 Copilot. The True-Up period, when you are reviewing your current SKU mix, is the right moment to evaluate this transition independently rather than accepting Microsoft's framing. If you are already paying for Copilot at $30/user/month as an add-on on top of E5, the E7 delta often represents better economics — but you should arrive at that conclusion through your own modelling, not Microsoft's sales pitch.

Mistake 9: Not Challenging Azure True-Up Components

EAs that include an Azure Monetary Commitment (AMC) require annual reconciliation of Azure consumption against the committed amount. If your Azure consumption is running below the committed level, you are effectively pre-paying for Azure that you are not consuming. The True-Up is the right moment to assess whether your AMC needs to be adjusted, and whether the uncommitted amount could be redirected to other Microsoft products or used as a negotiating lever.

Mistake 10: Using the Wrong Pricing Year

Microsoft publishes annual price increases — typically 10–15% on M365 products over recent cycles. EA pricing is typically fixed for the three-year term at your contracted rates. If your True-Up is processed using the current-year Microsoft price list rather than your contracted EA price schedule, you may be invoiced at a higher rate than your agreement specifies. Validating the invoice line items against the original EA pricing schedule is a basic but frequently skipped step.

True-Up Negotiation Tactics That Work in 2026

Beyond avoiding the mistakes above, there are specific negotiation moves that enterprise buyers should deploy in the True-Up context.

Negotiate True-Up Rate Protection at EA Signature

The time to negotiate True-Up pricing terms is when you sign the original EA — not when the True-Up bill arrives. Specifically, push for: (1) confirmation that all True-Up units will be priced at your contracted EA discount rate; (2) a growth buffer clause that allows the first N% of user growth to be deferred to the annual True-Up without creating a mid-year billing event; (3) price protection across the three-year term, so that even if Microsoft announces a price increase, your True-Up units are priced at the original committed rate.

Use Q4 True-Up Timing as a Negotiation Window

Microsoft's fiscal year ends June 30. If your True-Up anniversary falls in the April–June Q4 window, you have additional leverage: Microsoft's field team has strong incentives to resolve discussions quickly and cleanly to close the quarter. This applies not just to renewal negotiations but to mid-term True-Up discussions about growth pricing, SKU amendments, and Azure commit adjustments.

Convert True-Up Data into a Renewal Business Case

At your third and final True-Up, you will have three years of consumption data. Before entering the renewal negotiation, build a consumption analysis that shows: which products grew, which were underutilised, where you consumed above commitment (and at what cost), and where you held licences that provided no demonstrable usage. This analysis is the foundation of a right-sizing argument that can reduce your renewal baseline by 5–15% versus Microsoft's proposed status-quo-plus-uplift approach.

How NCE Pricing Affects True-Up Decisions

Microsoft's New Commerce Experience (NCE) has introduced an important variable into True-Up planning. Under NCE, monthly commit carries no discount — you pay list price. Annual commit provides up to 5% discount. Three-year commit offers better discounts but significantly reduced flexibility. The EA remains the most cost-effective vehicle for enterprise-scale M365 licensing — but for products added mid-term that are not yet in your EA commitment schedule, the choice between NCE annual versus adding to the EA has a material cost impact. Always model this before provisioning new Microsoft products outside the EA.