The Microsoft Enterprise Agreement true-down window opens only at the renewal anniversary, so the quantities you carry into the next three-year term are fixed at that single moment, and an estate that has not removed shelfware by then pays for it until 2029. A renewal is not an administrative event. It is the one negotiation in the cycle where committed counts can fall rather than only rise. Treating it as a 60-day procurement task forfeits the advantage. Treating it as an 18-month program captures it.
The three-year EA cycle
An Enterprise Agreement runs for 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, including discount, sits on top of the quantity you commit to at renewal. The mechanics of the underlying agreement are covered in our Microsoft EA complete guide.
The 18-month renewal timeline
The estates that renew well start a full 18 months before anniversary. The work front-loads, because the data takes months to assemble and the negotiation cannot begin until the true-down case is built.
| Months before renewal | Action |
|---|---|
| 18 to 15 | Commission an independent license baseline. Count deployed versus owned by product. |
| 15 to 12 | Identify shelfware, duplicated CALs, and over-provisioned suites. Build the true-down target. |
| 12 to 9 | Benchmark current pricing. Model NCE transition and channel options. |
| 9 to 6 | Open the renewal conversation. Introduce competitive tension on at least one 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. |
The most expensive mistake is starting at month three. By then there is no time to build a baseline, so the renewal defaults to the existing quantities plus the standard uplift, which is exactly the outcome a renewal strategy exists to prevent.
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 to 25 percent shelfware after three years of true-ups, departures, and project cancellations. Recovering that is the largest single lever in most renewals. The detailed method is in our Microsoft EA true-down guide.
The shelfware audit lever: 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 to 20 percent of committed seats that a default renewal would have carried forward unchanged.
The NCE transition decision
Microsoft is moving Enterprise Agreement workloads onto the New Commerce Experience (NCE) commercial model, which changes how term commitments and mid-term cancellations work. Under NCE, annual and three-year subscriptions carry a short cancellation window of 168 hours from purchase or renewal, after which the term is locked. This makes accurate quantity setting at renewal even more important, because the flexibility to back out shrinks once the term starts. Model the NCE choice against your forecast volatility using our NCE pricing guide before committing to a term length.
Levers beyond quantity
Once the baseline is reset, the discount levers apply. Competitive tension on Azure or on a security workload, timing against Microsoft fiscal year-end on 30 June, consolidation of fragmented spend, and a documented price benchmark all move the negotiated rate. 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, and the channel question is in our EA versus CSP cost analysis.
Common renewal pitfalls
Three pitfalls recur. The first is renewing on committed quantity rather than actual usage, which carries shelfware into the next term. The second is letting the timeline compress, which removes the advantage that only preparation creates. The third is treating Copilot and other new products as add-ons negotiated late, rather than folding them into the renewal where they carry the most weight. Avoiding all three is the difference between renewing the estate you have and renewing the estate you bought three years ago.
Building the renewal baseline
The baseline is the one deliverable that determines whether a renewal saves money, and it takes three to four months to build properly. It reconciles three data sets: what the agreement says you own, what is actually deployed, and what is actually used. Deployment data comes from the Microsoft 365 admin center, Entra sign-in logs, Configuration Manager, and any software asset management tooling in place. Usage data, which is distinct from deployment, comes from active-user reports that show which assigned seats are dormant. The gap between owned and used is the true-down target. A baseline that stops at deployment misses the dormant-seat layer, which is often the largest single source of recoverable cost.
Sequencing the negotiation
A Microsoft renewal is won in a sequence of moves, not a single ask. The disciplined cadence opens around month nine with the baseline and a documented benchmark, introduces a credible alternative on at least one workload by month seven, exchanges proposals through months six to four, and reserves the final commercial concessions for the fiscal-quarter close. Each round trades something the buyer can give, such as a longer term or a larger Azure commitment, for something Microsoft can give, such as discount, price protection, or true-down acceptance. The mistake to avoid is revealing the full budget early, which removes every subsequent round of negotiation.
| 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 fiscal-quarter window | Final concession against quota |
Price protection and the anniversary true-up
The annual true-up is the mechanism that adds seats during the term, and it should be priced at signature rather than at the prevailing list. By default, seats added at each anniversary are billed at the contracted rate, but 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, which erodes the original discount over the term. The renewal is the moment to confirm that growth is priced at the locked rate and that the uplift at the next renewal is capped.
Co-term and consolidation opportunities
Fragmented agreements cost more than a single consolidated one. Many enterprises carry multiple enrollments, separate subsidiaries on their own contracts, and overlapping CSP arrangements that each sit below the price level the combined estate could command. A renewal is the natural point to co-term these agreements onto one anniversary and consolidate the seat count, which can push the estate into a higher price level and open the structural discount that comes with it. The benchmark ranges that consolidation can reach are in our Microsoft discount benchmarks, and the channel trade-offs are in the EA versus CSP analysis.
The four metrics that decide a renewal outcome
A renewal can be scored on four numbers, and tracking them turns a subjective negotiation into a measurable one. The first is the true-down percentage, meaning the share of committed quantity removed against the prior term, where a well-run renewal recovers 12 to 20 percent. The second is the blended discount improvement over the current effective rate, where a strong outcome adds several points. The third is the renewal uplift cap, which protects the next term and should be held to a low single-digit percentage. The fourth is price protection coverage, meaning the proportion of the estate whose unit price is locked for the full term, which should approach 100 percent.
Setting targets for these four before the negotiation opens keeps the program honest. Without them, a renewal that simply repeats last year's quantities at a slightly better headline rate can look like a win while quietly carrying forward shelfware and exposing the estate to mid-term price increases. With them, the negotiation has a scorecard, and each concession the account team offers can be tested against whether it moves one of the four numbers in the buyer's favor.
The four metrics also frame the internal conversation with finance and the business. A CFO does not need the clause detail; the CFO needs to know how much committed cost was removed, how much the rate improved, and how much of the next three years is protected from increase. Presenting the renewal in those terms, rather than as a list of products and prices, is what turns a procurement task into a governed financial outcome and earns the mandate to start the next cycle 18 months early.
Aligning the internal stakeholders
A renewal is lost internally as often as it is lost across the table. The true-down case depends on data that lives outside IT sourcing: HR owns the headcount forecast, the business units own the project pipeline that drives demand, and finance owns the budget the renewal must hit. If these stakeholders are engaged only at the end, the true-down target cannot be defended and the renewal defaults to the safe option of repeating the current quantities. Bringing them in at the 15-month mark, when the baseline is being built, is what makes an aggressive true-down credible.
The business case for early alignment is straightforward. A renewal that removes 15 percent of committed seats and adds several discount points is worth millions over a three-year term, but only if the organization can stand behind the reduced counts when the account team pushes back. Stakeholder alignment converts a procurement assertion into an organizational position, and an organizational position is far harder for a vendor to erode in the final weeks before signature.
The throughline across all of this is that a Microsoft renewal rewards preparation more than it rewards bargaining skill in the final meeting. The estate that has built a baseline, aligned its stakeholders, documented a benchmark, and introduced a credible alternative has already won most of the negotiation before the closing call, because every concession the account team can offer has been anticipated and priced. The estate that arrives unprepared is negotiating only the size of its own increase.
The full renewal program, baseline through signature, sits in the Microsoft licensing pillar. For a managed renewal, our Microsoft advisory practice and software licensing advisory service run EA renewals as a structured 18-month engagement.