Most organisations choose a Microsoft licensing agreement once, under time pressure, on the advice of whoever is quoting. Then they live with it for three years. The CSP vs Enterprise Agreement vs MCA question looks like procurement, and it is answered as procurement, which is why the consequences arrive later and land somewhere else entirely: on the person who has to reduce twenty seats in March, or raise a ticket at two in the morning, or explain why the Azure bill moved when nothing was deployed.
This is a comparison written from the operating side rather than the buying side. What each agreement is, what changed in 2026, and what actually becomes harder depending on which one you signed.
The three agreements, briefly
Enterprise Agreement. Microsoft’s Enterprise Agreement page describes it as being for organisations with 500 or more users or devices, licensing software and cloud services for a minimum three-year period. Additions are reconciled once a year at the true-up, due 30 to 60 days before the enrollment anniversary, and seat counts cannot be reduced mid-term. Under an Enterprise Subscription Enrollment they can be decreased, but only at that anniversary. You will read elsewhere that Microsoft has raised the commercial minimum to around 2,400 seats. We went looking for that figure and could not source it to Microsoft: not the licensing programme pages, not the Enterprise Agreement guidance, not Volume Licensing Central, not the partner announcements. What Microsoft has actually said is narrower, and carries no seat number at all: that from 1 January 2025 a small percentage of cloud Enterprise Agreements in direct markets would no longer be eligible for renewal under the existing framework. What we see at renewal is smaller commercial estates being steered towards CSP or MCA-E whatever the published 500 says. Treat the 500 as the documented floor, treat the steer as real, and do not plan around a threshold nobody will show you in writing.
Microsoft Customer Agreement. Microsoft describes the MCA as having no purchase minimums and tailored billing plans, and, unlike traditional volume licensing, it never expires. There is an enterprise flavour, MCA-E, sold through Microsoft’s enterprise motion.
CSP. You buy through a partner rather than from Microsoft. Some products are only available this way: Business Central licences, for example, can only be purchased through CSP.
MPSA still exists too, at 250 or more users or devices, with no retirement notice on its page. It is rarely the answer for a new decision, but if you are on one, nothing has been announced that forces you off it.
The seven-day rule, which is the one people get wrong
Ask around and you will be told the new commerce cancellation window is 72 hours. It is not. For licence-based and software subscriptions it is seven calendar days, and the 72-hour window applies only to Marketplace SaaS offers. That is the good news. The rest of the rule is where organisations get hurt:
- Seats go up at any time. They come down only inside seven days. Licences can be decreased only within the first seven days of when they were added, and that applies whether they were added at initial purchase, at renewal, or mid-term. After that, the count cannot be reduced until the next window at renewal.
- The window restarts at renewal, precisely at the datetime renewal completes. That is the one moment each year when an annual commitment can be resized.
- Moving to a longer term is one-way. You can move to a longer term duration mid-term; you cannot move to a shorter one. Worse, taking the longer term costs you the exit, because a mid-term billing change does not open a seven-day window, so seat reductions are unavailable until renewal.
So the flexibility CSP is sold on is real in one direction only. In our view that makes term length the most consequential thing on the order form, and it should be chosen against how confident you are in headcount twelve months out, not against the discount. Monthly billing on an annual term carries a 5% premium over annual billing. When headcount is genuinely uncertain, that 5% is the cheapest insurance in the agreement.
What changed in 2026, and dates the advice you will find elsewhere
Three changes inside the last year make most existing guidance wrong.
The free grace period is gone. Effective 4 May 2026, the free grace period for accessing services on non-renewed CSP subscriptions was discontinued. A customer who does not renew either cancels at end of term with no service, or enters a paid extended service term billed monthly at the monthly rate plus 3%, or plus 23% where the SKU has no monthly plan.
Turning auto-renew off no longer stops a subscription. This is the one to check today. Subscriptions eligible for an extended service term that have auto-renew set to false, without an explicit cancellation, are converted to an extended service term with auto-renew set to true. A backfill applied that retrospectively in February 2026. Stopping a subscription now needs an explicit scheduled cancellation, not a toggle.
Two price rises land at renewal, not on their effective dates. Microsoft’s 2026 commercial price changes take effect at each customer’s next renewal after 1 July 2026: Office 365 E3 rises 13% to $26, Office 365 E5 8% to $41, Microsoft 365 E3 8% to $39, Microsoft 365 E5 5% to $60, Business Basic 16% to $7 and Business Standard 12% to $14, while Business Premium and Office 365 E1 are unchanged. Separately, from 1 October 2026 CSP software subscriptions such as SQL Server, Windows Server, CALs and System Center on annual terms billed monthly take a 5% cost of capital uplift, applied at renewal on or after that date.
Because a CSP price is fixed at the time of purchase and changes only at renewal, upgrade or term conversion, the number that matters to your finance team is not the effective date. It is your renewal date.
What actually changes about running the estate
This is the part that never appears on the comparison grid, and it is the part we get called about.
Who your users call. Under CSP, customers cannot raise support requests with Microsoft at all. Microsoft’s own documentation is blunt: CSP customers must contact their partner, the partner is expected to diagnose and resolve, and the partner may charge for that support. Microsoft does not send subscription communications directly to those customers, and the admin portals redirect them to their partner of record. If you buy through CSP, your support experience is your partner’s support desk, whatever the Microsoft SLA says.
What that costs when it goes wrong
A 1,200-seat manufacturer moved its Microsoft 365 and Entra ID licensing to a purely transactional reseller, for a saving the client put at around 3%. Six months later a Conditional Access change, combined with a directory sync that disabled accounts on-premises, locked every administrator out of the tenant.
Two doors had been shut months earlier, at purchase. Because every subscription had moved to the reseller, the client no longer met Microsoft’s condition for opening its own case: Microsoft requires at least one subscription bought directly from Microsoft, and where everything is bought through a partner, support runs through that partner. And the reseller held no delegated admin relationship carrying the service support administrator role, so it could not file on the client’s behalf through Partner Center either. An indirect reseller would have had to escalate through its own provider in any case.
There was still a route, and it is worth being precise about this rather than claiming there was none. Microsoft’s lockout guidance says a Global Administrator can call the business support line, and that is what the client did: roughly fourteen hours on the admin queue, with PIN verification against the tenant’s registered contact details, before the case reached someone who could act. What the 3% had bought away was not the existence of a route. It was the fast one, and the difference showed up as stalled shipping.
The fix costs nothing and is documented. Microsoft’s guidance on emergency access accounts is to keep at least two cloud-only accounts on the onmicrosoft.com domain, with phishing-resistant credentials that differ from your normal admin accounts, permanently assigned Global Administrator rather than eligible through PIM, excluded from any Conditional Access policy that blocks or restricts sign-in, and tested at least every 90 days. Cloud-only is the part people skip. Microsoft Entra ID will stop you deleting the last Global Administrator in the cloud, but it will not stop that account being disabled on-premises and synced in, which is exactly how a sync script takes the last door with it.
Who can change anything. CSP customers also cannot change their own subscriptions directly with Microsoft. Adding or cancelling goes through the partner. That is fine when the partner is responsive and painful when they are not, and it is worth knowing before you need it on a Friday.
What currency you are billed in. Azure is priced in US dollars worldwide under the Microsoft Customer Agreement and the Microsoft Partner Agreement, and in local currency under an Enterprise Agreement. For a business outside the United States, moving from EA to MCA or CSP moves exchange rate exposure onto your own bill.
Where the Azure discount actually comes from. In CSP the Azure price list holds direct prices, not a wholesale rate card. Any discount comes out of the partner’s own earned credit, which is compensation for managing the estate. That credit explicitly does not apply to reservations, savings plans, Spot virtual machines, third-party items or Marketplace purchases, which means a partner is least incentivised on exactly the commitments that save you the most.
Who controls your commitments. Azure savings plans apply to subscriptions purchased through an EA, MCA or Microsoft Partner Agreement. Under CSP the partner buys them for you or grants you permission to buy your own, and the price you pay for a reservation is set by the partner, which can differ from the price shown in the portal. Customers cannot exchange, cancel or renew a reservation without the partner. Separately, Microsoft Azure Consumption Commitment tracking in the portal is available only to direct MCA and EA customers, so if you have committed to a consumption number through a partner, you cannot watch it yourself.
Moving between them is not free
If you are already on an agreement, the exit has a shape worth knowing.
EA to MCA is a billing migration, and Microsoft lists what does not come with you: support benefits do not transfer, partner ID associations are not copied, custom and shared cost views are not migrated, budgets have to be recreated, export jobs do not migrate, the Azure Enterprise Reporting APIs are retired and unavailable, historical cost data stays in the EA scope, and a tax exemption certificate needs a support request to reassociate. Against that, an MCA supports multiple tenants, consumption commitments and discounts can be shared, and the billing profile ID never changes, where an EA enrollment number changes at every renewal.
EA to CSP for seat-based licences happens only at expiry, never mid-term. The transfer tool exposes agreements that expired in the last 90 days or end within six months, and the move cannot be undone, although the newly created CSP subscription has its own seven-day window. Microsoft’s own guidance puts it plainly: moving to CSP is not a renewal, it is a migration.
Letting an EA lapse has a price. Microsoft enables an extended purchase term by default for commercial customers and bills monthly after expiry at the current price level plus a 3% admin fee. And since April 2022 every renewal quote has carried a clause reducing the negotiated discount by at least three percentage points if the agreement is signed after the expiration date. Renewing late is not neutral.
One more, for anyone assuming the MCA is the universal destination: expiring indirect Enterprise Agreements currently cannot be renewed into a Microsoft Customer Agreement.
What we find when we look
Across 36 Microsoft estate reviews run for prospective and onboarding clients over the past two years, 29 of the 36 carried at least one structural licensing or support blind spot. More than four in five.
The caveat belongs here rather than in a footnote, because it changes how the number should be read. Nobody commissions a licensing review at random. These organisations asked for one because somebody inside already suspected a problem, so this is what a review turns up when there is a reason to commission one, not a rate across Microsoft customers generally.
Two of the findings are worth naming, and these are figures we measured rather than impressions.
Committed seats nobody was using. In 26 of the 36 estates, unassigned or dormant licences accounted for a median of 14% of annual licensing spend, with individual estates ranging from 11% to 18%. In money that was a median of $64,000 a year, across a range from $42,000 to $95,000. None of it is lost permanently. It is the annualised cost of committed seats nobody was using, and most of it can be right-sized at the renewal anniversary, which is exactly why the renewal date matters more than the headline price.
Nobody who could raise a ticket. In 19 of the 36, no named person held an active, verified role capable of raising a support case, either internally or at the partner. That is a configuration fact rather than a verdict on the agreement. Under CSP the partner being the only route to Microsoft is the model working as designed; it becomes a problem only when nobody is named and nobody has ever tested it.
The two travel together, and that is the finding underneath both. The estate where nobody owns the renewal is usually the estate where nobody is named on the support path, because both are symptoms of the same thing: a licensing relationship that somebody bought and nobody runs.
Our position: choose for the operating model, then negotiate
In our view the agreement should be chosen for how the estate is run, and the commercial terms negotiated afterwards, rather than the other way around.
If you have an internal team that raises its own tickets, manages its own subscriptions and buys its own reservations, a direct agreement keeps that control and the consumption commitment tracking that goes with it. If you do not have that team, and most organisations under a few hundred seats do not, then CSP is not a discount mechanism, it is an outsourcing decision, and the right question is not the price per seat but whether the partner answers the phone. We see the cost of getting that backwards more often than we see a bad price: an organisation with a good rate and nobody to call.
The corollary is uncomfortable and worth saying anyway. If your partner’s only contribution is a purchase order, you are paying an operating premium for a procurement service, and you should either get the support you are entitled to or move.
Where to start
Four things to check this week, whichever agreement you are on:
- Find your renewal date and put it in a calendar with a reminder eight weeks before. It is the only date on which you can reduce seats, change term length or lock a price ahead of an increase.
- Check your auto-renew settings, and confirm that anything you intended to stop carries an explicit scheduled cancellation rather than an auto-renew toggle.
- Count your actual seats against your committed seats. The gap is what you are paying for and cannot reduce until renewal.
- Ask who raises a Microsoft support ticket on your behalf, and test it before you need it.
If any of those produce a pause, talk to our team. We run a licence review against your actual usage rather than your order form, and where an estate needs someone to operate it rather than just supply it, that is what our managed services cover. For the Azure side of the same decision, our Azure practice picks up where the licensing stops. And if Power BI Premium is in your estate, its P SKU retirement is tied to your agreement term, which makes the two decisions one conversation. If you would rather talk it through first, get in touch.
Frequently asked questions
What is the difference between CSP and an Enterprise Agreement? An Enterprise Agreement is signed with Microsoft, is aimed at organisations with 500 or more users or devices, and runs for a minimum three-year period. CSP is bought through a partner, who also becomes your first line of support and the only route to changing your subscriptions. The CSP vs Enterprise Agreement choice therefore decides who you deal with day to day, not only what you pay.
Can we cancel a Microsoft subscription if we over-ordered? Within seven calendar days of the licences being added, yes, with a prorated refund. After that the seat count cannot be reduced until the cancellation window reopens at renewal. The seven-day window restarts at the exact time each renewal completes.
Is the cancellation window 72 hours or seven days? Seven calendar days for licence-based and software subscriptions. The 72-hour window applies only to Microsoft Marketplace SaaS offers, which is where the confusion comes from.
What happens if we do not renew a CSP subscription? Since 4 May 2026 there is no free grace period. You either cancel at the end of the term and lose service, or move onto a paid extended service term billed monthly at the monthly rate plus 3%, or plus 23% where the product has no monthly plan.
Will the 2026 Microsoft 365 price rise hit us on 1 July? No. It applies at your next renewal after 1 July 2026. An organisation mid-term keeps its existing pricing until then, which is why the renewal date matters more than the effective date.
Should we move from an Enterprise Agreement to CSP? Only at expiry, because seat-based licences cannot transfer mid-term, and the move cannot be undone once made. Check first whether the support and subscription-management model suits you, because that changes on the day you move.
Operations head with 20 years of experience delivering business intelligence, ERP and AI programmes across healthcare, finance and manufacturing. Focus areas include Power Platform adoption and governance, delivery models, and managed services.