
Should a 30-person law firm use version history, the recycle bin or Restore this library when case files in SharePoint or Teams are overwritten or deleted?
Match the tool to the damage. An overwritten file with a good earlier version goes back through version history. A deleted file, folder or library comes back from the SharePoint recycle bin, as long as it's still inside the 93-day retention period that starts at deletion. Restore this library is for widespread deletion, overwrite or corruption in the last 30 days, and a site admin should run it, because it rolls back every later change too.
Three recovery tools for three different incidents
- File version history fits when one existing document has an unwanted edit and the library tracks versions, so a usable earlier version exists; avoid it when the file was deleted or when the damage spans many files at once.
- The SharePoint recycle bin fits when a file, folder or whole library was deleted and is still within its 93-day retention period; avoid it when you're counting on the second-stage bin to start a fresh 93 days, because the clock keeps running from the original deletion.
- Restore this library fits when a widespread deletion, overwrite or corruption hit an existing modern library within the last 30 days; avoid it when only one file is affected, when the library itself was deleted or when the incident is older than 30 days.

Recommendation: the smallest action that covers the damage
Start with the narrowest tool that fully covers the incident. One bad edit to a pleading draft is a version history job. A deleted matter folder is a recycle bin job. A library-wide rollback stays off the table until someone has confirmed the damage really is spread across many files, because a rollback also reverses the good work your team did after the incident started.
One condition flips that order. When dozens of files across several matters were overwritten, deleted or corrupted at once, say by a bad sync or a bulk delete, and the earliest damage is under 30 days old, Restore this library becomes the right first move. File-by-file recovery at that scale is slow and easy to get wrong, so a named site admin runs the library restore after the matter owners agree how later legitimate work will be put back.
Leaving recovery to whoever notices the problem first costs more than an afternoon. A missing matter file stalls work that's due against a filing deadline. A well-meant library rollback undoes legitimate edits on unrelated matters, which then have to be found and redone. And an emptied recycle bin, or a 93-day period that quietly runs out, turns a recoverable file into a permanent loss, since Microsoft states that deleted files can't be restored once they've been removed from the site collection recycle bin. Chrysis Networks helps firms put a named recovery owner and a backup layer behind SharePoint's built-in tools, so getting a case file back doesn't hinge on someone remembering a deadline buried in a help article.
How each recovery path actually behaves
Version history only helps if the library was set to track versions before the bad edit happened. Microsoft's guidance on restoring a previous version conditions the whole process on lists or libraries tracking versions. Restoring an earlier version deals with an unwanted change to a file that still exists; a deleted file has no version list to open, so version history isn't a recovery route for deletions.
SharePoint's recycle bin works in two stages. Microsoft states that for SharePoint the retention time is 93 days, and that it begins when you delete the item from its original location. Items moved on to the second-stage bin stay there for the remainder of those 93 days and are then permanently deleted, so the second stage is a last chance, not an extension. Users can restore from the site recycle bin; the second-stage bin usually needs the site administrator. If a whole library was deleted, restore the library first and then its files, because the files need somewhere to go back to.
Restore this library is a time-based rollback of an existing modern library. In Microsoft's words, the restore will undo all the actions that occurred on both files and folders in the last 30 days. The tool shows a list of activities, and when you select one, all other activities that occurred after it are selected automatically. Picking the earliest unwanted change therefore also reverses every later edit in that library, including legitimate work on other matters. Record any errors the restore writes to its RestoreLog, because those are the files you'll need to chase by hand.
Dates matter when you read these pages. Microsoft's documents, inspected on 16 November 2026, carry document dates of 24 March 2025 for Restore this library (updated 13 October 2026), 23 February 2026 for the recycle bin and 13 March 2026 for version history. Those are documentation dates for long-standing features, not release dates, and none of them promises that a particular file is still recoverable.
A safe incident sequence for a missing or overwritten matter file
- Prerequisites: a modern SharePoint document library (Teams files live in one), versioning switched on for that library, and a named site admin who can reach the second-stage recycle bin and run Restore this library.
- Pause edits to the affected files and tell the matter team, so new changes don't pile on top of the damage.
- Ask the matter owner to name the last known-good copy and the time of the earliest unwanted change.
- Classify the incident: overwrite or deletion, one file or many, and whether the library itself still exists.
- For a single overwritten file, open version history, confirm the earlier version is the right one with the matter owner, and restore it.
- For deleted items, check the site recycle bin first, then have the site admin check the second-stage bin; restore a deleted parent library before its files, and note how much of the 93 days is left.
- For widespread damage inside 30 days, list and copy aside the legitimate work done after the earliest unwanted change, then have the site admin run Restore this library from that change.
- Check a sample of recovered files against what the matter owner expects, and record any RestoreLog errors for follow-up.
- If native recovery doesn't cover the loss, because the bin was emptied or the incident falls outside the window, escalate to the firm's backup or support process without promising the file will come back.
Frequently asked
Does the SharePoint recycle bin cover files deleted in Teams?
Yes. Teams files are stored in SharePoint, and Microsoft's recycle bin guidance covers items deleted from SharePoint or Teams.
Does moving an item to the second-stage recycle bin reset the 93 days?
No. The 93 days start when the item is deleted from its original location, and it stays in the second stage only for whatever remains.
Can Restore this library bring back a library someone deleted?
No. Restore the deleted library from the recycle bin first; Restore this library rolls back an existing library.
Who should run a library restore?
A site admin, coordinated with the matter owners, because selecting one activity automatically selects every later one.
Are these built-in tools a backup?
No. They're native recovery features with time limits, and a file removed from the site collection recycle bin can't be restored through them.