Switching from an EA to CSP or MCA — A Transition Checklist for a Smooth Change

Why the EA-to-CSP/MCA Transition Is Happening — and Why Timing Is Everything

Microsoft is no longer renewing Enterprise Agreements for a growing number of customers. Organisations with fewer than 2,400 seats, those without significant on-premises licensing needs, and customers whose Microsoft relationship is predominantly cloud-based are being directed toward the Microsoft Customer Agreement (MCA) or the Cloud Solution Provider (CSP) programme at their next renewal.

This is not optional for many enterprises — it is a forced migration dressed as modernisation. And like any forced migration, the organisations that plan it methodically achieve dramatically different outcomes from those that react at the last minute.

The single most important variable in the transition is timing. Mid-term EA exits carry financial penalties — the remaining term's commitment is typically still payable. The only practical transition window is at or near EA expiry. This means your planning must begin 12–18 months before that date, not 3 months before when Microsoft's account team calls with their "standard" MCA offer.

"In every EA-to-MCA transition we have advised, the organisations that started planning 18 months before expiry achieved 15–25% better pricing than those that started at 6 months. The reason is simple: time creates options. Options create leverage. Leverage creates discounts. Start early."

Phase 1 — Complete Licence Inventory and Entitlement Mapping

The foundation of a successful transition is a complete, verified inventory of every Microsoft product and entitlement in your current EA. This is not a spreadsheet exercise — it is a compliance exercise. Every item you miss creates either a gap (you lose access to something you need) or waste (you pay for something you do not need in the new agreement).

Phase 2 — Software Assurance Analysis and Mitigation

Software Assurance is the single largest benefit lost when leaving an EA. It is also the most frequently underestimated. Many organisations know they have SA but have never calculated its total value — which often exceeds the SA fee itself when Azure Hybrid Benefit, upgrade rights, and mobility are factored in.

Phase 3 — Pricing Negotiation and Channel Selection

The transition from EA to CSP or MCA is a procurement event — and like any procurement event, the price you pay depends entirely on how well you negotiate. The default pricing in both CSP and MCA is at or near Microsoft's retail list price, which is typically 15–30% higher than what you were paying under your EA's volume discount tiers.

Phase 4 — Service Continuity and Zero-Disruption Migration

The highest-stakes element of the EA-to-CSP/MCA transition is ensuring that no user loses access to any Microsoft service during the changeover. A disruption — even a few hours without email, Teams, or SharePoint access — creates organisational chaos, executive escalations, and lasting distrust in the licensing team's competence.

The good news: zero-disruption transitions are entirely achievable with proper sequencing. Microsoft provides a grace period (typically 30 days) after EA expiry during which services continue to function. This is your safety net, not your migration window. The actual transition should be completed before EA expiry, with the grace period serving as contingency only.

Phase 5 — True-Up Closure and EA Wind-Down

The EA does not simply disappear at expiry — it requires formal closure. This includes the final true-up settlement, confirmation of perpetual licence entitlements (if any), and documentation of any SA benefits that will be maintained through an MPSA or other vehicle.

Many organisations underestimate the administrative effort required to close an EA cleanly. The final true-up is particularly consequential: Microsoft will scrutinise it more carefully than mid-term true-ups because it represents the last revenue opportunity from the agreement. Under-reporting triggers a compliance liability that persists after closure and can be raised in future audits. Over-reporting wastes budget on licences you are transitioning away from. Invest the time to reconcile the numbers accurately — a few hours of diligence prevents months of dispute resolution.

Perpetual licence documentation is equally critical. After the EA closes, your proof of ownership for any on-premises perpetual licences rests on the VLSC records and your ordering documents. If these are incomplete or inaccessible, you may face challenges defending your entitlements in a future Microsoft audit. Download, archive, and store multiple copies of all entitlement records before the EA closes and VLSC access is potentially modified. Treat this as a compliance insurance policy — the documentation you create today protects you from disputes that may arise years after the EA has closed.

Phase 6 — Governance in the New World

The EA provided structural governance: fixed seat counts, annual true-ups, and a defined three-year review cycle. CSP and MCA remove these guardrails. Without replacement governance structures, licence costs drift upward as teams add subscriptions, user counts grow unchecked, and Azure consumption scales without budgetary controls.

The Complete EA-to-CSP/MCA Transition Checklist

The following checklist consolidates every action required for a successful transition. Use it as a project plan, assigning owners and deadlines to each item.

"The worst thing you can do is treat the EA expiry as a deadline to meet. Treat it as a negotiation to win. Every week of preparation you invest before the deadline translates directly into better pricing, better terms, and a cleaner licence estate on the other side."