Microsoft eliminated the free 30-day grace period and replaced it with a paid Extended Service Term that a lapsed subscription now enters by default. This guide maps the exact mechanics and the operational discipline you need so a slow migration or a missed renewal date never puts you on the penalty path.
Microsoft eliminated the free 30-day grace period and replaced it with a paid Extended Service Term that a lapsed subscription now enters by default. This guide maps the exact mechanics and the operational discipline you need so a slow migration or a missed renewal date never puts you on the penalty path.
For as long as most Microsoft buyers can remember, letting a Cloud Solution Provider (CSP) subscription lapse carried a soft landing. When a subscription expired, it dropped into a free grace period lasting roughly 30 days. Users kept working, admins kept their data, and the finance team had breathing room to sort out the paperwork. That cushion is gone. Microsoft announced the change on 14 October 2025 in its notice titled "New extended service term for Cloud Solution Provider (CSP) subscriptions," and the practical effect is simple: the free 30-day service window has been eliminated, and an expired subscription now drops into a paid Extended Service Term (EST) the moment its term ends.
The original effective date was 1 April 2026. Microsoft then postponed active enforcement to 4 May 2026, but do not misread the postponement as a reprieve. EST eligibility begins for qualifying subscriptions expiring on or after 1 April 2026; Microsoft simply began actively enforcing the billing on 4 May 2026. If your renewal cycle straddles those dates, you are already inside the new regime and should treat it as fully live.
The reason this matters to a buyer is money and data, in that order. The old grace period was a free buffer against administrative slippage. Under the new model, that same slippage bills at list price plus an administrative fee, and if you ignore it long enough the subscription is disabled and the data is deleted. This is a classic vendor move: take a free feature that quietly protected buyers from their own process gaps, and convert it into a metered revenue line with a penalty tail. In 25 years of watching Microsoft monetize the edges of its commerce model, this is one of the cleaner examples. Our companion piece on what changed on April 1, 2026 walks through the timeline in more detail.
The free grace period was insurance against your own administrative slippage. Microsoft has now converted that insurance into a metered bill with a deletion clause at the end.
When a CSP subscription reaches the end of its term, Microsoft's new policy presents three paths. Understanding all three, and knowing which one is the default, is the single most important thing an admin can carry out of this guide.
Here is the trap. If no choice is made in advance and auto-renew is switched off, Microsoft's new default is to move the subscription into EST automatically once it expires. This is the operational failure mode we expect to hit the most buyers. A subscription you intended to drop, or one whose renewal paperwork simply stalled, silently begins billing at a premium. As one partner platform put it bluntly on enforcement day: if you manage a CSP portfolio and have not reviewed your subscriptions, some of them entered EST that day, and you are being billed for a term you did not choose.
The asymmetry here is deliberate. "Cancel" requires an affirmative decision and punishes you with immediate loss of access. "EST" is the passive default and punishes you with a premium bill. There is no passive path that costs you nothing. The buyer discipline is therefore to make an explicit decision on every subscription before its anniversary, never to let the default decide. We cover the mechanics of doing this cleanly in our guide to avoiding the Extended Service Term during renewal slippage.
EST is not a flat penalty. It is a month-to-month continuation at a defined uplift, and the size of that uplift depends on whether the product has a monthly term SKU. Get this wrong in a budget model and you will materially understate the cost of a lapse.
| Scenario | Billing basis | Uplift | Effective premium vs annual |
|---|---|---|---|
| Product has a monthly term SKU | Monthly term rate | +3% administrative fee | Roughly +23% over annual (monthly is already ~+20% over annual) |
| Product has NO monthly term SKU | Annual/base rate | +23% surcharge | +23% over the base rate |
| EST duration ceiling | Month to month | Up to 12 months | N/A |
| Cancellation flexibility | Prorated | Cancel any time in month | Better than a locked monthly term |
Read the two layers carefully, because the vendor documentation and the partner commentary describe the same number from different angles. Microsoft's Partner Center documentation states EST is billed at the monthly term rate plus a 3% uplift. Where a product has a monthly SKU, you first pay the monthly premium (roughly 20% more than annual for the same seats) and then the 3% administrative fee on top. Where a product has no monthly SKU, the uplift is a flat 23% surcharge instead. Either way, EST is meaningfully more expensive than simply renewing on an annual term.
There is one genuine upside to EST relative to a standard monthly term subscription, and it is worth knowing when you are stuck. A monthly term subscription cannot be cancelled outside the first 7 days after purchase or renewal, which means you are on the hook for the full month. EST, by contrast, can be cancelled at any point during the month with prorated billing. So if you are unavoidably in EST while a migration completes, you at least retain the ability to exit mid-month once the new subscription is live. That is a small consolation, not a strategy. Our detailed breakdown of what the Extended Service Term actually costs models the specific SKU-by-SKU math.
EST is not a flat penalty. It stacks a 3% administrative fee on top of an already 20% monthly premium, or applies a flat 23% surcharge where no monthly SKU exists.
EST is not indefinite. Microsoft's Lifecycle and Extended Period Term documentation confirms the subscription bills monthly at the current published price for the enrolled affiliate's price level, plus the 3% administrative fee, for up to one year. When that 12-month ceiling is reached, or when you actively cancel, the disablement and deletion sequence begins. This is where the real risk sits, because it ends in permanent data loss.
The sequence works like this. When a subscription is cancelled or its EST ceiling expires, the seats move into a disabled state. That disabled period is typically 90 days, though Microsoft notes it might vary between offers. When the disabled period expires, the commerce portal moves the seats from disabled to deprovisioned, and deprovisioned means the user data is deleted. Microsoft's own Trust Center language frames the retention side of this: after a subscription expires or is terminated, customer data is stored in a limited-function account for 90 days, after which the account is disabled and the data is deleted, with deletion occurring within 90 days after the end of the retention period.
| State | Duration | What happens to users | What happens to data |
|---|---|---|---|
| Active / EST | Up to 12 months | Full access continues (at EST rate) | Fully intact |
| Disabled | Typically ~90 days | Access removed | Retained, recoverable if you buy a new subscription in-window |
| Deprovisioned | After disabled period ends | No access | Permanently deleted |
Two practical points sharpen this. First, the normal data retention lifecycle preserves data through the expired and disabled states, often cited as up to 120 days in total before deletion, and if you spin up a new subscription during that window, data and license assignments can be restored. That recovery window is your safety net, but it is finite and you should never plan to rely on it. Second, and this catches people out, you have never been able to reactivate an expired NCE subscription. You must purchase a new one. Restoration means new commercial terms, potentially new pricing, and the administrative work of reassigning licenses, not a simple resurrection of the old contract.
For any workload holding data you cannot afford to lose (mailboxes, OneDrive content, SharePoint sites, Teams history), map the deletion clock explicitly before you let anything lapse. Our companion piece on the data deletion timeline after non-renewal lays out the full 12-month clock and the restore mechanics so you can build a defensible retention plan rather than gambling on the recovery window.
Scope determines whether you need to worry at all, so pin it down for each of your agreements before doing anything else.
The scoping exercise is not academic. If your estate is a mix of grandfathered legacy subscriptions, newer NCE annual terms, and a handful of monthly SKUs, the EST risk is uneven across it. Build a subscription-level inventory that flags the purchase date, term type, expiry date, and auto-renew status of every line. That inventory is the single artifact that will keep you off the penalty path, and it is cheap to build relative to a surprise EST bill.
The most common way a buyer will accidentally trigger EST is not a deliberate cancellation. It is slippage. A renewal that needs sign-off from a manager on vacation. A purchase order stuck in procurement. A partner waiting on a signed order form. Under the old regime, a week of slippage cost nothing because the grace period absorbed it. Under EST, every day of slippage past the anniversary is billed at the premium rate, and the default behavior actively enrolls you.
The engineering answer is to remove the anniversary as a point of failure. There are three levers, and you should use all of them where the workload is staying:
There is a nuance worth stating plainly. Turning auto-renew off does not by itself trigger EST at the moment you toggle it. EST fires at expiration. But an auto-renew-off subscription that reaches its anniversary with no decision is exactly the case Microsoft's default rule captures. So the safe posture is: auto-renew on unless you have an active, documented plan to reduce or exit, and even then, a firm exit date before the anniversary. Our full playbook on avoiding the Extended Service Term during renewal slippage gives you the exact cadence and the escalation triggers.
Auto-renew on for anything you are keeping. That single toggle renews at the standard term rate and shuts off the EST default. Reserve auto-renew off for subscriptions you are actively exiting.
Partial non-renewal is where EST and the broader NCE seat rules collide, and it is easy to get wrong. Two constraints matter. First, on NCE annual terms, seat reductions are blocked mid-term. Outside the first 72 hours after renewal, seats can only be dropped at the next term renewal. Second, if you try to force a reduction by letting the oversized subscription lapse and re-buying a smaller one, you have just walked the whole subscription into EST or an immediate cancellation, depending on the path you take.
The clean approach to dropping SKUs is to plan the reduction to land exactly at the term boundary. Do not let the current subscription expire into EST. Instead, arrange the smaller replacement (or the reduced seat count) to take effect at renewal, so there is no gap and no lapse. Where you are dropping a SKU entirely rather than just reducing seats, the sequence is to stand up whatever replacement or coexistence arrangement you need before the anniversary, then either renew the reduced set or let the specific SKU cancel cleanly at term end with the retirement decided in advance.
The mistake we see is treating a seat reduction as an emergency and letting a subscription lapse to force the issue. That converts a routine renewal-time reduction into an EST event with a premium bill and a deletion clock. If you are planning any downsizing this cycle, model it against the term boundary first. Our guide to dropping Microsoft SKUs at renewal without losing access mid-term covers the sequencing in detail.
Changing your commercial vehicle (moving between partners, moving from EA to CSP, or changing regions) is the highest-risk moment for accidentally triggering EST, because it is precisely when subscriptions are most likely to lapse in the seams. There is also a genuine conflict in Microsoft's own guidance here that you need to understand before you plan a move.
One line of Microsoft guidance (from Microsoft Q&A, 4 May 2026) states that when moving between partners or regions, licenses cannot be transferred mid-term, and the supported approach is to leave existing subscriptions active until their natural end date and align the purchase of new subscriptions with the local partner at or just before expiry. Another line of Microsoft guidance (the Partner Center "Transfer NCE subscriptions" documentation, 8 May 2026) describes a live mid-term CSP-to-CSP transfer capability where the source partner is financially responsible up to the point of transfer and the target partner is responsible for the remainder of the term. Both are Microsoft-published and they appear to contradict each other.
The reconciliation is about the type of move. Mid-term peer-to-peer (P2P) transfers exist, but they are CSP to CSP only. The transfer feature does not support transferring Direct Bill (web direct) subscriptions to CSP partners. And it does not resolve region changes or EA-to-CSP moves, which are new-subscription events, not transfers. So the "align at natural expiry" guidance is the correct mental model for vehicle changes, while the P2P transfer is the correct mechanism for a straightforward CSP-partner swap where both sides are CSP.
| Move type | Supported mechanism | EST risk if mishandled |
|---|---|---|
| CSP partner A to CSP partner B | Mid-term P2P transfer | Low if transfer completes; source pays to transfer point, target pays remainder |
| Direct Bill (web direct) to CSP | No transfer supported; new subscription at expiry | High if old lapses before new is live |
| EA / MCA to CSP | New subscription aligned at expiry | High; classic gap scenario |
| Region change | New subscription aligned at expiry | High; treat as a lapse-and-repurchase |
If you are doing a CSP-to-CSP swap, use the P2P transfer and mind the timing. Transfer requests that are not acted on expire after 30 days, and transfers take up to 72 hours to complete. Initiate the request with enough runway that a 72-hour completion window plus any approval lag lands well before the anniversary, not after it. If you are doing any other kind of move, treat it as a lapse-and-repurchase and use the golden rule: keep the outgoing subscription active until its natural end date, and light up the incoming subscription at or just before that date so there is zero gap. For EA-to-CSP specifically, our guide to migrating from EA to CSP without a service gap in 2026 maps the sequencing step by step. The broader vehicle decision is covered in our Microsoft EA vs MCA renewal guide.
You cannot plan EST in isolation this year, because a separate cost event lands in the same window. Microsoft's price increases effective 1 July 2026 range from 5% to 43% depending on SKU. Microsoft 365 E5 is up 5%; M365 E3 and Office 365 E5 are up 8%; Office 365 E3 is up 13%; Business Basic and Standard are up 12% to 16%; and Frontline F1/F3 are up 25% to 43%. The increase applies globally to new and renewing customers effective 1 July 2026, and existing customers move to the new prices at their next renewal after that date.
Here is why this matters for EST. EST bills at the current published price for your price level. If you drift into EST after 1 July 2026, you are paying the increased list price plus the 3% administrative fee, which compounds the penalty. The frontline SKUs are the sharp edge: a 43% increase followed by a 3% EST fee turns a lapsed F3 subscription into a genuinely expensive mistake.
There is also a renewal-timing lever worth naming. Because existing customers move to new prices at their next renewal after 1 July 2026, a renewal completed before that date locks the pre-increase price for the term. That interacts directly with EST discipline: a slipped renewal that crosses 1 July does not just risk EST, it also forfeits the chance to lock the lower price. We treat the two events together in our 2026 Microsoft price increase preparation guide, and if you want hands-on help sequencing renewals around both, our Microsoft EA negotiation services team runs this analysis routinely.
Drift into EST after July 1, 2026 and you pay the increased list price plus the 3% fee. On a Frontline SKU up 43%, an accidental lapse becomes one of the most expensive administrative errors in the estate.
EST is primarily a risk to manage, but it also has a modest leverage dimension that experienced negotiators can use. The leverage is not against Microsoft directly; it is against the clock and against your own partner. Understanding that distinction keeps you from overplaying a weak hand.
Where EST helps you: it gives you a defined, bounded bridge (up to 12 months) to complete a migration off a Microsoft workload without an abrupt loss of access. If you are genuinely leaving a product, EST buys time at a known cost with the ability to cancel mid-month once the replacement is live. In a migration plan, that predictability is worth something, and it is better than the old grace period's hard 30-day cliff for buyers who need a longer runway. Based on our negotiation experience, framing a partner conversation around a planned, cost-capped EST bridge (rather than an emergency) tends to produce more cooperative sequencing on the partner side.
Where it backfires: EST is a terrible "threat." You cannot credibly threaten to let a subscription lapse into EST as a negotiating tactic, because the person absorbing the premium bill and the deletion risk is you, not Microsoft. Any leverage from EST is entirely about your own preparedness, not about applying pressure. If you go into a renewal implying you might just let it lapse, the sophisticated counterparty knows that path costs you more than it costs them. Our analysis of using the Extended Service Term as negotiation leverage (and when it backfires) works through the specific scenarios where the bridge framing helps and where it undermines you.
Translate all of the above into a concrete sequence. This is the checklist we would hand a licensing manager inheriting a CSP estate under the new rules.
Done consistently, this discipline reduces EST from a lurking penalty to a non-event. The entire policy change is designed to convert your process gaps into Microsoft revenue. The countermeasure is process, and process is cheap. If your estate is large enough that manual reconciliation is unrealistic, or you are facing a complex vehicle change on top of the July increase, this is exactly the kind of work our independent, buyer-side advisory carries out day to day.
EST eligibility begins for qualifying subscriptions expiring on or after 1 April 2026, but Microsoft postponed active enforcement to 4 May 2026. If your renewal cycle straddles those dates, treat the new regime as fully live. The old free 30-day grace period no longer applies to in-scope subscriptions.
EST bills month to month at the monthly term rate plus a 3% administrative fee. Because monthly terms already run roughly 20% above annual, the effective premium is around 23% over annual pricing. Where a product has no monthly SKU, a flat 23% surcharge applies to the base rate instead. After 1 July 2026 this stacks on top of the new increased list prices.
EST runs for up to 12 months. When the ceiling is reached or you cancel, seats move to a disabled state (typically about 90 days), and then to deprovisioned, at which point the data is deleted. You can restore data and license assignments by purchasing a new subscription during the disabled window, but you cannot reactivate the expired subscription itself.
Yes. If auto-renew is off and you make no decision before the term ends, Microsoft's default is to move the subscription into EST automatically and begin billing at the premium rate. Turning auto-renew on for workloads you intend to keep is the simplest way to avoid this trap, because auto-renew renews at the standard term rate, not the EST rate.
Subscriptions purchased before 1 April 2025 are not impacted. GCC-High licensing, which is sold under AOS-G rather than CSP/NCE, is also excluded. EST does apply to commercial and public sector subscriptions, including education, nonprofit, and standard GCC.
For a CSP-to-CSP move, use a mid-term P2P transfer, allowing for the 72-hour completion window and the 30-day request expiry. For Direct Bill to CSP, EA to CSP, or region changes, there is no transfer; treat them as new-subscription events. The safe rule is to keep the outgoing subscription active to its natural end date and light up the replacement at or just before that date so there is no gap.
Microsoft 365 E5 rises to 60 dollars on July 1, 2026. A buyer side response plan: overlap analysis, the E7 math, renewal timing levers, five recommendations.
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.
