A 84 page buyer side reference to the annual Microsoft Enterprise Agreement true up in 2026. Counting rules, seat baselines, Copilot interaction, audit triggers, the side letter clauses that protect against retroactive billing, and the negotiation moves to make before you sign the next true up order.
The Microsoft true up looks like an administrative process. It is not. It is the single largest unmanaged cost event in most Enterprise Agreements, and the counting rules in 2026 changed enough to surprise procurement teams that have run the same playbook for a decade.
Every Microsoft EA includes a true up obligation. Once a year, the customer counts the qualified users, qualified devices, and consumption based services that grew above the baseline, then issues a true up order to bring the agreement back into compliance. The principle is simple. The execution is not. Counting rules differ across products. Seat baselines move when subsidiaries are acquired or divested. Copilot, Defender XDR, and Power Platform consumption now intersect the user count in ways that did not exist when the EA was signed. The true up bill in 2026 is rarely a clean line item. It is a multi product reconciliation that exposes every gap in the Microsoft licensing posture.
Microsoft account teams understand this. The true up is also one of the few moments inside an EA term when the account team can credibly press for upsell. Copilot for Microsoft 365 lands inside the true up calculation when seats are added. The Defender XDR overlap drives Step Up SKUs that show up only when the true up is run. The Power Platform agent metering interacts with the user true up baseline. The combination is a billable event that grew faster than buyer side procurement teams have recalibrated their controls. The realized true up bill is now the negotiation event. Cross reference the Microsoft EA Renewal Playbook for the renewal calendar that surrounds every true up cycle.
This guide is the complete buyer side reference for the 2026 true up. We document the counting rules product by product, walk through the seat baseline reset mechanics, score the Copilot and security stack interaction, and document the negotiation moves we have used on Redress engagements to bring the realized true up bill down by between twelve and thirty four percent. The playbook is the manual every procurement and asset management team should read before the true up window opens.
The playbook opens with the counting rules. We split the Microsoft estate into five count families: per user SKUs in the Microsoft 365 stack, per device SKUs in the Windows and System Center families, per server SKUs across Windows Server, SQL Server, and the rest of the data platform, consumption based services in Azure and Power Platform, and the Copilot family with its own metering rules. Each family has a distinct counting rule, a distinct measurement window, and a distinct path to the true up order. The playbook documents every rule and the typical measurement gaps that buyers underestimate.
The middle of the playbook covers the seat baseline. Microsoft anchors the true up to the count at the start of the EA term plus the previous true up adjustments. The baseline moves when subsidiaries are acquired, divested, or restructured. The baseline interacts with Step Up SKUs in non obvious ways, and the baseline determines how aggressively the account team can press a Copilot for Microsoft 365 attach. We walk through the baseline reset mechanics, the corporate event clauses that govern divestitures, and the specific contract language to negotiate before any major reorganization.
The Copilot interaction chapter is the one most procurement teams wish they had read first. Copilot seats added during the year flow into the true up. Copilot Studio agent capacity flows into the consumption true up. Copilot prerequisite changes can force Step Ups on the underlying Microsoft 365 SKU. The playbook documents the interaction map and the levers that exist to manage Copilot growth without amplifying the true up bill. Pair this with the Microsoft Copilot Licensing Guide 2026 for the underlying Copilot mechanics.
The audit triggers chapter is the chapter Microsoft account teams hope you never read. The true up process surfaces deployment data Microsoft can use to start a Software Asset Management engagement that quickly converts into a formal audit. The playbook walks through the data points that matter, the disclosure controls every buyer should run before submitting the true up, and the side letter language that limits the use of true up data for audit triggering. Cross reference the Microsoft Audit Defense Playbook 2026 for the broader audit defense framework.
Email gated. Corporate addresses only. We will send you a direct PDF link and add you to the buyer side intelligence list. Unsubscribe in one click.
Prefer to talk to a human first?
Schedule a Microsoft Advisory Call →
Talk to a buyer side advisor. No pitch. No sales theatre. Thirty minutes, your numbers, our framework.
One letter a month. Negotiation moves, audit signals, and price book shifts.
