The criterion that now separates Microsoft renewal negotiators is vehicle fluency: whether the firm can price your estate across EA, MCA-E and CSP — with the price protection, discount and commitment clauses each one carries — rather than just haggle inside the contract you already have. This guide covers what a Microsoft renewal engagement involves in the migration era, the criteria and questions that expose real depth, the warning signs, and how fees are structured. It names no firms; see the firms that do this work →
Published 12 November 2025 · Last reviewed 2 February 2026
For three decades a Microsoft renewal meant re-signing an Enterprise Agreement at a better or worse discount. That frame is gone for most organisations. Microsoft stopped signing new EAs for most commercial customers in early 2025, removed the old A–D volume price levels from the EA price list, and from 1 November 2025 stopped renewing EAs below roughly 2,400 seats altogether. From March 2026 it began actively moving EA customers holding Azure consumption commitments onto MCA-E at renewal. If your EA survives, it is because your estate is large and stable; for everyone else, the renewal is the vehicle decision — MCA-E direct, CSP through a partner, or some split of the two.
That changes what you are hiring. A negotiator who treats this as a discount conversation misses that the EA's defaults — a price list locked for the term, an annual true-up, organisation-wide platform pricing — do not carry into MCA-E unless they are negotiated back in as bespoke clauses. The engagement therefore starts with a baseline: entitlements and assignments across Microsoft 365 plans, Azure commitment consumption against its runway, unified support spend, on-premises server estate and its CALs, and the shelfware a true-up history tends to hide. Each commercial path is then priced before talks open, timed against Microsoft's 30 June fiscal year-end and its quarter ends, when deal desks have the most room.
Renewals also surface compliance pressure in softer clothing. A “licensing health check” or SAM engagement offered around renewal time feeds the same data a formal review would; how you respond is a negotiation decision as much as a technical one. If a formal audit is already open, that is a different engagement — see the Microsoft audit defense page, one of the seven services the directory covers.
This guide is general information about selecting an advisor for Microsoft renewal and contract negotiation, not legal or licensing advice for your situation. It names no firms; the Microsoft firm directory lists providers with balanced pros and cons, listed, not ranked.
Microsoft renewal advice is sold by five provider types with five different incentive structures. None is wrong for every deal; each is a trade-off to weigh deliberately — and the Microsoft market has a structural wrinkle the others lack: the licensing solution partner who historically transacted your EA may also be bidding to advise on its replacement.
| PROVIDER TYPE | STRENGTH ON A MICROSOFT RENEWAL | THE TRADE-OFF TO WEIGH |
|---|---|---|
| Independent boutique | Buyer-side only; EA-to-MCA-E and CSP pricing comparisons are core trade; benchmark data from repeated Microsoft closes | Smaller bench than the large firms; verify the Microsoft team's depth survives one key departure |
| Reseller / LSP practice | Knows your transaction history; handles quoting and execution inside an existing supply relationship | Margin and Microsoft incentives on what you buy create a structural interest in the outcome it is advising you on — sharpened where CSP is the destination |
| Big 4 / large SI practice | Global reach for multi-country agreements; process rigour; board-level cover on a platform decision | The same house often holds Microsoft alliances or cloud-migration revenue tied to the estate under negotiation |
| Law firm | Contract drafting, privilege, contested interpretation of legacy terms | Not a licensing-data team; pairs with a consultancy rather than replacing one |
| Tooling / platform vendor | Continuous assignment and consumption data that feeds the baseline | A platform is not a negotiator; services arms vary widely in commercial depth |
Whatever the type, the structural question is constant: does the firm earn anything from Microsoft, from reselling its licenses, or from the migration work a renewal decision would create? Factual ties are not disqualifying, but they belong on the table before you share your position. The independence test is the cross-vendor version of this question.
Vehicle mechanics, not vehicle slogans. Ask a candidate what a customer gives up moving from EA to MCA-E and listen for specifics: term price protection becomes a clause you must negotiate, the annual true-up disappears into monthly billing, and discounts become bespoke rather than programmatic. A firm that has closed these migrations can tell you which protections Microsoft has conceded in writing and which requests routinely die. The EA vs MCA-E comparison covers the program facts; your candidate should know them cold and go beyond them.
Plan-mix economics. Most Microsoft renewals are decided inside the Microsoft 365 line: the E3-to-E5 step-up, the Copilot add-on, and the July 2026 repackaging that moved more security components into E5 all change what a seat should cost. A negotiator should model your plan mix from assignment and usage data, not accept the incumbent mix as given — the Copilot vs E5 question alone can move a renewal by more than the headline discount.
Azure commitment realism. A consumption commitment sized on optimism becomes a liability at renewal. Strong firms test your actual run-rate against the committed runway, model the trade between commitment size and discount depth, and treat commitment flexibility — carry-over, re-phasing, eligible-service breadth — as negotiable terms, because they are.
Calendar craft. Microsoft's commercial flexibility peaks into its 30 June fiscal year-end and, secondarily, at quarter ends. Ask what concessions tend to appear only late, what must be tabled early, and how the firm avoids your expiry date landing you in Microsoft's strongest quarter with no alternative priced.
Named references on your deal shape. A 60,000-seat multi-country agreement, a 3,000-seat estate forced off its EA, a CSP consolidation — each rewards different experience. Ask for anonymized references on your size and structure, and confirm the named individuals, not the brand, did the work.
A destination before a baseline. A firm certain you belong on MCA-E — or certain you should fight to keep the EA — before seeing your assignment data, Azure run-rate and contract stack is selling a conclusion, not advice.
Gain-share-only pricing pushed hard. Contingency fees measured against Microsoft's first proposal reward inflating the opening number, not improving the outcome. The model has legitimate uses; insistence on it is the flag. The fee models guide explains the mechanics.
Undisclosed transaction interest. If the advisor or an affiliate would also transact the CSP subscriptions or bid for the migration work, the advice and the pipeline interest need explicit separation — ask how, in writing.
“We know the account team personally.” Familiarity claims cut both ways: a firm whose value rests on its relationship with Microsoft has an interest in keeping that relationship warmer than your deal requires.
No appetite for the walk-away math. A negotiator unwilling to price reducing E5 counts, trimming the Azure commitment, or moving workloads is negotiating Microsoft's numbers instead of yours.
1. Walk me through the last EA-to-MCA-E migration you negotiated: what price protection did the client keep, and what did it have to trade for it?
2. How would you decide, from our data, whether MCA-E, CSP or a split serves us — and at what seat count does that answer change?
3. What does our leverage look like if we shrink the renewal — fewer E5 seats, a smaller Azure commitment — and have you priced that path for a client who executed it?
4. Which concessions have you seen Microsoft's deal desk grant only in June, and which must be tabled in the first proposal?
5. Who, by name, would staff this engagement, and how many Microsoft renewals of our size has each of them closed in the past two years?
6. Does your firm or any affiliate earn revenue from Microsoft, from reselling its licenses or CSP subscriptions, or from migration and deployment work?
7. If Microsoft offers a Copilot or E5 promotion late in the negotiation, how do you evaluate it against the discount structure already on the table?
The answers matter less as facts than as reflexes. A firm that answers question three with a costed scenario rather than a warning that shrinking is impossible is negotiating for you. The foundation guide 20 questions to ask extends this list beyond Microsoft.
Four models dominate. Fixed-fee projects scoped to the renewal event suit most negotiations because the endpoint is set by the contract date. Day-rate advisory fits narrower support, such as reviewing Microsoft's paper behind your own procurement team. Gain-share ties the fee to negotiated outcomes and needs a carefully defined baseline to avoid the inflation problem above. Retainers make sense when the renewal sits inside a longer programme — a phased cloud migration or an ongoing Microsoft managed SAM arrangement. We publish no prices anywhere on this site; models and their incentives are the useful comparison, and the fee models guide treats them in depth.
Whichever model a firm proposes, ask it to map the fee to your renewal timeline in writing. A proposal that cannot say what happens to the fee if Microsoft moves the goalposts — an early migration offer, a mid-term repackaging like the July 2026 E5 change — has not been stress-tested.
Firm-agnostic guides — when you are ready to compare actual firms, the Microsoft directory lists them with balanced pros and cons.
Choosing help for a net-new Microsoft deal →
What the forced migration changes →
Who your advisor really works for →
Fixed, day-rate, gain-share →
See the firms that do this work →
Every field guide on the site →
Twelve months before expiry is a sound default, and longer if your renewal doubles as a vehicle decision. If your Enterprise Agreement can no longer be renewed, the move to MCA-E or CSP changes billing, price protection and discount mechanics, and the alternatives that create leverage take months to model and validate.
Not necessarily, but the team on your engagement must show provable Microsoft depth: fluency in MCA-E and CSP commercial terms, Microsoft 365 plan composition, Azure commitment structures and Microsoft’s fiscal calendar. A multi-vendor firm with a named Microsoft bench can serve well; a generalist without one usually cannot.
Usually yes. An Azure consumption commitment is one of the strongest levers in a Microsoft renewal, and from March 2026 Microsoft has been moving EA customers holding such commitments onto MCA-E at renewal — which puts the commitment’s size, term and flexibility on the table whether you raise it or not.
This guide is firm-agnostic and explains how to evaluate candidates. The Microsoft renewals page lists the firms that actually do this work, each with balanced pros and cons, listed alphabetically and never ranked.
No. This is a directory, not a ranking. Firms appear in neutral alphabetical order with balanced pros and cons. Independence is shown as a pro; reseller, Big-Four or vendor-side ties are shown as a con — both stated as factual trade-offs for you to weigh.
Tell us your Microsoft renewal date, the agreement shape and where things stand, and we will route your brief to firms that genuinely cover Microsoft renewal negotiation. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.