Azure CSP versus EA, the vehicle is the discount
Azure under CSP gives monthly flexibility through a partner at pay as you go rates, while an Enterprise Agreement trades a multi year commitment for negotiated discounts, and since January 2025 Microsoft has been retiring the EA in direct markets, which makes the Microsoft Customer Agreement for enterprise the third vehicle every Azure buyer must model.
Prepared by Redress Compliance · August 6, 2026 · Microsoft advisory. Based on the Azure purchasing benchmark record of the Microsoft practice.
Executive summary
Three vehicles, three trades. CSP is partner led, monthly, and commitment free, with Azure billing at pay as you go retail rates and the partner's margin built into the arrangement.
The EA is a direct multi year commitment with negotiated discounts, and since January 2025 Microsoft has been refusing a growing share of direct market EA renewals.
The MCA-E is the evergreen replacement, where Azure discounts hinge on a negotiated consumption commitment rather than program price levels.
The breakeven is roughly $1 million. Below it, CSP's flexibility usually beats the committed vehicles' discounts; past roughly $1M of annual Azure spend, the committed vehicle wins on math, and the gap widens with scale.
The breakeven is a spend calculation, not a preference, and it moves as your consumption does, which is why the vehicle deserves a yearly re test.
The partner credit is negotiable at scale. CSP partner margin is built on the partner earned credit, and at material spend, part of it is negotiable back to you: the partner's economics are not fixed, and the buyer who knows the credit exists negotiates a different CSP than the buyer who does not.
Vehicles are inherited, not chosen. Across the estates we benchmark, companies sit on CSP long after spend justified a committed vehicle, or hold EA commitments they no longer fill, because nobody owns the re test.
The discipline is annual: the vehicle against current spend, with any transition started about nine months before enrollment expiry, because the vehicles' calendars are long and Microsoft's routing pressure is not neutral.
The three vehicles, compared where the money is
| CSP | Enterprise Agreement | MCA-E | |
|---|---|---|---|
| The construction | Partner led, monthly, commitment free | Direct, multi year, committed | Direct, evergreen, consumption committed |
| Azure pricing | Pay as you go retail, partner margin inside | Negotiated discounts against the commitment | Discounts hinge on the negotiated MACC, not price levels |
| Where it wins | Sub $1M spend, volatile estates, no commitment appetite | Legacy scale positions, while Microsoft still offers it | The destination vehicle: everything the EA routing sends |
| The watch item | The partner earned credit, negotiable at scale | The renewal Microsoft may decline to offer | The commitment sizing, where the whole discount lives |
The MCA-E moved the discount's home. Under the EA, program mechanics carried part of the pricing; under the MCA-E, the negotiated consumption commitment carries virtually all of it, which concentrates the entire Azure discount conversation into one number and its terms.
The commitment sizing discipline, floor not forecast, is no longer one lever among many; on the destination vehicle, it is the negotiation.
The breakeven, and the yearly re test
The arithmetic is stable: CSP's retail rates against the committed vehicle's negotiated discount, net of the commitment risk your consumption volatility actually carries. Below roughly $1M annually, flexibility usually wins; above it, commitment does, increasingly so with scale.
What is not stable is your spend, which is why inherited vehicles leak: the CSP arrangement outgrown three years ago, the EA commitment sized to a workload since re-platformed.
The re test is an afternoon a year: current spend against both models, the partner earned credit conversation where CSP stays, and the transition calendar drawn the moment the answer changes, nine months before expiry.
The commitment sizing on the committed side follows the estate's standard discipline, the post optimization floor with reserved coverage worked first, per the Microsoft leverage guide, and the Copilot consumption question addressed before the commitment per the credits and MACC brief.
The Microsoft EA renewal playbook
The seven levers on the twelve month calendar, with the vehicle decision, the MCA-E transition sequencing, and the commitment sizing worked on a representative estate.
Get the white paper →The EA retirement, and transitioning on your calendar
The January 2025 shift made the EA a vehicle with an exit date estate by estate: direct market renewals declined, populations routed to MCA-E, and the transition's terms decided by whose calendar it runs on.
The mechanics mirror the EA guide's transition analysis: moved at your renewal with the estate reconciled and protections drafted into the new paper, the transition carries your position forward.
Accepted as administrative routing, it resets whatever the EA protected, the Azure discounts first among it.
The nine month lead exists because the transition is three projects wearing one date: the commitment sizing negotiation, the licensing estate's carry over terms, and the operational cutover of billing and administration. Started early, each is a negotiation; started late, each is a form.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Azure purchasing decisions
Across the Azure estates we benchmark, the vehicle was inherited far more often than chosen, and the inheritance had a price in both directions:
Estates sitting on CSP retail rates years after spend passed the committed vehicle's breakeven.
EA commitments held against consumption that re-platforming had moved, paying for a discount the spend no longer earned.
The partner earned credit finding rounds it out: at material CSP spend, the credit conversation recovered points that no one had asked about, because the margin's existence was invisible to the buyer.
Purchasing vehicles reward exactly one behavior, the annual re test with current numbers, and punish exactly one, assuming last cycle's answer still holds.
Your first five moves
- Re test the vehicle annually: current Azure spend against all three models, owned, diarized, an afternoon a year.
- Open the partner earned credit conversation wherever CSP stays at material spend; the margin is negotiable to the buyer who knows it exists.
- Size any commitment to the post optimization floor, reserved coverage worked first, Copilot consumption addressed before the number.
- Start transitions nine months before expiry, because the MCA-E move is three negotiations wearing one date.
- Carry the EA's protections into the new paper explicitly, discounts, caps, and terms, or the routing resets them silently. The Microsoft practice and the Azure EA guide run the decision with you.
Frequently asked questions
What is the difference between Azure CSP and an EA?
CSP is partner led, monthly, and commitment free, with Azure billing at pay as you go retail rates and the partner's margin inside. The EA is a direct multi year commitment with negotiated discounts.
Since January 2025 Microsoft has been refusing a growing share of direct market EA renewals, routing estates to the MCA-E instead.
When does an Azure commitment beat CSP?
Once annual Azure spend passes roughly $1 million, the committed vehicle usually wins on math, and increasingly so with scale. The breakeven moves with your consumption, which is why the vehicle decision deserves an annual re test rather than the inheritance most estates give it.
What is the MCA-E and how does it price Azure?
The Microsoft Customer Agreement for enterprise, the evergreen successor the EA routing feeds. Azure discounts under it hinge on a negotiated consumption commitment rather than program price levels, which concentrates the entire discount conversation into the commitment's size and terms.
Can CSP pricing be negotiated?
At material spend, yes: CSP partner margin is built on the partner earned credit, and part of it is negotiable back to the customer. The conversation recovers points invisibly left on the table, and it only happens for buyers who know the credit exists.
Is Microsoft really retiring the Enterprise Agreement?
In stages: since January 2025 a growing share of direct market EA renewals have been declined, with estates routed to the MCA-E.
For affected estates the question is not whether but on whose calendar, and a transition run at your renewal with protections drafted beats administrative routing on every term that matters.
How long does an Azure vehicle transition take?
Plan nine months before enrollment expiry: the transition is the commitment sizing negotiation, the licensing carry over terms, and the operational billing cutover in one project. Each is a negotiation when started early and a form when started late, and the difference is priced accordingly.
