The Microsoft EA True-Up: A Complete Guide for Enterprise Buyers

What Is the Microsoft EA True-Up?

When an organisation signs a Microsoft Enterprise Agreement, it commits to a baseline quantity of licences at the start of the term. That baseline reflects the expected number of users, devices, and workloads at the point of signing. Over the subsequent 12 months, the organisation grows — onboards new staff, deploys additional software, spins up new Azure workloads, activates add-on services. The True-Up is the annual mechanism for reconciling that growth against the original baseline and paying for the difference.

In practical terms, a True-Up is an order that you submit to Microsoft — typically through your reseller or directly — which reports any increase in qualified usage since the last anniversary date. Microsoft invoices the additional licences at the unit price negotiated in your EA, back-calculated for the period during which the additional usage occurred. In a standard three-year Enterprise Agreement, there are three True-Up events: one at each anniversary of the enrolment date.

This sounds straightforward. In practice, the True-Up process is one of the most commonly mismanaged elements of a Microsoft enterprise relationship. Organisations routinely overpay by reporting more than they actually consumed, miss legitimate cost-reduction opportunities through poor inventory management, and fail to prepare in time to use the submission process as a strategic tool. Understanding the mechanics in depth is the first step toward a more effective outcome.

The True-Up Timeline: When to Start and What to Do

Microsoft recommends that organisations begin their True-Up preparation at least 120 days — approximately four months — before the enrolment anniversary date. This recommendation is grounded in the reality of what a proper True-Up preparation requires: a full software asset inventory, cross-referencing of active users and devices against licence entitlements, cloud consumption analysis, and internal sign-off from IT, finance, and procurement. None of these steps can be rushed without risk.

The formal submission deadline is between 60 and 30 days prior to the anniversary date. For the third and final True-Up — which falls within 30 days of the agreement's expiration date — Microsoft will not accept licence reservations, so timing is particularly critical. Missing the window does not eliminate the obligation; it simply means the reconciliation is completed without the additional lead time that makes it manageable.

The Four-Phase True-Up Calendar

A well-managed True-Up follows a consistent four-phase structure across the year. The first phase — which should begin approximately 120 days out — is the internal inventory and audit phase. This involves pulling actual deployment data from Microsoft 365 Admin Center, Active Directory, Azure Cost Management, and any third-party software asset management tools your organisation uses. The goal is an accurate count of every qualified user, device, and workload currently running under the EA.

The second phase, running from 90 to 60 days out, is analysis and optimisation. This is where you compare your actual deployment data against your baseline entitlement, identify any products where you are over-licensed relative to active usage, and make decisions about whether to true-up precisely to actual usage or to carry forward a modest buffer. This phase is also where you should identify any products that were added mid-year that need to be reflected in the order.

The third phase — 60 to 30 days out — is the submission phase. You prepare the True-Up order or Update Statement, have it reviewed internally, and submit it through your reseller channel. If your EA has complex components such as Azure MACC commitments, Dynamics 365 attach licensing, or specialised server products, this is the phase that requires the most careful technical review.

The fourth phase is post-submission management. Once the invoice is issued, verify that the charges align with what you submitted. Discrepancies between submitted quantities and invoiced amounts are not uncommon and should be resolved before payment. Use the outcome of this True-Up to begin updating your baseline model for the next 12-month period.

What Products Are Covered by the True-Up?

The True-Up covers all products and services that are part of your EA enrolment and that have had usage increases since the last anniversary. This scope is broader than many organisations realise, and it is one of the most common sources of unexpected costs in the reconciliation.

Microsoft 365 and Office 365 Seat Additions

Any new Microsoft 365 or Office 365 user subscriptions added during the year must be true-upped. This includes SKU tier upgrades — if you moved users from E3 to E5, or are planning the move from E5 to E7 at this True-Up, the per-user price difference is calculated and invoiced for the period during which the upgraded entitlement was in use. It also includes entirely new users onboarded since the last anniversary, even if those users were given licences via an interim purchase order rather than through the formal EA process.

One common complication is the treatment of E5 Security and E5 Compliance add-ons. Organisations that have purchased these as supplements to an E3 or E5 base SKU must track them separately. The True-Up for a user who moved from E3 with no security add-on to E3 with E5 Security requires the additional add-on cost to be reported for the applicable period, not the full-year E5 price.

As the Microsoft 365 E7 SKU enters commercial deployment in 2026, organisations renewing their EA this year will face a new decision at True-Up: whether E7 makes sense as the baseline for new users, or whether a segmented model — E7 for power users, E5 for professional staff, E3 for general knowledge workers, and F1 or F3 for frontline workers — is the more cost-effective architecture. This decision should be made before the True-Up, not during it.

Server Products and Infrastructure Licences

Enterprise products such as Windows Server, SQL Server, System Center, and similar infrastructure software must be included if usage has increased. The key inventory requirement here is tracking new server deployments, additional processor cores (for products licensed per core), and new Operating System Environments (OSEs). Organisations that have undertaken cloud migration projects during the year may find that the on-premises component of these products has decreased even as Azure consumption has increased. Ensuring that the True-Up reflects the actual position — not a conservative overestimate — is particularly important for these high-unit-cost items.

Azure and Cloud Services

Azure consumption above an organisation's Azure MACC (Microsoft Azure Consumption Commitment) baseline may need to be reflected in the True-Up, depending on how the commitment is structured. For organisations without a formal MACC, Azure consumption is typically billed on a consumption basis outside the EA True-Up process. However, certain Azure services purchased as part of an EA product bundle — Azure Active Directory Premium, Azure Information Protection, and similar — are subject to True-Up if the number of covered users has increased.

Microsoft 365 Copilot, now available at $30 per user per month as an add-on to E3 and E5 (or included in E7), is a growing component of True-Up orders for organisations that deployed Copilot mid-year without purchasing the full annual quantity at the start of the term. As AI deployments scale in 2026, expect this line item to represent an increasing share of annual True-Up spend for organisations that chose to deploy cautiously before committing at EA baseline.

Dynamics 365 and Power Platform

Dynamics 365 licences operate under attach licensing rules that link certain application licences to qualifying M365 base SKUs. Any increase in Dynamics 365 user counts — or any addition of new application modules — must be reported. The Power Platform (Power Apps, Power Automate, Power BI) follows similar rules, with capacity-based models for some components requiring careful tracking of consumption against committed thresholds.

True-Up vs True-Down: Understanding Licence Reduction Rights

One of the most persistent misconceptions about the Microsoft EA True-Up is that it offers symmetrical flexibility — that if your usage decreased during the year, you can report the reduction and receive a credit. This is not how the standard EA True-Up works, and failing to understand the asymmetry has significant cost implications for organisations that have over-licensed or experienced headcount reductions.

Under a standard EA, the True-Up mechanism reports and pays for increases only. If you have 1,000 E5 users in your baseline and only 900 are actively using E5 features, you continue to pay for 1,000 at each anniversary. The 100 unused licences cannot be removed until the EA renewal, at which point you can restructure the baseline downward. This is a deliberate feature of the EA from Microsoft's perspective — it provides revenue predictability during the term.

There is an important exception: Additional Online Subscription products such as Visio Online, Project Online, and certain Dynamics 365 modules are classified as "reduction eligible" products in Microsoft's Product Terms. For these products, you may be able to reduce your licence count at the anniversary date, sometimes down to zero. The specific rules vary by product and by agreement vintage, so confirming which of your subscriptions are reduction eligible is a valuable part of the True-Up preparation process.

Enterprise Agreement Subscriptions (EAS) — a variant of the EA — do provide mid-term reduction rights for most products at each anniversary. If your organisation has experienced significant structural change (a major divestiture, a large headcount reduction) and you are on a standard EA rather than EAS, the inability to reduce mid-term can represent a material trapped cost. This distinction is worth understanding when structuring the next EA term at renewal, and negotiating mid-term reduction rights for specific products is a leverage point that experienced buyers pursue.

The Five Most Costly True-Up Mistakes

After supporting True-Up processes for hundreds of organisations across EMEA and North America, we consistently observe the same five mistakes. Each of them is avoidable with the right preparation, and each of them has a direct cost consequence.

1. Reporting Allocated Licences Rather Than Active Users

The most financially damaging mistake is counting all allocated licences — including those assigned to dormant accounts, departing employees who have not been offboarded, or users who have been moved to a different product — rather than actual active users. This systematic overcount compounds annually. At scale, even a five percent overreport on a 10,000-seat estate represents thousands of wasted pounds per user per year. A rigorous offboarding process and a quarterly licence reclamation review are the preventive controls; identifying the overcount before submission is the corrective one.

2. Ignoring Cloud Service Growth

Many organisations manage on-premises True-Up meticulously but pay insufficient attention to cloud service additions. New Teams Phone add-ons deployed during a collaboration transformation project, Copilot seats rolled out to a pilot group and then extended, additional Power BI Premium capacity provisioned by a business unit — these all accumulate across the year and can produce a significantly larger True-Up order than the IT licensing team anticipated. Quarterly cloud licence reviews are the preventive mechanism; a cloud consumption dashboard maintained throughout the year is the operational tool.

3. Under-Reporting Due to Fear of Audit

Some organisations deliberately under-report in the True-Up, rationalising that they will deal with compliance exposure if it arises. This strategy has two failure modes. The first is an EA audit — increasingly common — in which Microsoft identifies the gap and invoices the back-dated licences at full list price without the EA discount, potentially with a surcharge. The second is that the inaccurate True-Up data corrupts the usage picture that should be informing your renewal negotiation. A clean, accurate True-Up history is a commercial asset; a manipulated one is a liability.

4. Treating the True-Up as a One-Time Annual Event

Organisations that only look at their Microsoft licence position once a year — in the 60 days before the True-Up deadline — inevitably find themselves reconciling 12 months of accumulated change under time pressure. The structural fix is to move to quarterly licence reviews, where IT and procurement meet to review active user counts, cloud consumption trends, and any mid-year purchases that will need to appear in the next True-Up. This transforms the True-Up from a scramble into a confirmation of a position that is already well understood.

5. Missing the Submission Deadline

Late True-Up submissions are a recurring problem. If the submission is delayed past the anniversary date, the reconciliation must still occur — but the leverage of timing it as a deliberate, prepared document is lost. For the third-year True-Up, which immediately precedes the EA renewal, a late or rushed submission sends exactly the wrong signal to Microsoft's account team: that your organisation has poor internal governance around licence management. In contrast, a clean, accurate third-year True-Up submitted on time demonstrates commercial discipline and positions you to enter renewal discussions from a position of strength.

Using True-Up Data as Renewal Leverage

The strategic dimension of the True-Up that most organisations miss is this: three years of True-Up data constitute the most granular and authoritative record of your Microsoft consumption trajectory that exists. It shows which products grew, which were under-deployed, where you over-licensed, where you under-licensed, and how the composition of your Microsoft estate has evolved. Microsoft's account team has access to this data too — and uses it to project your renewal spend. Your goal is to use the same data to challenge those projections.

Challenging Microsoft's Growth Assumptions

Microsoft's field teams arrive at EA renewal negotiations with an internal model of your expected spend, typically projecting 10 to 20 percent growth above the expiring agreement. That model is built from your True-Up history. If your True-Up data shows that you added fewer licences per year than Microsoft's model assumes — for example, because you completed a headcount rationalisation, changed your frontline worker model, or optimised your SKU mix — you have factual grounds to challenge the growth assumption and negotiate a baseline that reflects actual consumption rather than inflated projections.

This requires that your True-Up data is clean, accurate, and internally consistent across all three years. Organisations that have treated the True-Up process carelessly — overreporting, missing deadlines, failing to decommission unused licences — will find that their own historical data works against them in the renewal negotiation.

Justifying Quantity Reductions

Suppose your third-year True-Up showed that you added only 150 M365 E5 licences across the year against a baseline of 3,000, and that 400 users in your E5 baseline were never using E5-specific features. The True-Up data, combined with a Microsoft 365 usage report from the Admin Center, provides the evidence base for entering renewal negotiations with a proposed reduction in your E5 baseline, potentially offsetting the cost of an E7 upgrade for the users who genuinely need it. Without the data, this conversation is assertion-based. With the data, it is factual and defensible.

Negotiating Better Terms for Growing Products

True-Up data that shows consistent, large-scale growth in a specific product is also a lever to negotiate better pricing for that product at renewal. If you have been adding 200 Microsoft 365 Copilot seats per quarter — meaning your Copilot deployment will substantially exceed your renewal baseline — you can use that demonstrated demand trajectory to negotiate a volume discount or price protection on the Copilot add-on that does not exist in the standard price list. Microsoft's field teams are incentivised to secure commitments on growing products; buyers who can demonstrate genuine adoption trajectory have genuine leverage.

Managing the True-Up Across the Three-Year EA Term

The structure of the three True-Ups within a standard EA creates a progression of strategic opportunity that well-prepared buyers should exploit deliberately. Each True-Up builds on the previous one, and the quality of your third-year True-Up directly determines the strength of your position at the renewal negotiation that immediately follows it.

Year One: Establishing the Clean Baseline

The first True-Up is the most important for establishing commercial discipline. The baseline you entered the EA with may have already reflected a degree of over-licensing — an EA signed during headcount growth projections that did not materialise, or a platform consolidation plan that has run behind schedule. Year one is the opportunity to establish a clean, accurate count of actual deployment, and to begin the licence reclamation work that will reduce the burden of the second and third True-Ups.

Year one is also the time to establish the internal governance infrastructure that makes subsequent True-Ups manageable: the quarterly licence review cadence, the cloud consumption dashboard, the integration between IT asset management and the HR onboarding/offboarding process. Organisations that put this governance in place in year one approach years two and three with dramatically lower True-Up administration burden and dramatically higher data quality.

Year Two: Optimisation and Mid-Course Correction

By the second True-Up, you have 12 months of data on how your actual deployment compares to your original projections. Year two is the opportunity for mid-course correction — identifying products that have grown faster than anticipated and for which you should plan to adjust the year-three baseline, and products where adoption has been slower than projected and where you can challenge the renewal quantity at the upcoming negotiation.

Year two is also when Microsoft's account team typically begins renewal conversations. Your year-two True-Up data is the first tangible evidence of your consumption trajectory. Submit it accurately and on time, and be aware that Microsoft will be updating its renewal model based on what you report. This means that year two is a particularly poor time to over-report: inflating your year-two True-Up gives Microsoft a higher baseline from which to project your renewal spend.

Year Three: Setting Up the Renewal Position

The third True-Up is both a compliance obligation and a strategic document. It is the last data point Microsoft has before renewal negotiations conclude, and it signals your governance maturity, your consumption discipline, and your commercial intent. A well-prepared third-year True-Up that reflects accurate usage, reclaimed unused licences, and precisely right-sized quantities tells Microsoft's account team that you are an informed buyer who will not simply accept the renewal proposal. A rushed, overreported third-year True-Up tells exactly the opposite story.

Prepare your third-year True-Up in conjunction with your renewal preparation. The bill of materials you are building for the next EA term should be informed by what your third True-Up is showing you about actual consumption. Where year-three consumption is below your current baseline, use that data to propose a reduced baseline at renewal. Where year-three consumption is approaching or exceeding your baseline, use that trajectory to negotiate more favourable pricing for the additional volume you will be committing to.

True-Up Under the New Post-November 2025 Pricing Landscape

The elimination of volume discount tiers (Levels A through D) for online services in November 2025 has changed the financial context for True-Up management. Under the old structure, organisations in higher volume tiers received progressively better unit prices as their licence counts grew. A True-Up that pushed them above a threshold could, counterintuitively, reduce their per-unit cost by moving them to a better discount tier.

That dynamic no longer applies for online services. All organisations now negotiate from a Level A baseline, meaning the per-unit discount is determined by the initial negotiation and does not automatically improve as volumes grow. This makes the discipline of negotiating the right unit price at renewal — and locking it in for the full term — more important than ever. Mid-term additions via True-Up are priced at the EA unit rate regardless of total volume, so the renewal rate is the rate you live with across all True-Ups during the next term.

It also places greater emphasis on the quality of your initial quantity commitment at renewal. Over-committing in year one to get a perceived price advantage — only to have significant shelfware through years one and two — is less defensible when volume discount tiers no longer exist. Right-sizing the baseline at renewal, backed by three years of accurate True-Up data, is the more sustainable approach.

Building the Infrastructure for Effective True-Up Management

Effective True-Up management is not a project — it is a capability. Organisations that achieve consistently better True-Up outcomes have built specific processes and tools into their ongoing IT and procurement operations. These include a software asset management (SAM) platform that maintains a continuously updated inventory of Microsoft licence entitlements and deployments, integration between the HR system and the licence management process so that departing users are offboarded within a defined SLA, quarterly review meetings between IT, procurement, and finance to review consumption trends and flag emerging True-Up implications, and a documented escalation process for high-value or complex True-Up decisions that require executive input.

For organisations that do not have these capabilities in-house, or that are approaching a complex True-Up with limited preparation time, an independent adviser who has managed the True-Up process across many Microsoft EA customers can add significant value — not only in ensuring accuracy and compliance, but in identifying the cost reduction opportunities that organisations managing the process for the first time typically miss.