Microsoft EA vs CSP vs MCA: Choosing the Right Agreement for Your Enterprise

Why the Choice Between EA, CSP, and MCA Has Never Mattered More

Microsoft's active commercial campaign to migrate EA customers to MCA-E began in earnest in early 2025. From January 2025, Microsoft started notifying EA customers that renewal of certain EA agreements was no longer available. From March 2026, Microsoft is actively migrating EA customers on Azure consumption commitments to MCA-E. For enterprises with renewals due in the next 12 to 24 months, the question of which agreement model to choose is not a procurement formality — it is a strategic commercial decision with multi-million-dollar implications.

The three models cover fundamentally different commercial positions. The EA protects the buyer with price certainty and structured negotiation leverage. CSP gives flexibility with minimal discount but supports partner-managed relationships. MCA-E gives Microsoft annual pricing flexibility that the buyer does not share equally. Choosing between them requires understanding what each model actually delivers — not what Microsoft's account team presents it as delivering.

The Enterprise Agreement: Structure, Terms, and Trade-offs

The Enterprise Agreement is a three-year volume licensing contract typically available to organisations with 500 or more users or devices. It requires enterprise-wide deployment coverage for included products and includes Software Assurance for all licences. Pricing is fixed for the duration of the three-year term with an annual True-Up mechanism to report additions above the initial order quantity.

The EA's primary commercial advantage is price certainty. In a Microsoft licensing environment where list prices have increased at 8 to 25 percent in each of the last three renewal cycles, locking pricing for three years is a material budget protection. The EA also provides the most structured negotiation framework: discounts are negotiated against a defined baseline, Software Assurance benefits are catalogued, and the True-Up mechanism is contractually defined.

Current EA discounts off list price range from 10 to 20 percent for standard M365 workloads. The historical range of 15 to 25 percent has contracted as Microsoft has removed the volume tier pricing that previously rewarded large organisations with automatic discounts. Achieving the upper end of the current range requires structured negotiation leverage — competitive alternatives, Microsoft's Q4 timing pressure (April to June), and a well-prepared internal position.

The EA's limitations are meaningful. It requires organisation-wide commitment, which means paying for licences across the full qualifying user population regardless of deployment status. Software Assurance is compulsory and adds cost for organisations that derive limited value from SA benefits. And the three-year commitment reduces flexibility when technology needs change mid-term.

For the M365 SKU stack — E1, E3, E5, and the new E7 tier which represents the top of the stack above E5 — the EA remains the model that best protects large enterprises. E7, which bundles advanced AI, security, and compliance capabilities previously sold as E5 add-ons, is most effectively priced within a structured EA negotiation rather than through MCA-E or CSP.

The Cloud Solution Provider Programme: Flexibility with Partner Management

CSP is Microsoft's partner-managed licensing programme. Rather than transacting directly with Microsoft, the enterprise works through a Microsoft-authorised partner who manages billing, support, and licence administration. CSP licences operate on monthly or annual commitments under the New Commerce Experience (NCE) framework.

NCE pricing is blunt: monthly commit equals list price with no discount. Annual commit provides up to 5 percent discount over monthly pricing. Three-year commit provides better discounts but reduces flexibility significantly. None of these discount levels approach what a negotiated EA delivers for large enterprises.

CSP's commercial case rests on flexibility, not price. Licences can be adjusted more readily than under an EA, and the partner relationship can provide support, migration assistance, and managed services that the direct Microsoft relationship does not include. For organisations where the managed service wrapper has genuine value, CSP can be cost-competitive on a total services basis even if the licence unit price is higher.

For large enterprises managing primarily M365 and Azure workloads at scale, CSP is generally not the right primary vehicle. The discount gap versus a properly negotiated EA is too large, and the lack of structured Software Assurance benefits removes value that EA customers receive as standard. CSP is more appropriate for smaller organisations, specific workloads where flexibility genuinely matters, or as a complement to an EA for products not covered under the primary agreement.

The Microsoft Customer Agreement for Enterprise (MCA-E): Microsoft's Preferred Motion

MCA-E is an evergreen agreement with no fixed term. Subscriptions renew annually or monthly at Microsoft's current pricing — there is no price lock. The MCA-E was designed by Microsoft to solve a problem Microsoft had with EAs: three-year price locks prevented Microsoft from realising the full benefit of annual list price increases.

Microsoft's sales motion frames MCA-E as a simplification — fewer contractual obligations, no mandatory organisation-wide coverage, more flexible subscription management. The framing is accurate but incomplete. The flexibility cuts both ways, and the asymmetry favours Microsoft structurally.

Under MCA-E, Microsoft retains the right to change pricing at each annual renewal. The buyer's ability to reduce commitments is restricted to a narrow window — typically seven days after each order — which in practice means annual cost reductions are very difficult to execute at scale. Organisations that transitioned from EA to MCA-E without negotiated price protections saw 10 to 30 percent cost increases at their first MCA-E renewal as Microsoft removed EA-era discounts from the relationship.

Software Assurance is not available under MCA-E. For organisations with material SA benefit consumption — deployment planning services, training vouchers, licence mobility rights — the loss of SA represents real cost that must be sourced separately or foregone. This is rarely factored accurately in Microsoft's MCA-E migration proposals.

Pricing under MCA-E can be negotiated, but the structure requires per-subscription negotiation without the volume discount framework that EA provides. The result is typically lower aggregate discounts than an equivalent EA negotiation, particularly for large, complex Microsoft footprints spanning M365, Azure, Dynamics 365, and Copilot.

Head-to-Head Comparison on Key Dimensions

Price certainty: EA wins outright with a three-year price lock. MCA-E provides no price lock — annual renewal pricing is at Microsoft's discretion. CSP annual commit locks pricing for 12 months but at minimal discount.

Discount level: EA negotiated discounts of 10 to 20 percent off list substantially exceed CSP annual commit (up to 5 percent) and MCA-E (negotiated per subscription, typically lower aggregate discount). For a $10 million annual Microsoft spend, this gap represents $500,000 to $1.5 million per year.

Flexibility: MCA-E and CSP offer more subscription flexibility than EA. EA organisation-wide commitments create minimum licence floors. However, the True-Up mechanism manages additions, and mid-term right-sizing is possible with appropriate negotiation at the True-Up.

Software Assurance: EA includes compulsory SA with a defined benefit catalogue. MCA-E does not support SA. CSP does not include SA benefits. For organisations that use SA benefits effectively, this difference adds meaningful value to the EA model.

Negotiation structure: EA provides the most structured negotiation framework, with a defined baseline, established discount levers, and Microsoft's field team incentives tied to EA renewal outcomes. MCA-E negotiation is fragmented across individual subscriptions. CSP pricing is set through the partner relationship with limited enterprise negotiation leverage.

Microsoft's commercial preference: Microsoft is actively steering customers toward MCA-E because it removes the three-year price lock, eliminates the structured negotiation framework, and enables annual pricing adjustments. The fact that Microsoft prefers MCA-E is itself information about where the commercial advantage lies.

Who Should Choose Each Agreement Model

The EA remains the right primary vehicle for large enterprises with more than 500 users, significant M365 workloads across the E1, E3, E5, and E7 SKU stack, meaningful Azure consumption under a MACC commitment, and a procurement function capable of managing the negotiation and True-Up process. The EA's price certainty, Software Assurance benefits, and structured negotiation framework deliver the best total commercial outcome for this profile.

CSP is appropriate for organisations with fewer than 500 users, for workloads where monthly subscription flexibility genuinely matters over a three-year period, and as a supplement to an EA for specific products that benefit from partner management. CSP can also be the right vehicle for organisations where the reseller's managed service capability adds value that offsets the higher licence cost.

MCA-E becomes the only viable option when Microsoft declines to offer an EA at renewal — which is increasingly the case for organisations with fewer than 2,400 users. For these organisations, negotiating the best possible MCA-E terms — including pushing for multi-year price protections, defined renewal discount floors, and Software Assurance equivalent benefits where available — is the critical commercial task. Accepting MCA-E default terms is not the same as accepting that MCA-E cannot be negotiated.

Key Questions Before Choosing Your Agreement Structure

Before committing to any Microsoft agreement model, these questions should be answered with independent analysis rather than relying on Microsoft's commercial guidance.

• What is our three-year Microsoft cost forecast under each model at current list price trends? A 10 to 15 percent annual price increase compounded over three years is very different under MCA-E (reset annually) versus EA (locked at year-one price).
• What SA benefits are we currently consuming? If training vouchers, deployment planning services, and licence mobility rights are being used, their loss under MCA-E has a real cost that must be quantified.
• Is our Microsoft footprint stable or growing rapidly? Rapidly growing organisations benefit more from EA flexibility through the True-Up than stable ones. But the price lock advantage of an EA increases with rising list prices regardless of growth.
• What is the realistic discount we can achieve under each model? Microsoft's MCA-E proposal will typically show lower list price starting points. But once discounts are applied, the EA baseline is almost always lower for large, well-negotiated agreements.
• Is Microsoft offering EA renewal or steering us toward MCA-E? If Microsoft is steering away from EA, it is worth understanding why — and whether independent advocacy can change that position or improve the MCA-E terms significantly.