Microsoft Customer Agreement for Enterprise: What You Need to Know Before You Sign

Microsoft introduced the Microsoft Customer Agreement (MCA) as a simplified, streamlined replacement for the decades-old Microsoft Online Subscription Agreement and — gradually — as an alternative commercial framework to the Enterprise Agreement. The framing from Microsoft's account teams is consistently administrative: "it's just a modernised contract, your pricing stays the same, it makes things simpler." That framing is selective at best.

The MCA is a fundamentally different commercial document than the EA. It changes what Microsoft can do to your pricing, when and how Microsoft can audit you, how disputes are resolved, and what leverage you have in future negotiations. Signing it without a proper legal and commercial review — which is exactly what most organisations do because the account team presents it as routine — is a significant risk.

What the MCA Actually Is

The Microsoft Customer Agreement is a digital, clickwrap contract framework introduced by Microsoft in 2019 to replace multiple legacy agreements. Its defining characteristics are:

• Digital acceptance: You accept MCA terms online, typically through the Azure portal or Microsoft 365 admin centre — no paper signature, no negotiated amendments
• Evergreen terms: Microsoft can update MCA terms unilaterally with 30 days' notice. You can reject changes, but the consequence is that you stop using the product.
• Per-product, per-subscription structure: Rather than a single umbrella enrolment covering your entire Microsoft estate, MCA governs each product/subscription independently
• No minimum commitment: Unlike EA, MCA does not require a minimum licence count or three-year term commitment — which eliminates both the burden and the leverage of that commitment
• Microsoft Online Services Terms integration: Product-specific use rights are governed by the Online Services Terms (renamed Product Terms), which Microsoft updates monthly

For individual developers, small teams, and pay-as-you-go Azure consumption, MCA is entirely appropriate — it is the right vehicle for that consumption pattern. The question is whether it is appropriate as the primary governing agreement for an enterprise spending £5M+ per year on Microsoft.

MCA vs EA: The Commercial Differences That Matter

When Microsoft Proposes MCA to Enterprise Customers

In practice, enterprise customers encounter MCA proposals in several distinct scenarios, each with different implications:

Azure Direct Migration Proposals

This is the most common scenario. Your Microsoft account team proposes moving Azure consumption from EA billing to a direct MCA relationship. The stated rationale is typically "simplified billing," "faster provisioning," or "access to the latest Azure pricing structures." The actual implication is that Azure consumption leaves the EA enrolment, reducing your MACC leverage and potentially eliminating the deal desk relationship that generates significant Azure discounts.

Before accepting any Azure-to-MCA migration proposal, verify: whether your current EA Azure discounts are preserved, whether MACC commitments survive the migration, whether Azure Hybrid Benefit eligibility is maintained, and whether the new billing structure changes your month-end reconciliation process materially.

EA Renewal Alternative Proposals

Some account teams, particularly when faced with a complex renewal negotiation, will propose MCA as a "simpler alternative" to EA renewal. The pitch emphasises flexibility and reduced administrative burden. What it does not emphasise is that MCA eliminates the structured negotiation event — the three-year commitment that gives you deal desk access and creates genuine commercial pressure on Microsoft to perform.

For organisations spending more than £500,000 per year on Microsoft, accepting MCA as an EA replacement is almost always commercially inferior. The flexibility gain does not compensate for the discount leverage lost, particularly given that the EA discount ceiling for committed volume significantly exceeds what MCA structures can achieve.

New Product Onboarding

When adopting a new Microsoft cloud product that is not in your current EA, the default procurement path is MCA via the product portal or partner. For trial evaluations and limited pilots, this is appropriate. The risk is when a pilot becomes production-scale — you may find yourself in an MCA-governed subscription for a significant workload, outside your EA discount structure, with no straightforward path to bring it back into EA terms.

MCA-E: The Enterprise Variant

Microsoft is rolling out the Microsoft Customer Agreement for Enterprise (MCA-E) as a forward-looking replacement for the EA framework. As of 2026, MCA-E availability is still being selectively expanded. The design intent is to retain EA-style enterprise commitments and discount structures while using MCA's digital framework. Key questions before transitioning to MCA-E:

• Are your EA discount levels preserved in the MCA-E terms, or do you start a new negotiation from scratch?
• Does MCA-E provide equivalent MACC commitment structures and deal desk access?
• What amendment provisions exist in MCA-E — can you negotiate non-standard terms as you can in EA?
• How do your perpetual licence entitlements from the current EA survive the transition?

Critical MCA Clauses to Understand

If you are evaluating MCA for any significant workload, these are the provisions that carry the most commercial weight:

Clause 1: Microsoft's Right to Change Terms

The MCA contains explicit provisions allowing Microsoft to modify agreement terms with 30 days' advance notice. Your remedy if you object to changes is to stop using the product. For critical enterprise workloads — Microsoft 365, Azure infrastructure, Dynamics 365 — this remedy is theoretical rather than practical. This is a materially weaker protection than EA terms, which require mutual agreement for term changes during the enrolment period.

Clause 2: Pricing Structure and Price Increases

MCA does not provide the structural three-year price lock available under a negotiated EA. Microsoft can increase prices at each subscription renewal — and historically does so. The 2022 Microsoft commercial price increase (15–25% across M365 products) hit MCA customers at their next renewal date without the price protection mechanisms available to EA customers who had negotiated price lock provisions. See the history of Microsoft price increases for context on how frequently and significantly these occur.

Clause 3: Data and Usage Monitoring

Microsoft's right to monitor usage data in cloud services under MCA is broader than many procurement teams appreciate. While this data is primarily used for billing and compliance verification, the scope of monitoring rights — and how that data is used in commercial conversations — differs from EA audit provisions. Enterprise customers with strict data governance requirements should review MCA data provisions against their internal policies before signing.

Clause 4: Dispute Resolution and Governing Law

MCA includes binding arbitration provisions in many jurisdictions that restrict access to class action litigation. For most enterprise commercial disputes, this is unlikely to matter. But for organisations in highly regulated industries or with specific contractual requirements, the dispute resolution framework should be reviewed by legal counsel before acceptance.

Clause 5: Affiliate and Subsidiary Coverage

MCA's treatment of affiliates and subsidiaries differs from EA. EA provides clear frameworks for affiliate inclusion in the enrolment. MCA's subsidiary coverage can be less clearly defined, creating potential compliance gaps when acquired entities need to be brought into the Microsoft relationship. For organisations undergoing M&A activity, this distinction matters. See the Microsoft licensing in M&A guide for detailed treatment.

MCA and Negotiation Leverage

The most significant long-term commercial consequence of moving from EA to MCA is the loss of the structured negotiation event. EA renewal is a three-year commercial forcing function — Microsoft's account team has targets, deal desks have authority allocated for renewal cycles, and the threat of competitive alternatives (CSP, Google Workspace, AWS) has maximum salience at the moment of structured renewal.

MCA eliminates this forcing function. Without a defined renewal date and commitment structure, negotiation becomes entirely proactive — you must create leverage rather than exercise it at a natural commercial moment. Most organisations are not positioned to do this effectively, which is exactly why Microsoft benefits commercially from the transition.

The practical consequence is that organisations that move from EA to MCA frequently find their Microsoft costs increasing over a three-to-five-year period, not because of price increases alone, but because the disciplined renewal management that generated discounts in the EA framework has no equivalent structure in MCA.

If you are considering MCA, ensure you have a mid-cycle negotiation strategy in place — a structured approach to creating commercial leverage without a renewal deadline. Most organisations lack this capability.

Practical Guidance for Enterprise Buyers

Scenario A: Microsoft Proposes Azure Migration to MCA

Do not accept without quantifying the impact on your EA MACC structure and Azure discount levels. Request a written confirmation from your account team that all current EA discounts are preserved, and get that confirmation reviewed by an independent licensing advisor before execution. The "administrative simplification" framing should trigger, not allay, commercial scrutiny.

Scenario B: EA Renewal Coming Up, Microsoft Suggests MCA-E

Use the renewal moment as leverage. If MCA-E is genuinely comparable to EA in commercial terms, Microsoft should be willing to demonstrate equivalence via a side-by-side pricing and terms comparison. If they cannot or will not provide this, the transition is not equivalent. Proceed with EA renewal and revisit MCA-E when you have time and leverage on your side.

Scenario C: New Product Onboarding via MCA

For pilots and evaluations under 200 seats or 90 days, MCA is typically fine — it's the right vehicle for controlled experimentation. Build a clear criteria for when a pilot transitions to production, and make "bring into EA structure" part of the production-readiness checklist. Do not let an MCA pilot default into a production deployment without a deliberate commercial decision.

Scenario D: Already Running Significant Workloads on MCA

Audit what is on MCA versus EA. For each significant MCA workload, assess: what discount am I currently getting, what discount could I get if this were in an EA structure, and what is the annual cost differential? This analysis frequently reveals £100K–£500K annual savings opportunity from restructuring MCA workloads into EA or CSP annual subscriptions with better-negotiated terms.

Summary: What You Need to Know

The Microsoft Customer Agreement is not an administrative convenience. It is a commercially significant change to your relationship with Microsoft that affects your pricing protection, negotiating leverage, audit exposure, and long-term cost trajectory. Microsoft's framing of MCA transitions as routine simplifications reflects their commercial interest, not yours.

For most enterprise organisations spending more than £1M per year on Microsoft, the EA remains the superior commercial vehicle for core workloads. MCA has a role — Azure consumption pilots, new product evaluations, CSP supplement structures — but it should not replace the EA framework for committed, organisation-wide workloads without rigorous independent analysis.

If your account team is proposing MCA, the first question is simple: why now? The second question is: who benefits more from this change, and why? If the honest answer to both is Microsoft, that tells you what you need to know about how to respond.

For the full framework on buying vehicle decisions, see the EA to Cloud Transition guide. For the CSP comparison in detail, see the CSP vs EA comparison.