"It's not in the recycle bin" is what people say when they have looked in their recycle bin, on one site, for a file that was deleted by someone else, from a different folder, possibly last quarter. Most of the time the file still exists. Here are the five places, in the order that finds it fastest.
1. The bin you can't see: another user's deletions
The site recycle bin is personal unless you are a site collection administrator. A normal member sees only what they deleted themselves. If a colleague deleted the file, it is in the bin, just not in their view of it.
Fix: have a site collection admin open Site contents → Recycle bin. Admins see everything. Sort by Deleted by to find the culprit quickly.
2. The second-stage (site collection) recycle bin
When something is deleted from the site recycle bin, by a user emptying it, by a script, or by an over-eager tidy-up, it drops into the second-stage bin. Same 93-day budget, different page.
Site collection admins: Site contents → Recycle bin → Second-stage recycle bin (link at the bottom). In PowerShell:
Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/Finance -Interactive
Get-PnPRecycleBinItem -SecondStage | Where-Object LeafName -like '*Q3 forecast*'
3. The wrong site
Recycle bins belong to site collections. A file that lived in a Teams channel's private-channel site, a hub-associated site, or a subsite that became its own site during a migration is in that site's bin. The user's mental model is "the SharePoint recycle bin"; there is no such thing.
Fix: from the file's original URL, everything up to /sites/<name>/ is the site collection. Open that site's bin.
4. The Preservation Hold Library
If the site is under a Microsoft Purview retention policy, deleting a file does not remove it. A copy goes to the hidden Preservation Hold Library, which is neither recycle bin. It is also why storage sometimes refuses to go down after a clean-up.
Fix: site collection admins can open https://<site>/PreservationHoldLibrary/Forms/AllItems.aspx directly. Files there can be copied back. Compliance admins can also run a content search.
5. Past 93 days: Microsoft's own backup
Both recycle bins share one clock: 93 days from the original deletion. After that the item is purged. Microsoft keeps its own backups for a further 14 days, but a restore from those is a site-collection-level rollback done by Microsoft support, not a single-file recovery, and it overwrites everything in that site collection with the backup state.
So if you are at day 95: open a support request today, and understand that the answer may be "we can roll the whole site back to day 92" rather than "here is your file".
When it is really gone
- Someone emptied both recycle bins (a site collection admin can, and some clean-up scripts do).
- The 93 days and the 14 days have both passed.
- The site itself was deleted more than 93 days ago (deleted sites have their own 93-day window in the SharePoint admin centre).
At that point the honest answer is a backup product or the copy on someone's laptop.
Doing this without the tour
Every one of the five places is a different page, a different permission, and a different way of searching. If you are the person people come to, a recycle-bin search that covers both stages in one view, filters by name, date and deleted by, and shows what a site collection admin would see, turns this from a twenty-minute tour into one search. That is what Undelete365 is; the search part is free.