Microsoft EA vs MCA-E:
The Transition Microsoft Wants and What It Costs You

Microsoft EA vs MCA-E: The Core Structural Differences

The Microsoft Enterprise Agreement (EA) is a fixed three-year volume licensing contract. At the point of signing, you commit to a defined licence volume at a locked price for the full three-year term. Annual true-up reconciliation allows you to self-correct overages once per year. Software Assurance benefits are included, covering deployment support, step-up licensing rights, and training vouchers. The EA's defining characteristic is predictability: you know your Microsoft cost for three years from day one.

The Microsoft Customer Agreement for Enterprise (MCA-E) is an evergreen agreement with no fixed term. It operates on a pay-as-you-go model: subscriptions renew annually or monthly, prices are set at Microsoft's current rates rather than locked at commitment, and there is no structured annual true-up process. Software Assurance is not supported. The MCA-E's defining characteristic is flexibility — you can add and remove subscriptions at will — but that flexibility is asymmetric: Microsoft retains the right to change pricing at renewal, while your ability to reduce commitments mid-term is restricted to a narrow seven-day window after each order. Before evaluating which agreement structure is right for your organisation, use our Microsoft EA renewal readiness assessment to understand your current contract exposure.

Why Microsoft Is Pushing the EA-to-MCA-E Transition

From January 2025, Microsoft began notifying EA customers that renewal of certain EA agreements is "no longer possible." From March 1, 2026, Microsoft is actively migrating EA customers on Microsoft Azure Consumption Commitment (MACC) plans to MCA-E. The primary affected segment is organisations with 500–2,400 users — below the threshold Microsoft now applies to EA renewals. For these organisations, the EA has effectively been retired as a purchasing option, and MCA-E is presented as the only path forward.

Microsoft's commercial motivation is clear: the EA's three-year price lock constrains Microsoft's ability to pass through annual price increases. MCA-E, with annual renewal and no price lock mechanism, gives Microsoft a pricing lever that the EA does not. The elimination of the volume discount tiers (Levels A–D) that previously applied below 2,400 seats from November 2025 means that MCA-E customers pay list price unless they individually negotiate, removing the automatic discount that smaller enterprise EA customers previously received. For the NCE mechanics that govern how MCA-E pricing actually works through the CSP channel, see our detailed guide on Microsoft NCE price lock strategy.

What You Lose When You Move from EA to MCA-E

The three losses that matter most in an EA-to-MCA-E transition are price lock, Software Assurance, and negotiation leverage. Price lock under the EA means your Microsoft cost is fixed for three years — the July 2026 price increase, for example, does not apply to EA customers whose agreements were signed before the increase date. Under MCA-E, your Microsoft costs reset at each annual renewal at whatever Microsoft's current pricing is. Organisations that transitioned from EA to MCA-E without negotiation saw 10–30% cost increases at their first MCA-E renewal — a direct consequence of moving from negotiated EA pricing to MCA-E list pricing.

Software Assurance benefits — step-up licensing rights, training vouchers, Microsoft 365 Apps deployment support, and home use programme access — are not available under MCA-E. The sunk cost of SA investments in staff training and deployment infrastructure is forfeited at transition. Negotiation leverage is the subtlest loss: the EA's three-year renewal deadline creates a defined moment when Microsoft's quota pressure is highest and discounts are most available. MCA-E's evergreen model removes that deadline. Microsoft has no structural incentive to offer discounts at annual MCA-E renewal because there is no competing deadline — you are always already in contract.

How to Negotiate the EA-to-MCA-E Transition

The starting point for any EA-to-MCA-E negotiation is recognising that Microsoft's presentation of MCA-E as the "only option" is a negotiating position, not an absolute constraint. For organisations above 2,400 users, EA renewal is still available. For those below, the negotiating frame shifts to securing MCA-E terms that replicate as much of the EA's protection as possible. Specifically: multi-year commitment pricing that locks rates for 2–3 years; price escalation caps (typically 3–5% annually) that prevent arbitrary mid-term increases; Azure Consumption Commitment credits to offset transition costs; and Software Assurance equivalence provisions that compensate for the loss of SA benefits.

Your leverage in this negotiation comes from five sources. First, your Azure spend — a larger Azure commitment commands better terms. Second, your willingness to commit to new service adoption, such as M365 Copilot or Azure AI, as a condition of achieving favourable MCA-E pricing. Third, the documented cost of your EA-to-MCA-E transition, presented as a legitimate cost that Microsoft should offset. Fourth, competitive alternatives — Google Workspace, Salesforce, and other vendors' willingness to absorb your Microsoft switching costs as a conversion incentive. Fifth, the timing of your EA expiry — Microsoft is most flexible in the final 90 days before your EA ends when quota pressure is highest. Download our Microsoft EA Renewal Playbook for the full clause-by-clause negotiation framework, or book a confidential call to discuss your specific transition timeline with our Microsoft advisory team. For organisations whose licensing moves through a CSP reseller, understanding how NCE price locks interact with your MCA-E commitments is critical before signing anything.

The E3 vs E5 tier decision and the EA vs MCA-E agreement structure decision are interlinked: if you are moving to MCA-E and simultaneously under pressure to upgrade to E5, the combined cost impact can be substantial. Redress Compliance models both variables together — ensuring that your agreement structure and your licence tier decisions are optimised as a single negotiation, not two separate conversations where Microsoft extracts concessions from both. Our advisory work across 500+ Microsoft engagements consistently demonstrates that organisations that approach these as a unified negotiation achieve significantly better outcomes than those that sequence them separately.

The EA-to-MCA-E Transition Checklist: What to Audit Before You Sign

Before accepting any Microsoft transition proposal, enterprises should complete a structured pre-signature audit. First, extract a full licence inventory from the Microsoft 365 Admin Centre or VLSC and reconcile it against your current EA order form — discrepancies of 5–15% are common and represent immediate negotiation leverage. Second, obtain a written quote for equivalent MCA-E coverage and compare the total contract value against your EA renewal cost over the same period; the delta typically ranges from 10–30% and is rarely presented transparently by Microsoft account teams. Third, assess your Software Assurance benefits pipeline: any step-up rights, training vouchers, or deployment planning services not yet consumed are forfeited at EA expiry with no MCA-E equivalent — their residual value should be captured in cash or additional licences before transition. Fourth, validate your price lock position under each commercial vehicle; EA provides a three-year price lock on committed SKUs while MCA-E exposes you to annual price adjustments at Microsoft's discretion, a risk that materialised directly with the July 2026 increase.

Fifth, and critically, review your cancellation exposure. MCA-E annual subscriptions carry a seven-day cancellation window after each renewal date. Miss that window and you are committed for another 12 months regardless of business change. EA over-purchase can be corrected at the next true-up anniversary. This asymmetry means MCA-E requires tighter licence governance than most enterprise IT teams currently operate. Our Microsoft licensing audit and governance guide covers the operational changes needed to manage MCA-E commitments without accumulating waste.

Frequently Asked Questions: Microsoft EA vs MCA-E

Can you convert an active EA to MCA-E mid-term?

No. Microsoft does not permit mid-term EA conversion to MCA-E. Transition occurs at EA expiry. Enterprises approaching their EA anniversary should begin MCA-E modelling at least 12 months in advance to allow time for commercial analysis and negotiation positioning.

Does MCA-E support the same product catalogue as EA?

The core Microsoft 365 and Azure product sets are available under both agreements. However, certain legacy on-premises perpetual licences and some bundled Software Assurance benefits are EA-exclusive. Enterprises running hybrid on-premises/cloud estates should audit which products are available under MCA-E before committing to transition.

What minimum commitment does MCA-E require?

MCA-E has no published seat minimum, unlike the EA's 2,400-seat threshold. This makes MCA-E available to mid-market organisations that cannot qualify for EA. For organisations above 2,400 seats, however, the absence of a minimum does not mean MCA-E offers better economics — EA volume pricing typically remains more favourable at scale, and the price lock advantage compounds materially over a three-year term.