Home  ›  Blog  ›  MCA vs EA
Microsoft · Agreement Structure

Microsoft MCA vs EA — the agreement question every enterprise faces in 2026.

Microsoft is steadily migrating its enterprise customer base from the legacy Enterprise Agreement (EA) into the Microsoft Customer Agreement for Enterprise (MCA-E). The shift is not optional in the long run; for most customers it is now the default contract Microsoft offers at renewal. The trade-offs are significant: MCA-E removes the EA's price locks, restructures the commitment model, changes the role of the partner channel, and rewrites the audit clause. Here is the comparison every Microsoft buyer needs before the next renewal cycle.

Updated: May 2026 Reading time: 13 min Audience: CIO, IT Procurement, Legal
Contract comparison
Structure

What MCA-E actually is — and how it differs from the EA.

The Microsoft Customer Agreement for Enterprise (MCA-E) is the perpetual, evergreen master agreement that Microsoft has positioned as the EA's replacement. Once signed, MCA-E is the umbrella for all subsequent Microsoft purchases — subscription, perpetual, Azure consumption — through purchase orders, billing accounts and individual subscriptions rather than the three-year EA enrollment construct. There is no anniversary, no true-up, no concurrent EA enrollment lifecycle. Each subscription is its own term, billed and renewable independently.

The EA, by contrast, is a three-year fixed-term agreement with price locks, true-up at anniversary, and structural pricing tiers determined at signing (the volume Level — A, B, C, D — that drives discount). EA enrollments aggregate purchases into a single coterminous structure with predictable budgeting and unified renewal cycles.

Price locks and the EA advantage

The single largest structural advantage of the EA is the price lock: prices established at EA signing remain fixed for the three-year term on products purchased during the enrollment. Mid-term price increases on existing licence types are blocked. MCA-E carries no equivalent protection — Microsoft can adjust prices on any product at the next billing cycle, with notice as short as 30 days for monthly subscriptions and 12 months for annual subscriptions. For large estates, this single difference can be worth millions over a three-year horizon.

Microsoft pushing you off the EA?

The MCA-E transition is the single biggest commercial pivot most Microsoft customers will make this decade. Preparation matters.

Contact Us →
Flexibility

Where MCA-E wins — and where the flexibility is illusory.

MCA-E does carry real flexibility advantages. Subscriptions can be added or reduced at term boundaries rather than waiting for anniversary. Multi-currency billing is supported natively. Partner relationships are decoupled from the master agreement (the customer can change LSP/CSP partners at the subscription level without renegotiating the master). Azure consumption is purchased directly through the MCA-E without the MACC overlay (though MACC remains available for committed discount). For organisations with shifting headcount or rapid product portfolio changes, this matters.

The flexibility is also genuinely illusory in places. The Microsoft Customer Agreement gives Microsoft unilateral right to modify the agreement terms with 30 days' notice — including pricing, support obligations and product terms. The EA does not contain an equivalent unilateral modification right. Customers who treat MCA-E's flexibility as a one-way street consistently discover that the flexibility runs both directions.

The audit clause

EA and MCA-E both contain audit clauses but the language differs. The EA audit clause is narrower, with reciprocal cost provisions (if compliance is verified, Microsoft pays the audit cost). The MCA-E audit clause is broader on scope, with less explicit cost protection. Customers signing MCA-E should negotiate a separate audit-cost reciprocity addendum, which Microsoft will grant for sufficiently large customers but rarely volunteers.

Download the Microsoft EA Negotiation Guide.

The EA-to-MCA-E transition playbook, the protective clauses to insert in the MCA-E itself, and the pricing concessions worth fighting for.

Get the playbook →
Decision framework

When EA still wins — and when MCA-E is the right call.

In our experience across 340+ Microsoft engagements, the agreement decision follows three patterns:

  1. Large, stable enterprises with predictable user counts. EA continues to win. The price lock is worth the commitment. Renew the EA where possible and resist the MCA-E migration until a future cycle.
  2. Rapid-growth or rapid-contraction organisations. MCA-E often wins, because the subscription-level flexibility outweighs the loss of price lock. The negotiation moves toward establishing protective addenda (price escalation caps, audit reciprocity, termination assistance) on top of the MCA-E framework.
  3. Mixed estates with significant on-prem perpetual licensing. The EA still carries genuine advantages for perpetual licence holders (Software Assurance integration, predictable true-up). MCA-E is harder to operate for perpetual workloads.

Considering the MCA-E transition?

The protective addenda negotiated at MCA-E signing are worth ten to fifteen times the equivalent renegotiation cost mid-term.

Contact Us →

For Microsoft estates above $2M annually, independent advice on the agreement decision — the heart of our Microsoft EA optimization work — is worth four to twelve times the advisory fee over the next three years.

EA renewal up or MCA-E proposed on the desk?
The decision is structural — it shapes the next decade of Microsoft spend.

We have run EA-to-MCA-E transitions across estates from $500K to $200M annually.

The Compliance Brief

Weekly compliance intelligence for IT leaders.