SharePoint in Microsoft 365 uses a site Recycle Bin and a second-stage site collection Recycle Bin. Recover from the web site that owned the document, because the Windows Recycle Bin and a synced folder show only part of the deletion trail.
Fast route: Open the SharePoint site, select Recycle bin, choose the item, and select Restore. If it is absent, a site collection administrator should check the second-stage bin.
1. Identify the site and library
- Capture the old SharePoint URL from browser history, Teams, email, or a shortcut.
- Confirm the tenant, site, document library, and folder.
- Record the filename and deletion time.
- Note who deleted or last edited it.
- Check whether a parent folder or library was also deleted.
Searching the wrong team site is a common failure. A familiar filename in another library does not preserve the original permissions, links, metadata, or version history.
2. Restore from the site Recycle Bin
- Open the SharePoint site.
- Select Recycle bin in the site navigation.
- If it is hidden, use Site contents or site settings to reach it.
- Select the files, folders, list items, or libraries.
- Choose Restore.
- Return to the original location and inspect the result.
Users with edit permissions can restore eligible items, including items deleted by other people. Microsoft states that restoration returns content to the location from which it was deleted.
3. Check the second-stage Recycle Bin
When someone deletes an item from the site Recycle Bin or empties it, the item moves to the site collection Recycle Bin for the remaining retention period.
- Open the site Recycle Bin.
- Select Second-stage recycle bin at the bottom.
- Locate the item by name and deletion information.
- Select it and choose Restore.
- Ask a site collection administrator if the second stage is unavailable.
Administrator or owner permissions are required for this stage. Its presence is not a new retention window.
4. Understand the 93-day clock
Microsoft documents a 93-day retention period for SharePoint in Microsoft 365. The count starts when the item is deleted from its original location. Moving from the first stage to the second stage does not restart the count.
Items can disappear earlier if an authorized administrator permanently deletes them or recycle-bin quota behavior purges older content. Contact IT promptly rather than planning around the final day.
5. Restore parents before dependent items
SharePoint cannot always restore a child version or item when its parent no longer exists. If a library was deleted, restore the library before attempting its individual files. If a deleted folder contained the file, SharePoint may recreate that folder when restoring the item, but verify the resulting hierarchy.
When a file with the same name already exists at the original path, SharePoint can append a number to the restored filename. Search for numbered variants before concluding the restore failed.
6. Escalate content absent from both bins
Provide the Microsoft 365 administrator with:
- tenant and site URL;
- library and folder path;
- filename or item ID;
- approximate deletion time and time zone;
- deleting account, if known;
- whether either bin was emptied;
- whether a retention or legal-hold policy applies.
Microsoft documents an additional limited support backup window for SharePoint Online after actual deletion, but restores from those backups apply to site collections rather than individual files. The administrator should assess that option; it is not a user-level file restore.
7. Verify the restored SharePoint record
- Open the item from the web library.
- Confirm the folder and filename.
- Inspect metadata columns and content type.
- Open version history.
- Test sharing and inherited permissions.
- Check links, shortcuts, workflows, and dependent files.
Microsoft says a restored file includes the versions it contained when deleted. Verify this explicitly, especially when the recovery target was an earlier draft.
Select the proper recovery scope
| Incident | Best tool | Avoid |
|---|---|---|
| One file deleted recently | Site Recycle Bin | Whole-library rollback |
| First-stage bin was emptied | Second-stage bin | Waiting near day 93 |
| Parent library was deleted | Restore parent first | Restoring child version first |
| Existing file has wrong content | Version history | Deletion recovery |
| Many files changed or vanished | Restore this library | Ignoring valid later work |
| Both bins are empty | Administrator escalation | Promising item-level backup restore |
Prevent the next incident
Keep versioning enabled, limit permanent-delete privileges, and document site ownership. For high-value libraries, test retention and backup procedures before an incident. A synced local folder is convenient access, not an independent backup; deletions can synchronize across devices.