SharePoint Mass Deletion: What Protects You for Free, What Costs Extra, and What Prevents It

Recovery is included and prevention is not. SharePoint Online keeps deleted items for 93 days, a library can be rolled back 30 days, and version history undoes overwrites. A Microsoft Purview retention policy goes further: it keeps a copy of every deleted or edited file for as long as the policy says, so a deletion can never become a loss, and it is included in Microsoft 365 Business Premium, E3 and E5. Microsoft 365 Backup and third-party backup make a mass restore fast. None of those stop the user's hand. The only layer that does is design: permission levels without the delete right, split libraries, sync limits and an alert that fires while the deletion is still in progress.

The recycle bin. Microsoft's data deletion page for SharePoint in Microsoft 365 states the rule: a deleted item stays in the site recycle bin for 93 days from the moment it was deleted. If a user empties the first-stage bin, the item moves to the site collection recycle bin, which only site collection administrators see, for the remainder of the same 93 days. The clock does not restart. When the second-stage bin runs out of room it purges its oldest items, and the period cannot be lengthened. This is what saved the files in our case, and it is why "my files are gone" is usually a 10-minute conversation and not an incident.

Version history. Protects against overwrites, not deletions. Microsoft's version history limits page describes two modes: automatic limits, which keep up to 500 versions created in the last 30 days and then thin older versions by age, and manual limits, where the administrator sets the count. Organization-level changes apply to new libraries only, so a tenant that changed its default still has older libraries on the old setting.

Restore this library. Under a document library's Settings menu, Microsoft Support's "Restore a shared library" page describes rolling the entire library back to any point in the last 30 days, undoing every file and folder action after that point. It is a library-wide operation, it is not offered on classic libraries, and it needs the person running it to hold enough permission on the library.

Deleted sites. A deleted site sits in the SharePoint admin center for 93 days before it is permanently removed, per Microsoft's "Restore deleted sites" page.

The limits of layer 1 are the ones that worry an owner: it is recovery, not prevention; 93 days is a hard ceiling; restoring tens of thousands of items from the recycle bin is slow and manual; and anything an administrator empties from the second-stage bin is gone.

A Microsoft Purview retention policy on SharePoint sites and OneDrive accounts changes what delete means. Microsoft's "Learn about retention for SharePoint and OneDrive" page describes the mechanism: when a user deletes or edits content that a retention policy or label covers, the original is copied to a hidden Preservation Hold library on the same site and kept there for the retention period. The user still sees the file disappear, work continues, and nothing leaves the tenant until the policy expires. An administrator recovers it from the hold library or through eDiscovery at any time inside that period.

Three consequences follow. The retained copies count against the site's storage quota, so a policy of several years on a busy site needs storage planning; Microsoft's retention overview says so directly. The hidden library is not to be edited, moved or cleaned out by hand; Microsoft states that this is unsupported. And the policy does not stop the user's action, so the files still vanish from the normal view until someone restores them.

Licensing is more generous than most people expect. Microsoft's Purview service description lists retention policies as supported with Microsoft 365 Business Premium, E3 and E5 and the Office 365 equivalents, with SharePoint Plan 2 covering SharePoint and OneDrive locations. What needs E5-level licensing is the automation on top: applying retention labels automatically by content, and adaptive policy scopes. A firm with a regulatory or legal-hold duty gets that covered by the same policy.

Microsoft 365 Backup is Microsoft's own backup service, switched on in the Microsoft 365 admin center and billed pay-as-you-go to an Azure subscription. Microsoft's pricing page for the service gives a list price of $0.15 per GB per month of protected content, with restores free. Its overview page sets out what that buys for SharePoint and OneDrive: restore points every 10 minutes for the previous two weeks and weekly snapshots back to 52 weeks, a one-year retention period, backup data held in append-only storage that the service itself cannot alter, and a 90-day grace period to recover from backups after a site is removed from protection. Purview retention and deletion policies do not touch the backup retention period.

Granularity is the detail that matters for a mass deletion. Backup protects whole SharePoint sites and OneDrive accounts, and a full site restore to the same URL from one of the recommended express restore points is the fast path. Folder and file restore for SharePoint and OneDrive is listed in public preview as of December 2025 on the overview page, so a single file no longer forces a whole-site rollback.

The limits: it is still recovery, not prevention; the monthly cost scales with the size of what you protect; and one year is the ceiling. For a firm whose sites are a few hundred gigabytes, the monthly figure is small next to an afternoon of manual restores. For a tenant with terabytes of archive, protect the sites that change rather than everything.

Veeam, AvePoint and similar products back up SharePoint, OneDrive, Exchange and Teams to storage you control. The case for them is retention beyond a year, item-level restore across the whole estate, and a copy that lives outside Microsoft, which some insurers and auditors ask for in so many words. The case against is a per-user license, another vendor and another console to patch and watch, and restores that run through an API rather than Microsoft's internal snapshot, which for a very large restore is the slower path. If you already own one of these for Exchange, extend it to SharePoint before buying anything new.

Everything above makes an accident cheaper. These four make it rarer, and they cost design time rather than money.

Permission levels without the delete right. Most mass deletions happen because everyone has Edit on everything. The standard Contribute and Edit levels both include deleting items, so handing out Contribute does not help. SharePoint lets a site owner copy a permission level and clear "Delete Items" and "Delete Versions" from the copy; give that level to people who add and edit documents but should never remove them, and Read to people who only consume. Split the one enormous library into several, so that no single person's rights reach every file.

Friction on critical libraries. Required check-out and content approval slow bulk operations to a crawl, which is exactly what you want on a library of signed contracts.

Sync limits. A very common cause of "thousands of files deleted" is someone deleting a synced folder on their laptop, which syncs the deletion to SharePoint. For large or sensitive libraries, disable offline sync in the library's advanced settings, restrict the OneDrive sync client to managed devices in the SharePoint admin center, and keep Files On-Demand on so a laptop cleanup does not become a library cleanup.

An alert that fires during the deletion. Microsoft's alert policies page lists a default policy for an unusual volume of file deletion among the built-in alerts managed in the Microsoft Defender portal. Microsoft's own answers on the policy say the built-in version requires an E5-level subscription; other plans can create a custom alert policy on the file-deleted activity with a threshold that suits them. Either way the administrator hears about a bulk deletion within minutes, while the files are still in the first-stage recycle bin and before anyone opens a ticket.

1. Turn on a retention policy for the SharePoint sites that hold client work. It is included in Business Premium and the enterprise plans, and from that day a deletion can never become a loss.
2. Add Microsoft 365 Backup for the sites that matter most, so a repeat is a 10-minute restore instead of an afternoon. Work out the protected gigabytes first; the price is per GB per month of what you protect, not of the whole tenant.
3. Fix the permission model and the sync settings on the largest libraries, and switch on a deletion alert, so the accident is less likely and you hear about it immediately.

A retention policy and a backup together cover the two different failures: the file somebody deleted on purpose and regretted a year later, and the site that has to be whole again by nine o'clock tomorrow.

Does a retention policy stop a user from deleting files?

No. The user still deletes the file from their view. The policy keeps the original in the hidden Preservation Hold library for the retention period, where an administrator can recover it. Prevention comes from permission levels, not from retention.

Is the recycle bin a backup?

It is a 93-day safety net for deletions, not a backup. It does not protect against overwrites, it purges early when the second-stage bin fills, and an administrator can empty it. Microsoft 365 Backup and third-party backup are the backup layers.

Can Microsoft 365 Backup restore a single file?

The overview page lists folder and file restore for SharePoint and OneDrive in public preview as of December 2025. The fully supported path is a whole-site or whole-account restore to a point in time, and for a site under about a terabyte that path runs in well under an hour from an express restore point.

Which Microsoft 365 plans include retention policies?

Microsoft's Purview service description lists Business Premium, E3, E5 and the Office 365 equivalents, with SharePoint Plan 2 covering SharePoint and OneDrive locations. Automatic labeling by content needs E5-level licensing.

Does version history help after a mass deletion?

Not directly; it restores earlier versions of a file that still exists. Deleted files come back from the recycle bin or from a library restore, and the versions return with them.