In almost every Microsoft 365 project I run, someone eventually asks what happens to the OneDrive of departed users, and the answer is rarely as simple as people expect. When a user is deleted or disabled in Entra ID, their OneDrive doesn't just disappear. A clearly defined retention clock starts instead. In my experience, few admins or business teams really understand how this works or which delegation happens automatically. Getting the offboarding sequence right can spare you a lot of trouble and lost data, and it can even save money.

OneDrive starts a retention clock as soon as the user account is deleted

Once a user account is deleted, the OneDrive is unlinked from the user and the retention period you set in SharePoint admin center → Settings → OneDrive retention takes effect. By default, OneDrive content is kept for 30 days. Storage is still consumed during that time. The user's manager, as specified in Entra ID, automatically gets access (read, and edit if configured). For knowledge transfer or for pulling documents from a former employee, that access is extremely helpful. You can extend retention to as much as 10 years, but keep in mind that this is not a real archive. It only delays the final deletion.

After the retention window closes, the content is permanently deleted, though you still have another 93 days to restore files from the SharePoint recycle bin. I've seen this extra window rescue situations where the wrong account was purged or someone noticed too late that important data was still needed. Microsoft describes the process in detail in SharePoint and OneDrive retention and deletion, and the Purview retention documentation covers the wider policy scenarios.

Purview policies and the new archiving rule can override OneDrive retention

Many organizations I work with add global Microsoft 365 (Purview) retention policies on top. Those policies can override the technical OneDrive retention and keep content longer whenever a broader SharePoint/OneDrive policy applies. For compliance they are often unavoidable. The downside is that they can leave behind abandoned accounts and gigabytes of orphaned data nobody needs. That clutters the tenant and, in the worst case, becomes a compliance risk of its own.

There is one more thing to watch. In 2025, Microsoft announced that unlicensed OneDrive accounts are now archived automatically after 93 days and then either deleted or kept (and billed) if a specific setting is turned on. The idea is to clean up unused storage and make costs more transparent. In practice this only works if offboarding is handled carefully. Otherwise you end up with lost data or unexpected license charges. Details are in Unlicensed OneDrive accounts.

Manager delegation hands over access but can break in practice

On paper, "manager delegation" is straightforward. After the user is deleted, whoever is listed as their manager in Entra ID gets access to the OneDrive. Usually that works. It fails when the manager field was empty or wrong before deletion, or when HR offboards the user before the reporting lines are updated. And sometimes a project team or department needs access, not just the manager. For that reason I always recommend checking the delegation during offboarding and granting extra access manually where needed.

# PowerShell 7, SharePoint Online Management Shell, Role: SharePoint Administrator
Set-SPOSite -Identity "https://tenant-my.sharepoint.com/personal/firstname_lastname_domain_com" -LockState "NoAccess"

This command blocks access immediately, which helps with strict offboarding or when sensitive data is involved.

Practical tip: Check that delegation is in place before you remove the license or delete the account. If you don't, managers or colleagues may end up hunting for a way into files they urgently need.

Offboarding works best when the steps follow a fixed order

With departed users, a clean offboarding comes down to the right sequence and clear responsibilities. This is the order that has worked for me:

  1. Move key mail items to a shared mailbox (convert if necessary)
  2. Review OneDrive content and ensure the manager or team gets access
  3. Remove the Microsoft 365 license
  4. Delete or disable the user account, double-check OneDrive retention
  5. Confirm that delegation and retention settings are actually working

In larger organizations you should automate as much of this as you can with Entra ID lifecycle workflows. I've described my own setup in Lifecycle Workflows in Entra ID: automation in practice. Inactive accounts shouldn't pile up in your tenant either, and Inactive accounts Entra ID: Year-end cleanup in practice has practical advice on that.

This diagram shows the OneDrive lifecycle after offboarding

The following diagram outlines the OneDrive retention process for departed users:

flowchart TD
  Account["User account deleted"] --> ODStart["OneDrive retention starts"]
  ODStart --> Manager["Automatic manager delegation"]
  ODStart --> Period["Retention period (30 days–10 years)"]
  Period --> Recycle["Recycle bin (93 days)"]
  Recycle --> FinalDelete["Permanent deletion"]
  Manager --> Access["Data access / handover"]

Figure: OneDrive retention timeline after an employee leaves.

A documented process matters more than any single feature

For OneDrive and departed users, the technical controls are only as good as the offboarding process you have written down. Default retention is a safety net. Without clear ownership, defined handover steps and a regular look at your policies, you'll end up with either a data graveyard or compliance problems. Purview policies help on the legal and compliance side, but you still need to check what is actually accumulating in your tenant. Manager delegation is useful, yet it doesn't replace a proper exit process run by people. Microsoft gives you the tools, and your process decides whether they work.