Microsoft cloud agreements compared. EA, MCA E, CSP and MPSA by size and seat trend.

Microsoft sells the same cloud products through the EA, MCA E, CSP and the MPSA. Each sets a different term, flexibility and renewal mechanism, so choose the one that matches your size and where your seat count is heading.

Microsoft sells Microsoft 365, Dynamics 365 and Azure through several commercial agreements, and the same product behaves differently under each. The agreement decides how long you are committed, whether you can cut seats, how long your price holds and who you negotiate with.

Most renewals treat the agreement as paperwork. In our reviews it has decided more of the final cost than the discount did.

What are the main Microsoft cloud agreements?

Four agreements cover most enterprise buying: the Enterprise Agreement, the Microsoft Customer Agreement for Enterprise, the Cloud Solution Provider program and the MPSA. Each makes a different trade between commitment, price and flexibility.

Microsoft describes the programs in its how to buy guidance and sets the use rights in the Microsoft Product Terms. Use rights are largely the same whichever agreement you choose. The commercial wrapper around them is what differs: term, minimums, price protection and who bills you.

• Enterprise Agreement (EA). A three year, organization wide commitment with an annual true up, open to organizations with at least 500 users or devices (250 in the public sector).
• Microsoft Customer Agreement for Enterprise (MCA E). Microsoft's direct, cloud first contract. The agreement never expires, and each subscription under it carries its own term.
• Cloud Solution Provider (CSP). Sold and billed by a partner, with monthly or annual terms (three years on some offers) and flexible scaling.
• MPSA. A transactional agreement with no enterprise wide commitment and no end date, available to organizations with 250 or more users or devices. It keeps mixed buying simple, but Azure cannot be bought through it.

Who still fits the Enterprise Agreement?

Large organizations with stable seat counts and committed volume. The EA rewards predictability with structured discounts and a price sheet that holds for the full term, but it penalizes a shrinking organization that cannot true down mid term.

Two mechanics decide how the EA treats you. The annual true up order must reach Microsoft between 60 and 30 days before the enrollment anniversary. Microsoft's guidance also reserves annual decreases for the Enterprise Subscription Enrollment, so in a standard Enterprise Enrollment your Enterprise Product counts generally stay at their peak until the term ends.

What is changing with MCA E?

Microsoft is steering enterprises toward the Microsoft Customer Agreement, a direct, cloud first model that replaces the three year enrollment with an agreement that never expires. It changes how commitments and price protections work, so model it before you accept it as the default.

Billing changes first. EA enrollments, departments and accounts give way to a billing account, billing profiles and invoice sections. Azure is priced in US dollars worldwide, your historical EA cost data stays in the old EA scope, and finance may receive two invoices in the month of transition.

How do the agreements differ on term and flexibility?

Commitment and flexibility trade against each other. More commitment usually buys a better price and less room to change course when the business does.

Azure pricing and commitment options under these agreements are published in the Azure pricing documentation. Because Azure sits outside the MPSA, an MPSA customer who wants Azure needs a second agreement alongside it.

Can you reduce seats mid term?

Under the EA, generally not until renewal, and that is how surplus gets locked in. CSP allows monthly adjustment, which suits organizations whose headcount grows and shrinks with the business, but only on monthly term subscriptions.

Annual and three year CSP subscriptions are stricter than many buyers expect. Under Microsoft's new commerce rules, licenses can be reduced only within the first seven days (168 hours) after they are added, with a prorated refund. After that the count holds to the end of the term.

What does the agreement choice cost when seat counts change?

The cheaper agreement is the one whose rules match where your seat count is heading. A hypothetical example shows how quickly a better unit price can turn into a higher bill.

Say you license 3,000 users on Microsoft 365 E3, at the list price of $39 per user per month on an annual commitment that applies from July 1, 2026. You negotiate an EA price 10 percent below list, $35.10, and a CSP partner quotes list. After year 1, a divestment cuts headcount by 20 percent, to 2,400 users.

The locked EA ends up $140,400 more expensive than CSP despite its lower unit price. Two break even points tell you which way your own forecast points.

• Annual break even. At 2,700 users, a 10 percent drop, the CSP annual bill of $1,263,600 equals the fixed EA bill.
• Three year break even. CSP's higher year 1 bill has to be recovered in years 2 and 3, so over the full term CSP wins only below 2,550 users, a drop of 15 percent.

The third row is the cheapest by $505,440 against the locked EA. Keeping the EA discount and adding a right to reduce at the anniversary beat both alternatives, which is why the reduction clause deserves as much negotiating time as the price.

What have we seen in recent Microsoft agreement reviews?

Across roughly 35 to 50 Microsoft agreement reviews Fredrik Filipsson advised in 2024 and 2025, the choice of agreement drove more value than the headline discount. Three patterns came up repeatedly.

• Flexibility came at a price. Buyers pushed off the EA toward CSP or MCA gained flexibility but lost the predictable EA discount, 5 to 15 percent on average.
• Old commitments rolled forward. Overcommitted EA seats from earlier cycles renewed without a true down, which locked the surplus in for another term.
• Partner margins varied widely. Identical CSP baskets differed 8 to 20 percent between partners.

Most of those reviews predate the November 2025 price level change, which ended the published volume discount on cloud services. The EA discount on online services now comes only from negotiation, so do not assume the 5 to 15 percent gap will reappear at your next renewal.

How should you choose a Microsoft cloud agreement?

Choose by size, by how stable your seat count is and by what mid term flexibility is worth to you. Settle the structure first and negotiate the discount inside it.

• Stable and large. The EA or MCA E usually wins on price.
• Variable or growing. CSP flexibility often beats a rigid commitment.
• Mixed and uncommitted. The MPSA keeps buying simple without lock in.
• In transition. Model MCA E carefully before Microsoft transfers you by default.

Microsoft sets out the commerce and subscription mechanics behind these agreements in its Microsoft 365 commerce documentation, which is worth reading before any transition.

How does the answer change with company size?

• Around 600 users. You clear the published EA minimum, though the account team may steer you to CSP at renewal anyway. A three year organization wide commitment earns little negotiated discount at this size. Annual CSP terms quoted by two competing partners, with a small monthly term pool for contractors, usually give a better balance.
• 20,000 users across several regions. The EA or MCA E is the realistic choice, and the negotiation spans Microsoft 365, Azure and support together. Under a single MCA, Azure commitment benefits can be shared across associated tenants, which simplifies groups that run separate tenants by region or business unit.

Why renewing on the agreement you already have is often a mistake

The usual advice is to stay on whichever agreement you have, because switching is disruptive and the discount is familiar. We disagree. In the reviews we advised, staying by inertia locked buyers into surplus seats and a structure that no longer matched their size.

Model the EA, MCA E and CSP against your real seat trend at every renewal, and treat the agreement as a choice you negotiate. Switching costs are real, mainly billing setup and partner onboarding, but they are paid once. A mismatched agreement costs you every year of the term.

The right agreement can be worth more than several points of discount, because it controls your ability to true down when the business changes.

What will Microsoft say about your agreement, and how should you answer?

Expect the account team or partner to present the agreement as settled before price is discussed. These lines come up most often.

How do you handle a forced MCA move?

Treat it as a negotiation, not a migration task. Model the cost and price protections first, and engage independent licensing experts before agreeing the transition.

Write down what must carry over: discounts by SKU, price caps, Azure commitment balances and custom amendments. Then plan the operational work Microsoft's migration guidance lists. Accounts payable needs the new remittance details, budgets and cost exports must be rebuilt, and savings plans bought in a currency other than US dollars are canceled at migration and need repurchasing.

Why test multiple CSP partners?

CSP pricing includes partner margin, and margin varies widely between partners. The same basket can differ materially from one quote to the next, so competitive quotes are the simplest saving available to you.

Give each partner the same SKUs, quantities, term lengths and billing frequency, and ask for support priced separately. Some partners fold first line support into the license price and others charge for it on top.

What contract terms should you ask for in each agreement?

Each agreement has one or two terms that decide whether it keeps working for you. Ask for them before signature.

• EA, annual reduction right. The right to reduce subscription counts at each anniversary, or an Enterprise Subscription Enrollment. It turns a divestment from a three year cost into a one year cost.
• EA, price hold on future SKUs. Fixed pricing for products you may add mid term, such as Copilot or E5 step ups, so later growth is not priced at list.
• MCA E, a cap on renewal increases. The agreement has no end date to force a repricing talk, so the cap has to be written into each subscription renewal.
• MCA E, a carry over schedule. A signed list of the EA discounts and amendments that apply from the first day.
• CSP, margin fixed for the term. The partner's margin over Microsoft's price, committed for the full term including renewals, so a sharp first year quote does not drift upward.
• CSP, aligned end dates. Subscription end dates set to one point in the year, so the whole basket can be resized and requoted together.

How do you check your own position before choosing?

Four places in Microsoft's own portals show what you own, what you use and when each term ends. Pull all four before any agreement conversation.

1. Subscriptions and dates. In the Microsoft 365 admin center, Billing then Your products lists each subscription, its quantity, term end date and whether it renews automatically.
2. Real usage. Reports then Usage shows active users by service. Compare active users with assigned licenses to size the surplus.
3. Agreement records. The volume licensing pages in the admin center hold EA and MPSA agreements, enrollment end dates and license summaries.
4. Azure spend. Cost Management + Billing in the Azure portal shows your billing scope, commitment balance and which agreement each subscription bills under.

What mistakes cost buyers the most?

• Missing the true up window. An order that arrives outside the 60 to 30 day period before the anniversary leaves growth unreported and turns a routine order into a compliance question.
• Buying annual CSP seats for a shrinking team. After the first seven days the count cannot go down, so seats bought for a project that ends early are paid to term.
• Letting two agreements grow by accident. A subsidiary on CSP and headquarters on an EA can pay two different prices for the same SKU for years before anyone compares the invoices.

What to do next

1. List what you have. Record every current agreement, its term and its renewal date, including subsidiaries and Azure bought on separate accounts.
2. Forecast the seat trend. Build a three year forecast with HR and finance, covering hiring plans, divestments and contractor swings.
3. Model the options. Run EA, MCA E and CSP against that forecast, including a case with an annual reduction right.
4. Get competing partner quotes. Price any CSP basket with at least two partners on an identical request.
5. Put a number on flexibility. Quantify what the ability to reduce seats mid term is worth to your business, using the downside case of your forecast.
6. Decide before Microsoft does. Choose the agreement on purpose before the renewal conversation opens, and put the reduction and price terms on your list of asks.
7. Get independent help early. Engage independent licensing experts before any MCA transition, while the terms are still open.

Frequently asked questions