For most organizations between 500 and 2,400 seats, Microsoft CSP under New Commerce now lands 6 to 14 percent cheaper than an Enterprise Agreement once you strip out unused Software Assurance and the annual true-up, but above roughly 2,400 seats the EA discount tier and an Azure commitment usually reverse that result. The right answer depends on three numbers: your seat count, how much your headcount moves during the year, and how much Azure you commit. This page compares both models on real 2026 pricing and gives you a decision matrix you can apply to your own renewal.
The two models differ in structure before they differ in price. The Enterprise Agreement is a three-year commitment with a fixed seat baseline, an annual true-up for growth, locked pricing for the term, and Software Assurance bundled into every license. CSP, sold through a partner under New Commerce Experience terms, prices per subscription with annual or monthly terms, no enrollment minimum, and upgrade rights folded into the subscription instead of a separate Software Assurance line. For the full mechanics of each vehicle, see the Microsoft EA complete guide and the agreement comparison in MPSA vs CSP vs MCA vs EA.
Headline cost comparison
On a like-for-like Microsoft 365 E3 estate, CSP annual-term pricing runs 6 to 14 percent below the EA total cost of ownership for mid-sized estates, because CSP carries no Software Assurance you do not use and no true-up administration. The table below models a 1,200-seat E3 estate at representative 2026 rates.
| Cost element | Enterprise Agreement | CSP (New Commerce annual) |
|---|---|---|
| M365 E3 per user per month | $36.00 (Level A, locked 3 yr) | $33.75 (partner net) |
| Software Assurance | Bundled, ~9% of value | Included in subscription |
| Annual true-up admin | Internal cost, 40 to 80 hours | None |
| Flexibility premium | None (fixed baseline) | Built into net rate |
| 3-year total, 1,200 seats | $1,555,200 | $1,458,000 |
That is a $97,200 gap, or 6.3 percent, in CSP's favor at 1,200 seats. The gap widens for estates that shrink during the term, because the EA baseline cannot be reduced mid-term while CSP annual terms can be re-scoped at each renewal date.
Where the Enterprise Agreement still wins
Above 2,400 to 3,000 seats the EA reclaims the cost advantage through volume discount levels and Azure commitment. EA Level B pricing (2,400 to 5,999 qualified users) and Level C (6,000 plus) discount the per-user rate by amounts CSP partners cannot match, and a Microsoft Azure Consumption Commitment signed inside the EA earns additional credits. A 6,000-seat estate with significant Azure spend typically prices 4 to 9 percent below the equivalent CSP build. The EA also delivers price-lock certainty for the full three years, which matters when Microsoft raises list prices, as it did across several 2025 and 2026 SKUs covered in Microsoft NCE pricing 2026.
Where CSP wins
CSP wins on flexibility for any estate whose headcount moves more than 8 percent a year. The EA bills growth through the annual true-up but never refunds shrinkage inside the term, so a company that grows then contracts pays for the peak. CSP lets you align licenses to actual headcount at each anniversary. CSP also wins for organizations that want to avoid the 500-seat EA enrollment floor, that prefer a partner relationship over direct Microsoft administration, or that want to mix vendors at the desktop. For the product edition trade-offs underneath either vehicle, see Microsoft 365 vs Office 365.
The price-lock difference: The EA locks per-user pricing for 36 months. CSP annual terms re-price at each 12-month renewal at then-current rates, so a buyer who chooses CSP for a multi-year horizon is exposed to Microsoft's list increases at every anniversary. If you expect more than two list increases over three years, the EA price lock can be worth more than the CSP flexibility discount. Quantify both before deciding.
Decision matrix
The choice resolves cleanly against four variables: seat count, headcount volatility, Azure commitment, and Software Assurance benefit usage.
| Your situation | EA | CSP |
|---|---|---|
| Under 500 seats | Not eligible | Required path |
| 500 to 2,400 seats, stable | Competitive | Usually cheaper by 6 to 14% |
| 500 to 2,400 seats, volatile headcount | Overpays at peak | Cheaper, re-scopes yearly |
| 2,400 to 6,000 seats with Azure commit | Usually cheaper | Competitive |
| 6,000+ seats, heavy Azure | Cheaper by 4 to 9% | Rarely wins |
| Uses SA Planning Services, training vouchers | Retains benefits | Loses benefits |
Choose EA when, choose CSP when
Choose the Enterprise Agreement when your estate is above 2,400 seats, your headcount is stable, you are making a meaningful Azure commitment, you use named Software Assurance benefits, or you want a guaranteed three-year price lock against Microsoft increases. Choose CSP when your estate is under 2,400 seats, your headcount moves more than 8 percent a year, you want to re-scope annually, or you want a partner-managed relationship without the 500-seat floor and the true-up overhead.
The migration math
Moving from an EA to CSP is most valuable at the renewal boundary, not mid-term, because breaking an EA early forfeits the locked pricing without refund. The clean sequence is to model both quotes 9 to 12 months before EA expiry, run a true-down analysis to remove seats you no longer need (the method is in Microsoft EA true-down), then take both quotes into the renewal as competing options. Having a credible CSP alternative on the table is itself the strongest lever on the EA discount. For the negotiation playbook, see our Microsoft negotiation practice, and for the broader licensing context the complete Microsoft licensing guide.
How Azure changes the comparison
An Azure consumption commitment can shift the entire EA versus CSP decision by 10 points or more, because the EA is the vehicle that hosts the largest Azure discounts. When a buyer commits to a multi-year Azure spend through a Microsoft Azure Consumption Commitment inside the EA, Microsoft funds that commitment with credits and preferential rates that a CSP build cannot match for the same spend. An estate that is 60 percent productivity seats and 40 percent Azure consumption will almost always find the EA cheaper once the Azure commitment is priced in, even when the seat side of the deal would favor CSP in isolation. The mistake buyers make is comparing only the seat costs and treating Azure as a separate negotiation, which hides the cross-subsidy the EA provides.
The corollary is that an estate with little or no Azure footprint loses the EA's main structural advantage. A company running its infrastructure on a competing cloud, or fully on-premise, is paying the EA's commitment overhead without collecting the Azure benefit that justifies it. For those buyers the CSP flexibility discount is rarely outweighed, and the seat-only math in the headline table holds.
Software Assurance benefits at stake
Moving off the EA forfeits roughly nine named Software Assurance benefits, and three of them carry real money for larger estates. Planning Services, which fund Microsoft partner deployment days, disappear. Training vouchers for IT staff disappear. Home Use rights, step-up licenses that let you upgrade an edition mid-term at a reduced cost, and the spread-payment option on the EA all go with them. A buyer who actively uses Planning Services and training vouchers can be collecting $40,000 to $120,000 of annual value that simply vanishes on the move to CSP, value that must be subtracted from the CSP saving to compare honestly.
The practical test is usage, not entitlement. Many EA customers are entitled to these benefits and never redeem them, in which case losing them costs nothing and the CSP saving is real. The review that should precede any EA versus CSP decision is an audit of which Software Assurance benefits the organization actually consumed over the last three years. If the answer is none, the EA is carrying a benefit cost the buyer is funding and not using, which strengthens the case for CSP.
The administrative cost nobody prices
The EA annual true-up consumes 40 to 80 hours of internal procurement and IT administration a year, and that labor cost belongs in the comparison even though it never appears on an invoice. The true-up requires reconciling deployed seats against the baseline, documenting additions, and processing the order, work that recurs every year of the term. CSP shifts that administrative burden to the partner and to a simpler annual renewal, which is part of why mid-sized organizations without a dedicated licensing function often prefer it regardless of the headline price. For a 1,200-seat estate, the loaded cost of true-up administration over three years can reach $20,000 to $35,000, a small but real addition to the EA's total cost of ownership.
Common mistakes in the EA versus CSP decision
Three errors recur. The first is comparing year-one prices instead of three-year total cost of ownership, which ignores the EA price lock and the CSP renewal exposure that only appear over time. The second is excluding Azure from the comparison, which understates the EA for any buyer with meaningful cloud spend. The third is treating the salesperson's first CSP quote as the partner's best price; CSP is sold through partners who set their own margin, so the same Microsoft SKU can vary 3 to 8 percent between partners for an identical estate. A competitive partner quote is itself a lever, and buyers who solicit two or three partner bids routinely improve the CSP number before it even competes with the EA. The full agreement-selection logic across all four Microsoft vehicles is in MPSA vs CSP vs MCA vs EA.
The hybrid path many estates land on
The cleanest answer for a large, mixed estate is often not a single vehicle but a split: keep the EA for the Azure commitment and the stable core seat population where the price lock and volume tier pay off, and place the volatile or peripheral populations on CSP where the annual re-scoping matters most. A company with 4,000 stable knowledge-worker seats and a fluctuating population of 1,200 contractors and seasonal staff captures the EA discount on the stable base and the CSP flexibility on the variable layer, rather than forcing the whole estate into one model and overpaying on part of it. Microsoft permits this combination, and it frequently beats either pure approach by 5 to 9 percent for estates with a clearly variable segment.
The cost of the hybrid is administrative complexity: two vehicles, two renewal cycles, and the discipline to keep each population on the right one as headcount shifts. For organizations with a capable licensing function the trade is worth it; for those without, the simplicity of a single CSP relationship can outweigh the few points of saving. The decision should be made with the three-year total cost of ownership modeled for all three options, the EA, CSP, and the hybrid, not assumed. The wider context is in the complete Microsoft licensing guide.
Frequently asked questions
Is Microsoft CSP cheaper than an Enterprise Agreement?
For most organizations between 500 and 2,400 seats, CSP under New Commerce lands 6 to 14 percent cheaper than an EA once unused Software Assurance and the annual true-up are removed. Above roughly 2,400 seats the EA discount tier and an Azure consumption commitment usually make the EA cheaper.
What is the seat threshold where the EA wins?
The EA price advantage typically appears above 2,400 to 3,000 seats, where Level B and Level C volume discounts and an Azure commitment outweigh the flexibility premium CSP charges.
Can I cancel CSP subscriptions mid-term?
Under New Commerce annual terms, cancellation is only allowed inside a 7-calendar-day window after purchase or renewal. After that the annual term is non-cancelable, which removes most of CSP's former flexibility advantage over the EA.
Does CSP include Software Assurance?
No. CSP subscriptions fold upgrade rights into the subscription, so there is no separate Software Assurance line. Buyers who used Planning Services or training vouchers lose them when they leave the EA. To weigh both vehicles against your estate, talk to our software licensing advisory team.