A deleted user's OneDrive is retained for 30 days by default; administrators specify the retention period in the SharePoint admin center.
Key takeaways
- Confirm your retention setting before planning around the default.
- Record the deletion or directory removal date.
- Identify shared files and the people who depend on them.
- Assign a decision owner and an early deadline.
Files are easy to overlook because nothing visibly breaks on the day the account is removed. A retention clock starts quietly in the background and runs out on its own schedule. This post covers that clock and what partners and operations leads can do while it is still running.
Everything here comes from one Microsoft page, Restore a deleted OneDrive - SharePoint in Microsoft 365. Its rules apply to OneDrive in Microsoft 365. They are not a description of other storage products, and they are not a promise about every organization. Your settings may differ from the default, so check the value in your environment before you plan around it.
How long is the retention period by default?
The page states it plainly: "The default is 30 days." That sentence points readers to a separate article, Set the default file retention for deleted OneDrive users, so the number is a setting with its own documentation.
Treat 30 days as a starting point for planning, not a fact about your account. The page's main rule is that the OneDrive is kept for the number of days an administrator specifies, and that number may not be 30. Check the value your administrators set, and write down the date you checked it. A number you read in a document last year is not the same as one you confirmed this week.
What starts the retention clock?
Deleting the user in the Microsoft 365 admin center starts it. Removing the user through Active Directory synchronization starts it too. The page's exact sentence is: "When you delete a user in the Microsoft 365 admin center (or when a user is removed through Active Directory synchronization), the user's OneDrive is retained for the number of days you specify in the SharePoint admin center."
If your staff accounts come from a directory that syncs to Microsoft 365, ask the person who runs that sync how a departure reaches Microsoft 365 and when it happens. That tells you which date to count from. Do not guess the date from the day an employee gave notice or the day their final paycheck was issued. Those dates may matter to your HR process, but the quoted rule ties retention only to the deletion or removal of the user.
When you write your procedure, name the trigger in plain words, such as "the account was deleted in the admin center on this date" or "the account was removed by directory sync on this date." A note that says only "account closed" gives the next person nothing to count from.
Where do you check the retention number?
Check the number in the SharePoint admin center. The value your administrators chose governs a departed user in your environment, whatever the default says.
Record the value in your offboarding procedure, with the date you checked it and the name of the person who checked it. Because administrators specify the number, a dated note tells the next person whether the value was current when you looked. Keep the note with your other offboarding records so it is found when it is needed.
If your organization uses more than one tenant or more than one administrator, confirm the value for each one. The quoted rule describes the setting in the SharePoint admin center for the environment where you delete or remove the user. Check each environment separately.
How do you find the departed user's username?
You can find the username on the Active users page or the Deleted users page in the Microsoft 365 admin center. The page puts it this way: "You can find their username on the Active users (or Deleted users) page in the Microsoft 365 admin center." If the user is not on one list, check the other.
Put the username in your offboarding record early, so anyone who picks up the task later has it without searching. A name in an email signature or a folder label may not match the account that holds the files. Confirm the username in the admin center rather than relying on memory or a spreadsheet.
How do you restore the account inside the window?
For the restore steps, the page points to its Restore a user in Microsoft 365 article. The page says, "To learn how, see Restore a user in Microsoft 365." Read that article before you need it, rather than relying on memory. A restore is easier to finish calmly when the steps are already read and you know who on your team can do the work.
The 30-day limit changes the route, as the next section explains. So a practical deadline for any restore decision is earlier than the 30-day mark, not on it. Give your team a date that leaves time for a second attempt if the first one does not work. A deadline on the last day leaves no room for that.
Keep the restore decision separate from the question of what happens to the files afterward. Whether to restore a OneDrive, who should own its contents, how long they should be kept, and where they should live are different decisions. Put them on separate lines of your record so one is not mistaken for another. For related recovery work, see the guide to workpaper recovery.
What happens after 30 days?
After more than 30 days, the user no longer appears in the Microsoft 365 admin center, and PowerShell is needed to restore the OneDrive. The page says, "If you deleted the user more than 30 days ago, the user will no longer appear in the Microsoft 365 admin center, and you need to use PowerShell to restore the OneDrive."
For planning, choose an internal deadline before the 30-day mark and make sure the team knows that date. Keep this restore-route milestone separate from the retention period your administrator confirmed.
The page's PowerShell route begins with this line: "Connect to SharePoint as a SharePoint Administrator in Microsoft 365." Find out now who would do that work, and confirm that person can sign in as a SharePoint Administrator and has the tools they need. Do not wait until the files are needed to discover that the person cannot sign in, or that nobody on the team has ever run the commands.
If more than 30 days have passed before the restore is finished, plan around the PowerShell route the page describes. Do not promise partners a restore on the admin center timeline. Tell them what you can confirm and when you expect to confirm the rest.
For questions about file availability after your retention period, read the full Microsoft page and ask Microsoft support before the date arrives. Get the answer from the source, in writing, and add it to your record.
Do other people still get access during the window?
Yes, according to the page: "During this time, other users can still access shared content." This matters most for partners. Files a departed person shared with a colleague or outside partner may still be in use while the retention period runs, and those people can still reach them.
A plan that moves, renames, or ends those files without checking who relies on them can disrupt people who are still working. Before you change anything, list what the departed person shared and with whom. Use the list to find the people who depend on the files, not just the people who own them.
Tell those people the date your plan takes effect, in plain words, so they can move their own work before then. A short message is enough: what is changing, the date, and who to contact with a question. A surprise gap in the middle of a project takes far longer to fix than the message takes to write.
Why the date matters most
The date is the one fact every other decision depends on. You cannot decide whether to restore, whom to ask, or how much time to give a partner without knowing when the retention period ends. Counting files or folders tells you how much work there is, but not when it has to be finished. Start with the date, then size the work to fit inside it.
A common planning mistake is to schedule everything from the last day of work. If the departure and deletion dates differ in your process, write both down, and note which one started the clock.
When the date is clear, the rest becomes a sequence rather than a scramble. Confirm the trigger, confirm the value, identify the people who depend on the files, decide, and record. Each step can be checked by someone other than the person who did it.
Who should decide what happens to the files?
One named person should make the decision, after asking the departed person's manager which files still matter. A decision with no owner has nobody to chase it when a deadline is running. Pick the person before the deadline, and make sure they know they are the decision owner.
Give that person a short list of questions for each file or folder. Is the content still needed for ongoing work? Is it shared outside the organization? Does a partner or customer depend on it? Does your records policy require keeping it, and for how long? Write the answers down, even briefly.
Once the answers are in, choose one outcome for each group of files: keep the content with the department, hand it to a named successor, archive it where the team can find it, or set it to be removed. Record each choice with the date and the name of the approver. Records matter most for removed files, because the reason is easy to forget.
Do not permanently remove anything while questions are open. If a file's status is unclear, treat it as needed until someone confirms otherwise. Removing a file a partner still uses can damage that relationship, and no later apology undoes it.
When the decision is made, tell the affected partners what was decided. "The files are being handled" gives them nothing to act on. "This folder moves to this person on this date" does.
Build a simple timeline
Start the timeline on the day you confirm the deletion or removal, and count forward using the confirmed retention value. Write the dates on the offboarding ticket, not in someone's memory, so everyone involved can read them, including whoever takes over later.
Order the milestones by need. Confirm the trigger first, then the retention value, then the username and the list of shared content. Send the partner message early enough that they can respond. Set the decision date with room before the 30-day mark for any restore or PowerShell work. Set a final review date to confirm each action was completed. Have someone other than the person who did the work check each milestone, since a second look catches date and value mistakes.
Illustrative example: an early decision date
Suppose you confirm a 30-day retention setting and record the deletion date. For this illustrative plan, choose a decision deadline 10 days after deletion. The decision owner checks which shared folders are still needed and records their next owner. This leaves time before the retention period ends; it does not change the setting.
What belongs on your checklist?
Use this checklist for each departed user with a OneDrive, and keep the dated record with the ticket. For the wider departure process, use the guide to retention clocks when staff leave.
- Confirm the departure date and whether the user was deleted in the Microsoft 365 admin center or removed through Active Directory synchronization.
- Check the retention value in the SharePoint admin center, and record the date you checked it.
- Record the username from the Active users page or the Deleted users page.
- List what the departed user shared and with whom, and tell those people the date your plan takes effect.
- Name the decision owner, and set an internal deadline before the 30-day mark.
- If a restore is needed, follow the Restore a user in Microsoft 365 article before the admin center stops showing the user.
- If more than 30 days have passed, plan for PowerShell and a sign-in as a SharePoint Administrator, and read the full Microsoft page on what happens to the files.
- Record each decision, who made it, and when.
Today, open the offboarding ticket for a departed user and add the confirmed retention value, deletion or removal date, and decision owner's name. Ask that person to set the decision deadline.
What should you ask the manager?
Ask the manager which files still matter, before your decision deadline rather than after it. The manager may know which projects were in flight and which colleagues relied on the departed person's work. Ask people who use the files to help establish their business value.
Keep the conversation short. Ask for the names of folders still in use, the people outside the team who depend on them, and any deadlines in the coming months. Ask the manager to confirm the list in writing, even in a one-line email, so the decision owner has something to point to later.
What if the answers are uncertain?
Mark uncertain items as needed and ask the owner of that work to confirm. A manager may call a folder "probably old" without knowing whether a partner opens it each month. Leaving a question open is safer than closing it on a guess.
What if the manager is unavailable?
If the manager is unavailable or the answers arrive too late, say so in the record. Name the person who took over the decision, the date it was handed over, and the questions still open. An honest gap is more useful to the next person than a confident answer nobody can trace.