The decision rule is shorter than the acronyms: estates anchored by committed Azure spend and a direct Microsoft relationship belong on MCA-E, while seat-based estates that want partner support and competable quotes belong in CSP — and most organisations leaving an Enterprise Agreement in 2026 end up running both. What actually separates the two is not price but structure: MCA-E is an evergreen contract with Microsoft that never forces a renewal conversation, CSP is a partner channel where the quote itself is negotiable.
Published 7 November 2025 · Last reviewed 7 November 2025
For two decades this comparison did not exist, because the Enterprise Agreement absorbed both roles. That ended in stages: Microsoft stopped signing new EAs for most commercial customers in January 2025, stopped renewing them below roughly 2,400 seats from November 2025, and since 1 March 2026 has been moving EA customers with Azure consumption commitments onto the Microsoft Customer Agreement for Enterprise at renewal. The EA-to-MCA-E migration and the EA-to-CSP move each have their own guide; this page covers the choice that remains once the EA is no longer on the table.
It is a genuine choice, not a formality. The two programs put the negotiation in different places, assign support differently, and treat price protection in opposite ways. Organisations that pick by inertia — defaulting to whichever path their incumbent reseller or Microsoft account team proposes first — routinely discover the structural consequences at the first repricing event rather than before signature.
This guide is general information about two Microsoft commercial programs, not legal or licensing advice for your situation. 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.
The Microsoft Customer Agreement for Enterprise is direct paper: a short core agreement signed once with Microsoft, evergreen, with no enrollment term and no end date. Product terms attach dynamically as you subscribe to services, and Microsoft updates them on its own schedule. Billing runs through billing accounts and profiles in the Microsoft admin center rather than through a licensing solution partner, and committed Azure spend — the MACC — is negotiated and tracked here. Crucially, the MCA-E carries no programmatic price protection: pricing follows Microsoft’s current catalog unless a price hold for a defined period is negotiated into the deal.
The Cloud Solution Provider program is a channel: you buy subscriptions 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 three-year on many products — with a short cancellation window at purchase, after which the term runs to its end. There is no estate-wide commitment and no Software Assurance, and the one genuinely negotiable element is the partner’s quote, which can be competed between partners without re-buying anything.
Put bluntly: under MCA-E you negotiate with Microsoft and then administer the result yourself; under CSP you accept Microsoft’s program rules and negotiate with the channel. Neither reproduces what the EA did, which was both at once.
| DIMENSION | MCA-E (DIRECT) | CSP (NEW COMMERCE) |
|---|---|---|
| Counterparty | Microsoft directly; no LSP in the contract path | A CSP partner, who owns billing and first-line support |
| Term structure | Evergreen agreement, no end date; subscriptions and commitments carry their own terms | Per-subscription terms — monthly, annual, three-year — locked after a short cancellation window |
| Price protection | None by default; follows the current catalog unless a price hold is negotiated | Price fixed for each subscription’s term; partner margin sets the final figure |
| Where negotiation lives | With Microsoft, per subscription or commitment; no automatic volume tiers | With the partner; quotes compete between partners on the same program terms |
| Azure commitments | The home of the MACC; EA-with-MACC customers moved here from March 2026 | Azure transacts through the partner; formal committed-spend deals generally sit on direct paper |
| Renewal event | None built in — the agreement never expires, so leverage moments must be created | Every subscription term-end is a repricing and re-quoting opportunity |
| Support | Microsoft support plans, purchased separately | Partner provides first-line support as part of the relationship |
| Administration | Billing accounts and profiles in the admin center; self-managed | Partner-managed; switching partners is possible without repurchasing licenses |
Note what is absent from both columns: the EA’s organisation-wide platform commitment, its annual true-up, and its automatic three-year price lock. Whichever way you go, those constructs need replacing by design — they do not come back.
The deepest difference is the renewal event. An EA expired every three years, which forced both sides to the table on a known date; an MCA-E never expires. Discounts and price holds negotiated into it run on their own schedules and lapse quietly, and Microsoft is under no contractual pressure to reconvene. Organisations on MCA-E therefore have to manufacture their own leverage moments — typically around MACC renewal, major workload decisions or Copilot adoption — and calendar them with the same discipline an EA renewal used to impose from outside. The Microsoft renewal page describes how firms run that work.
CSP inverts the picture. Program terms are non-negotiable and list pricing is set by Microsoft, but the partner’s quote is set from margin — so the negotiation is continuous, competitive and low-ceremony. Every term-end is a chance to re-quote, and switching partners does not disturb the licenses themselves. The trade-off is that no CSP negotiation will ever reach the constructs a direct deal can: committed-spend discounts, price holds, bespoke terms.
Compliance posture differs less than buyers expect. Neither program carries the EA’s true-up, so both reward continuous license hygiene over annual reconciliation — under-deployment is the bigger financial risk in subscription estates, which is why this decision sits close to licensing advisory and optimization work. One genuine difference: under MCA-E, Microsoft’s dynamically updated terms mean the rules of your estate can shift mid-stream, and someone needs to be reading the updates.
MCA-E fits organisations whose Microsoft spend is Azure-weighted, who negotiate committed consumption, who want the direct relationship and have the procurement and SAM maturity to manage an evergreen contract without an external forcing function. It is also, increasingly, not a choice: EA customers with MACCs are being landed here at renewal regardless of preference, which makes the negotiation of entry terms — price holds, discount schedules, commitment flexibility — the real decision.
CSP fits seat-dominated estates, organisations that lean on a partner for support and managed services, and buyers who value the ability to compete quotes and adjust the term mix as headcount moves. For most mid-market organisations exiting the EA, CSP is the default landing zone, with the partner choice mattering more than the program choice.
The split is the norm at scale. A common post-EA architecture puts the MACC and directly negotiated subscriptions on MCA-E and seat-based licensing in CSP — sometimes across more than one partner. That structure is sound when designed, and a liability when accumulated: each additional piece of paper adds a renewal calendar, a support path and a reconciliation surface.
Reading MCA-E as the EA’s successor in substance. It succeeds the EA in Microsoft’s catalog, not in its protections. Signing it without negotiated price holds recreates the EA’s spend on an agreement with none of the EA’s price discipline.
Letting the discount schedule lapse silently. With no renewal event, negotiated positions on MCA-E expire on dates only your own calendar will surface. The estates that do well on direct paper run an internal renewal cadence as if the contract still had one.
Taking the first CSP quote. The partner margin is the negotiable element, and it only moves under competition. A single-quote migration into CSP forfeits the program’s one structural advantage.
Assuming Azure commitments work in CSP. Transacting Azure through a partner is routine; a formal MACC with negotiated tiers is direct-paper business. Estates planning committed-spend deals need the MCA-E leg whether they want it or not.
Forgetting the entitlement archive. Whichever program wins, the EA’s entitlement record — two decades of perpetual rights, Software Assurance benefits and price references — should be exported and preserved before the old enrollment lapses. It is the evidence base for both the next negotiation and any later compliance review.
What the forced migration changes →
The partner-channel exit →
How to pick the firm for this work →
Firms that negotiate the entry terms →
Programs, audits, firms, countries →
Every field guide on the site →
No. The EA was a three-year enrollment with a locked price list, an annual true-up and a guaranteed renewal event. MCA-E is an evergreen agreement with no end date, terms that Microsoft updates dynamically as you add services, and no programmatic price protection — pricing follows the current catalog unless you negotiate a lock for a defined period. Treating the move as a paperwork formality is the most expensive misreading of it.
Not by default. Where the EA locked a price list for the three-year term automatically, an MCA-E follows Microsoft’s current catalog pricing. Price holds for a defined period can be negotiated into an MCA-E, and committed Azure spend is typically negotiated alongside as a MACC — but both are outcomes of a negotiation, not features of the program.
Not automatically. EA discounting was programmatic and estate-wide; under MCA-E, discounts are negotiated per subscription or per commitment and expire on their own schedules. Organisations migrating from a well-discounted EA should treat the move as a full renegotiation of every material line item, not a transfer of an existing position.
Contractually, no — MCA-E is direct paper between you and Microsoft, and the licensing solution partner role that intermediated the EA does not exist in it. In practice many organisations keep a partner for advisory, support or adjacent services, and Microsoft also operates partner-led MCA variants. The difference is that under MCA-E the partner is optional and the billing relationship is Microsoft’s.
On direct paper. Since 1 March 2026 Microsoft has been moving EA customers with Azure consumption commitments onto MCA-E at renewal, and new committed-spend deals are generally written there. Azure can be transacted through CSP, but a formal MACC with negotiated commitment tiers belongs to the direct agreement — which is the main reason Azure-heavy estates land on MCA-E.
Yes, and the combination is becoming the standard post-EA architecture: an MCA-E carrying the MACC and any directly negotiated subscriptions, with CSP carrying seat-based licensing through a partner whose quotes can be competed. The cost is administrative — two renewal calendars, two support paths — so the split should be designed deliberately rather than accumulated.
Choosing between direct paper and the channel — then negotiating the price holds, the MACC and the partner margin that make either work — 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.