Microsoft is steering customers from Enterprise Agreements toward the Microsoft Customer Agreement (MCA) and Cloud Solution Provider (CSP) programme. This guide provides the complete transition checklist, from licence inventory and Software Assurance analysis through pricing negotiation, service continuity, and post-transition governance, so you move without losing discounts, dropping services, or creating compliance gaps.
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.
The single most important variable is timing. Mid-term EA exits carry financial penalties. The only practical transition window is at or near EA expiry. Organisations that started planning 18 months before expiry achieved 15 to 25% better pricing than those that started at 6 months. Time creates options. Options create leverage. Leverage creates discounts.
Download the complete enrolment detail from VLSC or the Microsoft 365 Admin Centre. This includes every product, SKU, quantity, effective date, and SA status. Reconcile it against your purchase orders. VLSC records are not always complete, especially for amendments executed mid-term. Always verify against the official record before planning the transition.
List every M365, Azure, Dynamics 365, Power Platform, and other cloud subscription, including quantities, assigned users, and utilisation rates. Identify subscriptions that are underutilised (less than 50% feature adoption) or unassigned. These represent immediate optimisation opportunities at transition.
List every perpetual licence in the EA: Windows Server, SQL Server, Office Professional Plus, CALs, RDS licences. Document which ones carry Software Assurance and calculate the annual value of each SA benefit: Azure Hybrid Benefit, version upgrade rights, licence mobility, training vouchers, and disaster recovery rights.
For every EA line item, identify the equivalent offering in CSP or MCA. Most M365 and Dynamics subscriptions map directly. On-premises products require more care: CSP offers some perpetual licences and server subscription options, but SA is not available through either CSP or MCA. Products without a direct equivalent (Visio, Project, speciality CALs) must be mapped individually.
Highlight every SA benefit you currently use that will not carry over to CSP or MCA. The highest-value items: Azure Hybrid Benefit (saving 30 to 40% on Azure Windows/SQL compute), licence mobility for server workloads, version upgrade rights, and Extended Security Updates for legacy products. Each requires a specific mitigation strategy.
Software Assurance is the single largest benefit lost when leaving an EA. It is also the most frequently underestimated.
| SA Benefit | What You Lose at EA Expiry | Annual Value (Typical Enterprise) | Mitigation Strategy |
|---|---|---|---|
| Azure Hybrid Benefit (AHB) | Cannot use on-prem licences to reduce Azure VM costs | $200K to $800K depending on Azure footprint | Maintain SA via MPSA for server licences; or accept higher Azure costs |
| Version Upgrade Rights | No right to install newer versions of on-prem software | Variable depending on upgrade cycle | Purchase new version licences when needed; or move to subscription equivalents |
| Licence Mobility | Cannot move server licences across servers without restrictions | Operational cost if restricted | Maintain SA via MPSA for mobile workloads; or consolidate onto fewer servers |
| Training Vouchers | No access to SA training benefit | $5K to $20K per year | Budget separately for training; use Microsoft Learn (free) |
| Extended Security Updates | No free ESU coverage for legacy products | $50K to $200K for Windows Server 2012/SQL 2014 estates | Migrate to current versions; or purchase ESU separately (3-year limit) |
If AHB saves more than the SA cost: maintain SA through a Microsoft Products and Services Agreement (MPSA). If you plan to retire on-premises within 3 years: accept the SA loss and budget for the temporary cost increase. If on-premises is strategic and long-term: negotiate a hybrid structure with MCA-E or CSP for cloud and MPSA for on-premises with SA. This is the most cost-effective approach for organisations with significant on-premises estates that will persist beyond three years.
The default pricing in both CSP and MCA is at or near Microsoft's retail list price, typically 15 to 30% higher than what you were paying under your EA's volume discount tiers.
For enterprises with 2,000+ seats and $2M+ annual Microsoft spend, MCA-E offers the best pricing potential. Microsoft's sales team has authority to offer discounts comparable to EA levels, but only when presented with a credible competitive alternative and a multi-year commitment. Expect 15 to 25% below list with strong negotiation.
CSP pricing includes the partner's margin (typically 2 to 8% above Microsoft's cost). For organisations that value managed services, technical support, and account management, the partner's margin is the price of that service. Direct pricing will be slightly higher than MCA-E, but the partner may offset this through optimisation services that reduce total cost.
Accepting the standard CSP or MCA proposal without negotiation is the most common and most expensive outcome. Organisations that transition at the last minute, without competitive evaluation or commitment leverage, consistently pay 15 to 30% more than their EA rate. This is the single most avoidable cost in the transition.
A 3,800-seat manufacturer was told its EA would not be renewed. Microsoft proposed MCA-E at list pricing for M365 E3 ($36/user/month), a 20% increase over the EA rate of $30. We helped the client issue a formal RFP to three CSP partners and Microsoft directly, conduct a Google Workspace pilot, and model a three-year consolidated deal. The winning CSP proposal: M365 E3 at $28.80/user/month (20% below list, 4% below the previous EA rate), plus managed services for Azure and Dynamics. Three-year savings versus the initial MCA-E proposal: $740K.
The highest-stakes element is ensuring no user loses access to any Microsoft service during changeover. Microsoft provides a grace period (typically 30 days) after EA expiry. This is your safety net, not your migration window.
| Phase | Timeline (Before EA Expiry) | Actions | Verification |
|---|---|---|---|
| Preparation | 60 to 90 days before | CSP/MCA agreement signed; tenant linked to new agreement; Azure plan configured | Confirm new agreement appears in admin centre; verify billing entity |
| Parallel Provisioning | 30 to 60 days before | Provision new M365 subscriptions under CSP/MCA in parallel with existing EA; do not assign to users yet | Verify all required SKUs and quantities available in new agreement |
| Licence Reassignment | 14 to 30 days before | Reassign user licences from EA to CSP/MCA subscriptions; batch processing via PowerShell or admin centre | Verify every user has active licence under new agreement; test service access |
| Azure Transition | 7 to 14 days before | Transfer Azure subscriptions to new agreement; re-establish reserved instances | Verify all Azure resources operational; check billing flows to new agreement |
| EA Closure | EA expiry date | Confirm all services running under new agreement; submit final EA true-up; close EA enrolment | Zero active subscriptions remaining under EA; no service interruptions |
If your new CSP/MCA agreement is not in place before the EA expires and the grace period ends, Microsoft will suspend services. Users lose access to email, Teams, SharePoint, and all M365 services. Recovery requires emergency licence provisioning at list price with no time for negotiation. This is entirely preventable with proper sequencing.
Your final EA true-up must account for any licences added since the last annual reconciliation. Under-reporting on the final true-up creates a compliance liability that persists after EA closure and can be raised in future audits. Over-reporting wastes money on licences you are about to transition away from. Microsoft will scrutinise the final true-up more carefully than mid-term true-ups because it represents the last revenue opportunity from the agreement.
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 all licence confirmations, ordering documents, and product key records before your VLSC access expires.
If maintaining SA through an MPSA, ensure the MPSA is signed and active before EA expiry. SA coverage gaps, even brief ones, can forfeit benefits permanently. Azure Hybrid Benefit, licence mobility, and version upgrade rights require uninterrupted SA coverage. Coordinate the MPSA activation with your CSP/MCA go-live date to ensure no gap in coverage.
CSP and MCA billing is monthly, not annual. Implement monthly reconciliation: compare active subscriptions against assigned users, identify unused licences, and adjust quantities. Under the EA, you paid a fixed annual true-up. Under CSP/MCA, you pay monthly for every active subscription. Unassigned licences are immediate waste, not deferred true-up adjustments.
Azure billing under CSP or MCA operates differently than under an EA MACC (Microsoft Azure Consumption Commitment). Set budgets, alerts, and spending caps in the Azure portal. If you had an Azure MACC under the EA, negotiate equivalent commitment discounts in the new agreement. Without a commitment, Azure pricing defaults to pay-as-you-go rates, which can be 15 to 25% higher than committed pricing.
Conduct a comprehensive Microsoft licence review annually: right-size M365 plans (downgrade E5 users who do not use E5 features to E3), reclaim unused licences, evaluate whether CSP partner is delivering value, and benchmark pricing against current market rates. The first annual review after transition typically identifies 10 to 15% additional savings that were not visible during the transition itself.
Yes, but only through negotiation. The default pricing in both CSP and MCA is at or near list price, which is 15 to 30% higher than typical EA volume discounts. MCA-E (direct with Microsoft) offers the best pricing potential for large enterprises. CSP partners can also offer competitive pricing, especially when presented with a competitive RFP process. The key is negotiating before the EA expires, not after.
SA is not available through CSP or MCA. When your EA expires, SA benefits end unless you maintain SA through a separate Microsoft Products and Services Agreement (MPSA). The most impactful benefit at risk is Azure Hybrid Benefit, which can save $200K to $800K annually depending on your Azure footprint. If AHB savings exceed the SA cost, maintain SA through an MPSA for your server licences.
Not if you plan properly. Microsoft provides a 30-day grace period after EA expiry. The actual transition should be completed before EA expiry through parallel provisioning: provision new CSP/MCA subscriptions alongside existing EA subscriptions, reassign users 14 to 30 days before expiry, and verify service access. If the new agreement is not in place before the grace period ends, Microsoft will suspend services.
MCA-E (direct with Microsoft) offers the best pricing for enterprises with 2,000+ seats and $2M+ annual spend. CSP (via partner) is better for organisations that value managed services, technical support, and account management. Many organisations use both: CSP for M365 with managed services, and MCA-E for Azure with direct Microsoft commitment discounts. Issue a competitive RFP to both channels to find the optimal combination. See EA vs CSP: The Full Guide.
Perpetual licences purchased under the EA remain yours after the EA expires. You retain the right to use the software at the version current when SA ended. However, without SA, you lose upgrade rights, Azure Hybrid Benefit, and licence mobility. Download and archive all licence documentation from VLSC before your access expires. The VLSC record is your proof of ownership.
Start 18 months before EA expiry. This provides time for complete licence inventory (2 to 3 months), SA analysis and mitigation planning (1 to 2 months), competitive RFP process with CSP partners and Microsoft (3 to 4 months), negotiation and agreement execution (2 to 3 months), and parallel provisioning and migration (2 to 3 months). Organisations that start at 6 months consistently achieve worse pricing and higher transition risk.
Accepting the first CSP or MCA proposal without negotiation. Default pricing is 15 to 30% above EA rates. The second biggest mistake is starting too late: organisations that begin planning 3 months before expiry have no time to create competitive tension, evaluate alternatives, or negotiate effectively. The combination of late start plus no negotiation routinely costs enterprises $200K to $1M+ in avoidable spend over the first three-year term.
Redress Compliance provides independent Microsoft advisory for EA transitions: licence inventory and entitlement mapping, SA analysis and mitigation, competitive CSP/MCA pricing negotiation, service continuity planning, and post-transition governance. We help enterprises achieve EA-equivalent pricing through structured negotiation and avoid the 15 to 30% cost increase that default transitions produce. Complete vendor independence. No Microsoft partnerships, no CSP affiliations, no resale commissions.
Microsoft Advisory ServicesIndependent Microsoft advisory helping enterprises transition from Enterprise Agreements to CSP or MCA without losing discounts, dropping services, or creating compliance gaps. Fixed-fee engagement models.