Microsoft EA to MCA-E: What Changes for Azure Costs and How to Negotiate (2026)

Moving from a Microsoft Enterprise Agreement to MCA-E changes three things for Azure costs: you lose the automatic volume price levels (already gone since November 2025 at renewal), you move to a monthly invoice per billing profile under an agreement that never expires, and price protection becomes something you negotiate rather than inherit. Your leverage sits in commitment design.

This post sticks to what Microsoft documents on Microsoft Learn and its licensing pages, and labels anything that comes from licensing advisors as their view. It ends with a negotiation checklist and a renewal timeline.

What did Microsoft change in November 2025?

On August 12, 2025, Microsoft announced that from November 1, 2025 it would expand single, consistent pricing across Price Levels A-D to all Online Services bought through the Enterprise Agreement (including OSPA in China) and the MPSA, aligned with the prices on Microsoft.com.

The details that matter:

• It bites at renewal. The change applies at your next agreement renewal, or when you add Online Services not already on your Customer Price Sheet.
• Exclusions. On-premises software pricing is unchanged, and US Government and worldwide Education price lists are excluded.
• Seat-heavy products feel it most. The level discounts mainly affected per-user Online Services such as Microsoft 365 and Dynamics 365. Azure EA pricing has always leaned more on negotiated commitment discounts, so check your own price sheet rather than assuming a flat uplift.

Licensing advisors have published estimates of the uplift by former level. Several put it at roughly 6% for Level B, 9% for Level C and 12% for Level D. Those are advisor figures, not Microsoft’s, and your Customer Price Sheet is the only number that counts.

On top of that, Microsoft raised list prices for several Microsoft 365 suites from July 1, 2026, for example Microsoft 365 E3 (with Teams) from $36 to $39 and E5 (with Teams) from $57 to $60 per user per month, with existing customers moving at renewal. That is not Azure, but it lands in the same renewal conversation and eats into the same budget.

What actually changes for Azure billing under MCA-E?

Microsoft Learn’s EA-to-MCA transition guide is specific. Here is how the two compare for Azure:

A few operational traps from the same guide are worth flagging to finance early:

• Budgets, custom cost views and export jobs don’t migrate. You recreate them in the new scope.
• Support plans don’t transfer. Buy a new one for the MCA billing account.
• Remit-to bank details differ, so accounts payable needs a second vendor record.
• Centrally managed SQL Azure Hybrid Benefit licences have to be reassigned manually after migration.
• Indirect EAs can’t currently be renewed into an MCA through this path, per Microsoft Learn.

What happens to reservations, savings plans and MACC?

This is where most of the money sits, so read it carefully.

Reservations and savings plans move to the new billing account with no change to benefits or term. The exception is currency. If your enrollment is not in USD, Microsoft cancels your savings plans and repurchases them in USD as 1-year plans billed monthly, whatever their original term. If you had 3-year plans, Microsoft says to contact Azure support immediately to buy new 3-year plans and keep the discount level. Monthly-paid reservations are also cancelled on a currency change, though those cancellations don’t count toward the USD 50,000 rolling refund limit. Many GCC enrollments are billed in USD, but confirm yours before transition day.

MACC works on both EA and MCA billing accounts. Eligible Azure services and Marketplace offers decrement it. If your MACC has milestones and you miss one, or you miss the total by the end date, Microsoft applies a shortfall charge as an Azure prepayment credit for the remaining balance. Admins get alerts at 90, 60 and 30 days. Spend covered by Azure credits doesn’t count toward MACC, and consumption covered by a prepayment doesn’t either, although buying the prepayment does.

Savings plans vs reservations is a design choice you should revisit at renewal. Azure savings plans for compute apply across regions and VM families, which helps if workloads may move, for example into the Saudi Arabia East region Microsoft has said is due in Q4 2026. VM reservations are tied to a region and size family but can be exchanged.

How should you negotiate an EA to MCA-E move?

Microsoft’s standard MCA terms are not usually rewritten for individual customers, so focus on commercial terms. Licensing advisors such as Redress Compliance and SoftwareOne say much the same, and describe MCA-E discounts as negotiated case by case, often tied to Azure commitments. Treat their specific percentages as opinions.

What is the timeline before renewal?

The bottom line

The EA to MCA-E move is less about the contract name and more about losing defaults: automatic price levels, a documented price ceiling and familiar reporting. Replace each default with something explicit, a negotiated price hold, a MACC you can actually burn, and cost reporting rebuilt before transition day.

If your renewal is inside the next 12 months, our Microsoft and Azure renewal cost review runs as a fixed-scope FinOps QA Assessment focused on your Azure commitments: we baseline consumption, test commitment coverage and utilization, model MACC size and milestones, and hand you a negotiation brief before talks start. Book a scoping call to check your timeline.