Eligibility now decides this question before preference does: since 1 November 2025, organisations below roughly 2,400 seats can no longer renew an Enterprise Agreement, so for most of the mid-market “EA vs CSP” really means “how do I leave the EA well.” Where both remain available, the EA still wins on a term-locked price list and deep Software Assurance constructs, while CSP wins on term flexibility, partner support and the ability to scale a changing estate — and since list pricing converged in late 2025, the decision is about structure, not headline rates.
Published 5 March 2026 · Last reviewed 10 March 2026
The Enterprise Agreement is a commitment instrument: a three-year enrollment, transacted through a licensing solution partner, built around an organisation-wide platform commitment, a price list locked for the term, an annual true-up to reconcile growth, and the full Software Assurance apparatus for on-premises estates. Its design assumption is a large organisation that standardises broadly and values predictability over agility.
The Cloud Solution Provider program is a channel instrument: you buy Microsoft cloud subscriptions — Microsoft 365, Azure, Dynamics 365, Copilot — through a CSP partner, who owns the billing relationship, sets the final price from its own margin, and provides first-line support. Under the New Commerce Experience, each subscription carries its own term: monthly, annual or, for many products since 2025, three years. Seats scale up at any time; they scale down only at the end of the term they were bought on, with a short cancellation window at purchase. There is no organisation-wide commitment, no true-up, and no Software Assurance.
Two structural consequences follow. First, in CSP the partner is a counterparty as well as a channel — quotes are genuinely competitive between partners, which never applied to the EA price list. Second, flexibility in CSP is something you architect, not something you receive: the standard pattern is a stable annual or multi-year core plus a monthly-term flex pool for seasonal or uncertain headcount, accepting the list premium that month-to-month terms carry.
This guide is general information about two Microsoft commercial programs, not legal or licensing advice for your situation. Microsoft’s program rules change and your contract governs. It names no firms; the firm directory lists Microsoft-capable advisors with balanced pros and cons, listed, not ranked.
Through 2025 Microsoft converted a preference into a policy. From January 2025 it stopped signing new EAs for most commercial customers; from 1 November 2025 it stopped renewing them below roughly 2,400 seats, pointing those organisations at CSP or at the direct MCA-E contract; and in the same period it removed the EA’s programmatic volume discount levels, so renewing EA customers now transact from a flat price list aligned with the successor programs. The EA itself has not been formally retired — it continues at qualifying enterprise scale, most commonly above 5,000 seats — but every one of these moves narrows it.
The practical sorting in mid-2026 looks like this: below the threshold, the live decision is MCA-E versus CSP, with CSP the default for organisations that lean on a partner and MCA-E for those that want a direct Microsoft relationship and committed Azure spend. Above the threshold, the EA-versus-CSP question is really a sequencing question — how long to keep the EA, and which workloads to move to CSP or MCA-E when its protections finally lapse.
| DIMENSION | ENTERPRISE AGREEMENT | CSP (NEW COMMERCE) |
|---|---|---|
| Eligibility in 2026 | Renewal generally limited to estates above roughly 2,400 seats; no new EAs for most customers | Open to any size; the designated home for most sub-threshold organisations |
| Term & commitment | Single three-year enrollment, organisation-wide platform commitment | Per-subscription terms — monthly, annual, or three-year on many products — with no estate-wide commitment |
| Price mechanics | Price list locked for the term; programmatic volume levels removed November 2025 | List pricing aligned with EA-equivalent commitments; final price set by the partner, so quotes compete; monthly terms carry a list premium |
| Scaling down | Reductions at anniversary within program rules; growth reconciled by annual true-up | Short cancellation window at purchase or renewal, then locked to term end; flexibility comes from mixing term lengths |
| On-premises & SA | Full Server/CAL and Software Assurance constructs; perpetual rights via L+SA | Perpetual licenses and server subscriptions available, but no Software Assurance; SA-dependent rights need restructuring |
| Azure commitments | MACC historically anchored here; those customers are being moved to MCA-E since March 2026 | Azure transacts through the partner; formal committed-spend deals generally require direct paper instead |
| Support & relationship | LSP transacts; support arrangements separate; Microsoft account team owns the relationship | Partner owns billing and first-line support; switching partners is possible without re-buying licenses |
The summary version: the EA concentrates everything — commitment, pricing, reconciliation — into one heavyweight instrument; CSP decomposes the estate into many light ones. Which is better depends entirely on whether your organisation benefits more from consolidation or from granularity.
CSP suits organisations with fluctuating or seasonal headcount, those that genuinely use a partner for support and adjacent services, mid-market estates that found the EA’s organisation-wide commitment heavier than their reality, and any buyer below the renewal threshold for whom the EA is simply no longer on the table. It rewards active management: term-mix design, renewal calendars per subscription pool, and periodic competitive re-quoting between partners — disciplines that sit naturally with cloud and SaaS cost optimization work.
The EA still suits large, stable estates that qualify to keep it: a locked price list across three years, one negotiation event instead of dozens of rolling ones, the true-up’s deploy-now-pay-later rhythm, and above all the Software Assurance machinery that deep on-premises Server/CAL positions depend on. For these organisations the EA’s remaining terms are an asset with a visible expiry date, to be used while planning the eventual landing zone.
Hybrids are normal. Committed Azure spend on direct paper, seat-based subscriptions in CSP, a legacy EA running out its term — many estates run all three at once. The design question is which workload sits on which paper and when each piece moves, not which single program wins.
Confusing CSP flexibility with month-to-month flexibility. New Commerce terms lock after a short cancellation window. An estate bought entirely on annual terms in a single week creates a single concentrated renewal cliff — the EA’s rigidity, reassembled by accident, without the EA’s price lock.
Carrying EA assumptions about reductions. There is no true-up and no anniversary right-sizing unless your term structure creates one. Over-buying at migration is the most common avoidable cost in EA-to-CSP moves.
Treating the partner quote as the price. The partner sets pricing from margin, and partners compete. A single-quote migration leaves the one genuinely negotiable element of CSP unexercised.
Forgetting the on-premises tail. Software Assurance does not exist in CSP. Upgrade rights, mobility rights and hybrid benefits need a mapped destination before the EA lapses — and the entitlement record for two decades of EA purchases should be exported and archived while the data is still easy to assemble, both for the negotiation and for any later compliance review.
Letting the EA expire before the alternative is signed. The strongest negotiating posture is holding a live EA with a credible plan to move; the weakest is an expired one with workloads stranded mid-decision. Twelve months out is a normal starting point for this work, as the Microsoft renewal page sets out.
The direct-contract alternative →
The post-EA choice →
How to pick the firm for this work →
The vendor-level view →
Firms that do this engagement →
Every field guide on the site →
For many organisations the choice is now made by eligibility. Since 1 November 2025, customers below roughly 2,400 seats have been unable to renew an Enterprise Agreement and are steered to CSP or MCA-E. Above that threshold the EA remains available through licensing solution partners, so larger estates still face a genuine three-way decision between an EA term, MCA-E and CSP.
Not structurally, any longer. Microsoft removed the EA’s programmatic volume discount levels in November 2025 and has aligned list pricing across programs, and CSP now offers one- and three-year terms at parity with equivalent commitments. The real difference is who sets the final price: under CSP the partner prices from its own margin, which means quotes are competitive between partners, while term length drives cost — month-to-month flexibility carries a list premium over annual and multi-year terms.
Generally no. Under the New Commerce Experience a subscription can be cancelled or resized downward only within the first days of purchase or renewal; after that window it runs to the end of its term. Flexibility comes from structuring the estate as a mix of term lengths — a stable annual or three-year core plus a monthly-term flex pool — rather than from any right to shed seats mid-term.
CSP sells perpetual on-premises licenses and server subscriptions, but it does not offer Software Assurance. SA-dependent constructs — upgrade rights, license mobility, hybrid benefits in their EA form — need to be mapped to CSP equivalents or restructured, and entitlements acquired under the EA should be documented before it lapses. Estates with deep Server/CAL plus SA positions are usually the hardest part of any EA-to-CSP analysis.
Yes, and hybrid structures are common: a direct agreement for Azure consumption commitments, CSP for seat-based subscriptions, sometimes more than one CSP partner. The cost of a hybrid is administrative — multiple renewal calendars, multiple support paths — so it should be a deliberate design, not an accumulation.
As a rule, formal MACC-style consumption commitments sit under direct agreements — historically the EA, and since March 2026 increasingly the MCA-E. Azure can certainly be transacted through CSP, but organisations negotiating committed-spend deals with Microsoft will generally be doing so on direct paper, which is one of the main reasons larger estates land on MCA-E rather than CSP.
Weighing an EA term against a CSP structure — and then designing the term mix, the partner competition and the on-premises landing zone — is exactly what a Microsoft licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.