An Enterprise Agreement renewal turns your annual true up into the number Microsoft anchors the next term on. Build a defensible license position before you submit, not after the quote arrives.
Many teams treat the annual true up as an administrative count. Under an Enterprise Agreement it is far more than that. The true up records the additional licenses you consumed during the year and prices them, and in the run up to a renewal that figure becomes the baseline Microsoft uses to frame the next agreement. Submit a loose number and you are negotiating the renewal from a position someone else set.
The buyer side move is to treat the pre renewal window as the moment to know your real position before Microsoft does. The true up you submit should reflect a license position you have already rebuilt and can defend line by line, not a raw export from a tool.
Outside a renewal cycle a true up settles a single year. Inside the renewal window it does two jobs at once. It closes the current year and it signals your trajectory. If your reported consumption spikes just before a renewal, Microsoft reads that as growth it can price into the new term, and it may also raise your audit profile through the anomaly detection it runs across licensing and telemetry.
That is why timing and accuracy matter together. A position that looks inflated because of double counted users, retired servers still showing in inventory, or cloud entitlements that were never reconciled against deployment will cost you twice, once in the true up and again across the renewal term.
Start from entitlement. Reconcile every product you are consuming against what your agreement actually grants, including Software Assurance benefits and any rights that travel with cloud subscriptions. Then map deployment against that entitlement the way an auditor would, using the same data sources Microsoft draws on, which include Azure, Microsoft 365, and management tooling.
A clean report from your own Software Asset Management tool is useful, but it is not the final word. Microsoft uses its own counting methodology and its own data, and where the two differ, Microsoft's calculation governs. Your pre renewal position has to anticipate that calculation rather than assume your tool agrees with it.
| Line | Raw tool count | Reconciled position |
|---|---|---|
| Windows Server cores | 2,400 | 1,920 |
| SQL Server cores | 640 | 512 |
| M365 E5 users | 5,100 | 4,650 |
| Indicative true up value | $1.9M | $1.3M |
The raw count includes decommissioned hosts, duplicate identities, and users who hold a lower tier in practice. The reconciled position removes them with evidence. The difference is what you would otherwise pay on a number you never checked.
Use the pre renewal window deliberately. Run your own internal assessment with independent help, close the gaps you can close, document the ones you cannot, and only then commit to a true up figure. A position you have rebuilt is also the position you carry into the renewal conversation, which means the same evidence defends both numbers.
Remember that the opening position Microsoft presents is built to be high, and that an Effective License Position is negotiated after the report rather than accepted on sight. The earlier you control your own number, the less room there is for the renewal to be anchored against you.
If a renewal is on the horizon, the work starts now, not when the quote lands. Our guarantee is straightforward: we reduce your exposure or we reimburse our service fee. We engage on a Fixed Fee from $18,000 or on Gainshare, a share of verified savings or avoided penalty with zero retainer and no risk to you.
For the full pre renewal playbook, read the survival guide below, then bring us your timeline.
If this is live on your desk right now, our EA true up defense team verifies the numbers before they become contractual.
Build a defensible pre renewal position and carry it into the renewal.
Download guideWeekly intelligence on Microsoft and SPLA audit moves and the buyer side defenses that work.