Microsoft EA vs MCA-E: Which Agreement Is Right for Your Enterprise in 2026

The Context: Microsoft's Migration Campaign

From January 2025, Microsoft began formally notifying EA customers that certain EA renewals were no longer available. The migration drive accelerated in 2026 — from March 2026, Microsoft is actively migrating EA customers with Azure consumption commitments (MACC) to MCA-E. Organisations with fewer than 2,400 users are increasingly directed toward MCA-E or CSP rather than EA renewal.

Microsoft's commercial rationale is straightforward. The EA's three-year price lock prevented Microsoft from realising the full benefit of annual price increases, which have run at 8 to 25 percent across different product categories over the past three renewal cycles. Under MCA-E, Microsoft can reset pricing annually. For a $10 million annual Microsoft spend, a 10 percent annual increase over three years without a price lock adds approximately $3.3 million in cumulative cost versus a locked EA baseline. That is the commercial value Microsoft extracts from the migration — and the commercial cost the buyer absorbs if they accept MCA-E without protection.

Enterprise Agreement: What It Delivers

The EA is a three-year volume licensing contract requiring 500 or more users or devices. It provides organisation-wide licensing coverage for included products, compulsory Software Assurance for all licences, and a fixed price for the full three-year term. The annual True-Up mechanism handles additions above the initial order quantity at the contracted price.

The pricing framework under EA is the most favourable available for large Microsoft workloads. Current EA discounts range from 10 to 20 percent off list for standard M365 workloads including the E1, E3, E5, and E7 tier spectrum. E7, which sits at the top of the M365 SKU stack above E5 and bundles AI, advanced security, and compliance capabilities previously sold as E5 add-ons, is most effectively licensed within a structured EA negotiation. Azure Reserved Instances and Savings Plans negotiated as part of the MACC commitment deliver compute savings of 65 to 72 percent versus pay-as-you-go.

Software Assurance provides deployment planning services, training vouchers, home use rights, and licence mobility rights. For organisations that actively consume these benefits, SA adds 10 to 15 percent value on top of the licensing cost — value that disappears under MCA-E.

MCA-E: What It Actually Delivers

MCA-E is an evergreen agreement — no fixed term, no mandatory organisation-wide coverage, annual subscription renewal at Microsoft's current list pricing. The structure that Microsoft presents as flexibility is genuinely more flexible in some dimensions. There is no requirement to commit to a user population at the start of the term, and subscriptions can be added with less administrative friction than an EA amendment.

The commercial asymmetries become clear when you read the MCA-E terms rather than accepting Microsoft's summary. Pricing at each annual renewal is at Microsoft's current rates — no price lock, no guaranteed discount floor, no volume-based pricing tiers. The ability to reduce subscriptions is restricted to a seven-day window after each annual order — meaning that if your user count falls or a product deployment fails to materialise, you have one week per year to reduce cost. Outside that window, you are committed for the full annual term.

Pricing can be negotiated under MCA-E, but the negotiation structure is different from EA. There is no baseline discount framework. Negotiation happens on a per-subscription basis, and the absence of volume tiers means that scale advantage is not automatic — it must be asserted and defended at every renewal. Organisations that accepted MCA-E without negotiated protections at their first renewal saw their account team remove EA-era discounts entirely, citing MCA-E as a new commercial relationship that reset the pricing baseline.

Head-to-Head on the Dimensions That Matter

Price certainty: EA locks pricing for three years. MCA-E provides no price lock — pricing resets annually at Microsoft's discretion. In a Microsoft environment where list prices have increased at 8 to 25 percent in each of the past three cycles, this is the single most significant structural difference between the two agreements.

Software Assurance: EA includes compulsory SA with a defined benefit catalogue. MCA-E does not support SA. The most financially material SA benefits for large enterprises — deployment planning services (funded consultancy), training vouchers, and licence mobility rights — are lost entirely under MCA-E.

Discount structure: EA negotiated discounts are volume-based, aggregated across the full enterprise scope, and benchmarked against comparable organisations. MCA-E negotiation is per-subscription, with no volume framework and no guaranteed renewal discount. In practice, MCA-E aggregate discounts are consistently lower than equivalent EA discounts for large, complex Microsoft footprints.

True-Up mechanism: EA has a defined annual True-Up process for additions. MCA-E handles additions through ongoing subscription management — simpler administratively, but it means there is no structured annual optimisation event where right-sizing decisions are formalised and negotiated.

Flexibility to reduce: EA is less flexible mid-term — organisation-wide commitments create a licence floor. MCA-E theoretically allows reductions but restricts the execution window to seven days per subscription per year. In practice, the flexibility advantage of MCA-E for large enterprises is considerably smaller than Microsoft's commercial narrative suggests.

Audit exposure: EA has defined compliance terms and a clear True-Up mechanism for resolving over-deployment. MCA-E's compliance terms are more fragmented across individual subscription orders. For organisations with complex Microsoft footprints, EA's unified compliance framework reduces audit risk compared to managing dozens of individual MCA-E subscription agreements.

The Case Where EA Is Clearly Right

If your organisation has more than 500 users, a significant M365 workload across the E1, E3, E5, and E7 SKU stack, material Azure consumption under a MACC commitment, and a Procurement function capable of managing the annual True-Up and three-year renewal cycle, the EA is the correct primary vehicle. The combination of price certainty, Software Assurance, and structured negotiation framework produces better total commercial outcomes than MCA-E for this profile — typically by $500,000 to $2 million per year for large enterprise Microsoft spends.

The Case Where MCA-E Cannot Be Avoided — and What to Do About It

If Microsoft declines to offer an EA renewal, or if your organisation falls below the 2,400-user threshold that increasingly triggers mandatory MCA-E migration, the commercial task is not to accept MCA-E on default terms — it is to negotiate MCA-E terms that include the protections an EA would have provided.

The critical MCA-E negotiation objectives are: a defined discount percentage that applies at every annual renewal for a specified period (typically three years), not just at initial signature; a price increase cap that limits the uplift at each renewal; a subscription reduction window that provides more than the default seven days; and SA-equivalent benefits or credit against the loss of SA value. None of these are in the standard MCA-E terms. All of them are achievable with structured negotiation, particularly during Microsoft's Q4 window (April to June) when field teams have maximum incentive to close deals.

Microsoft's field teams will resist these terms because they undermine the commercial value Microsoft extracts from MCA-E's annual pricing flexibility. The buyer's leverage comes from demonstrating credible alternatives — CSP through a competitive partner, Google Workspace for collaboration workloads, AWS for Azure-equivalent compute — and from engaging the negotiation during Microsoft's Q4 when deal pressure is highest.

Five Things to Negotiate Before Signing MCA-E

• Multi-year price protection: Push for a defined discount floor for a minimum three-year period. If Microsoft is unwilling to provide a three-year price lock equivalent, negotiate an annual price increase cap — for example, maximum 5 percent per year — written into the MCA-E order terms.
• Extended subscription reduction window: The default seven-day reduction window is commercially unworkable for large enterprises managing dozens of subscriptions. Negotiate a 30 to 60 day window or a quarterly reduction cycle that allows meaningful right-sizing.
• SA-equivalent benefit credit: Quantify the SA benefit value you are losing and negotiate either direct benefit equivalents (funded deployment services, training credits) or a discount uplift that compensates for the SA value loss.
• Renewal discount confirmation: Get Microsoft to confirm in writing that the negotiated discount percentage applies at each annual renewal — not just at initial signature. The standard MCA-E terms do not guarantee renewal discounts, meaning Microsoft can remove them at the next cycle.
• Azure commitment terms: If the MCA-E includes an Azure consumption commitment, negotiate the Reserved Instance and Savings Plan terms explicitly. MCA-E does not automatically carry over EA-era Azure discount structures.