When a Microsoft subscription lapses, your tenant data does not disappear on the expiry date, but it does start a fixed countdown to irreversible deletion. This page maps the disablement-then-deletion sequence, the exact day counts by contract vehicle, and the export moves you must complete before the window closes.
When a Microsoft subscription lapses, your tenant data does not disappear on the expiry date, but it does start a fixed countdown to irreversible deletion. This page maps the disablement-then-deletion sequence, the exact day counts by contract vehicle, and the export moves you must complete before the window closes.
The single most expensive misconception we see on the buyer side is that non-renewal is reversible for a long time. It is not. The moment a subscription expires or is terminated, Microsoft begins a defined retention-then-deletion sequence, and the outer boundary is hard. Per the Microsoft Trust Center, if you terminate or let a cloud subscription expire (except free trials), Microsoft stores your customer data in a limited-function account for 90 days so you can extract it or renew. Microsoft Service Assurance is blunter: no more than 180 days after a subscription ends, Microsoft disables the account and deletes all data, making it unrecoverable.
The 90+180 numbers describe the contractual data-retention envelope. Layered on top is a separate subscription lifecycle (Active, Expired, Disabled, Deleted) that governs administrative and user access. The two systems interlock but are not identical, and the day counts differ depending on whether you buy through Volume Licensing, CSP/NCE, or a Microsoft Customer Agreement (MCA). Getting these confused is what turns a routine renewal slip into a data-loss incident. If you are approaching a renewal decision, start with our 2026 buyer guide to the Extended Service Term and non-renewal for the commercial framing, then use this page for the data mechanics.
No more than 180 days after a subscription ends, Microsoft disables the account and deletes all data, making it unrecoverable. That boundary is not negotiable.
The contractual backbone sits in the Microsoft Products and Services Data Protection Addendum (DPA), April 2025 version. It codifies a two-stage structure. Stage one: Microsoft retains customer data in a limited-function account for 90 days after expiration or termination so the customer may extract it. Stage two: after that 90-day retention period ends, Microsoft disables the account and deletes customer data (including cached and backup copies) within an additional 90 days, unless retention is authorized under the DPA or required by law.
Two practical points follow. First, purging is gradual, not a single event. Microsoft's own Q&A guidance states the purge begins gradually after day 90 and completes beyond day 180. You should never plan around "the data is fine until day 180" because deletion for a given workload can begin at day 91. Second, the deletion-within-90-days commitment applies specifically to in-scope services as defined in the Data Processing Terms of the Product Terms. If a service is not in scope, that specific timing guarantee may not attach. Treat the 90-day extraction window as your working deadline and everything after it as unrecoverable risk.
| Stage | What it covers | Duration | Access during stage |
|---|---|---|---|
| Retention period | Data held in limited-function account for extraction | 90 days from expiry/termination | Admin can extract data |
| Deletion window | Account disabled, data (plus caches/backups) deleted | Up to 90 additional days | Access ending, purge in progress |
| Outer ceiling | Absolute deletion boundary | No more than 180 days total | None; data unrecoverable |
Running alongside the DPA retention clock is the subscription lifecycle that controls whether users and admins can sign in. Microsoft models four states: Active, Expired, Disabled, Deleted. If an admin does not renew before the end date, the subscription moves from Active to Expired, then to Disabled, then Deleted. The critical detail is that the day counts are flipped between standard/CSP subscriptions and Volume Licensing.
During the Disabled stage, user access is cut. Users cannot sign in or reach their data, but admins can still reach the admin center and, crucially, retain read and backup access to customer data. That admin-only window is your last practical extraction runway before deletion begins in earnest. Do not assume users will flag the loss for you; by the time helpdesk tickets arrive, you may already be inside the Disabled stage.
Everyone gets roughly 120 days of access before hard termination, but the split between Expired and Disabled is reversed for Volume Licensing versus CSP. Know which clock you are on.
The old model gave you a free grace period after expiry. That is gone. Per Microsoft's October 14, 2025 announcement (as summarized by Q-Advise), effective April 1, 2026 the free grace period for accessing services on non-renewed subscriptions is discontinued, with CSP enforcement following on May 4, 2026. In its place sits the Extended Service Term (EST): a paid, month-to-month continuation that applies when a subscription is neither renewed nor cancelled. For the full history of the transition, see our breakdown of the grace period elimination and what changed on April 1, 2026.
There are now three end-of-term paths on EST-eligible subscriptions: renew, cancel, or go to EST. The trap is the default behavior. EST activates automatically if auto-renew is off and no action is taken at term end. That means inaction no longer buys you a free buffer; it silently starts a paid month-to-month charge at the monthly rate plus a 3% uplift (or roughly 23% if the product has no monthly SKU). We size those numbers in what the Extended Service Term actually costs.
The one genuine buyer advantage in EST is cancellation flexibility. Unlike standard monthly-term subscriptions (which cannot be cancelled outside the first 7 days and bill the full month), EST can be cancelled at any point during the month with prorated daily billing. If you need licenses for ten more days to finish a migration, EST charges you for ten days, not thirty. That makes EST a legitimate short-term bridge tool, provided you actively cancel the moment extraction is complete. To keep it from firing by accident in the first place, read how to avoid triggering the Extended Service Term during renewal slippage.
This is where buyers get hurt. There are two ways to end an EST-eligible subscription, and they have very different data consequences. If you choose "Cancel at End of Term," the subscription ends on its expiration date and access is lost that same day. Per Microsoft Learn's Partner Center lifecycle documentation, this path sets the subscription to Disabled with no service, and it carries the standard data retention (the 90-day window still applies for extraction before deletion). It is a hard stop on access, not an instant purge, but it removes the Expired buffer entirely.
The far more dangerous action is explicit deletion of a subscription. Explicitly deleting skips the Expired and Disabled stages, and SharePoint and OneDrive data is deleted immediately. There is no gradual purge and no admin extraction window. We have seen tenants lose collaboration data because an admin "cleaned up" an unused subscription during a consolidation. Treat explicit subscription deletion as equivalent to hitting delete on the underlying data, because functionally it is.
| End-of-term action | Access loss | Data retention window | Reversibility |
|---|---|---|---|
| Renew / go to EST | None (paid continuation) | N/A while active | Fully active |
| Cancel at End of Term | Same day as expiry | 90-day retention still applies | Restore possible via new sub in window |
| Let Expired/Disabled run out | Gradual per lifecycle | ~120 days access, then deletion | Restore possible in window |
| Explicitly delete subscription | Immediate | None; SharePoint/OneDrive deleted at once | Not recoverable |
An expired NCE subscription has never been reactivatable. To restore service you must purchase a new subscription. The good news is that the data-retention lifecycle still runs underneath: data and license assignments are preserved through the Expired and Disabled states (up to roughly 120 days total). If you spin up a new subscription within that window, data and license assignments can be restored. Miss the window and the new subscription is a fresh, empty tenant.
Two structural changes tighten this further in 2026. As of February 9, 2026, the Expired lifecycle state no longer applies to license-based subscriptions bought directly through an MCA. And with the free grace period gone, the old comfort margin is narrower in practice. If your organization is moving vehicles, the risk of a service or data gap during transition is real; we cover the mechanics in migrating from EA to CSP without a service gap and, for reducing footprint at renewal, dropping SKUs at renewal without losing access mid-term.
There is no reactivate button. If the window closes, a new subscription gives you a fresh, empty tenant. Restore only works while data still exists in the retention lifecycle.
Based on 25 years of watching this vendor's lifecycle mechanics change (and the export tooling struggle to keep pace), here is the sequence we hand clients. In our experience, the practical extraction runway is far shorter than the headline 180 days, because admin access degrades during the Disabled stage and purge can begin at day 91. Work to a 90-day internal deadline, not 180.
Where does leverage sit for the buyer? Not in the deletion timeline itself, which is contractual and firm. It sits upstream, in avoiding the accidental EST trigger, in refusing marketing pressure to renew early "to protect your data," and in sequencing your migration so you exit cleanly. If Microsoft or a reseller frames data-loss risk as a reason to accept an uplift, that is a negotiation tactic, not a technical necessity: you control the export, and the retention window gives you the time. For how to turn that dynamic to your advantage, see using the Extended Service Term as negotiation leverage.
Microsoft retains data in a limited-function account for 90 days after expiry or termination for extraction, then deletes it within an additional 90 days. The absolute ceiling is 180 days, after which data is unrecoverable. Purging begins gradually after day 90, so treat 90 days as your real extraction deadline, not 180.
No. You cannot reactivate an expired NCE subscription; you must purchase a new one. However, if you buy a new subscription while the data is still within the retention lifecycle (up to roughly 120 days of access states), data and license assignments can be restored. Miss the window and the new subscription is empty.
Letting it expire runs the lifecycle (Expired, then Disabled) and preserves the 90-day retention window for extraction. Explicitly deleting a subscription skips those stages, and SharePoint and OneDrive data is deleted immediately with no admin extraction window. Never explicitly delete to save money.
EST replaces the free grace period as of the April 1, 2026 announcement (CSP enforcement May 4, 2026). It is a paid continuation, so while active your data stays live. If you Cancel at End of Term, the standard 90-day retention still applies, but access is lost the same day with no Expired buffer.
The 90+90 retention structure is the same, but the lifecycle access split is flipped. Volume Licensing gives 90 days Expired then 30 days Disabled; standard and CSP give roughly 30 days Expired then 90 days Disabled. Both total about 120 days of access before hard termination.
Retention that is authorized or required by law can override the standard deletion, per the DPA. But you must configure the hold before disablement removes your admin access. Reconcile all legal holds at the start of the non-renewal process, not after the subscription has expired.
The 12 month buyer side framework we use with Fortune 500 clients to cut the standard Microsoft EA uplift. Reduce, restructure, replace.
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.
