How Do You Back Up SharePoint Online?

What Is SharePoint Backup?

SharePoint backup is the process of copying SharePoint sites, document libraries, lists, versions, permissions, and metadata to separate storage on a schedule, so any of it can be restored to a point in time.

Backing up SharePoint matters as much as backing up any other Microsoft 365 service. SharePoint holds your organization’s documents, and it also stores the files behind every Microsoft Teams team and channel.

Why Does SharePoint Backup Matter?

Microsoft runs resilient infrastructure and handles recovery from its own platform failures. What it can’t protect you from is what happens inside your tenant:

• A user deletes a document library, and nobody notices until the Recycle Bin window has passed.
• A bulk move or migration goes wrong and strips metadata from hundreds of files.
• Ransomware encrypts files on a synced laptop, and the encrypted versions sync to SharePoint, overwriting clean content across an entire library.

None of these are infrastructure failures, and native tools handle them poorly once enough time has passed. Ransomware is the biggest risk: the Verizon 2026 Data Breach Investigations Report found ransomware in 48% of breaches.

How Does the Shared Responsibility Model Apply to SharePoint?

Under the shared responsibility model, Microsoft is responsible for the platform, its physical infrastructure, and its own disaster recovery. You’re responsible for your data, your access controls, and recovering from anything that isn’t a platform failure. If content ages out of the Recycle Bin, or a sync client pushes corrupted files into a shared library, recovery is on you.

What Native Options Does SharePoint Online Have?

SharePoint Online has several native recovery features, but none of them is a backup you control:

Is OneDrive Sync a SharePoint Backup?

No. Syncing a SharePoint library to your computer with OneDrive creates a local copy, but sync works both ways. If files are deleted, corrupted, or encrypted by ransomware on either side, the change syncs to the other. A synced copy can spread an attack instead of protecting you from it.

Is eDiscovery a SharePoint Backup?

No. eDiscovery is built to search, hold, and export content for legal and compliance purposes. You can export content with it, but it doesn’t take scheduled point-in-time backups or restore content to its original location with its structure intact.

What Are the Limitations of Native SharePoint Recovery?

Native recovery tools cover short-term accidents, but they leave five gaps:

1. Time limits. The Recycle Bin keeps items for 93 days, library restore goes back 30 days, and Microsoft’s backups last 14 days after deletion. Compliance needs measured in years aren’t covered.
2. No granular restore. Library restore rolls back the entire library. To recover one file, you’d restore the library, copy the file out, and roll the restore back. Microsoft’s own backups restore whole site collections only.
3. Same-tenant storage. Recycle Bin content, versions, and the Preservation Hold library all live in the same Microsoft 365 tenant as your data, so they’re exposed to the same compromised account or ransomware attack.
4. Retention isn’t recovery. Retention policies and holds keep copies for compliance, but recovering from them means finding content in a hidden library and putting it back by hand, without its original folder structure.
5. Manual effort. Every native method depends on someone noticing the problem in time and running the recovery themselves.

Which SharePoint Data Should You Back Up?

Back up everything, and be specific about what “everything” means. These items are the ones most often left out:

1. Version history: Prior versions of files, not just the latest copy.
2. Lists and list attachments: Many teams run real workflows on SharePoint lists, and they’re easy to exclude because they aren’t document libraries.
3. Site pages and web parts: When these disappear, users notice before IT does.
4. Permissions and sharing links: A restored library without its permissions is functionally broken.
5. Teams-connected sites: Teams stores its files in SharePoint, and every private channel creates its own separate site, which is easy to miss.
6. The term store: The metadata taxonomy that organizes content across your tenant.
7. Customizations: SharePoint Framework (SPFx) apps, PnP templates, and search configuration that shape how sites look and behave.

How Is SharePoint Online Backup Different From SharePoint Server?

The approach is different enough to matter:

• SharePoint Server (on-premises) has a built-in backup through Central Administration. You select a site collection under Backup and Restore, point it at a network location you control, and run it.
• SharePoint Online has no equivalent. Central Administration backup doesn’t exist in the cloud version, so tutorials that walk through Central Administration steps don’t apply to SharePoint Online.

SharePoint Online admins typically choose from four options: retention policies, selective exports through PowerShell or the Microsoft Graph API, Microsoft 365 Backup, or a third-party backup solution. PowerShell and Graph exports are often mistaken for backups, but they export only the content you ask for, not a complete point-in-time copy of a site.

How Often Should You Back Up SharePoint?

At least daily for active sites, and more often for sites where content changes throughout the day. Sites that rarely change can run on a slower schedule.

The better question is how much data you can afford to lose. If losing a day of work on a critical project site is acceptable, daily backups are enough. If it isn’t, back up more often. Compliance requirements can also set retention periods measured in years, so check that your backup can keep data that long.

How Do You Back Up SharePoint Manually?

Manual methods work for a quick, one-time copy of critical files, but they aren’t a backup strategy:

1. Download from the browser. Open the library, select the files or folders, and click Download. It requires discipline to repeat, and it doesn’t capture permissions, metadata, or versions.
2. Export with scripts. SharePoint Online has no supported full-backup cmdlet. You can use Microsoft Graph, CSOM, or PnP PowerShell to export selected content or site templates, but not to take a full point-in-time backup.

What Automated SharePoint Backup Options Are There?

Automated backup removes the reliance on someone remembering to act, and it closes the gaps native tools leave: scheduled point-in-time copies, granular restores, and long-term retention.

There are two main approaches:

• Microsoft 365 Backup: A paid add-on for SharePoint, OneDrive, and Exchange, priced at USD 0.15 per GB per month. It offers fast restores, and backups stay within the Microsoft 365 security boundary.
• Third-party backup: Solutions such as SpinBackup, Veeam Backup for Microsoft 365, AvePoint Cloud Backup, Druva, and Acronis Cyber Protect. They store copies outside your Microsoft 365 tenant, which keeps a clean copy available even if the tenant itself is compromised.

For a broader comparison, see SaaS backup solutions compared.

How Do You Back Up SharePoint Online With SpinBackup?

SpinBackup automates SharePoint Online backup and adds ransomware detection and response that native tools don’t offer:

• Automated backups: 1x daily on the standard plan or 3x daily on Enterprise, with no manual steps.
• Storage you choose: Keep backups in AWS, Google Cloud, or Azure, or bring your own storage, all outside your Microsoft 365 tenant.
• Retention you set: From 6 months to indefinitely.
• Granular restore: Recover exactly what you need without rolling back an entire library or site.
• Ransomware detection and response: Within SpinOne, 24/7 AI-driven detection stops ransomware attacks in progress and restores affected files, backed by a 2-hour incident response SLA.

SpinBackup is managed in the SpinOne dashboard alongside Microsoft 365, Google Workspace, Salesforce, Slack, Jira, and Confluence. Learn more about SharePoint backup and recovery or Microsoft 365 backup.

What Are SharePoint Backup Best Practices?

1. Capture the whole site, not just files. Include version history, lists, site pages, permissions, sharing links, the term store, and customizations.
2. Match backup frequency to how fast sites change. Back up high-change sites several times a day, and run heavy jobs outside business hours to avoid SharePoint throttling.
3. Keep a copy outside your tenant. Store backups off-tenant, ideally in immutable storage, so a compromised account or ransomware can’t reach them.
4. Don’t rely on the Recycle Bin or retention. Both are time-limited, and neither is designed to rebuild a site after a mass change or ransomware attack.
5. Include Teams sites and private channels. Their files live in SharePoint, and each private channel creates its own site.
6. Restore to an alternate location when needed, so you don’t overwrite current work.
7. Run restore drills every quarter. Restore a site or library, then check that permissions, pages, and navigation work. Assign tighter recovery targets to business-critical sites.

Can Spin.AI Back Up SharePoint Online?

Yes. SpinBackup backs up SharePoint Online automatically up to three times daily, stores copies outside your tenant in the cloud you choose, and restores at the granularity you need, with ransomware detection and response backed by a 2-hour SLA in SpinOne. Start a 15-day free trial or request a demo.

Frequently Asked Questions

Was this helpful?

Yes No