Editorial photograph of a Microsoft enterprise contract review meeting in a corporate boardroom
Microsoft Hub · Article

Microsoft EA to MCA Renewal

The Microsoft EA to MCA Enterprise transition in 2026. Billing changes, level pricing replacement, Software Assurance, and the seven levers behind the decision.

Contact Us EA Renewal Playbook
7Transition levers
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

The seven things to take away.

  • Microsoft is migrating enterprise customers from the Enterprise Agreement to the Microsoft Customer Agreement Enterprise across 2024 to 2027.
  • MCA Enterprise removes the Level A through Level D pricing tiers and shifts discount mechanics into the negotiated agreement itself.
  • Billing shifts from annual under EA to monthly under MCA Enterprise, with significant cash flow implications for the customer.
  • Software Assurance survives in MCA Enterprise for perpetual licenses. Cloud only customers on MCA do not need SA.
  • EA renewals remain available on a case by case basis through 2027 for qualifying customers with documented complexity.
  • The buyer side posture tests the MCA pricing against the existing EA and negotiates the transition discount as a single conversation.
  • Most customers transitioning to MCA Enterprise without an independent posture pay between 8 and 18 percent more across the first three year window.

The Enterprise Agreement carried Microsoft enterprise contracts for two decades. The contract was paper based, renewed every three years, and structured around volume level pricing tiers. The model is being replaced.

The Microsoft Customer Agreement Enterprise is the replacement. The contract is evergreen, the billing is monthly, and the discount mechanics shift from volume level tiers into the negotiated agreement itself. The 2026 renewal cycle is where most enterprise customers face the decision.

Why Microsoft is moving customers to MCA.

Microsoft published the MCA Enterprise direction in 2022 and has accelerated through 2026. The reasons run on the Microsoft side, not on the customer side. Three forces drive the migration.

The three Microsoft drivers

  • Direct billing relationship: MCA Enterprise places Microsoft in a direct billing relationship with the customer for cloud spend, replacing the Large Account Reseller model.
  • Evergreen contract: MCA Enterprise has no fixed term, no renewal date, and rolls forward indefinitely on monthly billing.
  • Pricing flexibility: Microsoft can change pricing more easily under MCA than under the multi year fixed EA structure.

What the customer gives up

The customer gives up the predictable three year price floor, the structured volume discount levels, the annual billing rhythm, and the LAR layer that historically held some commercial competition in the channel. The givebacks are real.

The pricing model change.

EA carried Level A through Level D pricing tiers based on total seat count. Each level carried a discount against the published list price. MCA Enterprise removes the level structure and shifts the discount into the negotiated MCA agreement.

The legacy EA pricing levels

Legacy EA pricing levels and indicative discount

EA LevelSeat rangeIndicative discount
A250 to 2,3995 to 8 percent
B2,400 to 5,9998 to 12 percent
C6,000 to 14,99912 to 16 percent
D15,000+16 to 24 percent

The MCA Enterprise replacement

MCA Enterprise replaces the level table with a negotiated agreement that carries a customer specific discount. The discount is anchored to a defined cloud commit and to a multi year posture. The math can land at or below the legacy EA Level D discount, or significantly above it, depending on the buyer side posture at signing.

The billing change.

The billing change is the operational shock of the MCA transition. EA carried annual billing through the Large Account Reseller. MCA Enterprise carries monthly billing direct from Microsoft.

The cash flow implications

  1. From annual to monthly: The customer cash flow shifts from one large annual outflow to twelve monthly outflows.
  2. Azure consumption included: Azure consumption is billed monthly through the same MCA channel.
  3. FX and tax handling changes: Direct billing changes the FX exposure and the tax treatment for global customers.

The operational implications

The internal AP team carries a higher transaction volume. The cost allocation across business units runs monthly rather than annually. The reconciliation against budget runs against twelve data points rather than one.

Software Assurance in the new world.

Software Assurance survives in MCA Enterprise for perpetual licenses. The benefits remain familiar: New Version Rights, License Mobility, planning services, training vouchers, and the support coverage on perpetual products.

When SA still matters

  • Windows Server and SQL Server: Perpetual licenses with SA continue to carry the established benefits.
  • License Mobility to non Azure clouds: SA enables mobility for SQL Server and other workloads to AWS and Google Cloud.
  • Hybrid use benefits: Azure Hybrid Benefit requires SA on Windows Server and SQL Server.

When SA no longer matters

Cloud only customers on Microsoft 365 and Dynamics 365 subscriptions do not need SA. The subscription includes the new version rights. SA becomes a question only where perpetual licenses persist in the estate.

The MCA transition is a contract change more than a product change. The buyer who treats it as a renewal pays the renewal price. The buyer who treats it as a new contract negotiates the new contract.

The seven MCA transition levers.

Microsoft holds seven levers for the MCA transition. The customer who pulls three to four of the seven lands at or below the legacy EA discount. The customer who pulls none lands materially above.

The seven lever map

  1. Transition discount: A one time discount applied to the first MCA term as the migration incentive.
  2. Multi year commit: A three year cloud commit in exchange for an additional discount.
  3. Price hold: A negotiated hold against in term price increases.
  4. EA bridge: A short EA extension covering complexity that MCA does not yet support.
  5. Azure commit conversion: Reuse of unused EA Azure prepayment against the new MCA commit.
  6. Partner of Record: A retained partner inside the MCA Enterprise structure for advisory and support.
  7. True forward replacement: Annual reconciliation replaces the legacy true up at year end.

The combined posture

Most renewals land three to four of the seven. The combined posture typically saves 8 to 14 percent against an MCA transition negotiated without the seven lever frame.

When holding the EA still makes sense.

EA renewals remain available through 2027 for qualifying customers. The qualifying conditions are specific. The customer needs documented complexity that MCA Enterprise does not yet support.

The four EA hold scenarios

  • Multi year EA still running: Existing EA terms can run to natural expiration before the MCA decision.
  • Government and regulated sectors: Specific GovCloud or regulated cloud requirements that map cleanly to EA.
  • Licensing complexity: Specific perpetual product combinations that MCA Enterprise does not handle simply.
  • M&A or divestiture in flight: Active corporate change that benefits from the predictable EA term.

What to do next.

The MCA decision benefits from a tested posture before the Microsoft account team opens the official transition cycle. The buyer side approach runs the seven levers against the existing estate.

The eight step MCA action checklist

  1. Inventory the current EA estate by product, by level, and by remaining term.
  2. Pull the trailing 24 months of Azure consumption against the EA Azure prepayment.
  3. Run the Microsoft 365 License Optimizer on the current estate.
  4. Build the MCA pricing model against the legacy EA Level discount.
  5. Score each of the seven MCA transition levers against the current estate.
  6. Test the EA hold scenarios if any qualifying complexity applies.
  7. Open the Microsoft EA Renewal Playbook.
  8. Engage Microsoft advisory ahead of the next renewal cycle.

Frequently asked questions.

What is the difference between EA and MCA?

The Enterprise Agreement is the legacy Microsoft enterprise contract, paper based, renewed every three years. The Microsoft Customer Agreement is the new direct cloud agreement, evergreen, with monthly billing. Microsoft is migrating enterprise customers to MCA Enterprise over the 2024 to 2027 window.

Is MCA Enterprise mandatory on renewal?

Not yet, but the EA is being phased out. Microsoft is offering MCA Enterprise as the default on most enterprise renewals in 2026. EA renewals remain available on a case by case basis through 2027 for qualifying customers.

What changes in pricing under MCA Enterprise?

Level A through Level D pricing tiers are replaced with simpler MCA pricing schedules. The new schedules typically remove the level discount on subscription SKUs and shift the discount mechanism into the negotiated MCA agreement itself.

Does Software Assurance survive in MCA Enterprise?

Software Assurance survives where the customer carries perpetual licenses. SA benefits like New Version Rights and License Mobility continue. Cloud only customers on MCA Enterprise do not need SA.

What is the billing change?

EA carries annual billing. MCA Enterprise carries monthly billing through the Microsoft 365 admin center, with Azure consumption billed monthly as well. The cash flow profile changes significantly.

Can a customer hold off the MCA transition?

Through 2026 yes, with conditions. Microsoft requires a documented case for extending the EA. The case typically rests on multi year EA terms still running or on specific licensing complexity that MCA Enterprise does not yet support.

What is the buyer side posture on MCA transition?

Test the MCA Enterprise pricing against the existing EA before agreeing to the transition. Negotiate the transition discount and the multi year posture as a single conversation. Avoid agreeing to the transition without confirming the seven levers Microsoft typically holds for the migration.

500+
Enterprise Clients
$2B+
Under Advisory
11
Vendor Practices
100%
Buyer Side
Industry
Recognized

The MCA transition is a contract change more than a product change. The buyer who treats it as a renewal pays the renewal price. The buyer who treats it as a new contract negotiates the new contract.

Microsoft Practice Lead
Redress Compliance
Score your Microsoft estate with the Microsoft 365 License Optimizer.
Open Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side reference on Microsoft EA renewal. Discount benchmarks, true up tactics, M365 right sizing, and the Azure commit conversation.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Microsoft contracts. No vendor influence. No sales kickback.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
More Reading

More from this practice.

Microsoft Hub →
Microsoft Enterprise Agreement 2026 Guide
Microsoft · Article
Microsoft Enterprise Agreement 2026 Guide
The full Microsoft EA reference. Pricing levels, true up math, M365 right sizing, Azure commits.
18 min read
Microsoft Unified Support Negotiation
Microsoft · Article
Microsoft Unified Support Negotiation
The Unified Support pricing model, the alternatives, and the buyer side posture.
12 min read
Microsoft Services
Microsoft · Article
Microsoft Services
The Microsoft advisory practice. EA, MCA, M365, Azure, Copilot, Unified Support.
9 min read
Microsoft Knowledge Hub
Microsoft · Article
Microsoft Knowledge Hub
Every Microsoft article, case study, and white paper in one place. Editorial, buyer side.
5 min read
Editorial photograph of enterprise contract negotiation strategy

Run the MCA posture against benchmark.

Seven levers. One transition. Buyer side independent. Bring the next renewal date and we will return a posture inside two weeks.

Microsoft licensing intelligence, monthly.

One email per month. EA to MCA benchmarks, Azure commit math, and one buyer side tactic. No vendor influence.