Microsoft EA True Up. The complete buyer side guide. 2026 edition. Qualified users, qualified devices, deployment counts, the annual cycle.

The Microsoft Enterprise Agreement true up is the annual reconciliation that compares actual deployment against the contracted EA baseline. Every Microsoft EA contains an annual true up that runs at the contract anniversary, and the commercial outcome depends heavily on whether the customer or the publisher controls the deployment numbers.

A true up typically captures growth above the contracted baseline across qualified users, qualified devices, the broader product mix, Microsoft 365, and Microsoft Azure consumed quantity. A disciplined buyer side approach anchors the true up against actual utilization rather than the publisher's opening position, and routinely delivers fifteen to thirty percent savings against the opening true up quote at the contract anniversary.

Read the related Microsoft services practice, the Microsoft EA renewal playbook, the Microsoft EA renewal playbook download, the Microsoft 365 license optimizer, the Microsoft knowledge hub, the Microsoft audit defense playbook, and the CIO playbook for Microsoft CSP and NCE licensing.

The Microsoft EA true up intersects with seven principal commercial dimensions across the customer's EA portfolio:

1. Qualified users. The user population entitled to access EA covered services.
2. Qualified devices. The device population covered by per device licensing.
3. Microsoft 365. The subscription mix across E3, E5, F3, and add ons.
4. Microsoft Azure consumed quantity. Metered consumption above the prepaid Azure commitment.
5. Software Assurance. The maintenance and benefits layer attached to perpetual entitlements.
6. The contracted EA renewal. The three year renewal window that follows the final anniversary.
7. Price protection. The contractual ceilings that govern unit price across the term.

Each dimension carries material commercial sensitivity, and a buyer side posture must anchor every one of them against actual deployment. Read aligning Microsoft support renewal with EA timing.

What is the Microsoft EA true up

The Microsoft EA true up is the annual EA reconciliation. The EA itself is a three year contract that fixes the customer's contracted quantity at the start of the term and expects deployment to grow over the three year cycle. The true up captures that growth above the contracted baseline on an annual basis at the contract anniversary.

The calculation is straightforward in principle. The contracted baseline is the customer's contracted quantity at the start of the EA cycle. The true up captures deployment growth above that baseline each year. Microsoft applies the publisher's opening price against the growth, subject to publisher minimums across the contracted EA.

A buyer side posture anchors the true up to actual deployment rather than to the publisher's opening position. Read the Microsoft licensing audit defense.

The annual cycle

The Microsoft EA annual cycle is the principal commercial process around the true up. It runs roughly ninety days before the contract anniversary, with the true up submission due at the anniversary itself. The cycle follows four principal stages:

1. Internal EA deployment count. The customer's own measurement of installed and active estate.
2. LSP counter check. The Microsoft Licensing Solution Provider's independent counter measurement.
3. True up submission. The reconciled count submitted to Microsoft via the LSP.
4. True up reconciliation. The negotiated landing against price, ramp, and protection terms.

The annual cycle typically generates a finding where the publisher's opening position lands well above the customer's actual deployment. A buyer side posture anchors the cycle to actual deployment and builds a credible competitive posture before submission. Read the Microsoft audit defense playbook.

Hour 1 to 90. Internal deployment count.

The first ninety days of the annual cycle reframe the true up around what is actually deployed:

1. Run the internal EA deployment count against the contracted EA baseline.
2. Run the qualified user count against the contracted qualified user baseline.
3. Run the qualified device count against the contracted qualified device baseline.
4. Run the Microsoft 365 count against the contracted Microsoft 365 baseline.
5. Run the Azure consumed quantity against the contracted Azure consumed quantity baseline.

Hour 60 to 30. LSP counter check.

The next sixty days align with the Microsoft Licensing Solution Provider:

1. Run the LSP counter check against the customer's internal EA deployment count.
2. Reconcile discrepancies in the EA deployment count line by line.
3. Brief the EA owner on the reconciled deployment count and the implications for submission.

Read the Microsoft license audit defense.

Hour 30 to 0. True up submission.

The final thirty days submit the true up:

1. Submit the reconciled deployment count to the Microsoft Licensing Solution Provider.
2. Negotiate the true up against the publisher's opening position.
3. Lock in EA price protection terms across the true up.

Qualified users

Qualified users are the principal user population for the true up. Microsoft typically anchors the qualified user count to its opening position. A buyer side posture anchors qualified users to actual deployment. The population covers employees, contractors, and third party users that access EA covered services on a regular basis.

Excluded from qualified users are occasional users, third party automated systems, and read only access users. Negotiate the qualified user count at the contracted EA and lock in qualified user price protection terms across the contracted EA. Read the Microsoft EA discount negotiation levers.

Qualified devices

Qualified devices are the principal device population for the true up. Microsoft typically anchors the qualified device count to its opening position. A buyer side posture anchors qualified devices to actual deployment. The population covers desktops, laptops, mobile devices, and virtualised devices that access EA covered services on a regular basis.

Excluded from qualified devices are development and test devices, third party automated systems, and read only access devices. Negotiate the qualified device count at the contracted EA and lock in qualified device price protection terms across the contracted EA. Read the Microsoft SPLA audit defense.

Microsoft 365

Microsoft 365 is the principal SaaS population for the true up. Microsoft typically anchors the Microsoft 365 count to its opening position across the Microsoft 365 E3, E5, and F3 SKUs. A buyer side posture anchors Microsoft 365 to actual utilization. The opening position applies publisher list price against Microsoft 365 deployment growth.

Negotiate Microsoft 365 against the publisher's opening position. Lock in Microsoft 365 price protection terms across the contracted EA. Read the Microsoft 365 license optimizer and the Microsoft 365 E7 framework.

Microsoft Azure consumed quantity

Microsoft Azure consumed quantity is the principal cloud population for the true up. Microsoft typically anchors Azure consumed quantity to its opening position. A buyer side posture anchors Azure consumed quantity to actual utilization. The opening position applies publisher list price against Azure consumed quantity growth.

Negotiate Azure consumed quantity against the publisher's opening position. Lock in Azure price protection terms across the contracted EA. Read the Azure Arc in the enterprise CIO playbook.

Software Assurance

Software Assurance is the principal maintenance layer attached to the EA. Microsoft typically anchors Software Assurance to its opening position. A buyer side posture anchors Software Assurance to actual utilization of the underlying entitlements. The opening position applies publisher list price against the Software Assurance population.

Negotiate Software Assurance against the publisher's opening position. Lock in Software Assurance price protection terms across the contracted EA. Read the Microsoft licensing audit defense.

Common true up mistakes

The most common true up mistakes leave the publisher's opening position substantially intact against the customer's actual deployment. The seven errors we see most often are:

1. Submitting the publisher position blind. Sending an LSP count back without ever running the internal EA deployment count.
2. Skipping the counter check. Failing to reconcile the LSP counter check against the customer's internal count.
3. Not negotiating. Failing to negotiate the true up against the publisher's opening position.
4. No price protection. Failing to lock in EA price protection terms across the true up.
5. No renewal alignment. Failing to align the true up with the contracted EA renewal cycle.
6. No leverage view. Failing to align the true up with the broader Microsoft licensing leverage.
7. No internal briefing. Failing to brief the EA owner on the reconciled deployment count.

A buyer side posture reframes each of these seven errors against actual deployment. Read the CIO playbook for Microsoft CSP and NCE licensing.

The exposure framework

Exposure is the principal commercial view of the true up. The exposure population segments across seven principal populations: qualified user exposure, qualified device exposure, Microsoft 365 exposure, Microsoft Azure consumed quantity exposure, Software Assurance exposure, renewal exposure, and price protection exposure.

Microsoft has applied substantial EA price increases against customers across the contracted EA, with documented cases at the upper customer scale. A buyer side posture anchors exposure to actual deployment and builds a credible competitive position across qualified users, qualified devices, Microsoft 365, Microsoft Azure consumed quantity, Software Assurance, and the contracted EA renewal. Read the Microsoft EA discount negotiation levers.

The buyer side moves

A disciplined buyer side approach to the Microsoft EA true up has eleven moves at the contract anniversary:

1. Anchor to actual deployment. Set the true up against the customer's measured estate, not the LSP's opening count.
2. Segment by dimension. Split the true up across qualified users, qualified devices, Microsoft 365, Microsoft Azure consumed quantity, and Software Assurance.
3. Run the shortfall view. Quantify the shortfall across the seven principal true up populations.
4. Negotiate against the opening position. Push back on the publisher's opening price for the true up.
5. Build a credible competitive posture. Make the alternatives real enough to move the negotiation.
6. Extend the shortfall to the contracted EA. Run the broader shortfall analysis against the full EA, not only this year's growth.
7. Negotiate the long term position. Address the publisher's preferred long term EA position alongside this year's submission.
8. Use bespoke structures where justified. Apply a bespoke true up structure where the customer's deployment shape justifies it.
9. Lock in price protection. Secure EA price protection terms across the true up.
10. Apply a ramp. Use a true up ramp where growth profile and consumption justify it.
11. Run the wider vendor posture. Treat the true up as one move inside the broader Microsoft vendor management posture across the contracted EA.

Read the Microsoft EA renewal playbook.

Microsoft EA renewal alignment

The Microsoft EA renewal is the principal renewal event for the true up cycle. Microsoft typically anchors the renewal to its opening position. A buyer side posture anchors the renewal to actual deployment. The renewal aligns with the third EA anniversary at the close of the contracted EA cycle.

Negotiate the renewal against the publisher's opening position. Lock in renewal price protection terms across the contracted renewal. Read the aligning Microsoft support renewal with EA timing.

How we engage

• Microsoft EA true up scoping. Six week engagement that scopes the true up. Microsoft services practice.
• Microsoft EA true up engagement. Twelve to sixteen week engagement that handles qualified users, qualified devices, Microsoft 365, Microsoft Azure consumed quantity, and Software Assurance. Microsoft EA renewal playbook download.
• Microsoft audit defense. Audit defense engagement across the contracted EA. Microsoft audit defense playbook.
• Vendor Shield. Always on multi vendor management posture across Microsoft. Vendor Shield.
• Run the assessment. The Microsoft 365 license optimizer sizes the Microsoft 365 estate.