What gets deleted when legal says delete
A search built to find 33 items came back with 1.27 million. That’s 2.4 TB, and the purge was the next step. Here’s what an eDiscovery purge actually trusts, and what to check before anyone presses delete.
The number
2.4 TB.
That’s what a deletion search returned when it was run one more time before the purge. The search had been written to find 33 items. On the re-run it matched 1.27 million.
Nobody did anything malicious. Nobody fat-fingered a button. The search definition was scoped wrong, and nothing in the process was built to notice. If the purge had gone ahead on that search, it would have been pointed at 1.27 million items instead of 33.

What was on the table
Here’s how deletion requests usually work in a Microsoft 365 tenant.
A client, their legal team or HR asks for something specific to be removed. In this case it was the client. Someone builds a search in Microsoft Purview to find it. That search becomes the contract between what was asked for and what actually gets deleted. Then the purge runs against whatever the search finds.
That’s the weak spot. The person who asked for the deletion never sees the search. The person who runs the purge trusts it. And a search definition doesn’t announce when it stops meaning what you think it means.
What we did instead
I was the director at the managed services firm doing the work. The search was re-run before purging, and the count came back: 33 had become 1.27 million.
The engineers’ first direction didn’t go deep enough. It treated the bad count as something to work around, not as proof the search couldn’t be trusted. I pulled it back.
Then we did the part that feels slower. We didn’t repair the broken definition. We found the scoping fault, built a clean replacement from scratch, re-verified that it returned what was actually requested, and only then ran the purge. It completed with zero errors.
Once a search has lied to you, you can’t prove what else is wrong with it. A clean search with a known scope is something you can defend later. A patched one is a guess.
What should have been asked
Deletion is the one IT job where “it looked right” isn’t good enough, because the mistake is the outcome.
Is the count the control? Before any purge, someone writes down how many items the search returns and checks it against what was asked for. If the number moves, the work stops.
Is purge even the right tool? Microsoft built search-and-purge for incidents like phishing messages or data spillage, not for general mailbox management, and it removes at most 10 items per mailbox per run (100 with premium features).1,2 If your deletion process involves very large numbers, the process needs a second look.
Do you know what’s on hold? Search-and-purge isn’t supported on a mailbox under litigation hold.1 If nobody knows which mailboxes are on hold, nobody knows what a purge will actually do.
Could you prove it? If a court, a regulator or a client asks what you deleted and what you kept, “we ran a search” isn’t an answer. The request, the search, the count and the result should all be written down.
Where this came from, and what my stake is. I was the director of a managed services firm when this happened. The client isn’t named and won’t be. Today I sell managed IT and compliance through Cybertitans. If your honest answer to the questions below is “we’d have to check,” that’s the kind of work I get paid for. The questions work without me.
Ten questions to ask before anyone presses delete
- Who in your company can permanently delete email or files across everyone’s mailbox today?
- When legal, HR or a client asks for a deletion, who writes the search, and who runs the purge? Is it the same person?
- Does anyone write down the result count before the purge runs?
- If the count changes between the draft and the purge, does the work stop?
- Is there a record of what was asked for, what was found and what was deleted?
- Do you know which mailboxes are under a legal hold right now?
- Could you prove to a court what you kept and what you didn’t?
- Who holds the eDiscovery admin roles, and when did anyone last review that list?
- Is your retention policy written down, and does your tenant actually enforce it?
- If a deletion went wrong last year, would you know?
Does this sound like something happening in your organization?
If more than two of those made you pause, that’s the conversation. No pitch.
This is the work: knowing what your tenant will actually do before anyone presses the button, and being accountable for it after.
Book 20 Minutes- Microsoft Learn, search for and delete email messages in eDiscovery. Purge is intended for event response, not general mailbox management; up to 10 items per location (100 with premium features); not supported on mailboxes under litigation hold. Search for and delete email messages
- Microsoft Learn, limits in eDiscovery, purge limits table. Limits in eDiscovery
