The choice between a CSP agreement and an Enterprise Agreement for Microsoft 365 comes down to size, growth, and price stability. There is no universally cheaper option. There is a right fit for your profile.
CSP and the Enterprise Agreement are two routes to the same Microsoft 365 licenses. The right one depends on your seat count, your growth, and how much price lock you need.
The Cloud Solution Provider program sells Microsoft 365 through a partner on a monthly or annual basis. You can add and remove seats with far more freedom than under a fixed term commitment. The Microsoft CSP overview sets out the model.
CSP suits organizations that change shape. Seasonal staff, acquisitions, and divestments all favor the flexibility CSP gives.
Since the New Commerce Experience became mandatory, CSP is more structured than the old month to month model. You pick a monthly, annual, or triennial term at the seat level, and each term sets its own cancellation and pricing rules.
The New Commerce Experience is the current CSP purchasing engine, and it trades some flexibility for lower headline pricing. Annual and triennial terms lock the seat count, while only the monthly term lets you cut seats each month.
Microsoft caps the cancellation window at 7 calendar days from purchase or renewal for license based subscriptions, with a prorated refund. After day 7 the seats are committed for the rest of the term. Microsoft documents the window.
The monthly term buys real flexibility but costs roughly 20 percent more per seat than the annual term. That premium is the price of shedding seats each month, so reserve it for genuinely variable populations.
A practical pattern splits the estate. Put the stable base of seats on an annual term for the lower rate, and hold a smaller pool on monthly terms for contractors and seasonal staff.
The Enterprise Agreement is a three year volume commitment that locks pricing and bundles the estate into one negotiated deal. Microsoft historically aimed it at 500 seats, then raised the practical floor sharply.
Since early 2025 Microsoft has declined most EA renewals for organizations under 2,400 users, steering them to CSP or the Microsoft Customer Agreement. The Microsoft Enterprise Agreement page describes the structure.
EA rewards scale and stability. If your headcount is large and rising, the annual price lock protects you from list increases that reprice CSP seats each cycle.
Price protection is the headline benefit. A locked rate across three years shields a growing estate from list increases that hit CSP buyers each renewal.
An EA also consolidates purchasing power. Volume pricing, a single true up, and one negotiated price sheet give large estates leverage that scattered CSP orders rarely match.
EA price protection weakened in late 2025, so read the fine print. On 1 November 2025 Microsoft eliminated programmatic Level B, C, and D discounts for Online Services, flattening the old volume tiers.
The change lifted effective prices by roughly 6 percent for former Level B estates and near 12 percent for Level D. The lock still holds within a term, but the price you lock starts higher than a 2024 renewal.
The Microsoft Customer Agreement for Enterprise, or MCA E, is now the third path, and it is where Microsoft steers large customers next. It is a Microsoft direct contract with no reseller in the room and no fixed term.
Unlike the EA, the MCA for Enterprise is evergreen. There is no three year enrollment, no annual true up, and no Customer Price Sheet to anchor the term. Product terms can change several times a year rather than staying fixed. Microsoft documents onboarding.
From 1 March 2026 Microsoft began moving EA customers on Azure commitment plans to the MCA for Enterprise ahead of their renewal date. Treat any renewal conversation as a three way choice now, not a binary between CSP and EA.
The evergreen model carries a hidden cost. The old EA true up was also the moment you reset quantities down, and the MCA removes it, so nothing forces a periodic rightsizing.
The buyer side move is to rebuild that discipline yourself. Set a quarterly seat review and press for a price protection clause, because the default MCA lets Microsoft reprice more often than the EA did.
MCA for Enterprise can still carry negotiated discounts and multi year price holds, but you must ask. They are not baked into the program the way EA levels once were.
The two routes deliver the same licenses but on very different commercial terms. The table below sets the main axes side by side.
CSP vs EA on the axes that matter
| Axis | CSP | Enterprise Agreement |
|---|---|---|
| Term | Monthly or annual | Three years |
| Seat flexibility | High, scale both ways | Low, add only mid term |
| Price lock | No, follows list | Yes, across the term |
| Best fit | Under 500 seats, changing | Large, stable, growing |
The table simplifies, so weigh two hidden factors. CSP repricing follows Microsoft list moves each renewal, while an EA holds the entered price for three years but now starts from a higher post 2025 base.
Seat bands decide the contract before any discount does, because Microsoft gates program eligibility on user count. The old EA volume levels still frame the math even after the 2025 discount changes.
The table maps the historical EA seat bands to the practical route Microsoft now offers at each size. Use it to sanity check any quote against your true user count.
| Seat band | Former EA level | Practical 2026 route | Note |
|---|---|---|---|
| Under 500 | Below Level A | CSP only | EA renewals declined |
| 500 to 2,399 | Level A | CSP or MCA for Enterprise | EA usually declined since 2025 |
| 2,400 to 5,999 | Level B | EA, CSP, or MCA E | Level B discount removed Nov 2025 |
| 6,000 to 14,999 | Level C | EA or MCA E | Strongest negotiation leverage |
| 15,000 plus | Level D | EA or MCA E | Direct field team engagement |
Below 2,400 users the realistic choice is CSP or the MCA for Enterprise, not an EA. Microsoft declines most EA renewals under that line, so a partner quote is usually your baseline.
Above 2,400 the EA is still available, but the flattened levels mean the discount gap over CSP has narrowed. The largest estates, once at Level D, saw effective prices rise near 12 percent when the tiers were removed.
Read your own count carefully. Microsoft counts qualified users and devices, so contractors, shared mailboxes, and frontline staff can push you across a band boundary you did not expect.
Start with two numbers. Your seat count and your expected growth direction. A large, rising estate leans EA for the price lock. A smaller or shrinking estate leans CSP for the flexibility.
The matrix below maps common organization profiles to the route that usually wins. Treat it as a starting hypothesis to test against your own seat forecast.
| Organization profile | Seat trend | Recommended route | Why |
|---|---|---|---|
| Under 500 seats, stable | Flat | CSP annual term | No EA access, lock the annual rate |
| Under 500 seats, seasonal | Variable | CSP monthly term | Release seats each month |
| 500 to 2,399, growing | Rising | CSP annual or MCA E | EA usually declined, lock annual |
| 2,400 plus, growing | Rising | EA three year | Price lock beats CSP repricing |
| 2,400 plus, shrinking | Falling | CSP or MCA E | Avoid trapping unused seats |
| Mixed core and project | Split | EA plus CSP | Lock core, flex the variable pool |
Yes. Many estates put stable core seats on an EA and variable or project seats on CSP. The Microsoft Product Terms govern both, so the licenses are identical.
Microsoft has narrowed EA eligibility and pushed smaller customers to CSP. If your EA renewal is declined, model the CSP equivalent before accepting the partner quote. Cross check entitlements in the Microsoft 365 enterprise plans.
Under CSP your price includes the partner margin, so the partner is a lever, not a fixed cost. Microsoft sets a wholesale price to the partner, who marks it up to you.
Partner base margins on Microsoft 365 are thin, often in the low single digits, topped up by Microsoft incentives the partner earns for provisioning and support. Ask each bidder to quote the markup over the Microsoft price explicitly.
Run a competitive CSP tender. Because any partner can sell the same license under the same Product Terms, switching partners is low risk and a credible threat that compresses margin.
Separate the license price from the service wrap. Pay a transparent markup for licenses, and price managed services on their own line, so you can benchmark each part against the market.
Three levers move a CSP price in practice:
The buyer side implication is leverage without lock in. CSP has no multi year handcuff, so you can retender annually and hold the incumbent partner honest.
Time any migration to your EA anniversary, because seats committed under one contract cannot move mid term without waste. Start the modeling twelve months out.
The sequence matters. Inventory entitlements, model each route against a conservative seat forecast, then run the tender before the renewal quote lands, not after it anchors the conversation.
| Timeline | Action | Owner |
|---|---|---|
| T minus 12 months | Inventory seats by plan and true user count | SAM |
| T minus 9 months | Forecast headcount direction for three years | Finance |
| T minus 6 months | Model CSP, EA, and MCA E for the forecast | Procurement |
| T minus 4 months | Run a competitive CSP partner tender | Procurement |
| T minus 2 months | Negotiate the winning route and lock price | Procurement |
| T minus 0 | Sign, then schedule quarterly seat reviews | SAM |
The most common error is starting at T minus 60 days, when Microsoft controls the clock. A twelve month runway lets you test CSP partner bids and the MCA for Enterprise route against the EA number.
Watch two traps at the switch. Annual CSP terms lock for a year, so align their start to the migration date, and confirm any Azure commitment moves cleanly to the new agreement.
The common advice is that the Enterprise Agreement is always the enterprise grade choice and CSP is for small business. We disagree. In roughly 40 to 60 Microsoft 365 reviews we ran, shrinking or flat estates on an EA overpaid by 10 to 20 percent because the three year lock trapped seats they no longer needed, while flexible CSP profiles released that cost. The buyer side move is to choose by seat trajectory, not by company size. If headcount is rising, the EA lock helps. If it is flat or falling, CSP flexibility usually wins, and a mix of both can beat either alone.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
There is no universally cheaper Microsoft contract. There is a contract that fits where your headcount is going over the next three years.
Not universally. CSP is usually cheaper for flat or shrinking estates because you can release seats. An EA is often cheaper for growing estates because the price is locked across three years.
Microsoft has historically aimed the Enterprise Agreement at 500 seats and above, and has narrowed eligibility further. Smaller customers are routinely directed to CSP.
Yes, typically at renewal. Model the CSP equivalent of your estate before the EA expires so you can compare locked pricing against flexible pricing.
Yes. Both deliver the same Microsoft 365 licenses governed by the same Product Terms. The difference is commercial, in term, flexibility, and price lock.
Overcommitment. A three year lock can trap seats you no longer need if headcount falls. Size the commitment to a conservative forecast, not an optimistic one.
Yes. Putting stable core seats on an EA and variable seats on CSP is a common and often optimal pattern.
Microsoft has been steering smaller customers to CSP. A declined EA renewal is a commercial signal, not a license loss. Price the CSP route before accepting any quote.
At every renewal, and whenever headcount changes materially. The right contract follows your seat trajectory, which shifts over time.
It is Microsoft's direct, evergreen enterprise contract, often shortened to MCA E. It has no three year term, no annual true up, and no Customer Price Sheet, and Microsoft is steering large EA customers toward it from 2026.
Yes. The monthly term runs roughly 20 percent higher per seat than the annual term. You pay that premium for the right to reduce seats every month, so use it only for variable populations.
Microsoft renewal moves, the EA framework, the M365 SKU 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.
Engage independent buyer side Microsoft advisors. We do not resell. We sit on your side of the table.
Open the Microsoft Practice page
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →