True-Up Assessments Are Not Always Right
The implicit assumption in most enterprise true-up processes is that Microsoft's assessment is correct and your job is to pay it. This assumption is wrong — and it costs enterprises significant money every year.
True-up assessments are built from multiple data sources: your own submission, Microsoft's telemetry, LAR-maintained records, and sometimes SAM partner inventory data. Each source can contain errors. Deployments counted at the wrong point in time, add-ons attributed to the wrong qualifying user population, SA coverage applied inconsistently, acquired entity assets counted without confirming their licence transfer status — these are not unusual edge cases. In assessments covering large, complex EA estates, they are routine.
Most enterprises never challenge a true-up assessment because they do not have a formal licence position to compare against it, because they assume the dispute process is adversarial and relationship-damaging, or because the people managing the true-up process lack the licensing expertise to identify where the assessment has applied incorrect rules. The result is systematic overpayment that accumulates across each three-year EA term.
Five Categories of Disputable True-Up Items
Before initiating any dispute, you need to know what you are looking for. The following five categories account for the large majority of material errors in enterprise true-up assessments.
1. Peak Deployment Count Errors
The true-up obligation is calculated on peak deployment during the anniversary year — the highest point-in-time user or device count for each product. If Microsoft's assessment captures peak count at a date that includes a known temporary spike — for example, a contractor population that was off-boarded within the same month — the peak figure is inflated.
To dispute this, you need Entra ID or Active Directory export data showing user status at the specific date Microsoft has used as the peak count reference, plus evidence of the temporary population's de-provisioning. If your own IT governance has maintained accurate provisioning records, this dispute category is highly winnable.
2. Incorrect Product Use Rights Application
Microsoft's Product Use Rights (PUR) documents are complex and update annually. SAM partners and even Microsoft's own licensing teams sometimes apply prior-year rules to current deployments, apply the wrong edition rights, or fail to credit downgrade rights that your EA entitles you to use. Windows Server CAL bridge rights, SQL Server edition downgrade rights, and Microsoft 365 service substitution rights are particularly frequent sources of miscalculation.
Disputes in this category require precise reference to the applicable Product Use Rights document for the licence grant date, and an independent interpretation of the relevant rule. This is technical licensing work — it requires a licensing specialist, not a contract administrator.
3. Software Assurance Coverage Miscalculation
SA coverage determines what additional rights your deployment is entitled to — including virtualisation rights, extended coverage for additional devices, and step-up licensing. If SA coverage is incorrectly mapped to the deployment in the true-up assessment, you may be paying for licences you are already entitled to under your SA terms. Virtualisation coverage is the most commonly miscalculated SA right: if you are running Windows Server in a virtualised environment and SA coverage is not correctly applied, the assessment may require additional licences that your SA already covers.
4. Acquired Entity Scope Errors
If your organisation acquired a company mid-term, the acquired entity's software deployments may have been included in your true-up assessment scope before the contractually-specified integration date. Most EA terms allow a period — typically six to twelve months — before acquired entity assets must be covered under your EA. If the assessment includes acquired entity deployments before this grace period expires, the items are disputable on contractual grounds.
5. Contractor and Third-Party User Counting
True-up counting rules for contractors, consultants, and third-party users who access Microsoft services vary significantly by product. Some products require full user licences for contractor populations; others allow CAL structures or limited-use provisions. If the assessment has applied a blanket full-user-licence requirement to a contractor population that qualifies for a different licence structure under the applicable PUR, the line items are disputable.
Building the Dispute Case
A successful true-up dispute requires three elements: identification of the specific disputable item with a precise statement of why it is incorrect; documentary evidence supporting your alternative count or interpretation; and a proposed resolution — your correct figure — with supporting calculation.
Documentation Requirements by Category
| Dispute Category | Primary Evidence Required | Supporting Documentation |
|---|---|---|
| Peak deployment count error | Entra ID / AD export at assessment reference date | User provisioning logs; de-provisioning records |
| Product use rights misapplication | Relevant PUR document with rule cited | Licence grant date; edition entitlement documentation |
| SA coverage miscalculation | SA coverage confirmation document | Virtualisation topology; deployment configuration records |
| Acquired entity scope error | EA amendment terms (integration period clause) | Acquisition date documentation; entity structure chart |
| Contractor user counting error | Contract records showing user status; PUR contractor provision | Access provisioning records; usage logs |
Compile all documentation before initiating formal dispute. Microsoft will request it, and an incomplete dispute package significantly weakens your position. The standard of evidence required is documentary, not anecdotal — "we believe our count was lower" is not a dispute; a timestamped Entra ID export showing the actual count is.
The Formal Dispute Process
Microsoft's formal true-up dispute process operates through three stages. Understanding each stage — and its timing requirements — prevents you from losing a valid dispute on procedural grounds.
Stage 1: Account Team Escalation (Informal)
The first step is a written communication to your Account Executive presenting the dispute items with supporting evidence. This is not yet a formal dispute — it is an informal resolution attempt that Microsoft's process expects you to attempt first. Frame the communication professionally and analytically: this is a factual correction exercise, not a complaint. Include your proposed corrected figures with the supporting calculation for each disputed item.
Most material disputes that have strong documentary evidence are resolved at this stage, because Account Executives have strong incentives to avoid formal escalation. The informal stage typically takes two to four weeks. If you receive substantive engagement from Microsoft and constructive back-and-forth on the evidence, this stage can extend — but do not allow it to drag beyond six weeks without requesting formal escalation.
Stage 2: Formal Written Dispute
If informal resolution fails, submit a formal dispute in writing to Microsoft's Volume Licensing team. The formal dispute should include: a precise identification of each disputed line item with the order form reference; the specific rule or count error you are disputing; your documentary evidence; and your proposed corrected figure with calculation. Reference your EA agreement number, the relevant anniversary year, and the date of the assessment you are disputing.
Microsoft is contractually required to acknowledge formal written disputes and to engage a resolution process. The acknowledgement timeline varies but should arrive within 15 business days. If you do not receive acknowledgement, follow up in writing — and document the follow-up. A pattern of non-response is relevant if the dispute subsequently requires legal escalation.
Stage 3: Escalation and Deadlock Resolution
If formal written dispute does not produce resolution, escalation options depend on the value of the dispute and your EA terms. Most EA agreements include a dispute escalation process that involves escalation to senior Microsoft management. For disputes above £100,000, engaging external legal counsel with Microsoft licensing expertise is advisable. For disputes involving systemic pattern errors — the same miscalculation applied across multiple products or years — documenting the pattern strengthens the escalation case.
In practice, Microsoft does not want formal legal dispute processes for true-up matters. Disputes that are well-documented, correctly framed, and materially significant (above £50,000) typically reach resolution through the formal written process because the alternative — a legal process that could expose Microsoft's assessment methodology to scrutiny — is not in Microsoft's interest.
Never sign a true-up order form that includes disputed items, even under time pressure from your account team. Signing constitutes acceptance of the assessment and eliminates your right to dispute the included items. If Microsoft is applying urgency pressure near the anniversary date, submit a written notification of your intent to dispute specific line items and request a revised order form. Do not allow urgency to foreclose a valid dispute.
Managing the Relationship During a Dispute
The most common reason enterprises avoid true-up disputes is concern about damaging the Microsoft relationship. This concern is understandable but largely unfounded when disputes are managed professionally. Microsoft's account teams deal with disputes regularly. A factually-supported, professionally-framed dispute does not damage the relationship — it signals that you are a sophisticated buyer who manages licensing professionally, which Microsoft's account teams actually respect.
What damages relationships is an aggressive, adversarial tone, poorly-documented claims, and disputing items that are genuinely not disputable. Focus your dispute on the items with strong documentary evidence and realistic prospects of resolution. Do not dispute items out of principle when your evidence base is thin — this wastes everyone's time and creates a pattern of crying wolf that weakens your position on legitimate items.
If your relationship with your Account Executive is genuinely strained by a dispute, that is a signal to escalate to their manager — not a reason to abandon a valid dispute claim.
Prevention: Clean Data Eliminates Dispute Necessity
The most effective approach to true-up disputes is to prevent the conditions that create them. Enterprises with mature licence governance — who maintain a current, independently-validated Effective Licence Position — rarely encounter material errors in their true-up assessments because they have already identified and corrected the data sources Microsoft will use to build the assessment.
Read our 2026 true-up preparation guide for the six-week remediation framework that establishes clean data before the assessment window opens. Read the True-Up and Compliance pillar guide for the quarterly governance framework that maintains this position year-round.
Dispute processes are necessary when governance has failed. Prevention — through structured governance, regular licence reconciliation, and accurate true-up submission — is the lower-cost, lower-stress alternative.