EN DE
Home
Solutions Optimization Service FinOps Zation Platform CSP
Portal CSP Portal CHF CSP Portal EUR Zation Platform
Insights Blog Success Stories
About us Contact
Guide

EA, CSP or MCA-E

What actually differs between the three Microsoft agreements, which one fits which estate, and why the decision is about quantity rather than discount.

EA, CSP and MCA-E are three ways to buy the same Microsoft licences. The Enterprise Agreement binds a quantity for three years in exchange for price stability; CSP trades some unit price for the ability to change seat counts at term boundaries; MCA-E buys cloud directly from Microsoft with operational flexibility but little negotiable. Microsoft has raised the seat threshold for the EA and removed volume discount tiers on Online Services, which is why organisations that never questioned their agreement are now choosing between the other two.

Updated

The differences that cost money

Not a feature matrix — the dimensions where the choice actually shows up on an invoice.

Dimension EA MCA-E CSP
Who you buy from Microsoft, via a licensing partner Microsoft, directly A CSP partner
Term Three years, fixed Rolling, cloud-first Monthly, annual or three-year
Reducing seats mid-term Not until renewal Depends on the term chosen Only within seven days of a purchase, renewal or addition
Price protection Historically the main reason to sign one Little to none across terms Within the chosen term
Who supports you Microsoft, support purchased separately Microsoft, self-service by default Your partner, first line
Room to negotiate Real, at renewal, with volume Very limited; largely standard terms Through the partner, on service and terms

Which one fits

An EA still fits

Large, stable seat counts that clear the current minimum, a hybrid estate with meaningful Software Assurance value, and enough volume that a renewal negotiation is a real negotiation rather than a form.

CSP fits

A headcount that moves, a preference for one partner who handles licensing and optimisation together, and a willingness to plan around the seven-day window rather than pretend it does not exist.

MCA-E fits

A cloud-only estate, an organisation comfortable transacting directly with Microsoft, and no expectation of negotiated terms or long price protection. Operationally light, commercially rigid.

The comparison that decides it is not unit price. It is how many seats you would remove if the agreement let you. An estate with a clean licence position can pick the cheaper instrument on the merits; an estate without one ends up negotiating a discount on a quantity nobody has verified — and a discount on seats you do not need is not a saving.

Questions, answered

Why are we being pushed off our Enterprise Agreement?+
Microsoft raised the seat threshold for Enterprise Agreements, so organisations below it can no longer sign or renew one and must move to CSP or the Microsoft Customer Agreement for Enterprise. Separately, volume-based discount tiers on Online Services were removed, which means an EA that can be renewed no longer carries the discount that justified it. Check your own numbers against the current threshold rather than the one that applied at your last renewal — it has moved.
Is CSP cheaper than an EA?+
It depends almost entirely on how stable your headcount is, and the comparison is usually made wrong. An EA commits you to a quantity for three years; CSP lets you right-size at term boundaries. If your estate carries seats you would remove given the chance, CSP wins on the quantity even where it loses on the unit price. If your headcount genuinely does not move, the EA's committed volume is the cheaper instrument. Compare total commitment, not unit price.
What is MCA-E, in one sentence?+
The Microsoft Customer Agreement for Enterprise: a digital, modular agreement for buying cloud directly from Microsoft, with operational flexibility but without the long price fixing, volume tiers or negotiated clauses an EA carried.
When should we start looking at this?+
Twelve to eighteen months before your agreement ends. Not because the paperwork takes that long, but because the only real leverage you have is a clean licence position — and building one, getting it agreed internally and acting on it takes a renewal cycle. Arriving at the negotiation with the quantity still unresolved means negotiating the discount instead, which is the smaller number.
Do licensing rights change when we move?+
Some do, and this is where migrations go wrong quietly. Software Assurance benefits and server CALs do not transfer between programmes the way people assume, and a few enterprise products are not available in every channel. Inventory the entitlements you rely on before the move, not after — the gap usually surfaces months later, in an audit or a failed deployment.

Decide on your numbers

We build the licence position first, then the agreement comparison means something.

Contact us Optimization Service