The Azure Enterprise Agreement and the Microsoft Customer Agreement are the two main commercial vehicles for buying Azure at scale, and the difference matters for cloud spend because they handle commitment, billing structure, and cost governance differently. The Enterprise Agreement is the older, upfront-commitment model many large customers have used for years; the Microsoft Customer Agreement, or MCA, is the newer digital agreement Microsoft is steadily moving customers onto. If you are on an EA, a transition is likely on your horizon, and planning it is a FinOps decision, not just a procurement one.
This article is part of our Azure cluster. Start with the complete guide to Azure cost optimization, the pillar this piece links up to. The agreement model sits at the See and Lock layers of our See, Cut, Lock, Run method: it determines what billing data you get and how you govern commitments.
The agreement decides the shape of your billing data, how reservations and savings plans are managed, and how cost rolls up across the organization. A poorly planned transition can fragment your historical cost data, disrupt reservation management, and break the allocation model you built. Treating the EA-to-MCA move as a finance and FinOps project, rather than a paperwork exercise, is how you keep continuity through it.
The two models side by side
The agreements differ less in the per-unit price of a VM and more in structure: how you commit, how the billing hierarchy is organized, and how you administer it. Those structural differences are what shape cost governance.
| Dimension | Enterprise Agreement (EA) | Microsoft Customer Agreement (MCA) |
|---|---|---|
| Model | Established, term-based enterprise contract | Newer digital agreement, the direction of travel |
| Commitment | Typically an upfront monetary commitment | More flexible, consumption-oriented structure |
| Billing hierarchy | Enrollment, departments, accounts | Billing account, billing profiles, invoice sections |
| Administration | EA portal concepts and roles | Managed in the Azure portal cost management |
| Direction | Being transitioned away from over time | Where Microsoft is moving enterprise customers |
What changes for cost management in the move
The most practical differences show up in day-to-day cost work. The billing hierarchy is structured differently, so the way you map spend to departments and teams changes, and any allocation model built on the EA structure needs to be re-expressed against MCA billing profiles and invoice sections. Reservation and savings-plan management carries over but is administered through the MCA structure, so the people who manage commitments need to relearn where things live. And historical cost data continuity is the thing to protect actively, because a clean transition keeps your trend lines intact while a rushed one can leave a gap.
Reservations and savings plans across the transition
Commitments are where care matters most, because they represent money already spent against future usage. The instruments themselves, reservations and savings plans, exist under both agreements, but their scope and management move with the billing structure. Plan the transition so commitment coverage is not disrupted and you do not end up with reservations stranded against the wrong scope. For how the two commitment instruments compare in the first place, see Azure Reservations vs Azure Savings Plan for compute, and time any new purchases around the move rather than across it.
Facing an EA-to-MCA transition?
Our Azure cost audit plans the move so allocation, reservations, and historical cost data survive it intact, and uses the transition as a moment to re-baseline and capture savings. On the performance model, you pay only from realized savings. No savings, no fee.
Book an Azure cost audit →Rebuild allocation and governance on the new structure
A transition is also an opportunity. Moving to MCA is the natural moment to re-express your cost allocation cleanly against the new billing profiles and invoice sections, rather than carrying forward whatever accreted under the EA. Map the new hierarchy to your tagging and management-group model deliberately so spend still rolls up to the right owners, as covered in Azure tagging and management groups for cost allocation. Re-point your budgets and alerts at the new scopes at the same time so governance does not lapse during the change.
Negotiation still matters, whatever the paper
Whichever agreement you are on, the commercial terms are negotiable at scale, and the agreement type does not remove your leverage. A large, committed Azure customer has room to negotiate, and a transition is a sensible point to revisit terms rather than rolling them over unexamined. We cover the broader commitment negotiation in how to negotiate a Microsoft Azure commitment (MACC). The structure of the agreement sets the rules; the discount within it is still yours to win.
The agreement structures and the EA-to-MCA transition described above reflect Microsoft's commercial models as of May 2026. Microsoft updates agreement terms and transition timelines regularly, so verify your specific transition path and the current MCA billing structure with Microsoft documentation and your account team before planning the move.
The Azure Cost Optimization Field Guide includes the EA-to-MCA transition checklist and the allocation-continuity plan we use on engagements. It is the downloadable companion to this article.
The short version
The Enterprise Agreement is the established upfront-commitment model; the Microsoft Customer Agreement is the newer, more flexible structure Microsoft is moving customers onto. The differences that matter for cost are the billing hierarchy, how reservations and savings plans are administered, and historical data continuity. Plan the transition as a FinOps project: protect commitment coverage and data, rebuild allocation and governance on the new structure, and use the moment to renegotiate. To place the agreement decision inside a full pass, follow how to run an Azure cost optimization assessment. When you want the transition planned so nothing breaks, that is exactly what our Azure cost optimization service delivers.