A late renewal used to be free for 30 days. Now it defaults you onto a paid Extended Service Term (CSP) or Extended Period Term (EA), and this guide gives you the exact calendar and checklist to keep a subscription alive on old terms while the new deal closes.
A late renewal used to be free for 30 days. Now it defaults you onto a paid Extended Service Term (CSP) or Extended Period Term (EA), and this guide gives you the exact calendar and checklist to keep a subscription alive on old terms while the new deal closes.
For two decades, a Microsoft renewal that slipped past the anniversary was a non-event. The subscription kept running, you finished the negotiation, and you backdated or trued up when the paper was signed. That safety net is gone. As of the CSP changes announced on 14 October 2025 and enforced from 4 May 2026, the old 30-day grace period is eliminated and replaced by a paid path called the Extended Service Term (EST). The Enterprise Agreement world has its own analog, the Extended Period Term (EPT), which has existed in contract language but is now being applied with far less tolerance.
The single most important behavioral change: turning off auto-renewal no longer stops the meter. It moves you onto the paid extension. The default flipped. Under the old regime, auto-renew off meant the subscription would lapse harmlessly. Under the new regime, a subscription with auto-renew off and no explicit cancellation instruction is treated as a candidate for EST and keeps billing. Microsoft even ran a backfill (completed by 16 February 2026) that converted eligible auto-renew-off subscriptions onto the EST path with auto-renew set true, specifically to preserve service after term end. In plain terms, Microsoft pre-loaded a lot of tenants onto the penalty rails without any action on the buyer's part.
This subpage assumes you already understand the mechanics at a high level. If you do not, start with the 2026 buyer guide to the Extended Service Term and non-renewal and the timeline of what changed on April 1, 2026. Here we focus on one narrow, high-stakes problem: keeping the subscription active on old terms while the new deal closes, without accidentally entering the penalty path.
Auto-renew off no longer means the meter stops. It now means the meter moves to the premium rate.
Renewal slippage lands you in one of two penalty regimes depending on your contract vehicle. They behave differently, and confusing them is where buyers lose money.
In CSP, the Extended Service Term (EST) applies to subscriptions purchased on or after 1 April 2025 with an expiration date on or after 4 May 2026, where auto-renew is off. EST bills monthly at a premium: the monthly term rate plus 3% for products that have a monthly plan, and a flat 23% uplift for products that do not. That 23% is roughly the 20% monthly-vs-annual penalty plus the 3% administrative uplift. The one mercy is flexibility: unlike a standard monthly NCE subscription (which cannot be cancelled after the first 7 days), EST can be cancelled mid-month with a prorated refund, effective from 4 May 2026. For a 10-day migration finish, EST charges 10 days; a monthly SKU would charge the full month.
In the Enterprise Agreement world, the Extended Period Term (EPT) governs. If an enrollment expires and is not renewed, EPT-enabled Online Services continue month to month, billed at the current published price for the affiliate's price level plus a 3% administrative fee for up to one year. Critically, pricing resets to Level A for each new year, which can raise your per-unit cost above the volume-discounted level you held under the EA. On your invoice, an EPT charge is marked with an "EXT" purchase order tag. That is the flag to watch for.
| Attribute | EST (CSP) | EPT (EA / EAS) |
|---|---|---|
| Trigger | Auto-renew off, no explicit cancel, eligible term dates | Enrollment expires without renewal |
| Premium | Monthly rate + 3%, or flat 23% if no monthly SKU | Published price at affiliate level + 3% admin fee |
| Price-level risk | Uses monthly list rate | Resets to Level A each new year, losing volume discount |
| Duration | Month to month until cancelled or converted | Month to month for up to one year |
| Mid-period cancel | Yes, prorated (from 4 May 2026) | Opt-out via OLSET form, stops future billing only |
| Credit / reversal | Convert to standard subscription for prorated credit | Backdated renewal within 30 days credits EPT in full |
| Invoice flag | EST line in Cloud Marketplace | Purchase order marked "EXT" |
Renewal slippage is a calendar failure before it is a commercial one. The following anchor dates are the ones that carry money. Build them backward from your anniversary date, not forward from today.
The EA opt-out deadline is anniversary minus 30 days. The EA credit cutoff is anniversary plus one month. Everything between those two dates is where deals are saved or lost.
The goal during a slipping renewal is continuity of service on your existing commercial terms while the new agreement is finalized, without paying the 3% to 23% premium or the Level A price reset. Work this checklist in order.
Several failure modes eliminate any path to recovery. These are not edge cases; they are the most common ways buyers lose money during slippage, and they recur across our engagements.
Migrating programs instead of renewing. EPT credits are only considered when you renew into another Enterprise enrollment, not across programs. If you migrate EA to CSP, ROC treats it as a migration, not a renewal, so it is ineligible for credit. If you also failed to file the opt-out, you are paying EPT invoices with no recourse. This is the single most expensive trap in the current regime. If a program change is on the table, read migrating from EA to CSP without a service gap before you let the EA lapse, and file the OLSET regardless.
Opting out after billing has started. Submitting the opt-out form once EPT invoices have already issued stops future billing but does not credit invoices already generated. The form is a forward-looking stop, not a rewind. This is why the 30-day-before-expiration deadline matters more than the reactive one.
Treating cancel as a soft lapse in CSP. Cancel is the sharp edge. It is not the old grace-period lapse. Users lose access the moment the term ends. Data is retained (30 days per some partner guidance, up to 90 days in Microsoft's broader lifecycle) and then deleted. If a slipping renewal quietly hits a cancel-at-end-of-term instruction, you lose service on the anniversary with no warning. Understand the full clock in the data deletion timeline after non-renewal.
Assuming EST is editable. Once a subscription enters EST, no modifications are permitted except cancellation. You cannot adjust seat counts or SKUs inside EST. To change anything, you convert to a standard subscription, which cancels the EST line, issues a prorated credit, and starts a fresh standard term the same day. Plan any seat or SKU changes as part of the conversion, not before.
There is a legitimate use for these mechanisms. EST's mid-month cancellation makes it a genuinely useful short bridge for a migration tail: pay only for the days you need rather than a full month under a standard monthly SKU. For a controlled cutover finishing on day 10 of a month, EST can be cheaper than the alternative. That is the one place the new regime works in the buyer's favor.
But do not confuse a deliberate 10-day bridge with an open-ended negotiation stall. A slipping renewal that runs on EPT for three months at Level A pricing plus 3% can erase a meaningful chunk of the discount you are fighting for at the table. In practice we have seen the extended-term premium quietly consume the concession the buyer thought they had won. The discipline is to decide, in advance, the maximum number of months you will tolerate on the bridge and what it costs, then hold the vendor to a close date. Used with intent, the extended term can even be a source of negotiation leverage; used by accident, it is pure margin transfer to Microsoft.
Two governance habits prevent almost all of this. First, start the renewal early enough that slippage is a contingency, not a plan. Our standard advice is to begin the renewal proposal evaluation at least 9 to 12 months out for large EAs. Second, align adjacent renewals so you are not managing overlapping clocks, including support renewal timing, which frequently drifts out of sync with the EA and creates its own slippage exposure.
The bottom line: Microsoft moved the default from free lapse to paid extension, and the protective calendar items (the EA 30-day opt-out and the one-month credit cutoff, the CSP explicit-cancel instruction and 7-day window) are unforgiving. Treat them as hard financial controls, not administrative afterthoughts.
No, and this is the most dangerous misconception under the 2026 regime. Auto-renew off now routes an eligible CSP subscription onto the paid Extended Service Term rather than stopping billing. To actually stop paying you must set an explicit cancel-at-end-of-term instruction, which also ends service on the expiration date.
A renewal submitted less than 30 days after enrollment expiration can be backdated and any EPT invoice for that month is credited in full. Deals submitted to the ROC more than one month late are not eligible for an EPT invoice credit. The one-month mark is a hard cutoff in our experience, with no discretion.
EST (Extended Service Term) applies to CSP subscriptions and bills at the monthly rate plus 3%, or a flat 23% where no monthly SKU exists. EPT (Extended Period Term) applies to Enterprise Agreements, bills at published price plus a 3% admin fee for up to a year, and resets to Level A pricing annually, which can raise your per-unit cost above your EA volume discount.
No. EPT credits are only considered when you renew into another Enterprise enrollment. A program migration such as EA to CSP is not a renewal and is therefore ineligible for credit. If you also failed to file the opt-out form, you will pay EPT invoices with no recourse, which is the single most expensive slippage trap.
Yes. From 4 May 2026, EST subscriptions can be cancelled at any point during the month with a prorated refund credit, unlike a standard monthly NCE subscription which is locked after the first 7 days. You can also convert an EST to a standard subscription, which cancels the EST line, issues a prorated credit, and lets you adjust seats or SKUs on the new term.
An Extended Period Term monthly billing purchase order is marked with the tag EXT. Set a standing invoice review to flag any EXT line so you can act inside the one-month EPT credit window. Once you see EXT, your enrollment has already lapsed onto the extended-term rails.
Buyer side white paper on the Microsoft Enterprise Agreement renewal. Mix shift, Copilot ramp, Defender stacking, true up timing.
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.
