Microsoft Customer Agreement (MCA) Explained: Structure, Risks, and Negotiation Strategy

What Is the Microsoft Customer Agreement?

The Microsoft Customer Agreement (MCA) is a standardised, digital, evergreen contract through which organisations can purchase Microsoft cloud products and services. Unlike the Enterprise Agreement (EA), which has a fixed three-year term with a defined renewal date, the MCA carries no expiry. You sign it once — typically via a digital click-through — and it remains in effect indefinitely until either party terminates it.

Microsoft introduced the MCA to replace the legacy Microsoft Online Subscription Agreement (MOSA) for commercial customers purchasing through the New Commerce Experience (NCE). Its original design was oriented toward mid-market and SMB buyers who wanted cloud-native, subscription-based access to Microsoft 365 and Azure without the commitment structure of an EA. Over time, Microsoft expanded the MCA upward to serve larger organisations, creating the Microsoft Customer Agreement for Enterprise (MCA-E) as a version intended for complex, multi-entity corporate customers.

As of March 2026, Microsoft is actively migrating EA customers on Microsoft Azure Consumption Commitment (MACC) plans to MCA-E at the point of EA renewal, and in some cases before renewal. Understanding what you are accepting — and what you are giving up — is essential before signing.

MCA vs. EA: The Critical Structural Differences

From a buyer's perspective, the Enterprise Agreement and the Microsoft Customer Agreement represent fundamentally different commercial relationships. The EA was designed for large enterprises with complex procurement needs. The MCA was designed for simplicity and digital commerce — which benefits Microsoft's internal cost to serve, not the buyer's negotiating position.

Contract Duration and Renewal Events

The EA is a three-year contract with a defined end date. That end date creates a concentrated negotiation window every three years during which Microsoft's field sales team faces quota pressure and the buyer has the maximum opportunity to negotiate discounts, commercial terms, and product commitments. The MCA, by contrast, is evergreen. There is no defined renewal date and therefore no concentrated leverage moment. Microsoft can propose price increases at any annual cycle, and the buyer's only formal leverage is the threat of termination.

This structural difference has a profound impact on the economics. Enterprise customers who managed EA renewals well — with independent benchmarking, competitive alternatives, and disciplined timeline management — frequently achieved 15 to 25 percent below list pricing across their core Microsoft 365 SKUs. Under MCA-E, achieving comparable discounts requires explicit negotiation at each annual renewal based on volume commitment, which Microsoft is under no obligation to grant.

Price Lock and Annual Resets

Under an EA, your per-user pricing for Microsoft 365 products is fixed for the three-year term. If Microsoft raises list prices — as they did in 2022 and again in 2025 — your EA price does not change until renewal. This price lock represents substantial value: for a 5,000-user organisation on E3 at EA pricing, a 10 percent list price increase that does not affect your in-term cost is worth approximately $216,000 over a three-year term.

Under MCA-E, pricing resets at each annual renewal at whatever Microsoft's current pricing is. Organisations that transitioned from EA to MCA-E in 2024 and 2025 without negotiation found their first MCA-E renewal reflecting both the elimination of EA volume tiers and Microsoft's 2025 price increases — cumulative increases of 10 to 30 percent over their previous EA cost.

Software Assurance Benefits

The Enterprise Agreement includes Software Assurance (SA) on perpetual licences, providing downgrade rights, home use programme entitlements, training vouchers, and licence mobility rights. The MCA does not include Software Assurance. For organisations with significant on-premises deployments — particularly Windows Server, SQL Server, or Office perpetual — this is a material loss that must be quantified before agreeing to transition.

Licence mobility rights under SA allow you to deploy certain Microsoft server products on third-party shared infrastructure (including competitor clouds) without incurring additional licences. Losing this benefit under MCA locks you more tightly into Azure for hybrid deployments, which is not coincidental from Microsoft's commercial perspective.

Understanding MCA-E: The Enterprise Variant

The Microsoft Customer Agreement for Enterprise (MCA-E) is designed for organisations that require more structured purchasing than the standard MCA provides. MCA-E retains the evergreen contract structure but accommodates multi-entity billing, more complex product mixes, and in some cases, custom pricing amendments negotiated with Microsoft's enterprise account team.

The critical distinction, however, is that MCA-E remains largely a take-it-or-leave-it standard agreement. Microsoft does not typically allow customers to insert custom contract terms, add bespoke SLA provisions, or negotiate the standard terms of service in the way that large EA customers historically could through formal EA amendments. The standard MCA-E terms govern your entire Microsoft commercial relationship unless Microsoft's account team agrees in writing to specific deviations — which requires substantial spend leverage to achieve.

NCE Pricing Under MCA-E

Under the New Commerce Experience (NCE) framework that MCA-E operates on, your pricing is determined by your commitment term. Monthly subscriptions are charged at list price with no discount. Annual subscriptions provide up to 5 percent discount versus monthly. Multi-year commitments (three years) offer better discounts but substantially reduce your ability to right-size or downgrade licences during the term.

This pricing structure is a deliberate deterioration from EA pricing. The EA historically provided volume discounts of 10 to 20 percent off list (down from historical highs of 15 to 25 percent) based on the total contract value and strategic nature of the relationship. NCE annual discount of up to 5 percent is a fraction of what well-negotiated EA pricing delivers.

Microsoft's preferred motion is now MCA or MCA-E because the buyer's leverage is structurally lower than under an EA. Enterprise buyers who transition without independent advice almost universally pay more — not because Microsoft's products have become more expensive in isolation, but because the contract vehicle that delivered price protection and bulk discounting has been replaced with one that does not.

What Microsoft Gains From MCA Adoption

To negotiate effectively under MCA-E, you must understand what Microsoft gains from the transition. First, Microsoft eliminates the concentrated EA renewal event where buyer leverage peaks. A large enterprise approaching EA renewal in Microsoft's Q4 (April to June, when Microsoft's quota pressure is highest) historically had tremendous leverage. Under MCA-E, there is no equivalent pressure point.

Second, Microsoft gains annual price adjustment flexibility. EA customers were protected against in-term price changes. MCA-E customers see annual pricing that reflects Microsoft's current list, including any price increases Microsoft introduces in the preceding 12 months. Microsoft raised list prices in 2022, 2025, and has announced further increases for July 2026, each of which flows through to MCA-E customers at annual renewal.

Third, Microsoft gains cleaner data on actual seat usage across the estate, which it uses to identify upsell opportunities. The MCA-E digital billing infrastructure gives Microsoft real-time visibility into deployment data that strengthens its position in next-year pricing conversations.

SKU Considerations Under MCA-E: E1 to E7

Whether you are on EA or MCA-E, Microsoft's current M365 SKU stack runs from E1 through E3, E5, and the newest tier, E7. E7 is the top SKU, positioned above E5, and bundles advanced AI capabilities including Microsoft 365 Copilot, advanced security, and compliance features that under E5 required separate add-on purchases. Microsoft's field teams are actively pushing E5 customers toward E7 at renewal, and this upsell motion intensifies under MCA-E where annual pricing conversations are the norm.

Buyers evaluating MCA-E transitions should model their total per-user cost under three scenarios: staying on E3 with add-ons, moving to E5, and moving to E7. The all-in cost comparison including Copilot, security add-ons, and compliance tools often makes E7 more economical than E5 plus individual add-ons — but the total per-user cost represents a significant step-up from E3, and not every user role justifies E7.

Negotiating Under MCA-E: What Levers Still Work

Despite the reduced structural leverage of MCA-E, buyers are not without options. The following levers remain available under a well-managed MCA-E negotiation.

Volume and Multi-Year Commitment

Microsoft will negotiate custom discounts for organisations willing to make explicit multi-year, multi-product commitments. Bundling Microsoft 365, Azure, and Dynamics 365 commitments into a single MCA-E negotiation creates the spend concentration that Microsoft's account team needs to justify discounts beyond the standard NCE tiers. Organisations spending more than $5 million annually with Microsoft have reasonable expectation of achieving 10 to 15 percent off list under MCA-E; those below $2 million will struggle to move Microsoft from standard NCE pricing.

Azure Consumption Commitment (MACC)

The Microsoft Azure Consumption Commitment is the mechanism through which Microsoft provides incentive pricing under MCA-E for Azure spend. MACC commitments are denominated in total Azure dollars over the commitment period and are typically structured in one, two, or three-year terms. Higher MACC commitments unlock better Azure unit pricing and can also provide leverage in Microsoft 365 licensing discussions within the same MCA-E agreement.

Timing: Microsoft Fiscal Year Dynamics

Microsoft's fiscal year ends June 30. The Q4 window — April 1 to June 30 — is when Microsoft's field sales team faces the maximum pressure to close deals. Even under MCA-E, initiating pricing discussions in Q4 improves outcomes because Microsoft's account teams have incentive to discount and close before their fiscal year-end. Organisations should aim to begin structured MCA-E negotiations no later than April of each year and never renew in the Q1 or Q2 of Microsoft's fiscal year (July to December) without independent advice, as Microsoft has the least incentive to move at these times.

Competitive Alternatives

The availability of credible alternatives strengthens your position under any Microsoft negotiation, including MCA-E. Demonstrating an active evaluation of Google Workspace, open-source alternatives for specific workloads, or alternative security vendors for components currently covered by E5 security add-ons signals to Microsoft that inaction on pricing carries revenue risk. Microsoft's account teams are instructed to protect ARR; evidenced competitive pressure opens conversations that standard NCE pricing does not.

When to Stay on EA vs. Transition to MCA-E

The decision to transition from EA to MCA-E is not binary, and Microsoft's push to move you is not neutral advice. Organisations should evaluate transition timing based on four factors: current EA pricing versus MCA-E equivalent, remaining EA term, on-premises footprint requiring Software Assurance, and anticipated seat count changes over the next three years.

If your current EA pricing is below list — as it should be for any well-negotiated agreement — transitioning early to MCA-E at NCE pricing is almost always more expensive. If your EA expires naturally and you cannot achieve comparable discounts in an EA renewal negotiation, MCA-E may be the only available vehicle. Our Microsoft EA advisory specialists team assesses this decision independently for every client before any transition discussions with Microsoft begin.

Microsoft's preferred motion is MCA-E because it benefits Microsoft. Your preferred motion should be determined by independent analysis of your total cost of ownership, including the value of price lock, SA benefits, and the negotiation leverage differential between the two contract vehicles.

Key Risks Summary

Organisations evaluating or facing an MCA-E transition should be aware of the following documented risks. Price lock disappears immediately on transition, exposing you to annual pricing resets at Microsoft's current list. Software Assurance benefits are not carried over, which matters most for organisations with perpetual on-premises licences. Negotiation leverage diminishes because the concentrated three-year EA renewal event — which historically drove the deepest discounts — no longer exists. Standard NCE discounts (up to 5 percent annually) are materially lower than achievable EA discounts. Finally, Microsoft's annual review cadence under MCA-E gives their account teams more frequent access to your deployment data, which they will use to identify upsell opportunities at every renewal cycle.

None of these risks mean that MCA-E is always the wrong vehicle. But they do mean that the decision requires independent analysis, not Microsoft's recommendation alone. The conflict of interest is obvious: Microsoft benefits commercially from the transition in every case.