
Enterprise guide to SharePoint file recovery covering first-stage and second-stage recycle bins, PowerShell restoration, versioning, retention policies, and prevention strategies.
How do you recover deleted files in SharePoint? Navigate to the Recycle Bin from the site's left navigation, select the deleted file(s), and click Restore. Files return to their original location with metadata and version history intact. If the file was removed from the first-stage recycle bin, check the second-stage recycle bin (Site Collection Recycle Bin) accessible to site collection admins. SharePoint retains deleted items for 93 days total across both stages. For bulk recovery, use PnP PowerShell: Get-PnPRecycleBinItem | Restore-PnPRecycleBinItem -Force.
File deletion in SharePoint is inevitable in any enterprise environment. Users accidentally delete documents, sync conflicts remove files, departing employees clean up their libraries, and automated processes occasionally misconfigure cleanup rules. The question is not whether files will be deleted — it is how quickly and completely you can recover them.
SharePoint provides multiple layers of file protection: recycle bins, versioning, retention policies, and the Preservation Hold Library. Understanding how these layers interact — and their limitations — is critical for any organization that relies on SharePoint for document management. A misconfigured retention policy can silently allow critical files to be permanently deleted, while a properly configured environment makes accidental data loss virtually impossible to cause permanent harm.
This guide covers every recovery mechanism available in SharePoint Online and SharePoint Server as of 2026, with enterprise-specific strategies used by EPC Group's SharePoint consulting team across Fortune 500 deployments in healthcare, financial services, and government.
SharePoint uses a two-stage recycle bin system that provides 93 days of recovery time. Understanding both stages is essential for enterprise IT teams.
The end-user recycle bin. Items land here immediately after deletion. Accessible to the user who deleted the item and anyone with site member permissions.
Recovery steps: Site Contents → Recycle Bin → Select item(s) → Click Restore. Files return to their original library with all metadata and version history preserved.
The site collection recycle bin (admin recycle bin). Items arrive here after being deleted from the first-stage bin. Only site collection administrators can access it.
Recovery steps: Site Settings → Recycle Bin → Second-Stage Recycle Bin → Select item(s) → Click Restore. Items return to their original location.
Understanding the 93-day retention clock is critical. The clock starts at deletion, not when the item moves between recycle bin stages.
User deletes a file from a document library. File moves to the first-stage recycle bin immediately. The 93-day retention clock starts.
File is visible in the site recycle bin. Any site member can restore it. File retains all metadata, permissions, version history, and its original location path.
If a user or admin empties the first-stage recycle bin, items move to the second-stage bin. They remain there for the remainder of the original 93 days.
After 93 total days from the original deletion, the item is permanently removed from both recycle bins. Standard SharePoint recovery is no longer possible.
Contact Microsoft support within 14 days of permanent purge. Microsoft may be able to restore from internal backups, but this is not guaranteed and depends on their backup schedule.
PowerShell is essential for enterprise-scale recovery. When hundreds or thousands of files need restoration, the browser interface is impractical.
# Using PnP PowerShell (recommended) Install-Module PnP.PowerShell -Scope CurrentUser Connect-PnPOnline -Url https://tenant.sharepoint.com/sites/sitename -Interactive
PnP PowerShell provides the most comprehensive recycle bin cmdlets. Use -Interactive for modern authentication with MFA support.
# List all first-stage recycle bin items Get-PnPRecycleBinItem | Select Title, DeletedByEmail, DeletedDate, ItemType, Size # List second-stage items only Get-PnPRecycleBinItem -SecondStage
Review deleted items before restoring. Filter by date, user, or file type to target specific recovery needs.
# Restore a single item by ID
Restore-PnPRecycleBinItem -Identity "item-guid-here"
# Restore items deleted in the last 7 days
Get-PnPRecycleBinItem | Where-Object {
$_.DeletedDate -gt (Get-Date).AddDays(-7)
} | Restore-PnPRecycleBinItem -ForceUse -Force to skip confirmation prompts during bulk operations. Always test with a small batch first.
# Restore all items deleted by a specific user
Get-PnPRecycleBinItem | Where-Object {
$_.DeletedByEmail -eq "user@company.com"
} | Restore-PnPRecycleBinItem -Force
# Restore all .docx files from recycle bin
Get-PnPRecycleBinItem | Where-Object {
$_.Title -like "*.docx"
} | Restore-PnPRecycleBinItem -ForceCombine filters for precise recovery. Common in ransomware scenarios where you need to restore specific file types deleted in a time window.
# Restore a deleted site collection Restore-SPODeletedSite -Identity "https://tenant.sharepoint.com/sites/deletedsite" # List all deleted site collections Get-SPODeletedSite | Select Url, DeletionTime, SiteId
Requires SharePoint Online Management Shell and Global Admin or SharePoint Admin role. Sites restore with all content, permissions, and settings.
The recycle bin recovers deleted files. Versioning recovers overwritten content. Together they cover the two most common data loss scenarios.
Every time a file is saved, SharePoint stores the previous version. Restore any prior version to recover from accidental overwrites, ransomware encryption, or sync conflicts. Open Version History from the file context menu and click Restore on the desired version.
Set major version limits per library (recommended: 100 for most libraries, 500 for critical content). Without limits, version history grows unbounded, consuming storage quota. SharePoint Online default is 500 major versions — review and adjust per library based on content type and change frequency.
Ransomware encrypts files in-place, creating new versions. Version history preserves the clean pre-encryption versions. Restore files to versions created before the attack timestamp. For OneDrive, Microsoft provides a one-click "Restore your OneDrive" feature that rolls back to any point in the last 30 days.
Major versions (1.0, 2.0) are published and visible to all users. Minor versions (1.1, 1.2) are drafts visible only to editors. Use major-only for most libraries. Enable minor versions only for publishing scenarios requiring draft/publish workflows.
Each version is a full copy of the file (not differential). A 10 MB file with 100 versions consumes up to 1 GB of storage. SharePoint applies shredded storage optimization to reduce this, but version limits remain important for storage management.
Version history serves as an audit trail showing who modified the file and when. For compliance-heavy industries (healthcare, finance), version history provides evidence of document changes required by regulators. Combine with Microsoft Purview audit logs for complete tracking.
Retention policies and the recycle bin serve different purposes. Understanding the distinction is critical for compliance in regulated industries.
| Feature | Recycle Bin | Retention Policy |
|---|---|---|
| Purpose | User recovery of deleted items | Compliance preservation |
| Visibility | Visible to users/admins | Hidden (Preservation Hold Library) |
| Maximum Duration | 93 days | Unlimited (configurable) |
| Can Users Delete? | Yes (moves to next stage) | No (preserved regardless) |
| Covers Modifications? | No (only deletions) | Yes (preserves original on edit) |
| Configuration | Automatic (no setup needed) | Microsoft Purview portal |
| Scope | Per site collection | Org-wide, site, or label-based |
| Cost | Included in SharePoint | Requires E3+ or compliance add-on |
EPC Group recommendation: Every enterprise should implement retention policies in addition to relying on the recycle bin. For HIPAA compliance, set 6-year retention. For financial services (SEC/FINRA), set 7-year retention. The recycle bin alone is insufficient for any regulated industry.
Microsoft's shared responsibility model means you own your data protection. Native tools provide 93 days of recovery — third-party solutions extend this to years.
Market leader for Microsoft 365 backup. Backs up SharePoint, OneDrive, Exchange, and Teams. Granular restore down to individual items, lists, and metadata. Supports on-premises and cloud storage targets. Unlimited retention with your own storage.
SaaS-based backup built specifically for Microsoft 365. Automated daily backups with point-in-time restore. Includes SharePoint, OneDrive, Exchange, Teams, Groups, and Power Platform. Granular comparison view shows what changed between backup points.
Enterprise-grade backup with advanced eDiscovery integration. Supports hybrid SharePoint environments (Online + Server). Deduplication and compression reduce storage costs. Integrates with existing enterprise backup infrastructure.
Microsoft native backup solution announced in 2024. Provides fast restore at scale for SharePoint, OneDrive, and Exchange. Currently in preview — enterprise adoption should wait for GA and proven reliability. Will not replace third-party solutions for complex requirements.
Native protection has limits: 93-day recycle bin, no protection against admin deletion of retention policies, no air-gapped backup, limited granular restore options. Third-party solutions provide independent backup copies, longer retention, ransomware protection, and compliance evidence for auditors.
Follow the 3-2-1 rule: 3 copies of data, 2 different storage media, 1 offsite copy. Test restores quarterly. Document recovery procedures. Encrypt backups at rest and in transit. Retain backups longer than your longest regulatory requirement. Monitor backup job success rates daily.
The best recovery strategy is preventing accidental deletion in the first place. These enterprise controls dramatically reduce data loss incidents.
By default, SharePoint Members have delete permissions. For critical document libraries, create a custom permission level that removes delete rights. Only site owners and designated content managers should have delete access on libraries containing business-critical documents.
Use Microsoft Purview retention labels to mark critical documents as records or apply "Do Not Delete" policies. Labeled content cannot be permanently deleted until the retention period expires, even by site collection admins. Auto-apply labels based on content type or sensitivity for consistent protection.
Configure Microsoft Purview audit logging to track all deletion events. Set up alerts for bulk deletion (more than 50 files in an hour) which may indicate ransomware or accidental cleanup. Audit logs provide forensic evidence of who deleted what, when, and from where.
Data Loss Prevention policies can block deletion of files containing sensitive information (PII, PHI, financial data). DLP scans file content and applies policy tips warning users before deletion. This is particularly important for HIPAA and PCI-DSS compliance.
Train users on the difference between deleting and archiving. Provide clear archive procedures so users do not delete files they think are no longer needed. Communicate recycle bin capabilities so users know they can self-service recover within 93 days.
Use Power Automate to create flows that trigger on deletion events in critical libraries. Send immediate notifications to library owners when files are deleted. For high-value document libraries, require approval before deletion is processed.
Real-world recovery situations and the exact steps to resolve each one.
EPC Group has recovered petabytes of enterprise data across healthcare, financial services, and government organizations. From recycle bin optimization to full disaster recovery architecture, we ensure your SharePoint environment is resilient and compliant.
To recover deleted files in SharePoint: 1) Navigate to the site where the file was deleted, 2) Click the Recycle Bin link in the left navigation (or go to Site Contents > Recycle Bin), 3) Select the file(s) you want to restore, 4) Click Restore. The file returns to its original location with all metadata, permissions, and version history intact. If the file is not in the first-stage recycle bin, check the second-stage recycle bin (accessible by site collection admins). Files remain in the first-stage recycle bin for 93 days, then move to second-stage for the remainder of the 93-day window. After 93 total days, contact Microsoft support within 14 days for potential recovery.
The first-stage recycle bin (also called the end-user recycle bin) is accessible to the user who deleted the item and site members. Items stay here for 93 days or until manually emptied. When an item is deleted from the first-stage recycle bin (or the bin is emptied), it moves to the second-stage recycle bin (also called the site collection recycle bin). The second-stage recycle bin is accessible only to site collection administrators. Items remain in the second-stage bin for the remainder of the original 93-day retention period. For example, if a file sat in the first-stage bin for 30 days before being deleted, it stays in the second-stage bin for 63 more days.
SharePoint Online retains deleted items for a total of 93 days across both recycle bin stages combined. The 93-day clock starts when the item is first deleted from the site. If the item is manually deleted from the first-stage recycle bin, it moves to the second-stage bin for the remainder of the 93 days. After 93 days, the item is permanently purged from both recycle bins. Important: this 93-day period applies to SharePoint Online. SharePoint Server on-premises has configurable retention periods set by the farm administrator, typically defaulting to 30 days for first-stage.
If the second-stage recycle bin has been emptied or the 93-day retention has expired, standard admin recovery is not possible through the SharePoint interface. However, there are options: 1) Contact Microsoft Support within 14 days of the 93-day expiration — Microsoft may be able to restore from their internal backups, 2) If you have Microsoft 365 Retention Policies configured, the content may be preserved in the Preservation Hold Library even after recycle bin deletion, 3) Third-party backup solutions (Veeam, AvePoint, Commvault) maintain independent backups with longer retention. For enterprise environments, EPC Group always recommends implementing at least one of these additional recovery layers.
Use the SharePoint Online Management Shell or PnP PowerShell for bulk recovery. With PnP PowerShell: Connect-PnPOnline -Url https://tenant.sharepoint.com/sites/sitename -Interactive. To list deleted items: Get-PnPRecycleBinItem. To restore a specific item: Restore-PnPRecycleBinItem -Identity <ItemId>. To restore all items: Get-PnPRecycleBinItem | Restore-PnPRecycleBinItem -Force. For second-stage items: Get-PnPRecycleBinItem -SecondStage | Restore-PnPRecycleBinItem -Force. For filtering by date: Get-PnPRecycleBinItem | Where-Object { $_.DeletedDate -gt (Get-Date).AddDays(-7) } | Restore-PnPRecycleBinItem -Force. PowerShell is essential for recovering hundreds or thousands of items that would be impractical to restore manually through the browser.
The recycle bin is a user-facing recovery mechanism — items move there when deleted and stay for 93 days. Retention policies (configured in Microsoft Purview) are compliance-driven preservation mechanisms that operate silently in the background. Key differences: 1) Recycle bin is visible to users; retention policies are invisible, 2) Recycle bin has a 93-day limit; retention policies can preserve content for years, 3) Recycle bin items can be permanently deleted by admins; retained items cannot be permanently deleted until the retention period expires, 4) Retention policies use the Preservation Hold Library (hidden) to keep copies of modified or deleted content. For regulated industries like healthcare and finance, retention policies are mandatory — the recycle bin alone is insufficient for compliance.
SharePoint versioning provides recovery for overwritten content (not just deleted files). When enabled, SharePoint keeps previous versions each time a file is modified. Recovery steps: Open the document library, click the three dots next to the file, select Version History, then click Restore on the desired version. Key settings: Major versions only (recommended for most libraries) or Major + Minor versions (for publishing scenarios). Set a version limit (e.g., 50-100 versions) to control storage. Versioning is your first line of defense against accidental overwrites, ransomware encryption, and sync conflicts. EPC Group recommends enabling versioning on every document library with a 100-version major version limit as the enterprise baseline.
Prevention strategies for enterprise SharePoint environments: 1) Unique permissions — restrict delete permissions to site owners, not all members, 2) Approval workflows — require approval before permanent deletion of critical documents, 3) Information management policies — auto-classify sensitive content as records (records cannot be deleted), 4) Retention labels — apply "Do Not Delete" labels to critical business documents, 5) Alerts — configure email alerts on document libraries for deletion events, 6) Audit logging — enable Microsoft Purview audit log to track who deleted what and when, 7) Training — educate users on the difference between deleting and archiving, 8) Sensitivity labels — DLP policies can prevent deletion of classified content. EPC Group implements layered prevention strategies for enterprise clients to reduce the need for recovery.
Yes. Deleted SharePoint sites go to the SharePoint admin center deleted sites collection. Site collection admins or global admins can restore them within 93 days: Go to SharePoint Admin Center > Active Sites > Deleted Sites, select the site, and click Restore. The site is restored with all content, subsites, permissions, and settings. For Microsoft 365 Group-connected sites, the associated group and its resources (mailbox, Planner, Teams) are also restored when the site is restored. After 93 days, the site is permanently deleted. PowerShell alternative: Restore-SPODeletedSite -Identity https://tenant.sharepoint.com/sites/deletedsite.
EPC Group implements a multi-layered SharePoint disaster recovery strategy: 1) Native protection — ensure recycle bin, versioning, and retention policies are properly configured across all site collections, 2) Retention policy design — create Microsoft Purview retention policies aligned with industry regulations (HIPAA requires 6-year retention, financial services often requires 7 years), 3) Third-party backup — deploy Veeam, AvePoint, or Commvault for independent backup with granular restore capabilities and longer retention, 4) Recovery runbooks — documented step-by-step procedures for common recovery scenarios (single file, bulk files, entire site, ransomware recovery), 5) Regular testing — quarterly recovery drills to validate backup integrity and train IT staff, 6) Monitoring — automated alerts for unusual deletion patterns that may indicate ransomware or insider threats. Our SharePoint consultants have recovered petabytes of enterprise data across healthcare, financial services, and government organizations.