Azure CSP vs EA. The 2026 buyer guide.

Azure under CSP gives monthly flexibility through a partner while an Enterprise Agreement trades a multi year commitment for negotiated discounts, so the right vehicle follows the size and predictability of your spend.

Since January 2025 Microsoft has also been retiring the EA in direct markets, which makes the Microsoft Customer Agreement for enterprise the third vehicle every Azure buyer must model.

This guide is for cloud and procurement leaders deciding how to buy Azure in 2026. Pair it with the Azure EA guide and the Microsoft Practice page so the purchasing and licensing strategy line up.

How do CSP and EA differ for Azure?

CSP buys Azure through a partner at published pay as you go rates with monthly billing and no minimum, while an EA is a direct three year contract with Microsoft that trades a monetary commitment for negotiated rates. The split is flexibility against commitment.

CSP keeps you nimble through a partner, while the EA locks a term in exchange for discount and price protection.

How does buying Azure through CSP work?

CSP is a partner managed model with monthly billing and no minimum. Microsoft documents the program in its Partner Center documentation, and the partner handles billing and first line support.

Under the Azure plan in the new commerce experience, you consume at Microsoft's published pay as you go rates, priced in USD and delivered to partners in real time through the Azure plan price list. The partner gets no wholesale discount on Azure consumption.

Its economics rest on the partner earned credit, a margin Microsoft pays only while the partner holds admin access to your environment.

That structure matters to buyers. The partner earns more when it manages your estate, so in CSP the service conversation and the price conversation are one negotiation.

How does buying Azure through an EA work?

The Enterprise Agreement is a direct commitment with Microsoft, usually three years. Microsoft outlines the program on its Enterprise Agreement pages, and the commitment unlocks negotiated discounts.

The EA carries a floor of 500 users or devices for commercial customers and 250 for public sector. Azure rides on the enrollment as an Azure prepayment, historically from around $12,000 a year, with your negotiated rate card held for the term of the enrollment.

Volume pricing runs through four levels, A through D, from 500 seats at Level A to 15,000 and above at Level D. Those programmatic level discounts are precisely what disappears when Microsoft moves you off the EA. That is why the vehicle question in 2026 is a money question, not an administrative one.

Is the enterprise MCA now the real third option?

Yes. Since January 1, 2025 Microsoft has been refusing EA renewals for a growing share of cloud customers in direct markets and offering the Microsoft Customer Agreement for enterprise instead, so most Azure buyers now face a three way choice.

Microsoft confirmed the change in a November 2024 licensing update. Cloud EAs in direct markets, starting with a small percentage of enrollments, stopped being eligible for renewal from January 1, 2025, with the enterprise MCA positioned as the successor. Direct markets are the countries where Microsoft transacts with you without a licensing solution provider in the middle.

The enterprise MCA is an evergreen contract. Microsoft's own Microsoft Customer Agreement page stresses that it never expires and carries no purchase minimums. That sounds like pure upside until you price it.

What you lose is the EA's programmatic machinery. There are no Level A through D price bands, no discounted Software Assurance renewal path, and Azure starts at retail rates until you negotiate a consumption commitment. Every discount becomes a deal by deal negotiation with no published floor beneath you.

Ask your account team, in writing, whether your enrollment sits in a refusal wave before treating an early transition as mandatory.

How does the cost compare between CSP and EA?

List rates are now broadly aligned across channels, so the real comparison is which discount instrument each vehicle lets you unlock. Small or lumpy spend favors no commitment, while large steady spend favors a committed discount.

When does CSP win?

• Variable spend: no commitment to overshoot or undershoot, and monthly billing tracks actual consumption.
• Smaller estates: below the 500 seat EA floor, or below the spend where Microsoft will negotiate seriously.
• Partner support: value added managed services bundled into the same relationship, funded partly by the partner earned credit.
• Exit optionality: you can move the billing relationship to another partner without touching the workloads themselves.

When does an EA win?

• Large spend: a negotiated committed discount beats retail list rates by an amount no partner margin can match.
• Predictable demand: the commitment is easy to fill, so the discount carries little consumption risk.
• Price protection: your negotiated rate card is held across the enrollment term while retail rates move.
• Budget certainty: a prepayment burning down against known rates is easier for finance to plan than a floating monthly invoice.

Where do the discounts actually sit in each channel?

EA discounts sit in a negotiated rate card locked at enrollment, enterprise MCA discounts sit in the Azure consumption commitment you negotiate, and CSP discounts sit inside the partner's own margin. Knowing which pocket the money comes from tells you who to press and how hard.

On an EA, Azure pricing is agreed at signature and held for the term. Price protection cuts one way in your favor: published reductions flow through, while increases wait until renewal. The negotiated discount is tied to your monetary commitment and your overall enrollment value.

On the enterprise MCA, Azure starts at pay as you go retail. The negotiable instrument is the Microsoft Azure Consumption Commitment, a contracted total spend over a defined period, and the discount percentages attached to it. No commitment usually means no discount, and price protection exists only where your deal writes it in.

In CSP, Microsoft sets the customer facing rate and compensates the partner through the partner earned credit on eligible consumption, paid only while the partner holds an eligible admin role in your tenant, as described in Microsoft's partner earned credit documentation.

Reservations, savings plans, and marketplace purchases sit outside that credit. Any discount you extract in CSP is the partner handing back margin.

Where is the breakeven by Azure spend band?

Below roughly $250,000 a year CSP is usually the cheapest total package, between $250,000 and $1 million the channels converge, and above $1 million a committed vehicle with a negotiated discount wins on arithmetic alone.

The arithmetic is short. A 5 percent committed discount on $3 million of annual Azure consumption returns $150,000 a year. A CSP partner cannot fund that from its earned credit and still run your estate profitably, so at that scale the committed channel wins before the conversation starts.

Run the bands against your trailing twelve month consumption, then stress the answer with your realistic growth plan. A commitment sized to an optimistic forecast is exactly how unspent MACC balances happen.

Jan 2025

First direct market EA renewals refused

500

User or device floor for a commercial EA

3

Purchasing vehicles every Azure buyer should model

Source: Microsoft licensing program terms and published announcements, 2026. Benchmark context from the Redress Compliance advisory engagement file.

How do CSP partner margins work and how do you negotiate them?

A CSP partner earns a Microsoft paid credit on your eligible Azure consumption plus whatever it charges for services, and once your spend is material, part of that margin is negotiable back to you.

The partner earned credit pays only while the partner holds an eligible admin role in your environment and provides ongoing management. It excludes reservations, savings plans, Spot virtual machines, and marketplace purchases. A reservation heavy estate therefore generates far less partner margin than its headline spend suggests, and a good buyer knows that number before the partner quotes.

The access requirement is the buyer side trade. Standing admin rights are a security decision as much as a commercial one, so scope the role to least privilege and review it quarterly.

When your annual CSP consumption clears a few hundred thousand dollars, put the arrangement on paper with these asks:

• Price transparency: invoices reconcile line by line against Microsoft's published USD rates, with the markup or markdown stated.
• Margin share: a defined rebate on consumption above an agreed threshold, paid quarterly.
• Service scope in writing: the managed service the margin funds is specified, with response times, not implied.
• Reservation pass through: reservations and savings plans transact at cost, since they sit outside the partner credit anyway.
• Exit terms: a 30 day right to move to another partner, no termination fee, and cooperation on the transfer.

Every channel now starts from the same retail rate card. The only question is which instrument you hold to pull the price down, and who is sitting across the table when you use it.

How should you choose between CSP and EA?

Choose on three numbers: your trailing twelve month Azure run rate, the share of it that is steady state, and the discount each channel will commit to in writing. The choice is not permanent. Re test it as Azure spend grows, because the crossover point moves with your consumption.

Predictability matters as much as scale. Commit against the floor of your consumption, not the average, because a workload that may leave Azure next year supports no commitment at all.

Where is the crossover point?

The crossover sits where the committed discount under an EA or an enterprise MCA outweighs the flexibility of CSP, typically near $1 million of annual spend. Model all three against your real twelve month Azure run rate before deciding.

Do the modeling with written numbers. Ask the partner for its best margin share at your volume, and ask Microsoft what discount attaches to a MACC sized at 80 percent of your run rate. The winning sheet is your answer for the next twelve months.

How do you change vehicles without losing ground?

Treat the move as a nine month project that starts well before your enrollment expires, because your leverage is highest while Microsoft still wants the transition signed. One fact helps you: since August 1, 2019, expiring Azure EA enrollments roll into an indefinite extended term at your existing rates rather than lapsing, which buys negotiating room.

1. Inventory every enrollment: expiry dates, Azure prepayment balances, unspent MACC, and any attached program funding.
2. Export twelve months of consumption plus your full reservation and savings plan portfolio with end dates.
3. Get each channel's discount offer in writing against the same workload forecast, so the sheets compare like for like.
4. Confirm in writing how reservations and savings plans move. Between EA and enterprise MCA billing they can transfer; a move into CSP usually means repurchasing them through the partner.
5. Time the signature toward Microsoft's fiscal year end on June 30 or a quarter end, when discount approvals loosen.
6. Plan the administrative rebuild: billing accounts, invoice sections, budgets, and RBAC assignments all change with the vehicle.
7. Keep the old enrollment in extended term as your fallback until the new deal is signed, not merely agreed.

What do Microsoft reps push and why?

Expect the rep to push a larger MACC, an early enterprise MCA transition, and AI attach, because Azure consumption and consumption commitments are what Microsoft sellers are measured on. None of these pushes is irrational; each simply needs a counter.

The commitment push is the one to watch. An unspent MACC balance at expiry is typically forfeited, so every dollar of oversizing converts your discount into a donation.

• A bigger MACC than your forecast: counter by sizing at about 80 percent of steady state consumption and banking the growth as renegotiation leverage.
• An early EA exit framed as mandatory: counter by asking in writing whether your enrollment is actually in a refusal wave before you surrender the term you already hold.
• Copilot and AI service attach inside the commitment: counter by checking which services actually retire MACC and pricing the attach on its own merits.
• Unified support priced as a percentage of spend: counter by scoping it before the Azure number grows, since the fee scales with everything you sign.
• June 30 urgency: counter by using the fiscal year end for discount headroom while ignoring manufactured deadlines; the quarter ends four times a year.

Where the common advice on CSP versus EA is wrong

The common advice is to stay on an Enterprise Agreement because it looks like the enterprise grade vehicle. We disagree. For many estates the EA floor and the fixed three year commitment lock in spend that a CSP or the newer Microsoft Customer Agreement would let you flex down as workloads move. The buyer side move is to model all three vehicles against your real Azure trajectory and seat count before you renew, not after. This is not the default your account team will steer you toward.

What to do next

1. Pull your real trailing twelve month Azure spend and split it into steady state and variable.
2. Model that spend under CSP, under an EA commitment, and under an enterprise MCA with a MACC.
3. Confirm in writing which vehicles Microsoft is actually offering you, including whether your EA renewal sits in a refusal wave.
4. Get the partner's margin share and Microsoft's committed discount on paper against the same forecast.
5. Check how your reservations and savings plans transfer before you agree to any move.
6. Test whether your spend is predictable enough to commit, and size any MACC at about 80 percent of steady state.
7. Weigh partner support value against direct committed discounts.
8. Re review the vehicle every year as spend changes, starting nine months before any enrollment expiry.

Frequently asked questions

What is the difference between Azure CSP and EA?

Azure under the Cloud Solution Provider model is bought through a partner with monthly flexibility and no minimum commitment. Azure under an Enterprise Agreement is a direct commitment with Microsoft, usually a three year term with a spend commitment in exchange for negotiated discounts.

Which is cheaper, Azure CSP or EA?

It depends on scale and predictability. CSP can be cheaper for smaller or variable spend because there is no commitment. EA tends to win at larger, predictable spend where the committed discount and price protection outweigh the flexibility of CSP.

Does Azure EA still exist in 2026?

Yes, but it is being retired in stages. Since January 1, 2025 Microsoft has refused EA renewals for a growing share of cloud customers in direct markets and offered the Microsoft Customer Agreement for enterprise instead. Ask in writing whether your enrollment can still renew before you plan around it.

What is the Microsoft Customer Agreement for enterprise?

It is Microsoft's evergreen direct contract that replaces the Enterprise Agreement for transitioned customers. It never expires and has no purchase minimums, but it drops the EA's programmatic price levels, so Azure discounts must be negotiated deal by deal, usually against a consumption commitment.

Can you negotiate Azure pricing under CSP?

Yes, but with the partner, not Microsoft. Azure bills at published pay as you go rates, and the partner's room comes from its earned credit and service fees. At material spend, negotiate a margin share, price transparency, and reservation pass through at cost.

What is the minimum commitment for an Azure EA?

A commercial EA requires at least 500 users or devices, and Azure has historically attached as an annual prepayment starting around $12,000. The commercially meaningful threshold is higher, because Microsoft negotiates real Azure discounts only against substantial committed spend.

What is a MACC and which vehicles support it?

A Microsoft Azure Consumption Commitment is a contracted total of Azure spend over a defined period, exchanged for negotiated discounts and often program funding. It attaches to Enterprise Agreements and enterprise MCA deals, is retired only by eligible consumption, and an unspent balance at expiry is typically forfeited.

Do reservations and savings plans transfer if I change vehicles?

Sometimes, and you must confirm it in writing before moving. Transfers between EA and enterprise MCA billing are supported in most cases, while a move into CSP usually means repurchasing reserved capacity through the partner. Map every reservation end date before you sign the new vehicle.

Does a CSP partner need admin access to my Azure environment?

The partner needs an eligible admin role to earn its partner earned credit, which is how the CSP model funds partner margin. Grant scoped, least privilege access and review it quarterly; you may remove it, though that changes the partner's economics and usually its pricing.

Should a growing company use CSP or EA?

Growing companies often start on CSP for flexibility, then move to an enterprise MCA or an EA once spend is large and predictable enough to justify a commitment, typically near $1 million a year. Review the crossover point each year as Azure spend climbs.