Search the Preservation Hold Library
Find files kept under retention
When a file under a retention policy or hold is edited or deleted, SharePoint keeps a copy in the site's Preservation Hold Library. SharePoint's search does not look in that library, so its own search box finds nothing even when the word is right there in a column. This reads every file in the library and searches all of their details as you type.
What does it tell you?
- Whether a deleted or changed file was kept, and where it used to live.
- When SharePoint preserved it and who last modified it.
- What the copy is called inside the library, which is usually not its original name.
- Why it is still there: Why is this still here? goes through each thing that can keep a copy - Microsoft's 30 days, the file's retention label, retention policies on the site, eDiscovery case holds, records and disposition review - and says which one keeps it and until when, or that nothing does and when Microsoft should remove it.
How it runs
- Sign in and choose a site. One site, or paste its address.
- Wait for the read. A large library takes a while. Stop keeps what has been read.
- Search. Every word must appear somewhere: name, original location, dates, people or any other column. Quotes keep a phrase together.
- Take what you need. Tick the files you want, or use Select all matches. Download the ticked files or every match into a folder - each lands in folders matching where it came from, with an Excel report beside them - or get an Excel report of all matches without downloading.
- Ask why it is still here. Select one file, tick several, or leave nothing ticked for every match, then Why is this still here?. The first time, it asks whether to check retention policies and eDiscovery case holds too: those live in the compliance centre, so a PowerShell window may ask you to sign in once. Each reason shows ✓ (not keeping it), ✗ (keeping it, until when) or ? (can't tell, and why). Copy as text for a reply, or an Excel report with each file's answer.
How does it work?
It first checks whether the site has a Preservation Hold Library at all. A site where SharePoint answers that there is none is reported that way; a site that could not be checked is reported as an error, never as having no library. Then every row of the library is read once, with a running count on screen.
Searching, sorting and ticking work on that copy in memory and send nothing to SharePoint, which is why it finds text SharePoint's own search does not: SharePoint leaves this library out of its index. A search looks in every column shown, the copy's name and path inside the library, and every other column SharePoint returned. If the read is stopped or fails part-way, the page says so and searches only what was read.
Downloads run one file at a time. Each file is saved under its original name, in folders that recreate where it came from; when the same document was preserved more than once, later copies get the preservation date added to the name. Nothing already on disk is overwritten: each file is written under a temporary name and renamed only once complete, and it is given the copy's Modified date where possible. A file too large to download from here is listed as skipped, a failed file is listed with its reason and the run carries on, and an Excel report is written beside the files.
Nothing in the library is changed, by a search or by a download.
Why is this still here? reads the site's own published retention labels and its time zone once, and, if you agree, the compliance centre's retention policies, labels and eDiscovery case holds once per visit. Each file is then answered on this computer. Anything that could not be read becomes "can't tell", never "nothing keeping it", and the answer changes nothing.
What do you need?
- Access to the site's Preservation Hold Library. Site collection administrators always have it.
- For retention policies and case holds: the Compliance Administrator role (or View-Only Retention Management), and an eDiscovery role for case holds. Without them those reasons say "can't tell" - never "none".
What will it not do?
- Nothing in the library is changed. SharePoint manages it and refuses edits while a hold applies.
- Files up to 250 MB download from here. Copy the library address to open a larger one in SharePoint.
- A site that has never had a preserved file has no Preservation Hold Library, and the page says so.
- The search covers every match; the screen shows the first 2,000 and Export to Excel writes all of them.
- After a policy or hold is released Microsoft keeps its content 30 more days, and that can't be seen from here, so a copy with nothing keeping it may still take that long. Microsoft's clean-up then runs about every 7 days and moves expired copies to the second-stage recycle bin for 93 days.
- A policy scoped by an adaptive scope, or an event-based label, can't be worked out from here: those show as "can't tell".
- Dates for created- or modified-based policies are the latest they can end, because the original file is usually gone.
Microsoft's own documentation
- Learn about retention for SharePoint and OneDrive: When SharePoint creates the Preservation Hold Library, what is copied into it, and when copies are removed.
- Learn about retention policies and retention labels: What wins when several settings apply, and the 30 days after a policy is released.