Microsoft MCA Transition: What Every Enterprise Buyer Must Know Before Moving from EA

Why Microsoft Is Driving This Transition

The Enterprise Agreement has been the backbone of Microsoft's commercial licensing for over two decades. It gave large buyers pricing certainty, volume discounts, Software Assurance benefits, and a defined three-year negotiating window in which both sides had leverage. Microsoft's field teams often faced real competition at EA renewal — from alternative vendors, from optimisation exercises, and from the blunt fact that a three-year commitment is a significant enough decision that procurement teams engaged properly.

The Microsoft Customer Agreement for Enterprise (MCA-E) changes that equation entirely, and deliberately so. Under MCA-E, Microsoft's preferred new framework, subscriptions renew annually or on a monthly rolling basis. There is no hard three-year deadline that creates negotiating pressure on Microsoft's account teams. The contract is evergreen — you are, structurally, always already in contract. That removes the single most powerful lever buyers held under the old EA model.

From November 1, 2025, Microsoft also eliminated the tiered volume discount structure (Levels A through D) that previously applied to Online Services under both EA and MPSA. Every organisation, regardless of size, now starts at Level A pricing — the public list price. For large enterprises previously at Level D, that represents an effective price increase of 8–15% on top of whatever list price increases Microsoft has implemented in the interim.

What Changes When You Move to MCA-E

The MCA-E is not simply a renamed Enterprise Agreement. The differences are substantive and, for most buyers, unfavourable. Understanding them is essential before you engage with your Microsoft account team on a transition.

Software Assurance Is Gone

Under the EA, Software Assurance (SA) was typically included as a standard component of the agreement. SA provided step-up licensing rights, deployment planning vouchers, training access, home use programme licences, and various other benefits that enterprises had built into their operational planning. Under MCA-E, SA does not exist — the model is subscription-based, and the perpetual-licensing framework that SA was designed to support has no direct equivalent. Organisations that have relied on SA benefits need to plan for their replacement, which in practice often means paying separately for capabilities that were previously bundled.

The True-Up Process Disappears

The EA's annual True-Up was a structured reconciliation mechanism: once a year, on the anniversary of the EA start date, organisations reported deployment growth and paid for additional licences consumed since the last True-Up. This gave IT and procurement teams a manageable framework for tracking consumption against entitlement. Under MCA-E, there is no True-Up. Subscriptions are managed on a per-order basis, with no annual reconciliation cycle. Microsoft expects consumption to be managed in near real time, which places a higher operational burden on IT teams and removes the predictability of the True-Up model.

Pricing Flexibility Shifts to Microsoft

One of the EA's most valuable features was price lock: once you signed a three-year agreement, your per-unit pricing was fixed for the term. Microsoft could not increase prices on committed products mid-term. Under MCA-E, pricing can change at each annual renewal. Microsoft retains the contractual right to adjust prices, and there is no automatic lock that prevents increases from flowing through at your next renewal date. The only way to achieve price lock under NCE is to commit to an annual or multi-year term — and even then, the lock expires at term end, at which point Microsoft's current list price applies.

Seat Reduction Is Severely Restricted

Under a traditional EA, organisations had defined mechanisms to reduce their licence commitment at renewal. This gave IT teams the ability to right-size ahead of the three-year commitment. Under NCE annual terms in MCA-E, seat reduction is only permitted in a seven-day window immediately after each subscription renewal date. Outside of that window, you cannot reduce your seat count mid-term. If your user count drops due to redundancy, restructuring, or business transformation after the seven-day window has passed, you continue paying for unused seats until the next renewal date. This asymmetry — Microsoft can adjust pricing upward, while buyers are locked into seat counts — is one of the most commercially damaging features of MCA-E for large enterprises.

The Negotiation Landscape Under MCA-E

The removal of automatic volume discounts does not mean that pricing under MCA-E is non-negotiable. It means that discounts are no longer automatic — every percentage point of reduction must be negotiated individually, typically in the context of a commitment to specific workloads, products, or consumption growth. Microsoft's account teams are incentivised to sell Azure consumption growth, Microsoft 365 Copilot adoption, and security bundle consolidation. Commitments in those areas give Microsoft's account team quota credit and create internal justification for discount approval.

In practice, organisations that transition to MCA-E without independent Microsoft licensing advisory support typically see initial direct quotes from Microsoft that are 10–20% higher than their previous EA spend. The difference between an informed buyer and an uninformed buyer in this negotiation is real and measurable. Buyers who can demonstrate genuine multi-cloud optionality — credible Azure alternatives, an optimised licence estate, a willingness to delay commitment — consistently achieve better outcomes than those who signal urgency to transition.

Microsoft's Q4 Window Still Matters

Even under MCA-E, Microsoft's internal fiscal calendar creates pressure that buyers can exploit. Microsoft's fiscal year ends June 30. The April-to-June period — Microsoft's Q4 — is when account teams face their strongest quota pressure and when deal approval thresholds are at their most flexible. If your renewal or transition conversation is scheduled to complete in this window, your negotiating position is structurally stronger. If it is not, consider whether you can accelerate or delay timelines to align with Q4.

Azure MACC Commitments as a Negotiating Tool

Microsoft Azure Consumption Commitments (MACC) are a significant lever in MCA-E negotiations for organisations with meaningful Azure footprints. A MACC is a contractual commitment to consume a defined amount of Azure services over a defined period. In exchange, Microsoft is willing to offer meaningful discounts on Microsoft 365 and other cloud services as part of the same commercial discussion. For organisations that were already planning Azure investment, framing that investment as a MACC in the context of MCA-E negotiations can recover a significant portion of the discount headroom lost when automatic volume tiers were removed.

SKU Considerations During the MCA-E Transition

The MCA-E transition often coincides with pressure from Microsoft's field teams to move up the Microsoft 365 SKU stack. The current M365 SKU hierarchy runs E1, E3, E5, and E7 — with E7 as the newest and most comprehensive tier, released above E5. Microsoft field teams are actively running upsell motions from E5 to E7 at renewal, positioning E7's bundled AI, security, and compliance capabilities as a cost-effective alternative to maintaining separate add-on licences.

Buyers should evaluate E7 proposals carefully. The bundle economics can be attractive if you are already paying for Microsoft 365 Copilot at $30 per user per month as a standalone add-on, since E7 includes Copilot as part of the bundle. However, the per-user uplift from E5 to E7 adds meaningful cost per seat, and the benefit realisation depends on actual deployment of the bundled capabilities. Accepting an E7 upsell during MCA-E transition discussions without a usage roadmap is a common source of shelfware in the post-transition period.

What to Do Before You Sign the MCA-E

The single most important action before transitioning to MCA-E is to conduct a comprehensive licence optimisation exercise. Every unused seat, every over-provisioned SKU, and every capability being paid for but not deployed represents leverage in the negotiation — but only if you document it before you engage with Microsoft. Once you have signed the MCA-E with a given seat count and SKU mix, your ability to reduce that commitment is constrained to the seven-day window after each renewal date.

In parallel, procurement teams should model the total cost of the MCA-E proposal over a three-year period using realistic assumptions about annual price increases. Microsoft's list prices for cloud services have increased by between 15% and 25% over the last three years. Assuming flat pricing over the MCA-E term systematically underestimates the true cost of the agreement. A properly constructed TCO model, incorporating projected price escalation and the loss of SA benefits, often reveals that the apparent flexibility of MCA-E carries a higher long-term cost than a well-negotiated three-year EA commitment.

Working with Independent Advisors on MCA-E Transitions

The complexity and commercial significance of the EA-to-MCA-E transition is exactly the kind of situation where independent Microsoft licensing advisory expertise delivers measurable return on investment. Microsoft's account teams are experienced, well-resourced, and operating in their home territory — they have run hundreds of these transitions and know where buyers typically leave money on the table.

An independent advisor brings three things that internal teams rarely have in isolation: deep familiarity with the commercial structures and negotiating levers in MCA-E; benchmark data from comparable organisations that reveals what terms and discounts are achievable; and the ability to engage with Microsoft without the operational urgency that makes internal teams vulnerable to timeline pressure.

At Redress Compliance, our Microsoft EA negotiation specialists work exclusively on the buyer side. We have no commercial relationship with Microsoft and no incentive to recommend any specific agreement structure or product mix. Our role is to ensure that your MCA-E transition is structured on terms that reflect your actual negotiating leverage — not Microsoft's preferred commercial narrative.

Summary: Key Risks in an Unmanaged MCA-E Transition

Organisations that approach the MCA-E transition without preparation typically encounter a consistent set of risks. First, they accept Microsoft's opening proposal, which is routinely 10–20% above a negotiated outcome. Second, they fail to optimise the licence estate before committing, locking in shelfware at the new seat count. Third, they underestimate the value of what they are losing — SA benefits, True-Up predictability, price lock — and do not negotiate compensating provisions. Fourth, they accept a SKU mix that includes E7 or Copilot upsells without a deployment commitment, generating immediate cost without near-term value realisation.

None of these outcomes are inevitable. They are the product of insufficient preparation and insufficient leverage in the negotiation. The EA-to-MCA-E transition is a consequential commercial decision that deserves the same analytical rigour and external expertise as any other major procurement exercise.