A working Microsoft true-up calculator uses six inputs to estimate anniversary exposure: per-SKU entitlement count, per-SKU deployment count, per-SKU negotiated price, prorating window, applicable EA volume band, and SA-coverage status. The exposure formula is straightforward — (deployment minus entitlement) times negotiated price times prorating fraction — but the buyer-side discipline is what makes the number defensible. The framework below builds the estimate from disclosed entitlement data and validated deployment counts; it produces the pre-modelled position that resists Microsoft’s opening reconciliation framing. The companion true-up risk assessment tool is the 10-question scorecard for organisations whose true-up exposure is unclear.
A Microsoft true-up calculator is not a black-box spreadsheet; it is a six-input estimation framework that the buyer-side licence-management team runs at T-120 ahead of each anniversary. The framework, the formula, and the validation discipline below are drawn from active 2024–2026 true-up defence practice. The output is the pre-modelled position; the value is in the discipline of producing it before Microsoft sends the anniversary invitation.
The six inputs to a Microsoft true-up calculator
Each input has a single source of truth and a single validation step. The discipline is to populate every input from the buyer-side source — not from Microsoft account-team statements.
Per-SKU entitlement at signing plus prior true-ups
The per-SKU licence count the buyer holds, including the Year-0 EA enrolment quantity plus every prior true-up acquisition. Source of truth: the VLSC (Volume Licensing Service Center) entitlement record plus the EA enrolment paperwork and every true-up amendment.
entitlement_count = enrolment_qty + sum(true_up_qty)Per-SKU active deployment as of true-up snapshot date
The per-SKU count actually deployed as of the snapshot date. Source of truth: M365 admin centre exports for cloud SKUs, MECM / Intune deployment reports for on-premises SKUs, Azure billing exports for Azure consumption, hypervisor inventory for SQL Server and Windows Server cores. Active deployment, not provisioned-but-unused; the distinction can materially reduce the exposure.
deployment_count = admin_centre_export | mecm_deploy_count | hypervisor_core_countThe buyer’s negotiated price, not Microsoft retail list
The per-SKU price the buyer negotiated at signing or at the most recent comparable renewal. Source of truth: the EA pricing schedule. Microsoft’s default true-up pricing for SKUs not on the schedule is retail list; the buyer-side rebuttal anchors to the negotiated tier on the schedule. The pricing gap between retail and negotiated can be 20 to 40 percent of the apparent exposure.
price_per_sku = ea_pricing_schedule | comparable_renewal_pricingMonths between deployment date and anniversary
The fraction of the anniversary year the new SKU was actually deployed. EA default true-up pricing is full-year regardless of deployment date; the buyer-side rebuttal anchors prorated pricing for partial-year deployment. Source of truth: the deployment activation log, Azure subscription start date, M365 licence assignment timestamp.
prorating_fraction = months_deployed / 12Buyer’s qualified EA volume band (A/B/C/D)
The buyer’s qualified EA volume band, which determines the underlying tier pricing. 2026 amplifier: the EA tier collapse means the band positioning carries less marginal value than it did pre-collapse; the band still matters for some SKU families. Source of truth: the EA enrolment paperwork and the buyer’s total deployment count across all EA-eligible SKUs. See the tier collapse pillar.
volume_band = qualified_band_per_enrolmentSoftware Assurance coverage on the underlying entitlement
Whether the underlying entitlement carries Software Assurance. SA-coverage materially affects the true-up math: SA-covered entitlements include version upgrade rights, step-up rights, and certain Software Assurance benefits that can offset apparent deployment gaps. The 2026 amplifier is the SA step-up pattern for E3-to-E5 step-up and the bundling changes (Defender for Office P1 into E3, Intune Suite into E5). Source of truth: the VLSC SA-coverage record.
sa_offset = sa_step_up_credit | version_upgrade_credit | sa_benefit_creditThe Microsoft true-up calculator formula
The per-SKU exposure formula is the product of the deployment gap, the negotiated price, the prorating fraction, and the SA offset.
The total true-up exposure is the sum across all SKUs in the EA scope. The buyer-side total is the pre-modelled position the buyer brings to the anniversary conversation. Microsoft’s opening number is the reference point; the buyer-side total is the rebuttal anchor.
Worked example: a five-SKU calculation
A worked example illustrates the framework. Assume a buyer with an EA covering five primary SKUs at anniversary: M365 E3 (cloud SKU), M365 E5 (cloud SKU), Windows Server Datacenter (core-licensed), SQL Server Enterprise (core-licensed), and Copilot for M365 (cloud SKU). Each row uses the six-input framework.
| SKU | Entitlement | Deployment | Gap | Price (negotiated) | Prorating | SA offset | Exposure |
|---|---|---|---|---|---|---|---|
| M365 E3 | 10,000 | 10,840 | 840 | $28 / mo | 1.00 | $0 | $282,240 |
| M365 E5 | 1,200 | 1,415 | 215 | $54 / mo | 0.83 | $0 | $115,652 |
| Windows Server Datacenter (cores) | 620 | 684 | 64 | $6,150 / core | 0.92 | SA step-up $0 | $362,112 |
| SQL Server Enterprise (cores) | 96 | 118 | 22 | $13,750 / core | 1.00 | $0 | $302,500 |
| Copilot for M365 | 1,800 | 2,260 | 460 | $30 / mo | 0.67 | $0 | $110,952 |
| Total estimated exposure | $1,173,456 | ||||||
The buyer-side pre-modelled position is $1.17M. Microsoft’s opening reconciliation number on the same SKU set typically lands 35 to 65 percent higher, driven by retail pricing on Copilot (no negotiated tier on schedule), no prorating on partial-year deployments, and missed SA offsets on the Windows Server step-up. The buyer-side rebuttal anchors back to the pre-modelled position.
Anniversary approaching? The six-input framework runs at T-120, not T-60.
30-minute scoping call with a senior partner. True-up modelling is part of standard advisory work.
How to validate the buyer-side true-up calculator output
Three validation steps separate a reliable pre-modelled position from a wishful estimate.
- Reconcile every deployment count against two independent sources. The M365 admin centre count must match the Entra ID active-licence assignment count. The MECM deployment count must match the hypervisor inventory for on-premises SKUs. Discrepancies are not noise; they are gaps in the buyer’s data discipline. See the audit licence position article for the broader ELP discipline.
- Reconcile every entitlement count against the VLSC record plus the true-up amendment trail. The entitlement should match what is in VLSC; if it does not, the gap is either a missing true-up amendment or a VLSC sync error. Either gap is worth resolving before anniversary.
- Reconcile every price against the EA pricing schedule. The negotiated price per SKU is on the pricing schedule, the EA amendment, or the comparable-renewal pricing. The price-per-SKU input is the second-most material driver of the exposure number after the deployment gap; it is the input Microsoft’s opening reconciliation gets wrong most reliably. See how Microsoft calculates discounts.
2026 amplifiers that shift true-up calculator math
Four 2026 inflection points alter the calculator math materially.
- The July 2026 price increase. Anniversaries after July 2026 use post-increase pricing for added SKUs. The price-per-SKU input must reflect the price-protection clause if one exists; if no price-hold clause exists, the post-increase pricing applies. See the July 2026 pricing pillar and the price increase handling article.
- E7 / Frontier Suite step-up. The E5-to-E7 step-up pattern is new in 2026 and changes how SA offsets work for the upper-tier M365 SKUs. See the E7 article.
- Agent 365 tier mix. The Agent 365 Standard / Pro / Enterprise tier mix creates a new SKU family in the true-up envelope. Most enrolments are Year 1 or Year 2; tier-mix drift in subsequent anniversaries is probable. See the Agent 365 article.
- Copilot Studio consumption. Copilot Studio CCCU and ACU usage creates consumption-driven true-up exposure that did not exist for prior Copilot generations. The deployment-count input becomes a usage-count input for this SKU family. See the Copilot Studio 2026 article.
The single highest-leverage discipline in true-up calculation is to maintain the inputs continuously, not at anniversary. Quarterly licence position reviews keep the entitlement, deployment, and price inputs current; quarterly reviews surface drift early. Anniversary becomes a confirmation exercise rather than a discovery exercise. The buyer who runs the calculator at T-120 with current quarterly inputs negotiates from evidence; the buyer who runs the calculator at T-60 with stale data negotiates from estimates. The discipline is what makes the framework valuable.
The Microsoft Negotiations briefing
Monthly. True-up tactics, audit defence, EA negotiation, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the true-up calculator next
The calculator framework pairs with the broader true-up and audit framework. The true-up risk assessment tool is the 10-question scorecard for organisations whose exposure is unclear; the true-up defence service is the productised engagement; the true-up leverage article walks the seven seller-side moves and counters; the true-up reduction playbook walks the nine buyer-side moves the calculator output supports; the true-up timing strategy covers the four windows where adding licences costs less than the default anniversary path; the VLSC report guide is the evidence pull that feeds each calculator input; the overage response playbook covers classification across the seven overage categories; the audit defence pillar covers the structural overlap with Verification. For organisations approaching anniversary, the scoping call is the direct engagement channel; for organisations in active EA renewal cycles, the free EA assessment is the broader scoping channel.