The EA renewal was the one day Microsoft had to earn your business again
Microsoft is steering Enterprise Agreement customers onto the Microsoft Customer Agreement at renewal. The move is sold as modernization, and it also removes the renewal cliff that gave you leverage. The MCA is an evergreen digital contract that never expires, so it has no scheduled moment forcing Microsoft to compete, and estates that do not build their own review event simply stop negotiating. The contract you sit on decides when, and whether, Microsoft has to compete for your business.
Prepared by Redress Compliance · August 9, 2026 · Microsoft advisory. Based on roughly 25 to 40 Microsoft EA to MCA transitions advised 2024 to 2025.
Executive summary
The MCA is evergreen, so it removes the renewal cliff that was your strongest annual leverage moment.
The Microsoft Customer Agreement is a single evergreen digital contract that never expires and can be signed direct or through a partner, against the EA's fixed three-year term, and that term boundary is the structural difference that matters most for leverage.
Because the MCA never expires, there is no three-year deadline forcing a renegotiation, which removes administrative friction and, with it, your scheduled moment of maximum leverage.
The change sounds administrative; it is strategic, because the EA renewal was the one day Microsoft had to earn your business again, and on an evergreen contract that day never arrives unless you put it on the calendar yourself.
Terms can shift underneath you, because Microsoft prefers the MCA precisely because product rules can change without a renegotiation.
The MCA pulls its product rules from the Microsoft Product Terms, which Microsoft can revise, and on an evergreen contract those revisions reach you without a renewal at which to push back.
That is the trade the modernization pitch does not mention: the convenience of never renewing is paid for with the loss of the deadline that used to force the negotiation.
Customers who moved without engineering a review event lost one of their two main leverage moments, so the price protection clause becomes your only forward lever and has to be negotiated hardest.
Heavy committed Azure spend is the one case where the MCA is clearly the cleaner home.
For large cloud spend the MCA carries a Microsoft Azure Consumption Commitment that draws down against real usage, and estates with committed Azure cut administrative overhead by 10 to 20 percent on the MCA, so a heavy-Azure, volatile estate with a lean license team is the clear fit.
Keep the EA where a large stable seat base values the three-year price certainty, where the scheduled renewal is leverage you use, or where hard-won EA pricing is worth protecting.
The move is not automatic: eligibility, timing and your Azure shape all drive the choice, and for large estates the EA remains available even as the default path shifts.
The work is not the signature, it is the reconciliation, and 6 in 10 transitions surfaced entitlement gaps at cutover.
A clean move aligns entitlements, dates and commitments so you never pay twice or leave a coverage gap, and it takes 6 to 9 months: baseline every active license, align dates to avoid a coverage gap or a double-pay window, and lock price protection and Azure terms in writing.
The standard reseller pitch is that the MCA is simpler and evergreen so you should move and stop worrying about renewals; we disagree, because in 6 of 10 transitions the move quietly removed the customer's strongest leverage moment.
Engineer your own review event on the calendar, treat any annual price protection clause as the lever you negotiate hardest, and reconcile entitlements before signing.
EA versus MCA at renewal
| Dimension | Enterprise Agreement | Microsoft Customer Agreement |
|---|---|---|
| Term | 3 years fixed | Evergreen, no expiry |
| Leverage moment | Renewal cliff | None unless engineered |
| Azure fit | Legacy commitment | MACC and drawdown |
| Term changes | Fixed for the term | Can revise underneath you |
| Admin overhead | Higher | Lower |
The MCA is the right move for a heavy-Azure, volatile estate with a lean license team; the EA is right where a large stable seat base values price certainty and the renewal cliff as leverage.
When the MCA fits: heavy committed Azure, where a MACC is the cleanest home for large cloud spend; a volatile estate, where evergreen flexibility suits rapid change; and a lean license team, where lower administrative overhead frees scarce people.
When to keep the EA: a large stable seat base, where three-year price certainty is an asset; where leverage matters and you value the scheduled negotiating event; and where a strong discount history is worth protecting.
The move is not automatic, so eligibility, timing and your Azure shape drive the choice. The vehicle comparison sits in the EA vs CSP vs MCA guide, and the deeper channel read in the CSP vs EA pillar.
Executing the move cleanly
- Baseline entitlements: map every active license before the move, because 6 in 10 transitions surface entitlement gaps at cutover, and the gap you miss is one you pay to re-cover.
- Align dates: reconcile the renewal and term dates to avoid a coverage gap or a double-pay window at cutover, which is where the reconciliation effort actually goes, not the paperwork.
- Lock protections in writing: capture price protection and the Azure terms before signing, because on the evergreen MCA there is no later renewal at which to add them.
- Engineer your own review event: put a scheduled review on the calendar to replace the lost EA cliff, because estates that do not build one simply stop negotiating.
- Negotiate the price protection clause hardest: it is your only forward lever on an evergreen contract, and it is the one term worth trading a longer Azure commitment or a reference for. The renewal mechanics sit in the EA guide.
The Microsoft EA and MCA renewal guide
How to plan a Microsoft EA renewal that may shift to MCA-E, with the reconciliation sequence and the price-protection clauses.
Get the white paper →The lost leverage, and how to replace it
The change sounds administrative but it is strategic, because the contract you sit on decides when, and whether, Microsoft has to compete for your business.
The EA renewal was the one day Microsoft had to earn your business again.
And on an evergreen contract that day never arrives unless you put it on the calendar yourself, which is why the MCA removes the deadline that used to force the negotiation and estates that do not build their own review event simply stop negotiating.
The reconciliation is where the real work sits: baseline every active license before the move, align the renewal and term dates so there is no coverage gap or double-pay window at cutover.
And lock the price protection and Azure terms in writing, because on the evergreen contract there is no later renewal at which to add them.
For committed Azure spend the MCA carries a Microsoft Azure Consumption Commitment that draws down against real usage and reduces administrative overhead, which makes it the cleanest home for large cloud spend.
So the honest split is heavy-Azure and volatile estates toward the MCA and large stable seat bases that value the renewal cliff toward the EA.
The buyer-side move is to engineer your own review event on the calendar, treat any annual price protection clause as the lever you negotiate hardest, and reconcile entitlements before signing, because evergreen is convenient and convenience that costs you your only negotiating deadline is not free.
The seat-reclaim tooling to run before you commit sits in the M365 license optimizer, and the wider EA framework in the EA comprehensive pillar.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Microsoft EA to MCA moves, 2024 to 2025
Across roughly 25 to 40 Microsoft EA to MCA transitions we advised between 2024 and 2025, the contract change quietly reshaped customer leverage more than the price, and the common advice hands that leverage away.
The standard reseller pitch is that the MCA is simpler and evergreen, so you should move and stop worrying about renewals. We disagree:
Customers who moved without engineering a review event lost one of their two main leverage moments, the scheduled renewal cliff.
Transitions that surfaced entitlement gaps during the reconciliation, which is why the baseline before the move is the real work.
Estates with committed Azure spend cut administrative overhead by 10 to 20 percent on the MCA, which is the one clear advantage, but customers who moved without engineering a review event lost a scheduled leverage moment, and 6 in 10 transitions surfaced entitlement gaps at cutover.
Microsoft prefers the MCA because product terms can change without a renegotiation, so on an evergreen contract those revisions reach you without a renewal at which to push back, which makes the price protection clause your only forward lever.
The buyer-side sequence is to confirm whether your estate is still EA eligible at the next renewal, separate committed Azure spend from variable cloud consumption, pull a full entitlement baseline across every existing agreement.
Decide whether you value the renewal cliff more than the evergreen convenience, engineer your own review event on the calendar if you move, negotiate any annual price protection clause as your primary forward lever, run the seat optimizer before you commit.
And engage independent advisory before signing.
Evergreen is convenient, but convenience that costs you your only negotiating deadline is not free. The wider library sits in the Microsoft practice.
Your first five moves
- Confirm whether your estate is still EA eligible at the next renewal, because for large stable estates the EA remains available even as the default path shifts.
- Separate committed Azure spend from variable cloud consumption, because heavy committed Azure is the one case where the MCA is clearly the cleaner home.
- Pull a full entitlement baseline across every existing agreement, because 6 in 10 transitions surface entitlement gaps at cutover and the gap you miss is one you pay to re-cover.
- If you move, engineer your own review event on the calendar, to replace the lost renewal cliff, because estates without one simply stop negotiating.
- Negotiate any annual price protection clause as your primary forward lever, and reconcile entitlements before signing. The Microsoft practice runs the transition with you.
Frequently asked questions
What is the Microsoft Customer Agreement?
The Microsoft Customer Agreement is a single evergreen digital contract that replaces older paper agreements and does not expire. It can be signed direct with Microsoft or through a partner, and it underpins Azure MACC commitments and a growing share of Microsoft 365 buying.
Because it never expires, it removes the administrative friction of a scheduled renewal, and with it the scheduled moment of maximum leverage that a fixed-term Enterprise Agreement provides.
How is the MCA different from an Enterprise Agreement?
The EA is a fixed three-year term with a renewal cliff, while the MCA is evergreen and never expires. The structural difference is leverage: the EA gives you a scheduled negotiating moment that the MCA removes unless you engineer one.
The MCA also pulls product rules from the Microsoft Product Terms, which Microsoft can revise without a renewal at which to push back, so terms can shift underneath you on the evergreen contract.
Is Microsoft forcing customers off the EA?
No formal end date has been published, but Microsoft has narrowed EA eligibility and is steering more customers toward the MCA at renewal. Large stable estates can usually still keep an EA, but the default path is shifting.
The move is not automatic, so eligibility, timing and your Azure shape all drive the choice, and it is worth confirming whether your estate is still EA eligible at the next renewal before assuming the MCA is the only option.
Should you move from an EA to the MCA?
It depends on your Azure shape, estate size, and appetite to manage leverage yourself.
Heavy committed Azure spend favors the MCA, because a MACC is the cleanest home for large cloud spend and administrative overhead drops 10 to 20 percent, while a large stable seat base that values the renewal cliff and hard-won EA pricing often favors keeping the EA.
For some estates the MCA is clearly better; for others it is a quiet downgrade in negotiating position.
What is the main risk of moving to the MCA?
Losing your strongest leverage moment. Because the evergreen contract has no renewal cliff, there is no scheduled deadline forcing Microsoft to compete, so estates that do not build their own review event simply stop negotiating.
You must engineer your own review event on the calendar to replace the lost renewal, and negotiate any annual price protection clause as your primary forward lever, because on the evergreen MCA that clause is the only scheduled point at which the price is contestable.
How long does an EA to MCA transition take?
Plan 6 to 9 months for a clean move. The effort is in reconciling entitlements, aligning renewal and term dates, and avoiding a coverage gap or a double-pay window during the cutover, not in the paperwork itself.
Baseline every active license before the move, because 6 in 10 transitions surface entitlement gaps at cutover, and lock the price protection and Azure terms in writing before signing, since there is no later renewal at which to add them.
Your 2027 Renewal Is Not Your 2024 Renewal
Session 1 of the Microsoft EA Renewal 2027 Series. The discount levels are gone, the suites cost more, support multiplies both, and the EA itself is only committed through 2027. What changed, what it does to your renewal, and where you should already be today.
