Microsoft EA true up. The asymmetric mechanic.

The Microsoft Enterprise Agreement true up is the annual reconciliation that occurs at each EA anniversary. The customer reports the actual seat counts, qualified users, and qualified devices for each licensed product. Microsoft invoices for any net additions since the last anniversary, prorated to reflect partial year usage. The customer is not refunded for net reductions in the same period.

The asymmetry is the structural feature of the mechanic that produces the bulk of unplanned Microsoft EA spend across the customer base. Most CIO finance teams know the asymmetry exists. Most do not have a contractual response to it.

This guide covers the buyer side framework on the EA true up. It walks through the mechanic itself, the qualified user versus qualified device choice, the four common traps that produce material unplanned spend, the true down on divestiture clause that the renewal cycle should add, the timing considerations across the EA anniversary calendar, and the named pitfalls.

• Renewal framework: read the Microsoft EA renewal playbook.
• Preparation sequence: read the Microsoft EA renewal preparation toolkit.
• Deeper true up reference: read the complete guide for Microsoft Enterprise Agreement true up.

1. The mechanic

The Microsoft EA true up runs on an annual cadence at each EA anniversary. The customer's Licensing Solution Provider (LSP) issues the true up form approximately 60 days before the anniversary. The customer fills in the actual counts for each licensed product, qualified user or device, and submits the form to the LSP for processing.

Microsoft invoices for the net additions, prorated to reflect partial year usage where applicable. The invoice is typically due 30 to 60 days from issuance. The full process runs from the 60 day notice through to invoice payment over approximately 90 to 120 days each year.

The annual true up timeline at a typical EA anniversary.

Phase	Days from anniversary	Customer activity	Microsoft activity
Notice	-60 to -45	Receive true up form from LSP	LSP issues form, baseline counts referenced
Reconciliation	-45 to -15	Internal usage data pull, qualified count calculation	n/a
Submission	-15 to 0	True up submitted to LSP	LSP processes, forwards to Microsoft
Invoice	0 to +30	Receive invoice	Microsoft invoices for net additions
Payment	+30 to +60	Pay invoice per terms	Reconciliation closed

2. The asymmetry

The structural feature of the EA true up is the one way nature of the reconciliation. Net additions are reported and paid for. Net reductions are absorbed by the customer as sunk credit. The publisher's framing is that the EA is a fixed term commitment with growth flexibility built in. The buyer side reading is that the asymmetry produces material unplanned overcharge across the term, particularly at customers with active M&A cycles, divestiture activity, or natural workforce reductions during the EA term.

3. Qualified User versus Qualified Device

The choice of metric on each licensed product determines how the true up calculation runs. Microsoft 365 and most enterprise products allow either Qualified User or Qualified Device, with the customer choosing at EA execution. The choice has material commercial implications across the term and is one of the most overlooked decisions at the renewal table.

Qualified User versus Qualified Device. Definitions and fit profile.

Metric	Counts	Includes	Best fit
Qualified User	Each user that uses or has access to the licensed software	Employees, contractors, consultants engaged in customer business operations	One to one user / device ratios. Knowledge worker dominant estates.
Qualified Device	Each device on which the licensed software is installed or accessed	Workstations, laptops, kiosks, shared terminals	Plant floor, retail, healthcare frontline. Shared workstation environments.

The metric choice changes the operational definition of the count. A manufacturing customer with 8,000 plant floor workers sharing 1,200 kiosks and shared workstations pays for 8,000 Qualified Users versus 1,200 Qualified Devices. The Qualified Device structure produces a 6.7 to 1 ratio in favor of the customer.

The buyer side framework defaults to Qualified Device on populations with low user to device ratios, and Qualified User on populations with one to one ratios. Many customers default to Qualified User across the entire estate without considering the alternative, which is the largest single overcharge on most manufacturing and retail EAs.

4. Four common true up traps

1. The M&A acquisition trap. Customers that complete an acquisition during the EA term inherit a population that needs M365 seats. The publisher's framing is that the acquired population is added to the contracted base via true up at the next anniversary. The buyer side framing is that the acquired population should be added through the acquisition agreement at the negotiated rate, not through the true up at standard rates. Customers who fail to engage Microsoft at the acquisition transaction pay materially higher unit rates on the acquired population.
2. The divestiture trap. The mirror image. Customers that divest a business unit during the EA term lose the seat requirement on the divested population. The contracted seat count remains. The customer pays the same EA fee for a smaller deployed population. The contractual response is the true down on divestiture clause documented below. Without the clause, the divestiture produces a structural overcharge for the remainder of the term.
3. The seat reduction trap. Customers that go through a workforce reduction event of 5 percent or more during the EA term experience the same divestiture asymmetry on a smaller scale. The seat count drops. The contracted base does not. The fix is the annual seat reduction allowance clause, also documented below.
4. The Copilot true up surprise. Copilot was added to many EAs during the 2024 cycle as an enterprise wide attach. Customers that deployed Copilot to a smaller active population than the contracted seat count pay the contracted count, not the active count. The true up does not refund for inactive Copilot seats. The fix is the Copilot scale down clause inserted at the renewal cycle.

5. The true down on divestiture clause

The true down on divestiture clause is the single most valuable contract addition on the Microsoft EA renewal, and it is the addition that most customers fail to negotiate. The clause grants the customer a defined contractual right to reduce the contracted seat count when a defined business event occurs, without true up settlement on the affected population.

The standard publisher EA paper is silent on the clause. The publisher's account team rarely volunteers it. The buyer side framework asks for it at every renewal.

6. Timing the true up

The EA anniversary date is set at EA execution and runs for the full three year term. Customers can influence the anniversary date through the original EA negotiation, but cannot change it during the term.

The choice of anniversary matters because the true up captures the population at a specific point in time. Customers with seasonal hiring patterns, M&A cycles concentrated in specific quarters, or natural attrition cycles tied to fiscal year end should consider the anniversary date carefully at the renewal cycle.

• Calendar year end anniversary (December 31). Captures the population at peak headcount in most enterprises. Useful for customers with growing trajectory because the true up reflects the peak. Disadvantageous for customers with December attrition because the count is high at exactly the wrong moment.
• Microsoft fiscal year end anniversary (June 30). Aligns the true up timing with Microsoft's fiscal year end pressure. The publisher's account team has the strongest commercial incentive to be flexible on the customer's true up at fiscal year end.
• Customer fiscal year end anniversary. The most operationally clean choice for most customers. Aligns the true up reconciliation with the customer's existing financial close cadence.

7. Common pitfalls

1. Pitfall one. Treating the true up as a procurement formality. The true up is a contractual commercial event. Customers who delegate it to administrative teams pay materially higher amounts than customers who treat it as a negotiation.
2. Pitfall two. Ignoring the metric choice. Qualified User versus Qualified Device is a high leverage decision. Customers who default to Qualified User across the full estate routinely overpay by 15 to 30 percent on populations where Qualified Device is the right structure.
3. Pitfall three. Failing to negotiate the true down clause. The clause must be added at the renewal cycle. The window closes on signature. Customers who divest during the term without the clause absorb the cost.
4. Pitfall four. Not engaging Microsoft at acquisition events. Acquired populations should be added through the acquisition agreement, not through the true up. Microsoft's account team has commercial flexibility at acquisitions that disappears once the population is reported through the standard true up.
5. Pitfall five. Submitting late. Late submission triggers LSP and Microsoft follow up. Persistent non submission can trigger an EA audit. Submit on time, every time, with the right number.

FAQ

What is a Microsoft EA true up?

The Microsoft Enterprise Agreement true up is the annual reconciliation that occurs at each EA anniversary. The customer reports actual seat counts, qualified users, and qualified devices for each licensed product. Microsoft invoices for any net additions on those counts since the last anniversary, prorated to reflect partial year usage. The customer is not refunded for net reductions in the same period.

What is the difference between qualified user and qualified device?

Qualified User counts every employee that uses or has access to the licensed software, including contractors and consultants engaged in the customer's business operations. Qualified Device counts each device on which the licensed software is installed or accessed, regardless of how many users access it. The choice between the two metrics depends on the user to device ratio.

Why does the true up only go up?

The standard Microsoft EA paper does not include a contractual right to reduce the seat count during the term. Net additions are reported and paid for. Net reductions are absorbed by the customer as sunk credit. The publisher's framing is that the EA is a fixed term commitment with growth flexibility built in. The buyer side reading is that the asymmetry is a structural overcharge that customers can negotiate through specific clauses inserted at the renewal table.

Can I negotiate a true down clause?

Yes, but only at the renewal cycle. Microsoft accepts true down on divestiture clauses in well prepared renewals at the upper end of the customer scale. The standard ask is the right to reduce contracted seat counts on M&A divestiture, business unit closure, or geographic exit, without true up settlement on the affected population. The clause language is contested and requires legal review. Customers who fail to negotiate the clause at renewal forfeit the right for the term.

What happens if I do not submit the annual true up?

Microsoft's standard EA paper requires the annual true up submission. Customers who do not submit on time are typically followed up by the LSP and by Microsoft directly. Persistent non submission can trigger an EA audit, which expands the publisher's scope and the dispute window.

Does Vendor Shield cover EA true up advisory?

Yes. The Vendor Shield subscription covers Microsoft in every tier including annual true up advisory. Coverage extends to the metric choice review, the qualified count calculation, the divestiture clause negotiation, and the M&A integration commercial event.