Switching from EA to CSP or MCA: Transition Checklist and Guide

Why Enterprises Are Leaving the EA

The Enterprise Agreement was Microsoft's dominant commercial model for large organisations for over two decades. Its core value proposition — volume discounts, price lock, and a unified commercial framework — justified the three-year commitment and minimum seat requirements that defined the programme. That value proposition has eroded significantly since late 2025.

Microsoft removed volume-based discount tiers (Levels B through D) from the EA for online services in November 2025. All EA customers now pay a single standard Level A rate regardless of how many licences they commit to. The volume discount advantage — historically as much as 15 to 20 percent for large-scale commitments — has been entirely eliminated. Organisations that previously justified EA commitment on the basis of volume pricing now face a fundamentally different economics equation.

Simultaneously, Microsoft raised the minimum EA eligibility threshold to approximately 2,400 qualifying licences. Organisations below this threshold are being declined EA renewals at contract expiry and redirected to alternative programmes. Mid-market organisations that have held EA agreements for years are discovering at renewal that they no longer qualify, with transition timelines that often provide less than six months' notice.

The combination of these two changes has created a large population of enterprises that either cannot renew their EA or must reconsider whether the EA still delivers sufficient value to justify its structural inflexibility.

The Three Transition Destinations

Organisations leaving the EA have three primary commercial destinations. Understanding the structural differences between them is essential for selecting the right model for your organisation's profile.

Cloud Solution Provider (CSP)

The CSP programme allows organisations to purchase Microsoft cloud services — M365, Dynamics 365, Azure, Power Platform — through a certified Microsoft partner. CSP offers monthly or annual subscription terms with the flexibility to adjust licence counts at each anniversary. Three-year CSP terms are now available, providing price parity with EA annual pricing on most Microsoft products while retaining annual flexibility adjustments.

CSP's primary advantage over EA is its flexibility. Organisations can reduce licence counts at CSP annual anniversary dates — something impossible mid-term in an EA. For organisations with variable headcount, CSP eliminates the risk of paying for unused licences through a rigid three-year commitment. The CSP billing premium for monthly payment on annual terms (five percent from April 2025) is the primary cost trade-off against this flexibility.

CSP transactions through a certified partner also introduce a support relationship that can be valuable during licensing queries, service incidents, and commercial disputes. Partners with strong Microsoft relationships can escalate issues to Microsoft's support organisation with more authority than individual direct customers in many cases.

Microsoft Customer Agreement for Enterprise (MCA-E)

The MCA-E is Microsoft's newer commercial framework, being positioned as the successor to the EA for cloud-first organisations. It offers a streamlined agreement structure without the traditional EA's annual true-up process, with consumption-based billing for Azure and subscription-based billing for M365 and Dynamics 365. Price level protections similar to the EA's Level A pricing are available under MCA-E, but the absence of volume discount tiers means both programmes now start from the same baseline.

MCA-E organisations transitioning from EA without negotiation have reported 10 to 30 percent cost increases, primarily because the MCA-E's billing structure does not include the legacy EA commitments and True-Up credits that many organisations had accumulated. MCA-E transitions must be planned carefully to avoid billing surprises in the first quarter after transition.

Microsoft is reportedly planning to transition EA customers on Microsoft Azure Consumption Commitment (MACC) plans to MCA-E as their EA agreements expire, making MCA-E understanding increasingly important for any enterprise renewing a Microsoft agreement that includes Azure commitments.

Direct from Microsoft (for Large Enterprises)

Very large enterprises — typically those with Microsoft spend exceeding $5 to $10 million annually — may qualify for direct engagement with Microsoft's enterprise commercial team outside the standard EA or MCA-E frameworks. These bespoke commercial agreements can include custom pricing, extended terms, service level commitments, and deployment support that are not available through standard programme vehicles. Organisations in this category should engage directly with Microsoft's enterprise division and consider independent commercial advisory to ensure the bespoke terms are competitive.

Pricing Implications of Transitioning

The pricing impact of transitioning from EA depends significantly on three factors: the nature of your current EA pricing (whether you held legacy Level B, C, or D pricing that you are now losing), the specific Microsoft products in scope, and how effectively you negotiate the transition terms.

For M365, organisations holding legacy EA Level D pricing (the deepest discount tier, historically available at very large volumes) will see unit price increases at transition, even when moving to CSP or MCA-E at standard pricing. The removal of discount tiers means the unit price gap between legacy EA and new programme pricing can be material for organisations that negotiated deeply discounted EA rates before the 2025 changes.

For Dynamics 365, the pricing impact is typically smaller because Dynamics 365 list pricing is already standard across EA and CSP channels following the discount tier removal. The primary Dynamics 365 pricing lever now is optimisation of licence types (base-and-attach mechanics, Team Members tier allocation) rather than channel-level negotiation.

For Azure, the transition from EA to MCA-E requires particular care around Azure Reservations (pre-purchased compute commitments), Savings Plans, and any MACC commitments. These constructs behave differently under MCA-E billing and need explicit reconciliation at transition to avoid double-billing or lost reservation value.

Ten-Step Transition Checklist

1. Confirm EA expiry date and transition deadline. Identify the exact date your EA expires and the point at which Microsoft requires confirmation of your transition destination. Most EA agreements require notification six months before expiry if renewing on different terms or transitioning to a different programme.

2. Audit current licence usage across all Microsoft products in scope. Before transitioning, establish accurate counts of active users by product and licence type. Over-licensed users create unnecessary cost in any new programme, and inactive users should be removed before the new programme baseline is set.

3. Map Azure commitments, Reservations, and Savings Plans. Identify all Azure financial commitments — MACC amounts, active Reservations, Savings Plans, and any EA-specific Azure credits. These constructs must be explicitly addressed in the transition plan to avoid losing value or creating billing disruption.

4. Model CSP vs MCA-E economics at your actual usage. Produce a financial model comparing the three-year total cost of CSP (with three-year term pricing) versus MCA-E versus any available EA renewal option at your audit-adjusted user counts and Azure consumption projections.

5. Evaluate CSP partner options. If transitioning to CSP, assess multiple certified partners based on technical capability, support response, pricing, and Microsoft relationship quality. The partner relationship is a long-term commercial dependency — the selection deserves careful evaluation, not default to the incumbent Microsoft reseller.

6. Negotiate transition terms proactively. Both CSP partners and Microsoft's MCA-E commercial team will negotiate on pricing, service credits, migration support, and transition timelines. Organisations that approach the transition as a negotiated commercial event — not a passive migration — achieve significantly better terms than those that accept the first proposal presented.

7. Plan licence subscription start dates to avoid billing gaps. A common transition error is allowing a gap between EA expiry and new CSP or MCA-E subscription activation. Even a one-day gap creates service interruption for users. Plan the subscription start date to be concurrent with or immediately before EA expiry.

8. Confirm product feature parity between programmes. A small number of Microsoft product features are available only through specific commercial programmes. Confirm that every product and feature your organisation relies on is available under the new programme before committing to the transition.

9. Update procurement and finance processes for the new billing model. EA billing — annual true-up with a single invoice — is structurally different from CSP billing (monthly or annual invoices through a partner) and MCA-E billing (consumption-based Azure billing plus subscription billing). Finance and procurement processes must be updated to handle the new billing cadence, reconciliation requirements, and purchase order workflows.

10. Engage independent advisory support for the commercial negotiation. EA transitions are infrequent, consequential, and commercially complex. Microsoft's account team is optimising for Microsoft's revenue through the transition. An independent adviser with no vendor affiliation models the economics objectively, manages the transition negotiation, and ensures the commercial outcome protects your organisation's interests.

Avoiding the Five Most Common Transition Mistakes

Accepting Microsoft's default transition proposal: Microsoft's initial EA transition proposal is designed to maintain or increase Microsoft's revenue. It will not offer the optimal mix of CSP term structure, MCA-E pricing, and licence optimisation. Independent modelling is required before accepting any Microsoft transition proposal.

Not resetting the licence baseline at transition: Transitioning with the same licence quantities as the expiring EA means carrying all existing over-licensing waste into the new programme. The transition is the natural moment to right-size the estate before committing to a new term.

Ignoring the five percent monthly billing premium: Organisations transitioning to CSP and maintaining monthly payment on annual terms incur a five percent billing premium from April 2025. For a $1 million annual Microsoft spend, this is $50,000 per year in avoidable cost. Annual upfront payment eliminates this premium entirely.

Failing to address Azure financial constructs at transition: Azure Reservations, Savings Plans, and MACC commitments have specific mechanics under MCA-E and CSP billing. Failing to explicitly plan for these at transition creates the risk of stranded financial commitments or unexpected billing outcomes in the first quarter after transition.

Selecting a CSP partner without competitive evaluation: CSP partners vary significantly in technical capability, pricing aggressiveness, Microsoft relationship quality, and service responsiveness. A default to the incumbent reseller without competitive evaluation misses the opportunity to select a partner who can deliver long-term value across the licensing relationship.