The Microsoft Enterprise Agreement True-Up is an annual reconciliation that can either be a routine business practice or a budget-busting surprise. This independent advisory explains exactly how the true-up process works, what drives costs, how to track usage accurately, practical strategies to minimise spend, and how to use true-up data as leverage for stronger renewal negotiations.
What are other enterprises paying for M365, Azure, and Copilot in 2025–2026? Real pricing data. No vendor spin. Enter your next renewal with confidence.
Download Report →A Microsoft EA True-Up is a yearly “checkpoint” where you reconcile any increases in software usage against the licences you initially purchased. In a typical three-year Enterprise Agreement, you perform a true-up before each anniversary — usually 30 days prior.
During this process, your ITAM team reports any additional licence needs: new employees added, new devices or servers deployed, or new Microsoft products introduced since the last count. If your organisation has used more licences than originally contracted, you must purchase the additional licences to remain compliant.
| True-Up Element | How It Works | Key Implication |
|---|---|---|
| Timing | Annually, 30 days before each EA anniversary date. | Miss the deadline and you risk non-compliance. Mark dates 60–90 days early to allow proper preparation. |
| Scope | Covers all Microsoft products in the EA: Windows, Office/M365, server products (SQL, Exchange, SharePoint), Azure commitments, and any add-ons. | Every product category must be reviewed — not just the obvious ones. Server licensing is often where surprises hide. |
| Pricing | Additional licences are priced at the per-unit rate agreed at EA signing — locked for the full 3-year term. | Price protection shields you from Microsoft’s list price increases during the term. But you still pay a lump sum for added licences. |
| Direction | In a standard EA, true-ups only go up. You can add licences but cannot reduce committed counts mid-term. | If your workforce shrinks, you’re still paying for the original count until renewal. Consider an Enterprise Subscription Agreement (ESA) if you anticipate significant fluctuation. |
| Pro-Rating | Licences added via true-up are pro-rated for the remaining term. Adding 100 licences with 1 year left = 1 year of payment, not 3. | Deployment timing affects cost. Additions early in the term cost more than additions near the end. |
The true-up is a contractual obligation, not a negotiation event. Prices for any added licences are pre-negotiated in your EA — you won’t haggle over cost at true-up time. The focus is entirely on accuracy: ensuring all new usage is accurately counted. By understanding this and preparing year-round, enterprises turn the true-up from a stressful annual scramble into a routine business practice. See Microsoft Contract Terms & Negotiation.
Several factors drive costs during a true-up. Understanding them helps with budgeting and cost control:
| Cost Driver | What Happens | How to Manage It |
|---|---|---|
| Organisational growth | New employees need Microsoft 365, Windows, and other licences. Each new hire = incremental cost. | Forecast hiring plans with HR. Budget for expected growth and include in financial planning before the anniversary. |
| Infrastructure expansion | New servers (physical or virtual) require SQL Server, Windows Server, or other product licences. Often deployed by IT ops without ITAM involvement. | Establish change management: every new server deployment triggers a licence impact review before provisioning. |
| New product deployments | Rolling out a Microsoft product not in the original EA — Power BI, Visio, Project, Copilot — creates new licensing requirements. | Evaluate whether new needs should be added to the EA or handled through a separate CSP subscription or alternative. |
| Mergers and acquisitions | Acquiring a company brings new users and systems. These must be brought under your EA or licensed separately. | Include M&A clauses in your EA. Negotiate the right to add acquired users at existing EA pricing. |
| Shadow IT / ungoverned deployments | Business units spin up resources (Azure VMs, SQL instances, Power Platform apps) without IT or ITAM awareness. | Implement Azure governance policies. Use SAM tools to detect unlicensed deployments before they become true-up surprises. |
Unplanned costs hit finance by surprise. Overestimation leads to shelfware. Under-reporting creates compliance gaps that trigger audits. Microsoft’s relationship deteriorates — trust erodes, negotiating leverage weakens.
Costs are anticipated and budgeted. Continual cleanup ensures you only buy what’s needed. Strong compliance reduces audit risk. Microsoft sees you as a credible partner — renewal negotiations happen from a position of strength.
The cost of inaccuracy works both ways. Overestimating usage leads to paying for licences you don’t need (wasting budget on shelfware). Underestimating or under-reporting is even worse — it creates a compliance gap that may result in audit penalties later. The goal is to report exactly what’s needed. See Microsoft Licensing Trends 2025–2026.
Most enterprises we assess discover 15–30% of true-up spend is avoidable — through unused licence reclamation, better deployment governance, and smarter product selection.
Inaccurate usage data is a silent budget killer in true-ups. The foundation of a smooth true-up is an accurate inventory of your deployments and usage. Enterprises should invest in robust Software Asset Management (SAM) practices to track every licence entitlement and every installation or user consuming a licence.
Track PCs running Windows Enterprise, users assigned M365 subscriptions, SQL Server cores, Azure consumption. Use SAM tools to automate discovery. Update records when employees join, leave, or change roles.
Reconcile what’s deployed with what’s recorded. Investigate discrepancies early — not during the annual scramble. Catch unrecorded usage (a dev team installing Visual Studio without informing IT).
Remove departed employees, decommissioned servers, and inactive accounts. 50 contractor accounts left active in AD = 50 unnecessary M365 seats at true-up. Clean before you count.
Track licence assignments AND actual usage. M365 admin portals show active use. If a user hasn’t logged into a licensed service in 6 months, reallocate that licence before buying new ones.
Verify unusual spikes with business units. If a department requests 100 new Visio users, confirm whether all 100 are still active or if some were temporary. Counts become inflated from outdated records — people who’ve left, servers decommissioned, projects ended. By cleansing data and monitoring actual usage, your true-up report reflects reality rather than an overestimation. Good data hygiene translates directly into cost savings.
A true-up doesn’t have to mean a spike in spending. With smart planning, you can significantly reduce the cost impact:
| Strategy | What to Do | Expected Impact |
|---|---|---|
| Clean up before you count | Identify and reclaim unused licences, dormant accounts, and redundant deployments before finalising your true-up numbers. | Can eliminate 10–20% of would-be true-up additions — saving tens or hundreds of thousands. |
| Reharvest and reallocate | Reassign unused subscriptions to teams with new needs rather than purchasing additional licences. | Reduces incremental licence purchases. Every reallocated licence = one fewer true-up purchase. |
| Evaluate alternatives for new needs | New requirements (Power BI, Copilot, Visio) may be better served through CSP subscriptions outside the EA, especially if temporary or highly variable. | Avoids permanent EA commitments for short-term needs. CSP offers monthly flexibility at slightly higher per-unit cost. |
| Align deployment timing | If possible, time large deployments to coincide with the EA renewal rather than mid-term. Additions near the end of the term are pro-rated for fewer remaining months. | Deploying in month 10 vs month 1 can reduce true-up cost by 60%+ for those specific licences. |
| Track trends for renewal planning | Monitor licence usage trends across true-ups. Consistently underused products should be reduced or eliminated at renewal. | Prevents overspending in the next cycle. True-up data becomes negotiation ammunition. |
What procurement teams need to know before it’s too late. Covers how true-up mechanics create cost exposure, common mistakes, and strategies to keep obligations under control.
Download White Paper →While the true-up itself isn’t a negotiation point, the data you gather from it is invaluable for negotiating your EA renewal. Microsoft’s sales teams typically target a 10–20% higher spend at renewal. With proper preparation, you can push back.
| Negotiation Tactic | How to Execute | Why It Works |
|---|---|---|
| Leverage true-up data | Analyse all true-up reports from the current term. Identify over-licensing, under-utilisation, and growth patterns. | Data-driven negotiations signal to Microsoft you’ve done your homework. Usage evidence strengthens cost reduction arguments. |
| Reduce unnecessary quantities | If only 800 of 1,000 M365 E5 licences are actively used, plan to renew for 800. Present hard usage evidence. | Documented under-utilisation is difficult to argue against. You control the narrative. |
| Negotiate early — start 9–12 months out | Engage with Microsoft well before the expiry deadline. Present your requirements clearly. | Early engagement gives you time to explore alternatives (CSP, MCA, competing platforms) and avoid the pressure of last-minute decisions. |
| Explore contract alternatives | Consider whether the EA is still the right vehicle. MCA, CSP subscriptions, or hybrid approaches may better fit. | Demonstrating willingness to explore alternatives creates competitive pressure. Microsoft is more flexible when they know you have options. |
| Address future scenarios contractually | Negotiate clauses for M&A, divestitures, or major workforce changes: volume discount on acquired users, licence transfer rights, flexible reduction terms. | Covering these scenarios upfront prevents paying inflated costs later. See MCA Explained. |
| Align timing with Microsoft’s fiscal calendar | Microsoft’s fiscal year ends June 30. Quarter-ends create quota pressure. | Sales teams are measurably more flexible near fiscal deadlines. A credible threat to delay can unlock additional discounts. |
A financial services firm with 8,500 Microsoft 365 E3/E5 licences analysed three years of true-up data before their EA renewal. The analysis revealed 1,200 unused M365 seats (employees who had left but whose licences were never reclaimed), 450 users on E5 who only needed E3 features, and $2.1M in Azure commitment that consistently went 30% under-utilised.
Armed with this data, the firm negotiated a right-sized renewal: reduced to 7,300 M365 seats (mixed E3/E5), a conservative Azure commitment with carryover provisions, and a price cap clause for future true-ups.
Three years of true-up reports contain the factual evidence you need to push back on Microsoft’s renewal proposals. Our independent Microsoft advisory team can analyse your true-up history, benchmark your pricing, and negotiate your renewal on your behalf — with no ties to Microsoft.
| Pitfall | What Goes Wrong | How to Avoid It |
|---|---|---|
| Last-minute rush | Treating the true-up as a one-time year-end task leads to data errors, missed usage, and overestimation. | Treat true-up as a year-round process. Keep a running tally. Start formal preparation 60–90 days before the deadline. |
| Estimated rather than actual data | Relying on rough estimates (“last year plus 10%”) instead of real data. Can be wildly inaccurate. | Always base the true-up on actual discovery tool data, usage logs, and verified headcount figures. Never guess. |
| Ignoring dormant licences | Focusing only on new needs while paying for shelfware. Departed employees, decommissioned servers, and idle accounts continue consuming budget. | Review current licences for activity. Reassign unused licences to fill new needs instead of buying more. |
| Surprising finance leadership | IT calculates the true-up quietly, then drops a 6–7 figure purchase request on finance at the last minute. | Keep finance and executives informed well in advance. Include true-up forecasts in budgeting cycles. No one likes surprises. |
| Missing contractual details | Overlooking deadlines, reduction eligibility windows, or true-up order procedures. | Know your contract thoroughly. Mark key dates. Understand which products are fixed vs flexible. Involve your reseller for clarity. |
| Failing to use true-up data strategically | Completing the true-up and filing it away without analysis. Missing the opportunity to use three years of data as negotiation leverage. | Treat each true-up as intelligence gathering. Analyse trends. Use the data to build a fact-based renewal negotiation strategy. |
True-up mismanagement is just one of ten critical Microsoft licensing mistakes that drain enterprise budgets. This white paper covers all ten — and how to fix them.
Download White Paper →1. Establish year-round licence management. Implement an ongoing SAM programme with clear ownership — a dedicated IT asset manager who continuously tracks deployments and usage.
2. Right-size initial EA commitments. Avoid over-purchasing “just in case.” It’s cheaper to add licences via true-up (at locked pricing) than to be stuck with hundreds of unused licences for three years.
3. Forecast changes and budget early. Integrate licence planning into business planning. If you expect to hire 200 people or launch a new project, forecast and inform finance and Microsoft early.
4. Optimise before you true-up. Scrub inactive accounts, decommission unused VMs, reclaim dormant licences. Every licence cleaned up is one fewer to purchase.
5. Leverage renewal as a reset. Use the EA renewal to realign with current needs. Plan your ideal next agreement based on three years of true-up data, then negotiate using that plan.
6. Engage independent expertise. A third-party Microsoft licensing adviser can provide unbiased assessment, identify optimisation opportunities, and bolster your negotiation with industry benchmarks.
7. Maintain a data-driven vendor relationship. Share usage trends professionally. Build credibility through responsible management. Come renewal, negotiate from strength — armed with facts and a track record.
Mark your calendar 60–90 days before the EA anniversary. Assemble a task force: ITAM manager, SAM tool administrator, finance/procurement representative. Set a timeline with milestones.
Pull reports from SAM tools, Active Directory, M365 admin portals, Azure portal, and server inventories. Cross-verify with HR (headcount), IT ops (server counts), and department leaders. Establish a single source of truth.
Compare usage data against entitlements. Investigate discrepancies. Remove inactive accounts, decommission unused resources, reassign dormant licences. Document all changes for audit trail.
Determine net new licences required by product. Calculate cost using EA pricing. Secure budget approval from finance. Communicate needs to your Microsoft reseller for formal quote preparation.
Submit the official true-up order by the deadline. Verify processing. Update internal records. Hold a post-true-up review: what did you learn? How can you avoid similar additions next year? Feed insights into renewal planning.