Auto-Renew Off No Longer Means Free: The MSP Playbook for Extended Service Terms
TL;DR
- Starting May 4, 2026, Microsoft replaces the free 30-day grace period on expired CSP subscriptions with paid Extended Service Terms (EST).
- A subscription with auto-renew off no longer means a pending decision; under the new rules it means automatic enrollment into paid EST at expiration.
- EST bills month to month at the monthly rate plus a 3% uplift, or 23% for products with no monthly SKU.
- Subscriptions in EST cannot be modified; you must convert back to a standard subscription first, with a prorated credit for unused EST time.
- Avoiding surprise EST charges requires an explicit cancel-at-end-of-term action, and distributor portals may handle that differently than Partner Center.
There is a setting in your licensing stack that quietly changed meaning. For years, auto-renew off on a CSP subscription meant "we have not decided yet," and the free 30-day grace period after expiration absorbed the indecision. As of May 4, 2026, that same setting means "enroll this customer in a paid month-to-month extension with an uplift."
If your PSA, billing system, or internal playbook treats auto-renew off as a pending-decision state, this change affects you and every customer you manage. Here is the full picture, what to do before May, and the customer emails to send this week.
How the grace period works until May 2026
Today, when a CSP subscription reaches end of term with auto-renew off, the customer does not lose access. The subscription enters a free grace period of about 30 days. Everything keeps working: users log in, email flows, files stay put, and nobody gets billed. After those 30 days, the subscription moves to a 90-day disabled state where admins can still reach the data but users are locked out. After 90 more days, it is deleted.
That grace period has been the MSP safety net. It buys time for the renewal conversation, the budget approval, or just the everyday chaos of running a business. Forgiving, flexible, free. And it is going away.
The three paths after May 4, 2026
When a subscription reaches end of term under the new rules, there is no waiting around. One of three things happens.
Renew. The subscription rolls into a new term at the normal rate. This is the default when auto-renew is on, and nothing about it changes.
Cancel at end of term. The subscription ends on its expiration date and the customer loses access that same day. No buffer, no grace period, a hard stop. Critically, this path must be chosen explicitly. Turning off auto-renew is not the same thing.
Extended Service Terms (EST). The paid replacement for the grace period. The subscription keeps running month to month at the monthly rate plus a 3% uplift. If the product has no monthly SKU, the uplift is 23%. EST can be cancelled at any time or converted back into a regular subscription.
Where the 3% versus 23% line falls
Most common Microsoft 365 SKUs (Business Basic, Business Premium, E3, E5, and so on) have a monthly plan in the price list, so EST bills at that monthly rate plus 3%. The 23% uplift applies to products with no monthly SKU at all: niche products, specialized offers, and certain Dynamics and Power Platform SKUs sold only in annual terms. For those, Microsoft derives a monthly rate and adds 23%.
What EST locks you out of
Once a subscription is in EST, you are not stuck forever, but your options narrow.
The big constraint: no modifications while in EST. No adding or removing seats, no term changes, no SKU swaps. To make any change, convert the subscription back to a standard subscription first, then change it. The good news is that converting or cancelling earns a prorated credit for any unused EST time.
That prorated billing is also EST's one genuine advantage over a monthly subscription. Monthly term subscriptions cannot be cancelled outside the first 7 days after purchase or renewal; after that you owe the full month. EST cancels at any point with prorated billing, so if you only need licenses for 10 days to finish a migration, you pay for 10 days.
Who is in scope
The eligibility rule is "purchased or renewed on or after April 1, 2025," and the renewal part catches people. A subscription bought years ago that auto-renewed in June 2025 is now eligible for EST at its next expiration. A multi-year term that has not renewed since before April 2025 keeps the old grace period rules for its current term.
Scope-wise, EST applies to commercial and public sector subscriptions, including education, nonprofit, and government community cloud (GCC). There has been no indication that GCC-High licensing, which runs under AOS-G rather than CSP/NCE, is affected. Trials and end-of-sale SKUs are not eligible, though end-of-sale SKUs with conversions (endofsalewithconversion) are.
Five moves to make before May
- Audit your subscriptions. Pull every subscription with auto-renew off and decide each one: renew, cancel, or EST. Partner Center now offers a data export of all EST-eligible subscriptions to speed this up.
- Set explicit cancel actions. For anything that should end, do not just leave auto-renew off. That now means paid EST enrollment. Explicitly set cancel at end of term; it is the only way out.
- Interrogate your distributor. If you buy through Pax8, Sherweb, TD SYNNEX, Ingram, or another distributor, find out how this works in their platform before May, not during it. Cancel workflows and EST behavior may look different in their portal than in Partner Center, and some distributors may not have the renew-into-EST option available yet. Worse, what a distributor labels "cancel" in their UI may actually just disable auto-renew at the Microsoft level, which under the new rules means EST enrollment, not cancellation. Ask them directly: how do we set an explicit cancel at end of term, and how will EST appear in our billing?
- Update your tools. Anywhere a PSA, billing system, or runbook uses auto-renew off as a pending-decision flag, that workflow now produces paid EST. Rewrite it.
- Tell your customers now. Letting a subscription lapse no longer means 30 days of free service. The templates below are ready to send.
One more operational warning: be careful when transitioning a customer between subscription types. MSPs have reported entire tenants going down when cancelling one subscription type to switch to another, because the cancellation processed before the new subscription activated. Always overlap: purchase the new subscription, confirm it is active, then cancel the old one. Never cancel first.
If a cancelled subscription does expire, remember there is no reactivation in NCE; you purchase a new subscription. The normal data retention lifecycle still applies, with data preserved through the expired and disabled states for up to 120 days before deletion, so a new subscription created in that window can have data and license assignments restored.
Copy-paste customer outreach
Subject: Important Change to Your Microsoft 365 Renewals
Hi [Customer Name],
Microsoft is changing how subscription renewals work starting May 2026. Previously, if a subscription wasn't renewed on time, there was a free 30-day window where everything kept working even if there was a lapse in a subscription expiration. That free window is going away.
Going forward, subscriptions will either renew automatically, cancel immediately (with no buffer), or move to a paid month-to-month extension. Your subscriptions are not set to auto-renew today so we need to review your options with you on a call. Would any of the following times work in the coming week?
Subject: Action Needed - Your [Product] Subscription Renewal by [Date]
Hi [Customer Name],
Your [Product Name] subscription is set to expire on [Date]. Due to a recent Microsoft change, we need to confirm what you'd like to do before that date. There is no longer a free grace period after expiration.
Your options: (1) Renew for another year at the current rate, (2) Cancel - access stops on [Date] with no extension, or (3) If you need more time to decide, we can set up a paid month-to-month extension.
Please let us know by [Date] so we can avoid any surprise charges or service disruptions.
The official documentation
The primary reference is Use Extended Service Terms (EST) for Cloud Solution Provider (CSP) subscriptions on Microsoft Learn (opens in new tab), backed by the Partner Center announcements that introduced and refined the change:
Frequently asked questions
Does EST affect subscriptions with auto-renew turned on?
No. If auto-renew is on, the subscription renews exactly as it always has. EST only comes into play when auto-renew is off at expiration.
Which subscriptions are eligible for EST?
Any CSP subscription purchased or renewed on or after April 1, 2025, including education, nonprofit, and GCC tenants. Trials and end-of-sale SKUs are not eligible, though end-of-sale SKUs with conversions are. There is no indication GCC-High (AOS-G) licensing is affected.
Why use EST instead of just buying a monthly subscription?
Monthly term subscriptions cannot be cancelled outside the first 7 days after purchase or renewal, so you pay the full month. EST can be cancelled at any point with prorated billing, so 10 days of licenses to finish a migration costs 10 days, not a month.
Can an expired and cancelled subscription be reactivated?
No, and that has always been true for NCE: you have to purchase a new subscription. Data is preserved through the expired and disabled states for up to 120 days total, so a new subscription spun up in that window can have data and license assignments restored.
While you audit renewals, audit posture
Subscription hygiene and security hygiene drift the same way: quietly, until it costs money. CloudCapsule assesses 250+ controls across every tenant you manage in about 60 seconds, with reports your clients can read.
Run a free scan
Written by
Nick Ross
CEO · Microsoft MVP · Founder, T-Minus 365
Nick is not just a CEO, he's a respected thought leader and influencer in the MSP space. Tens of thousands of MSPs learn through his YouTube channel, T-Minus365. Nick has been honored as a three-time Microsoft MVP for his educational content; his expertise and influence are the backbone of our mission, ensuring that you are in the best hands when it comes to security.
Nick joined Pax8 in 2017, where he would ultimately oversee product management for PSA and Microsoft integrations. Following his tenure at Pax8, Nick has continued to demonstrate his leadership prowess as an executive at various MSPs, culminating in his most recent role at Sourcepass.
Nick holds a Bachelor's Degree in Business Management from Florida State University, as well as a Minor Degree in Entrepreneurship. In his free time, Nick is an avid hiker, reader, and fitness-junkie.
