Microsoft sells one catalog through three contracts. The Enterprise Agreement, CSP, and the Microsoft Customer Agreement lock, flex, and price differently. Pick the vehicle before you argue the discount.
Microsoft sells the same products through three contracts. The Enterprise Agreement, the CSP program, and the Microsoft Customer Agreement each price, lock, and flex differently. This guide compares all three and shows which fits your seat count, your Azure spend, and your tolerance for commitment.
Microsoft does not sell three different products. It sells one product catalog through three contracts. The catalog is the same. The commercial terms are not.
That is the trap. Buyers compare SKUs when they should compare vehicles. The SKU price is similar across all three. The lock, the flex, and the exit are where real money moves.
The short answer is commitment versus flexibility. The EA commits you for three years in exchange for volume pricing. CSP keeps you flexible for a margin you share with a partner. The MCA is the evergreen contract Microsoft now prefers underneath both.
The Enterprise Agreement is a three year commitment for organizations with scale. You fix your platform base, true up additions once a year, and settle at renewal.
CSP is the partner channel. You buy monthly or annual subscriptions through a Microsoft partner under the New Commerce Experience terms. The partner sets service and price within Microsoft rules.
The Microsoft Customer Agreement is a single digital contract that does not expire. It can be signed direct or through a partner, and it underpins most new Azure and a growing share of M365 buying.
Microsoft EA, CSP, and MCA compared
| Dimension | Enterprise Agreement | CSP | Microsoft Customer Agreement |
|---|---|---|---|
| Term | 3 years fixed | Monthly or annual | Evergreen, no expiry |
| Seat flex down | Locked for the term | At term boundary | Per subscription rules |
| Typical floor | 500 plus users | No practical floor | No practical floor |
| Azure fit | Legacy commitment | Pay as you go | MACC and drawdown |
| Who sells it | Microsoft direct or LSP | CSP partner | Direct or partner |
The EA still wins for large, stable estates that value price certainty over flexibility. If your headcount is predictable and your platform base is broad, the three year lock is an asset, not a liability.
The EA punishes volatility. You cannot reduce the platform base mid term, so a layoff or a divestiture leaves you paying for seats you no longer use. The lock that protects price also freezes shelfware.
CSP rarely beats the EA on headline discount, but it can beat it on real cost when headcount moves. The flex to reduce seats at a term boundary is worth more than two or three points of discount for many buyers.
Under the New Commerce Experience, annual CSP terms lock the price for the year while monthly terms cost more but flex faster. A good partner blends both, holding stable seats annual and seasonal seats monthly.
The MCA removes the renewal event. Because it does not expire, there is no three year cliff to negotiate against. That sounds convenient and it is, but it also removes your strongest leverage moment.
For committed Azure spend, the MCA carries a Microsoft Azure Consumption Commitment that draws down against real usage. Microsoft documents Azure pricing and commitment mechanics on its Azure pricing pages, and the MCA is the cleanest home for that commitment.
The MCA pulls product specific rules from the Microsoft Product Terms, which Microsoft can revise. Because the contract is evergreen, those revisions reach you without a renewal to renegotiate them. Read the terms on a cadence, not once.
The standard reseller pitch is that the Microsoft Customer Agreement is simpler, so you should move to it and stop worrying about renewals. We disagree. In roughly six out of ten estates we have modeled, the evergreen contract quietly removed the customer's best leverage.
The reason is timing. The three year EA expiry was the one moment Microsoft had to compete for the renewal. The buyer side move is to keep an engineered renewal event on your calendar even on an evergreen contract, and to treat any annual price protection clause as the lever you negotiate hardest. Convenience is not cost control.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The product is identical across all three contracts. You are not buying software when you pick a vehicle. You are buying a position on commitment, and that position is the price.
Start with two numbers. How volatile is your headcount, and how committed is your Azure spend. Those two answers route most estates to the right vehicle before any discount conversation begins.
If you run a blend, align the renewal and term dates so they do not drift. The most expensive mistake in a mixed estate is paying for the same user on an EA seat and a CSP seat at the same time. Microsoft explains the buying paths on its how to buy page, but the reconciliation is on you.
The Enterprise Agreement is a three year volume contract, CSP is a partner sold monthly or annual subscription, and the Microsoft Customer Agreement is a digital direct contract that increasingly underpins both. The EA suits large stable estates, CSP suits flexibility, and the MCA is where Microsoft is steering most customers.
No formal end date has been published, but Microsoft has narrowed EA eligibility and is steering smaller and midsized customers toward CSP and the MCA. Treat the EA as available for large estates while building a fallback plan in case eligibility tightens at your next renewal.
The practical floor is around 500 users or devices, and Microsoft has signaled higher expectations for new EA enrollments. Below that band, CSP through a competent partner is usually the better commercial vehicle, with the MCA as the direct alternative.
Not on list mechanics, but CSP can win on flexibility and partner margin sharing. CSP lets you reduce seats at term boundaries that an EA locks for three years, so the effective cost can be lower for a volatile headcount even when the headline discount looks smaller.
Yes, and most large enterprises do. A common pattern keeps the stable core on an EA, runs project and seasonal demand on CSP, and uses an MCA for Azure consumption. The risk is duplicate entitlements and stranded licenses across the vehicles.
The Microsoft Customer Agreement is a single, evergreen digital contract that replaces older paper agreements and does not expire. It can be signed direct with Microsoft or through a partner, and it is the legal backbone for Azure MACC commitments and a growing share of M365 buying.
Plan 6 to 9 months for a clean move between an EA, CSP, and the MCA. The work is not the paperwork, it is reconciling entitlements, aligning renewal dates, and avoiding a coverage gap or a double pay window during the cutover.
For large committed Azure spend, the Microsoft Customer Agreement with a MACC is usually the cleanest vehicle. It carries the Azure commitment directly, supports consumption drawdown, and avoids forcing your cloud spend through an aging EA enrollment.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
