Only four MCA-E clause families are truly closed to amendment, and every one of them is buyable back at the order layer for roughly the 20% the 2026 uplift and discount-band removal already took
Microsoft standardized the MCA-E master terms and then let buyers assume the whole document is fixed. In practice the evergreen term, the standard commercial framework, the removal of Software Assurance, and the base audit and IP language are the only genuinely closed items, while price protection, uplift caps, swap rights, regulated-industry protections, and consumption commitments all remain writable in addenda, amendments, and the order. Knowing which is which decides whether you spend six weeks losing an argument or six weeks buying back a 12% discount band and an 8.3% E3 increase.
Prepared by Redress Compliance · September 9, 2026 · Microsoft advisory. EA and MCA-E transition engagements, 2024 to 2026.
Executive summary
The evergreen structure is the only non-negotiable that actually costs you money, because it removes the expiry date that generated 100% of your historical EA leverage.
An MCA-E is signed once and does not expire, so the negotiable surface moves entirely to the subscription order and the addendum layer, and your leverage has to be manufactured from renewal dates on individual subscriptions, Azure commitment timing.
And competitive workloads rather than from the master agreement.
The default MCA-E carries no price protection at all, which converts a fixed clause into a priced one: without explicit language, list changes flow through at the next anniversary and the 2026 stack lands at roughly 20%.
The M365 increases effective 1 July 2026 (E3 +8.3% to $39, E5 +5.3% to $60) sit on top of the November 2025 removal of volume discount levels, where Level D was around 12% off list, producing about $3 million a year of extra cost on a 25,000-seat E5 estate.
Microsoft has publicly conceded amendment rights in a narrow band, and that band is wider than most legal teams assume: regulated-industry amendments, publicity terms, and Azure-linked investment funds are all explicitly available.
The Data Protection Addendum, the Financial Services Amendment with its regulator access and penetration-testing provisions.
And the DORA Addendum in force for EU financial entities since January 2025 already contain quotable protections, including a no-penalty termination right on unresolved regulatory-change concerns.
The two concessions Microsoft has said no to on the record, five-year terms and ramped pricing, should be asked once and then converted into cash: the public-sector 10% annual phasing precedent is the template that gets accepted.
Microsoft's own government guidance phases suite increases above 10% total over multiple years with no more than 10% applied annually, which is the cleanest available anchor for a negotiated uplift cap in a commercial MCA-E.
The four closed clause families, and where the negotiable surface actually sits
Stop redlining the master. Four clause families are genuinely closed, and every hour spent arguing them is an hour Microsoft gets for free while your renewal clock runs down.
The evergreen non-expiring term is closed because it is the whole point of the program: it strips expiry-date leverage out of the relationship permanently.
The standard commercial framework with Level A list pricing as the default is closed because Microsoft spent two years dismantling Levels B, C, and D to get there (Level D was roughly 12% off list for 15,000-plus seats).
Software Assurance removal is closed by construction, since subscription SKUs cannot carry it, and support becomes a separate purchase.
Base audit, IP, and indemnity language is closed at the master layer, though it is bounded in the order and addendum layers, which is a different fight worth having.
Everything else that matters, price hold, uplift cap, swap rights, commitment sizing, the 5% monthly billing premium, and Copilot metered tails, lives in documents Microsoft's field can sign without a legal queue.
| Clause family | Amendable? | Compensating protection to demand | Where it lives |
|---|---|---|---|
| Evergreen non-expiring term | No | Order-level committed term with defined end date, plus written non-auto-renew | Order form |
| Level A default / discount bands | No | Order-level discount schedule restated annually, uplift cap at 10% | Order form |
| Software Assurance removal | No | Support credits, deployment funding, Azure investment funds tied to the purchase | Addendum plus order |
| Base audit and IP/indemnity | No at master | Notice period, scope limits, self-audit first, single-audit-per-24-months | Addendum, per bounding the Microsoft audit clause |
| Regulated industry (HIPAA, DORA, FSA) | Conditionally | Regulator access, penetration testing, no-penalty termination on unresolved regulatory change | Standing addendum |
| Publicity and reference rights | Conditionally | Written pre-approval per use, no logo use by default | Amendment |
| Price hold, uplift cap, swap, commitment sizing | Yes | The full ask, in writing, in the order | Order form |
The table cannot show you the behavioral pattern. Microsoft's negotiators are trained to answer clause-level asks with a single line: "the MCA is standard." That answer is true and it is also a trap, because it invites you to keep litigating the master while the commercially valuable asks go unmade.
Every one of the closed items above has a paid or contractual equivalent that never reaches Microsoft legal, because the order form and the annual purchase schedule are field-signable.
A price hold in an order form and a price hold in the master are worth the same money to you and are worth radically different amounts of internal friction to them.
Practically: build one page listing your four closed items with the compensating ask beside each, hand it to the account team, and say you will not table master redlines.
That single move converts a six-week legal stalemate into a commercial conversation, and commercial conversations are where the clauses worth fighting for actually get won.
Price protection is not a term, it is a purchase: what the price hold costs and what it must say
The EA three-year lock did not transfer. Under MCA-E, absent an explicit clause, list price changes flow through at your next anniversary, and Microsoft will not volunteer to fix that. Treat the hold as a line item you buy with commitment, not a term you request.
Scope it precisely or it is worthless: all in-scope subscription SKUs, a freeze on list price rather than on discount percentage (a percentage freeze on a rising list is not protection), applicable at anniversary and at mid-term true-up.
And surviving seat growth so that expansion seats price at the frozen rate rather than the current one.
Get the exact price hold language tabled early, because retrofitting it after the order is signed costs you the entire renewal cycle.
Two dated levers are still live. Renewals completed before 1 July 2026 hold current rates for the full committed term under NCE mechanics, which is the cheapest price protection available: pulling a renewal forward avoids the 8.3% E3 and 5.3% E5 increases outright.
Separately, the 5% premium on annual subscriptions billed monthly, introduced April 2026, is a standardized uplift, not a discount question. Break it out as its own line, then either waive it or capitalize it by moving to annual billing.
On a 25,000-seat E5 estate, that 5% is real money and Microsoft treats it as recoverable if the billing cadence changes.
A strong outcome, in numbers: a 36-month list-price hold on 100% of the committed base, an uplift cap at 10% annually on anything outside it (see negotiating a renewal uplift cap), monthly billing premium waived or billing moved to annual, and expansion seats priced at the frozen rate.
Microsoft will counter with a 12-month hold on a subset and a percentage discount restated annually. That counter is worth roughly nothing after two list moves; hold the line on list-price mechanics.
First move: pull your current committed spend by SKU, calculate the 2026 uplift plus the lost discount band as one combined number (in our experience the stacked effect lands near 20%), and put that figure in the room as the price of the hold you are asking for.
Move from EA to MCA without losing your terms
How to move from a Microsoft EA to the MCA without losing discounts or terms: the transition traps, the price protections to keep, and the timing.
Get the white paper →The analysis: Microsoft did not remove your leverage, it relocated it to the order form
The Enterprise Agreement's expiry date was a blunt instrument, but it worked. A fixed end date created a moment where Microsoft's revenue was genuinely at risk and yours was not, and every concession any of us ever extracted traced back to that asymmetry.
The evergreen MCA-E design removes the date deliberately: you sign once, subscriptions sit on top, and there is no cliff to negotiate against. What Microsoft did not do, and could not do, is remove the commercial risk.
It relocated all of it into the order form, a document its own field organization treats as administrative paperwork rather than legal paper. That mismatch is the opening.
Understand what "standard terms" actually means inside Microsoft. It is a resourcing decision, not a legal one.
Microsoft has hundreds of thousands of MCA-E customers and a legal function that cannot review bespoke master redlines at that volume, so the master gets frozen and the review capacity gets pushed into two places: the standing addenda (Data Protection Addendum, Financial Services Amendment.
DORA Addendum) and the order.
Read that correctly and it tells you exactly where Microsoft will bend, because bending in those places costs Microsoft process capacity it has already budgeted for. A demand to amend the master triggers a review Microsoft has structurally decided not to perform.
A demand written into the order triggers a discount approval, which is a routine, quantified, delegated decision your account team makes weekly.
The channel change compounds this. Under MCA-E the LSP has no transactional relationship with you, which means the party that historically modeled your true-up exposure, priced the alternatives, and told you when the quote was bad has been removed from the transaction.
Microsoft is now the sole interpreter of its own paper and the sole source of the math. Every buyer who has not replaced that function with independent modeling is negotiating against a counterparty holding the only calculator in the room.
Then there is the calendar. Reports of MACC customers being moved to MCA-E from March 1, 2026 arrive alongside Microsoft's refusal to notify specific customers which cloud EAs in direct markets are affected. Ambiguity is the tactic.
It is manufactured urgency, and it collapses the moment you send a written request for your named entity's migration date, the governing agreement at migration, and confirmation of which existing amendments carry over. Ask in writing. Do not sign anything until you have the answer in writing.
This is why the T-3 to T-6 starter loses arguments the T-12 to T-18 starter wins. The extra months are not preparation time, they are manufacturing time.
They are what let you complete a competitive workload assessment, get a Google or AWS proposal onto real letterhead, run an entitlement true-down before Microsoft sets the baseline, and reach the quarter where your account team needs your number. Start at T-3 and you have opinions.
Start at T-12 and you have alternatives.
Without an expiry date, you synthesize one. Stagger subscription anniversaries so a meaningful slice of spend comes up for reduction every few months rather than all at once. Hold the Azure commitment renegotiation as a separate, timed event so it does not get absorbed into the M365 conversation.
Name the workloads under competitive review and attach seat counts to them. Then take the fight to the order: price hold language, uplift caps, swap rights, reduction windows.
Buyers who accept the master and fight the order routinely land 15 to 20 points better than buyers who spend six weeks arguing about indemnity language Microsoft has no mechanism to change.
Compensating protections: what to demand where the clause is genuinely fixed
Where the clause is closed, price the loss and recover it elsewhere in the same order. Software Assurance is gone because MCA-E is subscription-based, so support is now a separate purchase and a separate negotiation.
Do not let it become an unpriced afterthought: put Unified or Premier into the same order document with committed response times by severity, a stated annual price for the full term, and a multi-year support price hold.
Support pricing floats on your Microsoft spend, so an uncapped support line quietly inflates alongside the 8.3% E3 and 5.3% E5 increases you are already absorbing.
Against the evergreen term, the compensating right is anniversary-level flexibility. Demand subscription-level reduction and termination rights at each subscription anniversary with a defined notice window, plus a written migration-notice period before Microsoft moves you between agreement vehicles.
Evergreen without a reduction right is a perpetual commitment with an annual price escalator attached.
On audit, the base language in the master will not move, so bound it in the addendum and order layer instead: advance written notice, defined scope, self-audit-first, named-tool restrictions, and a remediation window before any financial claim.
The specific redlines that survive review are covered in our work on bounding the Microsoft audit clause, and the same language is far more likely to be accepted attached to an order than proposed as a master amendment.
For indemnity and jurisdiction, the standardized master is the wrong battlefield.
Regulated buyers should route through the Financial Services Amendment, which already carries regulator access, penetration testing provisions, and the right to terminate an Online Service with no penalty where a regulatory-change concern cannot be resolved.
Read the fine print: no prepaid amounts, including annual fees, are refunded.
That right is only worth something if prepayment is negotiated separately, so keep billing frequency annual-in-arrears where possible, avoid multi-year prepay unless it buys a hard discount, and note the 5% monthly-billing premium before you treat monthly as the safe default.
Trade currency: Copilot, E7, and the give-backs that fund the concessions you want
Everything else in the MCA-E conversation is a cost line. Copilot is the one thing on the table the Microsoft field wants badly enough to pay for in contract terms, and you should price it accordingly.
The list is $30 per user per month on annual commitment, which takes an E3 seat to $69 and an E5 seat to $90 all-in once the 1 July 2026 increases land.
Microsoft has been running the discount ladders itself: 15% at 10 or more seats brought the effective rate to $25.50 (that offer expired 30 June 2026), and a separate three-year 15% program at 300 or more seats runs 1 June to 30 September 2026. Read those programs correctly.
When the vendor is publishing standing discounts, discount is the cheap currency and terms are the expensive one.
Trading a 2,000-seat Copilot commitment for another five points off is a bad trade you can make in an afternoon; trading the same commitment for a 36-month price hold on the full M365 stack and a capped renewal uplift is the trade that survives contact with the 2029 renewal.
E7 arrived 1 May 2026, deliberately ahead of the July increases, and it exists to reset the anchor upward before the uplift hits. Treat it as inventory the field needs to move, not as an upgrade you are lucky to be offered.
The give-backs sitting inside the new packaging are real but they carry tails: E5 now includes Security Copilot at 400 Security Compute Units per 1,000 licensed users per month, with anything above that metered through Azure.
In our experience with metered AI attachments, the overage line is the one nobody models and everybody pays. Demand a hard annual dollar ceiling on SCU overage, written into the order, with consumption above the cap requiring a signed change order rather than an invoice.
A strong outcome on a mid-size estate looks like this: Copilot at or below $25.50 effective, a three-year hold on E3 and E5 unit pricing, an uplift cap of CPI or 3% (whichever is lower) at renewal, and a stated SCU overage ceiling.
That package is worth roughly the 20% the uplift and band removal already took back.
Evidence base: what we see repeat across MCA-E transitions
The July 2026 uplift stacking on the November 2025 discount-band removal produces roughly 20% net, about $3 million a year on a 25,000-seat E5 estate formerly on Level D.
Every EA, EA Subscription and MPSA customer defaults to Level A list pricing after cutover, so the 15,000-seat discount vanished without a price increase being announced.
The calendar has been consistent since new EA enrollment closed in October 2024: sub-2,400-user renewals blocked after 1 November 2025, MACC customers reportedly moving from 1 March 2026.
And Microsoft's public position that cloud EAs in direct markets go to MCA-E without customer-specific notification.
That last point is not an administrative gap, it is pressure by design. Force a written date.
Buyer-side failures repeat with equal reliability: assuming custom EA amendments and FromSA SKUs carry across (they do not), spending six weeks redlining the master when the money sits in the order form, discovering the price-lock loss after signature rather than before.
And opening at T-3 to T-6 when the walk-away is already gone.
Vendor behavior is equally scripted: "the MCA is standard" as a conversation-ender, deliberate ambiguity about your transition date, and a discount-only counter that leaves the uplift entirely uncapped.
Our analysis of the 2026 increase mechanics shows the discount narrowing did more damage than the list move.
- 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
Your first five moves
- Get the migration timeline in writing before you get in a room. Microsoft has told the market that cloud EAs in direct markets move to MCA-E without notifying specific accounts, so send a written request naming every enrollment, anniversary date, and MACC balance, and treat any refusal to commit dates as your evidence that the pressure is manufactured; a strong result is a named cutover date at least nine months out.
- Model the stacked 20% before the first call, not after the quote. The July 2026 uplift (E3 +8.3% to $39, E5 +5.3% to $60) sits on top of the November 2025 removal of Level D's roughly 12% discount, and a 25,000-seat E5 estate on Level D is looking at about $3 million more per year; walk in with your own seat-by-seat number so the reseller's spreadsheet is the second one on the table.
- Table the price hold and uplift cap as order-form language, not master redlines. Microsoft will not amend the MCA-E master, and arguing about it burns six weeks; instead put a 36-month price hold on committed quantities and a 10% uplift cap at anniversary into the order and amendment layer, with true-up pricing frozen at the same rates.
- Route every compliance ask to the addendum layer. DPA, Financial Services Amendment, and DORA addendum carry real audit rights, penetration testing terms, and regulator access; asking for the same protections as master redlines gets a refusal you cannot walk back.
- Hold Copilot and E7 back as the paid trade. Do not name a Copilot number until hold length, swap rights, and a capped metered tail on Security Compute Units are all conceded in writing.
Frequently asked questions
Which MCA-E terms will Microsoft genuinely never amend?
Four families: the evergreen non-expiring term structure, the standard commercial framework including the Level A list-price default, the removal of Software Assurance and its attached benefits, and the base audit, indemnity, and IP language in the master.
Asking for edits to these consumes weeks and returns nothing. Every one has a compensating protection available at the order or addendum layer instead.
Can I still get a three-year price lock under MCA-E?
Yes, but only if you negotiate it explicitly. The MCA-E does not carry the EA-style three-year price lock by default, and without a clause, list price changes flow through at the next anniversary.
Push for a 36-month list-price freeze on the full committed base, written into the subscription order rather than the master agreement.
What amendments does Microsoft actually allow to the MCA-E?
Microsoft has conceded amendments for regulated-industry requirements such as HIPAA, GDPR, and financial services, changes to publicity terms, and the addition of investment funds tied to a specific Azure purchase.
Beyond that, protections live in standing addenda: the Data Protection Addendum, the Financial Services Amendment, and the DORA Addendum for EU financial entities since January 2025.
How much will the 2026 changes actually cost my organization?
The 1 July 2026 increases are E3 +8.3% ($36 to $39) and E5 +5.3% ($57 to $60), with Frontline plans up 25 to 43% (F1 $2.25 to $3.00, F3 $8.00 to $10.00).
Stack that on the November 2025 removal of volume discount levels, where Level D was roughly 12% off list, and the combined impact is closer to 20%. A 25,000-seat E5 estate previously on Level D faces roughly $3 million more annually.
Is a five-year MCA-E term or ramped pricing achievable?
Microsoft has said on the record that five-year terms and ramped pricing deals will not be available anytime soon.
Ask once to establish the record, then convert the refusal into cash: a longer price hold, a 10% annual uplift cap modeled on Microsoft's own public-sector phasing precedent, or expanded swap rights.
When should I start an MCA-E negotiation?
T-12 to T-18 months. Starting at T-3 to T-6 eliminates walk-away leverage and forces acceptance of Microsoft-preferred terms, and that effect is worse under MCA-E because there is no master-agreement expiry to create natural pressure.
The extra months are used to stagger subscription anniversaries, sequence Azure commitment timing, and validate competitive alternatives for named workloads.
What happens to my custom EA amendments when I move to MCA-E?
Assume none of them carry over unless Microsoft confirms otherwise in writing. Organizations relying on on-premises products, FromSA SKUs, or custom amendments regularly hit obstacles in transition.
Inventory every negotiated protection in your current enrollment before the first migration meeting and get a written position on each one, so you know exactly what you are being asked to give up.
