Microsoft EA renewal strategy and timeline.
An Enterprise Agreement renewal is the only moment in the three-year cycle when committed quantities can fall rather than rise. The true-down window opens once, at anniversary, and closes fast. This note lays out the 18-month program, the true-down mechanics, the NCE transition, and the levers that reset the baseline before it locks for another term.
A Microsoft EA renewal is not a procurement task — it is the one negotiation in the cycle where committed counts can fall. The true-down window opens only at anniversary, and the quantities carried into the next three-year term lock there. The estate that starts 18 months early resets its baseline; the estate that waits renews last term's shelfware plus the standard uplift.
01 Key findings
Renewal is the only downward reset. During the 36-month term the annual true-up adds seats but never removes them. Quantities ratchet up and lock down — only the renewal anniversary lets the baseline fall.
Shelfware is the largest single lever. A typical estate carries 12–25% shelfware after three years of true-ups and departures. A documented true-down case built from real deployment data recovers 15–20% of committed seats a default renewal would carry forward.
Preparation beats bargaining. The renewal is won before the closing call. The usage baseline takes three to four months to build; the estates that renew well start a full 18 months out, not at month three.
NCE compresses flexibility. Under the New Commerce Experience, annual and three-year subscriptions carry only a 168-hour cancellation window before the term locks — making accurate quantity-setting at renewal more consequential, not less.
Price protection is won at signature. True-up additions bill at prevailing list unless the contract locks the rate explicitly, and the next renewal uplift must be capped. Unprotected growth quietly erodes the original discount across the term.
02 The three-year EA cycle
An Enterprise Agreement runs 36 months. During the term you can add seats through the annual true-up, but you cannot remove them — quantities ratchet up and never down. The renewal anniversary is the only point at which the baseline can be reset downward, and the new baseline then locks for the following three years. This asymmetry is the central fact of EA cost control: every other lever, discount included, sits on top of the quantity you commit at renewal. The mechanics of the underlying agreement are covered in our Microsoft EA complete guide.
The annual true-up should be priced at signature, not at prevailing list. By default, seats added at each anniversary bill at the contracted rate only if the contract locks that rate explicitly. Estates that fail to secure price protection on true-up additions pay the increase on every seat they add as they grow, eroding the original discount over the term. The renewal is the moment to confirm growth is priced at the locked rate and that the uplift at the next renewal is capped.
03 The 18-month renewal timeline
The estates that renew well front-load the work, because the data takes months to assemble and the negotiation cannot begin until the true-down case is built. The most expensive mistake is starting at month three — by then the renewal defaults to existing quantities plus the standard uplift.
| Months before renewal | Action | Objective |
|---|---|---|
| 18 to 15 | Commission an independent license baseline | Count deployed versus owned by product |
| 15 to 12 | Identify shelfware, duplicate CALs, over-provisioned suites | Build the true-down target |
| 12 to 9 | Benchmark current pricing; model NCE and channel options | Set the discount and term thesis |
| 9 to 6 | Open the renewal conversation | Introduce competitive tension on a workload |
| 6 to 3 | Negotiate quantity, discount and term | Resolve true-down and product mix |
| 3 to 0 | Final pricing, paper and signature | Confirm the new baseline in writing |
04 The true-down window
True-down is the right to reduce committed quantities at renewal to match actual deployment. It is not automatic: you must identify the reductions, document that the seats are genuinely unused, and assert them before the new agreement is papered. A typical enterprise estate carries 12–25% shelfware after three years of true-ups, departures and cancelled projects. Recovering it is the largest single lever in most renewals. The detailed method is in our Microsoft EA true-down guide.
The baseline is the deliverable that decides whether a renewal saves money, and it reconciles three data sets: what the agreement says you own, what is actually deployed, and what is actually used. The gap between owned and used is the true-down target. A baseline that stops at deployment misses the dormant-seat layer — often the largest single source of recoverable cost.
Microsoft account teams propose renewals from the current committed quantity, not from actual usage — because the current quantity is higher. A defensible true-down case built from real deployment data shifts the starting point of the entire negotiation downward before discount is even discussed. Estates that present a documented usage baseline at month nine typically remove 15–20% of committed seats that a default renewal would have carried forward unchanged.
05 Negotiation levers beyond quantity
Once the baseline is reset, the discount levers apply: competitive tension on Azure or a security workload, timing against Microsoft's fiscal year-end on 30 June, consolidation of fragmented spend, and a documented price benchmark. A renewal is won in a sequence of trades — each round exchanges something the buyer can give, such as a longer term or a larger Azure commitment, for something Microsoft can give: discount, price protection, or true-down acceptance.
| Renewal stage | Buyer move | Target concession |
|---|---|---|
| Open | Present baseline and benchmark | Reset starting quantity downward |
| Mid | Introduce competitive alternative | Discount on contested workloads |
| Late | Offer term or Azure commitment | Price protection and uplift cap |
| Close | Sign in the fiscal-quarter window | Final concession against quota |
The benchmark matters most, because Microsoft renewal proposals routinely sit several points below the discount the estate could support. The realistic ranges are in our Microsoft discount benchmarks; the NCE term choice is in our NCE pricing guide; and the channel question is in the EA versus CSP cost analysis.
06 The renewal framework
Four disciplines separate a governed renewal from a repeated one. Weight them to your estate before the negotiation opens.
Baseline reconciliation
Reconcile owned, deployed and used. Deployment data comes from the M365 admin center, Entra sign-in logs and SAM tooling; usage data from active-user reports that expose dormant seats.
Timeline discipline
Front-load the program 18 months out. The baseline alone takes three to four months, and a compressed timeline removes the advantage that only preparation creates.
Competitive tension
A credible alternative on at least one workload — Azure or a security tool — converts the renewal from a captive conversation into a contested one and moves the negotiated rate.
Stakeholder alignment
HR owns the headcount forecast, the business units own the pipeline, finance owns the budget. Engage them at the 15-month mark so the true-down target can be defended.
07 Recommendations
Start the independent license count first. It takes three to four months and it sets the true-down target that every later concession is measured against. Without it the renewal defaults to current quantities.
Present the deployment-versus-usage gap at month nine, before discount is discussed. A documented case shifts the starting quantity down and typically recovers 15–20% of committed seats.
Secure the true-up rate in writing and cap the next renewal uplift to low single digits. Unprotected growth erodes the discount you just negotiated across the full term.
08 Sequencing the negotiation
A Microsoft renewal is won in a disciplined cadence, not a single ask. The process choice matters as much as the individual concessions:
Disciplined cadence Recommended
Open around month nine with the baseline and a documented benchmark, introduce a credible alternative on at least one workload by month seven, exchange proposals through months six to four, and reserve final commercial concessions for the fiscal-quarter close.
Compressed timeline Weaker
Starting at month three leaves no time to build a baseline, so the renewal defaults to existing quantities plus the standard uplift — exactly the outcome a renewal strategy exists to prevent. Revealing the full budget early removes every subsequent round.
09 The renewal scorecard
A renewal can be scored on four numbers, which turn a subjective negotiation into a measurable one and frame the conversation with finance. Set targets before the negotiation opens; test every concession against whether it moves one of them.
Presented in these terms — committed cost removed, rate improved, share of the next three years protected from increase — the renewal reads as a governed financial outcome rather than a list of products and prices. The full program sits in the Microsoft licensing pillar, and our Microsoft advisory practice runs EA renewals as a structured 18-month engagement.
Renew the estate you have, not the one you bought
Structured EA renewal programs reset committed quantities by a median of 17% and improve discount by 9 points across the next term.
The Licensing Edge
Weekly vendor and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.