Microsoft discontinued the automatic 30-day free buffer on nonrenewed subscriptions and replaced it with a paid Extended Service Term. This is the precise before/after, the SKUs affected, and the moves that keep renewal slippage from becoming an unbudgeted invoice.
Microsoft discontinued the automatic 30-day free buffer on nonrenewed subscriptions and replaced it with a paid Extended Service Term. This is the precise before/after, the SKUs affected, and the moves that keep renewal slippage from becoming an unbudgeted invoice.
Microsoft eliminated the automatic free grace period that used to protect a Cloud Solution Provider (CSP) subscription after its term ended. In its place sits the Extended Service Term (EST), a paid continuation that bills at the current monthly rate plus an uplift. The change was first announced on October 14, 2025 in the notice titled New extended service term for Cloud Solution Provider (CSP) subscriptions, which stated that "effective April 1, 2026, the free grace period for accessing services on non-renewed subscriptions will be discontinued."
Watch the date. Microsoft postponed enforcement from April 1, 2026 to May 4, 2026 (Giacom, March 3, 2026), and its own Partner Center documentation updated May 29, 2026 confirms EST is "generally available and enforced since May 4, 2026." So the policy carries an April 1 headline but a May 4 live-fire date. If a reseller told you nothing happened on April 1 and you assumed the change died, it did not. It shifted five weeks and is now fully enforced.
The April 1 announcement is not the day the buffer disappeared. May 4, 2026 is. Anyone who relaxed after April 1 relaxed too early.
Under the old model, a CSP subscription that reached term end with auto-renew off entered a free grace period of roughly 30 days. Everything kept working, and nobody was billed. After that 30 days, the subscription moved into a 90-day disabled state where admins could still reach data but users were locked out. That gave finance and procurement a full month of cover to sort out a slipped renewal at zero cost.
After May 4, 2026, the term end date is the service interruption date. There is no automatic free grace at all. The subscription either cancels (service stops immediately) or rolls into paid EST. The table below is the practical before/after you should paste into your renewal runbook.
| Dimension | Before (pre-change) | After (EST live) |
|---|---|---|
| Term end behavior | 30-day free grace, service continues | Immediate interruption unless EST or renewal |
| Cost of the buffer | $0 for 30 days | Monthly rate + 3% (or +23% with no monthly plan) |
| End-of-term options | 2 (auto-renew on / off) | 3 (renew, cancel at term, or enter EST) |
| Default of auto-renew off | Stop after grace | Continue into paid EST |
| User access on non-payment | Preserved 30 days, then disabled | Cut at term end unless EST active |
The single most dangerous shift is the reversed default. As SAMexpert put it on June 14, 2026, "Previously, auto-renew off meant stop after the grace period. Now it means continue at the premium rate." The setting you have used for years to safely wind a subscription down now does the opposite. Our companion analysis on avoiding an accidental EST trigger during renewal slippage walks the settings line by line.
EST is not a token fee. Microsoft's official formula bills monthly at the current monthly term rate plus a 3% uplift where a monthly plan exists, or a flat 23% uplift where no monthly plan exists (SAMexpert, June 14, 2026, confirms the two rates are separate). The 23% is the number that hurts, because most enterprise annual-commit customers do not carry a matching monthly SKU, so slipping into EST from an annual commitment triggers the 23% path, not the 3% path.
| Scenario | Base | Uplift | Extra cost |
|---|---|---|---|
| 100 x Business Basic at $6.00 | $6.00/user/mo | 3% | +$18/month total |
| 10,000 x M365 E5, annual billing | annual commit | 23% | +$134,500/month |
| $1.5M/mo portfolio, EST for 1 day | $1.5M/mo | 23% path | ~$50,000 for a single day |
Read the third row twice. AppXite's support documentation models a $1.5 million monthly portfolio accidentally converted to EST for one day at roughly $51,500 ($1,545,000 divided by 30). A single misconfigured auto-renew flag, discovered a day late, can cost more than an entire year of some smaller vendors' contracts. The full cost breakdown lives in what the Extended Service Term actually costs, and it is where you should send your finance team before renewal season.
For 10,000 E5 users, slipping into EST costs an extra $134,500 per month versus renewing on time. That is the price of a late signature now.
Eligibility is broad. EST applies to commercial and public sector (education, nonprofit, government community cloud) license-based services across CSP, MCA-E, and Buy-Online channels, in all markets, and across all durations (monthly, annual, and triennial). The precise trigger from Microsoft Learn: subscriptions purchased or renewed between April 1, 2025 and May 4, 2026 with term end dates after May 4, 2026 are in scope.
That "renewed since April 2025" window is a trap for multi-year buyers. Per T-Minus365 (March 20, 2026): if your subscription auto-renewed in, say, June 2025, that renewal counts and it is now EST-eligible at its next expiry. If it is a multi-year term that has not renewed since before April 2025, the old grace rules still apply for the current term. You cannot assume your triennial term is safe until you check its last renewal event date.
If your estate straddles EA and CSP, the exclusion list matters for sequencing. Perpetual licenses and Azure commitments sit outside EST, but your seat-based M365 and Dynamics do not. Buyers mid-migration should read migrating from EA to CSP without a service gap before touching any auto-renew flag, because a botched transition now lands in EST rather than a free buffer.
Turning auto-renew off without an explicit cancel often auto-enrolls the subscription into paid EST at term end (HubSite365, March 22, 2026). The muscle memory of a decade of admins is now wrong. If your intent is to stop a subscription, you must actively choose cancel, not merely disable renewal.
Cancel is the opposite failure mode. SoftwareOne (March 17, 2026) is blunt: cancel is "the dangerous option ... it means the service stops the moment the term ends." Data is retained for 30 days but users lose access immediately, and Microsoft's own documentation confirms the subscription "can't be recovered or reactivated." For email, this can halt a business at 12:01 am on the term-end date. There is no take-back.
While a subscription sits in EST you cannot add seats or change the term. To make any change you must first convert it back to a standard subscription (T-Minus365). So EST is not a comfortable holding pattern where you calmly negotiate seat counts. It is a metered pause, and the meter runs at up to base plus 23%.
Behavior varies by provider. Some distributors did not have the "renew into EST" option in their portal on the same timeline as Microsoft (T-Minus365). Others pre-empt the risk in the opposite direction: AppXite's platform forces "Cancel at end of term" when a customer disables auto-renewal after February 16, 2026. So the same auto-renew-off action can produce paid EST on one platform and hard cancellation on another. You must confirm your reseller's default in writing. Do not assume.
Auto-renew off can now mean pay 23% more, or lose all access instantly, depending on your reseller. Get their default in writing before any term ends.
This is not purely a takeaway. As SAMexpert framed it, what you lose is a free 30-day buffer; what you gain is that services keep running while you resolve a renewal, so nobody loses data because finance took too long. The 23% premium is, in effect, delay insurance. There is also a genuine proration advantage: monthly term SKUs cannot be cancelled outside the first 7 days, leaving you on the hook for the full month, whereas EST can be cancelled at any point in the month with prorated billing.
That proration matters for one specific play: if you know a renewal will slip by a week or two, a short controlled EST window can be cheaper and cleaner than forcing a full monthly SKU you cannot exit. Used deliberately, the mechanism has leverage. Our analysis of using the Extended Service Term as negotiation leverage covers when that works and, more importantly, when it backfires against you at the table.
The risk sits almost entirely on the buyer side of the term-end date. Microsoft removed a free option and replaced it with two paid or destructive ones, and it flipped the default so that inaction now costs money instead of gracefully stopping. The leverage you retain is timing and configuration discipline: EST only ever triggers because a term ended without a clean decision. Every dollar of EST cost is avoidable with a governed renewal calendar.
There is a second exposure most buyers miss: the data clock. Cancellation retains data for only 30 days, and the broader non-renewal lifecycle has its own deletion schedule. If your renewal decision drags, you can lose not just access but recoverability. Map your dates against the 12-month data deletion clock after non-renewal so a cost problem does not become a data-loss problem. For partial reductions, dropping SKUs at renewal without losing access mid-term shows how to trim seats without tipping the whole subscription into EST.
For the full framework across all of these decisions, start with the pillar, the 2026 buyer guide to the Extended Service Term and non-renewal, and place this change in wider context with our summary of every material Microsoft licensing change in 2026.
The change was announced October 14, 2025 with an effective date of April 1, 2026, but Microsoft postponed enforcement to May 4, 2026. Its documentation updated May 29, 2026 confirms the Extended Service Term has been generally available and enforced since May 4, 2026. Treat May 4, 2026 as the live date, not April 1.
EST bills monthly at the current monthly term rate plus a 3% uplift where a monthly plan exists, or a flat 23% uplift where no monthly plan exists. Most annual-commit enterprise customers land on the 23% path. For 10,000 M365 E5 users on annual billing, that is roughly $134,500 in extra cost per month versus renewing on time.
EST applies to commercial, education, and nonprofit license-based services across CSP, MCA-E, and Buy-Online, in all markets and all durations, purchased or renewed between April 1, 2025 and May 4, 2026 with term end dates after May 4, 2026. Software licenses, Azure reservations, savings plans, third-party offers, trials, and most end-of-sale SKUs are excluded.
No, and this is the biggest trap. Turning auto-renew off without an explicit cancel often auto-enrolls the subscription into paid EST at term end. The default reversed: auto-renew off used to mean stop after the free grace period, but now it can mean continue at the premium rate. Confirm your reseller's specific default behavior in writing.
Yes, but cancel stops service the moment the term ends, with no buffer, and it cannot be recovered or reactivated. Data is retained for only 30 days. Use cancel only for subscriptions you are certain to never reactivate, and never as a gentle wind-down mechanism.
No. You cannot make changes to a subscription while it is in EST, including adding seats or changing the term. To make any change you must first convert it back to a standard subscription, during which time the EST premium continues to accrue.
Every material Microsoft licensing change in 2026: EA terms, Copilot pricing, Defender packaging, and Azure rules, plus what each one costs you.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
