The Microsoft True-Up Negotiation
Annual true-ups are typically treated as administrative exercises — a costly mistake. The true-up is a contractual negotiation event where you have leverage to renegotiate pricing, restructure commitments, and address over-deployment on favourable terms. This paper reframes the true-up as a strategic opportunity.
Executive Summary
For most enterprises, the annual Microsoft true-up is treated as a compliance obligation — a reconciliation exercise where the organisation counts its deployments, reports the numbers, and pays the invoice. This approach surrenders significant commercial value every year.
The true-up is, in contractual terms, a negotiation event. It is the moment when Microsoft learns the actual scale of your deployment, when over-deployment creates both liability and leverage, and when your commitment to the next year's consumption is formalised. Every one of these dynamics creates an opportunity to renegotiate pricing, restructure licence commitments, eliminate waste, and improve your commercial position.
Our analysis across more than 200 enterprise Microsoft true-ups reveals that organisations that approach the true-up strategically — with deployment audits, pricing benchmarks, and a negotiation plan — reduce their true-up cost by 15–40% compared to those that treat it as a passive administrative exercise.
5 Key Findings
The true-up is a contractual negotiation event, not an administrative obligation. Organisations that reframe it as such consistently achieve better commercial outcomes — including retroactive pricing adjustments and commitment restructuring.
Over-deployment is leverage, not just liability. When properly positioned, over-deployment creates a commercial conversation that Microsoft is incentivised to resolve favourably — particularly when the alternative is a licence reduction or platform migration.
Most organisations overpay by 15–40% at true-up because they fail to conduct pre-true-up deployment audits, benchmark pricing against market rates, or challenge the licence counts Microsoft's tools report.
Preparation is 80% of the outcome. Organisations that invest 90 days in pre-true-up preparation — deployment audit, pricing analysis, restructuring options — achieve dramatically better results than those that begin at the true-up deadline.
True-up restructuring can reset your commercial baseline for the remainder of the EA or MCA term, compounding savings over multiple years rather than achieving a single-year cost reduction.
The True-Up as a Negotiation Event: Reframing the Opportunity
Under both the Enterprise Agreement and the Microsoft Customer Agreement, the true-up is the contractual mechanism through which your organisation reconciles actual deployments against committed quantities. It is the point at which any gap between what you committed to and what you actually deployed is formalised, priced, and invoiced.
Most organisations approach this moment passively: they count licences, report the numbers, accept the pricing, and pay. This is the equivalent of walking into a contract renewal and signing the first offer without discussion. It ignores the fundamental commercial dynamics at play.
Why the True-Up Creates Leverage
At the true-up, several dynamics converge to create negotiation leverage that does not exist at other points in the agreement cycle:
Microsoft Wants Revenue Recognition
The true-up generates incremental revenue for Microsoft. Your account team has an incentive to process the true-up smoothly and maximise the reported quantities. This incentive gives you leverage to negotiate the terms under which those quantities are priced.
Over-Deployment Creates a Two-Way Conversation
If you've over-deployed, Microsoft needs you to formalise those licences. But you have alternatives: you can reduce deployment, migrate workloads, or restructure commitments. Each alternative changes the commercial conversation.
Under-Deployment Reveals Waste
If you've under-deployed, you're paying for licences you don't use. The true-up is the moment to reduce commitments, downgrade SKUs, or restructure the mix to eliminate waste — but only if you've done the analysis before the deadline.
Commitment Resets Compound Over Time
Changes negotiated at the true-up affect your baseline for the remainder of the term. A pricing improvement or commitment reduction at Year 1 compounds across Years 2 and 3, making the true-up the highest-ROI negotiation point in the EA cycle.
Key Insight: The true-up is the only point in the EA/MCA cycle where you have both current deployment data and forward commitment leverage simultaneously. Miss this window and you wait another 12 months.
The True-Up Preparation Framework
Effective true-up negotiation requires structured preparation that begins 90 days before the true-up anniversary date. The following four-phase framework covers every workstream needed to convert the true-up from a cost event into a commercial opportunity.
Deployment Discovery & Audit
Conduct a comprehensive deployment audit across all Microsoft products — M365, Azure, Dynamics 365, Power Platform, and any on-premise server licences. Reconcile actual usage against contractual entitlements. Identify over-deployment, under-deployment, and misallocated licences. Do not rely solely on Microsoft's admin centre data — cross-validate with your own tooling.
Pricing Benchmark & Market Analysis
Benchmark your current per-unit pricing against market comparables for your size, industry, and geography. Identify where you're paying above market and quantify the gap. Build a pricing benchmark report that becomes your evidence base during negotiation.
Restructuring Options & Cost Modelling
Model every viable restructuring option: SKU changes (e.g., E5 to E3 for low-utilisation users), commitment reductions, subscription term adjustments, and workload migration scenarios. Each option needs a 3-year cost model showing the financial impact against the status quo.
Negotiation Strategy & Execution
Develop a negotiation strategy document with specific asks, fallback positions, and escalation triggers. Engage the Microsoft account team with your restructuring proposal. Use deployment data, pricing benchmarks, and competitive alternatives as leverage. Execute amendments or true-up terms before the deadline.
Deployment Audit Methodology
The deployment audit is the foundation of the true-up negotiation. Without an accurate, independently verified picture of your actual Microsoft deployment, you cannot negotiate effectively. Microsoft's own admin portals provide usage data, but this data often overstates deployment in ways that favour Microsoft's commercial position.
What to Audit
| Product Area | Key Audit Points | Common Findings |
|---|---|---|
| Microsoft 365 | Active vs. assigned licences, E5/E3/E1 utilisation by feature, shared mailboxes consuming paid licences, inactive accounts | 15–25% of E5 licences underutilise premium features; 5–10% assigned to inactive accounts |
| Azure | Reserved Instance utilisation, orphaned resources, right-sizing opportunities, dev/test vs. production pricing | 20–35% overspend from unoptimised reservations and orphaned resources |
| Dynamics 365 | Named user vs. actual login frequency, module utilisation, Team Member eligibility, dual-use rights | 30–40% of named users qualify for lower-cost Team Member licences |
| Power Platform | Premium connector usage, per-app vs. per-user plans, seeded vs. standalone capacity | Many organisations over-licence Power Apps/Automate when seeded rights cover actual usage |
| On-Premise / Server | SQL Server editions, Windows Server core counts, CAL allocation, SA utilisation | Software Assurance frequently renewed without utilising upgrade or mobility benefits |
Independent Verification
Microsoft's admin centre and licence management portals report assigned licences, not utilised licences. The distinction matters enormously at true-up. A licence assigned to an account that has not logged in for 90 days is waste, not deployment. Your audit should differentiate between assigned, active, and genuinely utilised licences across every product.
We recommend cross-validating Microsoft's data against your own identity management system (Azure AD / Entra ID logs), SCCM or Intune deployment data, and financial records showing which cost centres are actually consuming the services.
Audit Red Flag: If Microsoft's reported deployment count exceeds your HR headcount for a product like M365, something is wrong. Shared mailboxes, service accounts, and retained leaver accounts are common culprits that inflate true-up counts.
Pricing Benchmarks & Leverage Points
Pricing benchmarks are the second critical input to the true-up negotiation. Without market-comparable pricing data, you cannot know whether your current per-unit rates are competitive or whether you have grounds to request adjustments.
Building Your Pricing Benchmark
Effective pricing benchmarks for Microsoft products require three data dimensions: your current contracted pricing (including any historical discounts), Microsoft's current list pricing (which changes frequently), and comparable pricing achieved by organisations of similar size, industry, and geography. The gap between your pricing and the market comparable is your negotiation target.
Pricing varies significantly by enterprise size, geographic region, and Microsoft's strategic priorities for the fiscal quarter. An organisation with 10,000 M365 seats in financial services should not be benchmarking against a 500-seat technology company. The benchmark must be contextually accurate to be effective.
Six Leverage Points at True-Up
Volume Commitment
If your true-up increases your total commitment, this additional volume justifies a pricing discussion. More licences should mean better per-unit pricing — but only if you ask.
Competitive Alternatives
Credible alternatives — Google Workspace, AWS, Slack, Zoom — create competitive pressure. You don't need to intend to switch, but Microsoft needs to believe the evaluation is real.
Licence Mix Restructuring
Offering to consolidate fragmented SKUs or migrate from E3 to E5 gives Microsoft a richer deal to report. Use this as a negotiation chip for improved pricing on the restructured mix.
Multi-Year Commitment Extension
Extending commitment terms in exchange for improved pricing creates a win-win. Microsoft gets revenue predictability; you get unit cost reduction and price certainty.
New Workload Adoption
If you're planning Azure, Dynamics, Copilot, or Security workloads, bundle them into the true-up negotiation. New workload adoption is Microsoft's highest priority and creates disproportionate leverage.
Fiscal Quarter Timing
Microsoft's fiscal year ends June 30. True-ups that coincide with Q4 (April–June) benefit from end-of-year commercial urgency. Even if your true-up falls outside Q4, referencing fiscal timing can accelerate deal desk engagement.
Negotiation Tactics: Converting Liability Into Position
The true-up negotiation requires a different approach from a renewal or new agreement negotiation. You are negotiating within an existing contractual framework, which constrains some tactics but enables others. The following tactics are specifically designed for the true-up context.
Tactic 1: Lead with Data, Not Requests
Present your deployment audit and pricing benchmark data before making any commercial requests. This establishes credibility, demonstrates preparation, and frames the negotiation as evidence-based rather than adversarial. Microsoft account teams respond better to structured data presentations than to positional demands.
Tactic 2: Negotiate the Count Before the Price
Before discussing pricing, negotiate the deployment count itself. Challenge any inflated counts from shared mailboxes, service accounts, or inactive users. A 10% reduction in the count at existing pricing is often more valuable and easier to secure than a 10% discount on an inflated count.
Tactic 3: Present Restructuring as a Microsoft Win
Frame your restructuring proposal in terms that align with Microsoft's incentives. SKU upgrades (E3 → E5), new workload adoption (Copilot, Azure), and commitment extensions all give Microsoft positive metrics to report. Package your cost reduction requests alongside elements that Microsoft's account team can present as wins internally.
Tactic 4: Create Time Pressure Without Confrontation
If your true-up deadline is approaching and terms are unresolved, make it clear that you will submit a minimum true-up (reporting only what you're contractually certain about) and resolve the remainder in a subsequent amendment. This creates urgency without being adversarial and prevents you from overpaying while negotiations continue.
Tactic 5: Escalate Strategically
Regional account managers have limited pricing authority. If your restructuring requires discounts beyond their approval threshold, request escalation to the deal desk early — not as a threat, but as a practical acknowledgement that the commercial scope exceeds the local team's authority. Frame it as efficiency: "Let's get the right people involved now rather than cycling proposals."
Tactic 6: Document Everything in the True-Up Order
Any pricing, commitment, or restructuring agreement reached during the true-up negotiation must be documented in the true-up order form or an accompanying amendment. Verbal commitments from account managers do not survive personnel changes. If it's not written down, it doesn't exist.
Negotiation Principle: The true-up is not a confrontation — it's a commercial conversation where both parties have incentives to reach resolution. Your job is to ensure the resolution reflects your interests, not just Microsoft's convenience.
Common True-Up Traps
Across hundreds of enterprise true-up engagements, we consistently see the same mistakes costing organisations significant commercial value. Each trap is avoidable with proper preparation.
Trap 1: Treating the True-Up as Administrative
Assigning the true-up to procurement operations rather than strategic vendor management guarantees a compliance-only outcome. The true-up is a commercial negotiation and should be treated as one, with senior stakeholder involvement.
Trap 2: Accepting Microsoft's Count Without Verification
Microsoft's admin portal reports assigned licences, not utilised licences. Shared mailboxes, service accounts, retained leavers, and test accounts all inflate the count. Independent verification routinely finds 10–20% overstatement.
Trap 3: Starting Preparation at the Deadline
Deployment audits, pricing benchmarks, and restructuring analysis require 60–90 days of preparation. Organisations that begin at the true-up deadline have no time for negotiation and accept whatever Microsoft presents.
Trap 4: Ignoring SKU Optimisation
Paying for E5 licences when E3 or E1 would suffice is the single largest source of Microsoft waste. A feature-utilisation analysis against your E5 population almost always reveals 20–30% of users who can be downgraded without impact.
Trap 5: Not Leveraging Competitive Alternatives
Microsoft's pricing is elastic — it responds to competitive pressure. Organisations that arrive at the true-up without any reference to alternatives (Google, AWS, Zoom) have no leverage to challenge pricing above market rates.
Trap 6: Failing to Document Negotiated Terms
Verbal commitments from Microsoft account managers do not survive. Pricing adjustments, commitment restructuring, and any concessions must be documented in the true-up order or an amendment. Personnel turnover at Microsoft means verbal commitments are worthless.
Recommendations: 7 Priority Actions
The following actions should be initiated immediately for any organisation with a Microsoft true-up approaching within the next 120 days.
Reframe the True-Up Internally
Communicate to stakeholders — procurement, IT, finance, and executive sponsors — that the true-up is a commercial negotiation event, not an administrative exercise. Assign senior ownership and allocate preparation time accordingly.
Conduct an Independent Deployment Audit
Audit all Microsoft products — M365, Azure, Dynamics, Power Platform, and on-premise — at least 90 days before the true-up date. Cross-validate Microsoft's reported counts against your own identity, deployment, and financial data.
Build a Pricing Benchmark
Benchmark your current per-unit pricing against market comparables for your size, industry, and geography. Quantify the gap and use it as evidence during negotiation. If you're above market, you have grounds for adjustment.
Model Every Restructuring Option
Build 3-year cost models for every viable restructuring option: SKU downgrades, commitment reductions, workload migrations, and term extensions. Each model should show the net savings against the status quo true-up cost.
Prepare Your Competitive Position
Develop a credible assessment of competitive alternatives. You don't need to plan a migration, but you need Microsoft to understand that the evaluation is real. Reference specific workloads where alternatives are viable.
Engage Microsoft 60 Days Before the True-Up
Present your deployment audit findings and restructuring proposal to the Microsoft account team at least 60 days before the true-up deadline. Lead with data. Frame restructuring as a win for both parties. Request deal desk escalation early if the scope requires it.
Document Everything in Writing
Every pricing adjustment, commitment change, or restructuring term agreed during the true-up negotiation must be documented in the true-up order form or a formal amendment. Accept nothing verbal. If it's not written, it's not real.
How Redress Can Help
Microsoft Practice
100% Independent — Zero Vendor Affiliations — No Reseller Agreements
Redress Compliance's Microsoft Practice provides end-to-end true-up negotiation support — from deployment audit and pricing benchmarks through restructuring analysis and direct negotiation with Microsoft's account team and deal desk. We represent your interests, never Microsoft's.
Our true-up engagements typically deliver 15–40% cost reductions through a combination of deployment count correction, SKU optimisation, pricing renegotiation, and commitment restructuring. Every recommendation is backed by auditable data and supported through execution.
We operate on a fixed-fee or success-fee basis — never as a percentage of your Microsoft spend. Our independence means our recommendations are driven by your commercial interests, not by any vendor relationship.
Book a Meeting
Speak with a Microsoft licensing specialist from our independent advisory team. We'll assess your true-up exposure, review your deployment data, and outline a negotiation strategy to convert your next true-up into a commercial opportunity.
Redress Compliance
1314 E Las Olas Blvd, Fort Lauderdale, FL 33301
[email protected] | +1 (239) 402-7397