Here’s the short version: Microsoft is ending the free 30-day grace period for expired CSP subscriptions. Starting May 4, anything that lapses without an explicit action gets automatically rolled into Extended Service Terms — month-to-month billing at a premium rate. If you’re not actively managing this, you’re going to eat surprise invoices and very confused client calls.

The long version is why this matters more than you think.

What’s Actually Changing

For years, when a Microsoft 365 CSP subscription expired, it got a quiet 30-day buffer. Services kept running, no extra charge. You had time to sort out the renewal, talk to the customer, handle the admin. It wasn’t elegant, but it worked.

That’s gone on May 4, 2026. Under the new model, expired subscriptions that don’t have a renewal or explicit cancellation on file roll straight into Extended Service Terms. Month-to-month. Higher rate. Locked seat counts — you can’t reduce licenses during EST, only cancel prorated.

Three paths at term end: renew, cancel-at-end-of-term, or enter EST. Microsoft has added new Partner Center tools to export subscriptions approaching EST so you can see what’s coming.

The Hidden Gotcha

This one is going to burn people.

Toggling auto-renew to OFF is no longer enough to stop service continuation. Under the new system, turning off auto-renew without submitting an explicit cancel-at-end-of-term action can still land the subscription in paid EST. You have to take a deliberate cancellation action — not just flip a switch.

If your renewal workflows rely on “just turn off auto-renew and we’re good,” those workflows are broken. Fix them now. This is exactly the kind of operational detail that separates growing MSPs from stagnant ones in the MSP bifurcation playing out this year.

What This Costs

Microsoft hasn’t published official EST premium rates across all SKUs, but the EST pricing is confirmed to be higher than standard annual pricing. Add that to July 2026 M365 price increases already in the pipeline, and MSPs who miss the May window on large tenants could get stacked twice — once on EST rates, again when July pricing kicks in.

The math on a 100-seat M365 Business Premium tenant, sitting in EST at even a 10% premium for a billing cycle before you catch it, isn’t catastrophic. On a 500-seat enterprise customer with a mix of E3, E5, and add-ons, it gets interesting fast. And it’s your invoice dispute, not theirs.

What to Do Monday Morning

This is a process problem, not a technology problem. The fix is operational:

1. Pull your renewal report now. Use the new Partner Center export to identify every subscription hitting term end between now and August 1. That’s your risk list.

2. Categorize by intent. For each subscription: renew, cancel, or knowingly enter EST (some customers will want the flexibility). Document the decision.

3. Set explicit cancels where needed. Don’t toggle auto-renew off and call it done. Submit the cancel-at-end-of-term action for anything you genuinely want to stop billing.

4. Talk to your distributors. Ask how EST appears in their portals. If you’re billing through Ingram, TD SYNNEX, or Pax8, the EST status may surface differently than in Partner Center direct. If you’re not sure which distribution model fits your practice, our master agent vs. TSD vs. distributor explainer covers the differences. Get aligned before May 4.

5. Communicate proactively to clients. Especially enterprise and mid-market accounts. Frame it simply: subscriptions no longer get a free buffer period; they renew, cancel, or continue on a month-to-month basis at a modestly higher rate. Send the email before they call you about an unexpected charge.

The Upside Nobody’s Talking About

EST isn’t purely punitive for partners. For customers evaluating whether to renew to annual or stay flexible — migration projects, acquisitions, pending budget approvals — EST gives you a short-term tool. “We’ll hold you in EST for 60 days while you finalize” is actually a useful conversation to be able to have.

But you have to know the customer is in EST on purpose. Accidental EST is a billing dispute. Intentional EST is a managed service you’re delivering.

Also worth noting: Microsoft 365 E7 is coming, and early details suggest it targets enterprise AI and security at a premium above E5. We broke down the E7 renewal conversation when it was first announced. If you’re renewing enterprise customers this summer, get ahead of the E7 conversation now. Lock annual terms before July at today’s pricing where it makes sense, and build the E7 migration into your H2 roadmap.

May 4 is six weeks out. That’s enough time to fix this — if you start today. And while you’re auditing, make sure your MSP tools aren’t creating their own attack surface — billing hygiene and security hygiene go hand in hand.