Why the Agreement Type Decision Is High-Stakes
The choice between Microsoft's Enterprise Agreement, Microsoft Customer Agreement, and Cloud Solution Provider model is one of the most consequential commercial decisions an enterprise makes — and one that is increasingly being made under time pressure at renewal, rather than with careful independent analysis.
Microsoft's commercial motion in 2025 and 2026 has emphasised MCA migration as a modernisation story. In specific situations, that narrative is accurate. In many large-enterprise contexts, it is not — and buyers who migrate to MCA without understanding what they are giving up often discover the cost difference in subsequent renewal cycles, when the pricing flexibility that defined their EA is simply no longer available.
This comparison covers the three models that matter for enterprise buyers: the Enterprise Agreement, the Microsoft Customer Agreement Enterprise (MCAE), and purchasing through Cloud Solution Providers (CSP). It is structured for buyers who need to make an informed decision — not a marketing decision.
The Enterprise Agreement: What It Is and Why It Still Dominates
The Enterprise Agreement is Microsoft's premier volume licensing vehicle for organisations with 500 or more users or devices. Despite persistent predictions of its decline, the EA remains the dominant mechanism for large enterprise Microsoft procurement — because it offers something that newer agreement types do not: genuine negotiation rights.
Commercial Structure
An EA is a three-year commitment that covers a defined set of Microsoft products — typically a core suite of M365 or Office 365 licences, plus optional product additions. The annual licence fee is based on a committed user count at the start of the agreement, with annual true-up adjustments for growth. The pricing is expressed as a discount from Microsoft's publicly listed price list (ERP), with the specific discount level determined through negotiation.
That last phrase — determined through negotiation — is the critical distinction. EA pricing is not fixed by a price list. It is negotiated. And because it is negotiated, a well-prepared buyer with independent advisory support can achieve pricing outcomes that bear no resemblance to Microsoft's opening proposal. Our average cost reduction across 500+ EA engagements is 32% from Microsoft's initial position.
What the EA Provides That Alternatives Do Not
The EA's commercial advantages over MCA and CSP include: price lock for three years (critical protection against Microsoft list price increases, which have averaged 8–12% per annum in recent years); negotiable true-up terms that define how growth is priced; Software Assurance benefits including upgrade rights, Licence Mobility, and training vouchers; the right to run licensed products on-premises under certain conditions; and contractual audit rights that constrain Microsoft's ability to unilaterally demand licence compliance evidence.
For organisations with complex on-premises infrastructure, multinational footprints, or significant software asset management complexity, these protections are material. Losing them through MCA migration is not a neutral outcome.
The Microsoft Customer Agreement: The Reality Behind the Modernisation Narrative
The Microsoft Customer Agreement Enterprise (MCAE) is Microsoft's newer transactional vehicle, designed to simplify procurement and accelerate migration to cloud-only consumption. Microsoft frames it as a modern, flexible alternative to the EA. The commercial reality is more nuanced.
What MCAE Is Designed to Do
MCAE eliminates the three-year commitment structure, replacing it with monthly or annual billing with greater flexibility to add and remove licences. It is purchased through the Microsoft Commerce Experience (MCX) platform with a more standardised pricing structure and fewer negotiation touchpoints than the EA. For organisations with highly variable licence needs or cloud-only workloads, this flexibility has genuine value.
What MCAE Gives Up
The tradeoffs are significant for most large enterprises. MCAE pricing is largely non-negotiable — you receive standard published pricing with limited ability to negotiate at the agreement level. The concept of a three-year price lock is replaced by Microsoft's right to adjust pricing with 30 days notice. Software Assurance benefits, including upgrade rights and Licence Mobility, are not available under MCAE in the same form as EA. On-premises licensing rights are more restricted. And the true-up mechanism — with all the negotiating leverage it creates — is replaced by a subscription model where growth is simply billed at list price.
For organisations that spent the last decade building negotiating leverage around their EA commitments, MCAE removes that leverage by design. Microsoft's commercial incentive to promote MCA migration is not altruistic — it converts negotiated pricing relationships into standardised billing relationships, at a net benefit to Microsoft's revenue predictability.
The EA-to-MCA migration decision should never be made at renewal as a secondary agenda item. It is a strategic commercial decision with implications for pricing flexibility, on-premises rights, and Software Assurance benefits that extend across the full next agreement cycle. Buyers who make this decision in the final 30 days of a renewal process rarely have the analysis needed to make it well.
CSP: When Channel Buying Fits — and When It Doesn't
The Cloud Solution Provider model routes Microsoft product purchases through an authorised partner rather than directly through Microsoft. The partner adds margin to Microsoft's pricing and in return is expected to provide value-added services such as support, migration assistance, and platform management.
Where CSP Has Genuine Value
For organisations under 300 users, organisations with primarily cloud workloads, and organisations that genuinely need and consume the wraparound services that a CSP provides, the CSP model can be cost-effective. The administrative simplicity of a single partner relationship and consolidated billing has real value for organisations with limited internal IT and procurement resource.
Where CSP Fails Enterprise Buyers
For organisations above 500 users with complex Microsoft footprints, CSP pricing is structurally higher than an EA negotiated by a prepared buyer. The CSP partner's margin is embedded in the per-unit price. The partner's incentive is to sell more Microsoft product — not to optimise your spend. And the CSP relationship removes your direct negotiating relationship with Microsoft, eliminating any ability to negotiate agreement-level terms.
We regularly encounter organisations spending 25–35% more in CSP arrangements than they would pay under an EA at comparable scale. The convenience of CSP is real. But it is expensive convenience — and for large enterprises, the costs typically outweigh the administrative savings.
Side-by-Side Comparison: EA vs. MCA vs. CSP
| Dimension | Enterprise Agreement | Microsoft Customer Agreement | CSP |
|---|---|---|---|
| Minimum Size | 500 users/devices | No minimum | No minimum |
| Pricing Model | Negotiated discount from ERP; three-year price lock | Published pricing; limited negotiation; can change with 30-day notice | Partner pricing; typically 15–25% above EA equivalent |
| Commitment Term | 3 years (annual true-up) | Monthly or annual, no multi-year lock | Monthly or annual per partner agreement |
| Negotiation Rights | Full negotiation on pricing, true-up terms, SKU mix, Azure MACC | Limited — standardised commercial terms | None with Microsoft; negotiation with partner only |
| Software Assurance | Full SA benefit catalogue available | Limited/equivalent benefits under different terms | Not available in traditional form |
| On-Premises Rights | Strong — perpetual licence rights, Licence Mobility | Reduced — primarily SaaS/cloud focus | Limited — cloud subscription only for most products |
| Audit Rights | Negotiable contractual constraints | Microsoft standard terms apply | Partner-managed; Microsoft retains audit rights |
| Billing | Annual; aligned to commitment | Monthly or annual; consumption-based for Azure | Monthly invoice through partner |
| Best For | 500+ user orgs with complex footprints; on-premises workloads; price lock priority | Cloud-first orgs; variable licence needs; flexibility priority | SME; cloud-only; value-added partner services required |
The Decision Framework: Four Questions That Determine the Right Choice
1. Do you have significant on-premises infrastructure?
If yes, the EA is almost certainly the right vehicle. On-premises licence rights under MCAE are materially weaker than under the EA. Organisations running SQL Server on-premises, Windows Server in private or co-located data centres, or Dynamics 365 on-premises cannot replicate EA's on-premises protections under MCA.
2. Is pricing stability over 36 months commercially important?
Microsoft has raised list prices consistently — Office 365 E3 has increased from $20 to $36 per user per month between 2020 and 2026, a compound annual growth rate above 10%. Under an EA with a three-year price lock, those increases do not affect your committed products during the agreement term. Under MCAE, they can be passed through with 30 days notice. If price stability is important to your budget cycle, the EA's price lock is a concrete financial advantage.
3. Does your organisation require agreement-level negotiation?
If your renewal scale, complexity, or strategic importance to Microsoft's business warrants agreement-level negotiation — as most 1,000+ seat organisations do — the EA is the only vehicle that enables it. MCAE pricing is standardised. CSP pricing is partner-determined. Only the EA gives you a direct negotiating relationship with Microsoft commercial.
4. What is your actual cloud-only workload percentage?
MCAE's primary advantage — flexibility — is most valuable when your Microsoft footprint is genuinely and predominantly cloud workloads with variable demand. If more than 40% of your licensed products are either on-premises or have predictable user counts, the EA's price lock and true-up mechanism will outperform MCAE's flexibility for the majority of your spend.
Right for the majority of large enterprises
If your organisation exceeds 500 seats, carries meaningful on-premises workloads, values pricing certainty, and has the procurement capability to negotiate the agreement, the EA continues to offer superior commercial outcomes to MCA or CSP. The negotiation friction is real but recoverable. The pricing advantages, properly negotiated, are permanent for three years.
Right in specific cloud-first circumstances
MCAE makes sense for organisations that have substantially completed their cloud migration, have genuinely variable licence needs that the EA's annual true-up cannot accommodate efficiently, and can accept the loss of EA-grade pricing negotiation in exchange for commercial flexibility. This is a smaller population than Microsoft's marketing suggests.
Right for SME; expensive for enterprise
CSP pricing for large enterprises rarely competes with a properly negotiated EA. The model works when the partner's added services genuinely offset the pricing premium — which is unusual at scale. Large organisations in CSP arrangements should benchmark their per-unit pricing against EA-equivalent pricing. The delta is often the size of a small software vendor contract.
Handling MCA Migration Pressure at Renewal
If your account team raises MCA migration during your EA renewal conversation, treat it as a separate decision that requires its own analysis timeline — not a condition of your renewal. Microsoft's interest in MCA migration is real but not time-constrained by your renewal date. You can renew your EA on its existing terms and conduct an independent MCA analysis in parallel.
The key questions to ask your account team when MCA is proposed: What specific commercial benefits does MCA offer our organisation compared to our current EA pricing? What on-premises rights do we retain under MCA for each product we currently license? What happens to our Software Assurance benefits? How is pricing protected against Microsoft list price changes? What is the specific pricing we would pay for each SKU under MCA?
Most account teams cannot provide satisfactory answers to all of these questions in a renewal meeting. That is the appropriate signal to conduct independent analysis before making the decision. Our EA to MCA Decision Framework provides a 24-dimension analysis methodology for this decision. The EA to MCA Transition Advisory service provides independent guidance for organisations navigating this choice.
For the broader context on EA negotiation strategy — including how to handle MCA pressure within a live renewal — see the Complete Guide to Microsoft EA Negotiation.