Articles

Microsoft 365 Backup: How It Works + Best Practices

This guide explains how Microsoft’s native backup service works, what it leaves out, and the six practices that keep Exchange, OneDrive, SharePoint, Teams, and Entra ID data recoverable.

Team Eon
Written by
Team Eon
Published: 
Nov 13, 2026
0
 min read

Quick Summary

  • Microsoft’s native backup service protects SharePoint, OneDrive, and Exchange Online for $0.15 per GB per month, with 10-minute restore points and policies set in the admin center.
  • Built-in safety nets like recycle bins (93 days) and Exchange’s Recoverable Items folder (14 days by default, 30 at most) undo recent mistakes, then expire on a fixed clock.
  • The native service skips Teams chats and Entra ID, keeps restore points for two years at most, and stores every copy inside the same Microsoft 365 boundary as production.
  • A complete plan follows the 3-2-1 rule, automates the schedule, matches retention to compliance needs, keeps one copy outside the tenant, and tests restores on a calendar.

‍

Someone deletes a file in OneDrive, and the recycle bin brings it back. That’s the easy case. Microsoft 365 backup is built for the harder ones: ransomware that encrypts a few thousand synced files, or a compromised admin account that starts changing policies.

Microsoft now sells its own backup service for those cases, and plenty of admins are still working out what it covers. It handles three workloads well. It also leaves Teams chats and Entra ID out, and it keeps every copy inside the same tenant boundary as the data it protects.

What is Microsoft 365 Backup?

Microsoft 365 Backup is Microsoft’s native, pay-as-you-go service for backing up SharePoint sites, OneDrive accounts, and Exchange Online mailboxes, managed from the Microsoft 365 admin center. 

You choose what to protect in backup policies, and the service keeps point-in-time restore points you can roll back to after ransomware or a mass deletion.

It’s sold separately from your Microsoft 365 licenses. Microsoft charges $0.15 per GB per month of protected content, billed through an Azure subscription, and restores cost nothing extra.

Backing up Microsoft 365 more broadly means keeping independent, point-in-time copies of mail, files, sites, chats, and identity data that you can restore after the built-in safety nets have run out. Microsoft’s service is one way to do it. A third-party tool that stores copies outside the tenant is another, and a lot of enterprises run both.

What the native service covers

Microsoft’s service protects the following today:

  • Workloads: SharePoint sites, OneDrive accounts, and Exchange Online user and shared mailboxes. Room and group mailboxes aren’t supported, and only mailboxes fully hosted in Exchange Online qualify.
  • Restore points: Every 10 minutes for Exchange across the prior 52 weeks. OneDrive and SharePoint get 10-minute points for two weeks, then weekly points out to 52 weeks.
  • Recovery window: 3 months, 6 months, 1 year, or 2 years per policy, an option Microsoft added in September 2026. Existing policies stay at 1 year unless an admin changes them.
  • Storage: Backups stay inside the Microsoft 365 data trust boundary on append-only storage.
  • Restores: Full sites and OneDrive accounts roll back to a point in time, and mailboxes restore down to single items. File- and folder-level restore for SharePoint and OneDrive became generally available in 2026.

What does Microsoft 365 protect by default?

Microsoft 365 protects your data by default with recycle bins, a Recoverable Items folder in Exchange, version history, and retention policies. Each one is designed to undo a recent mistake or hold content for compliance, and each runs on its own clock.

Built-in feature What it protects How long it lasts
SharePoint and OneDrive recycle bins Deleted files, folders, and lists 93 days from deletion, across both stages
Exchange Recoverable Items Permanently deleted mail 14 days by default, up to 30
Version history Earlier versions of a file Until the library’s version limit is hit
Retention policies and holds Content kept for legal or compliance reasons As long as the policy says

These tools cover the user who deletes the wrong folder, but they buckle under a real incident. Versions don’t scale to a large ransomware recovery and can run out at the version limit, and legal holds are built for eDiscovery export. Neither one rolls 5,000 encrypted files back to a clean point from before the attack.

They also expire on a clock. If nobody notices a deleted SharePoint folder until day 94, the recycle bin has already let it go.

Microsoft’s shared responsibility model splits the job: Microsoft keeps the service running and available, and protecting and recovering your data is on you. A failed disk in its data center won’t cost you a mailbox, but once content ages out of a recycle bin or a retention window, getting it back depends on a plan you made beforehand.

How does Microsoft’s native backup work?

Microsoft’s native backup works through backup policies. Each policy lists the sites, OneDrive accounts, or mailboxes to protect and how long to keep restore points. Once a policy is active, the service saves each change as a new version every 10 minutes and exposes restore points you can roll back to.

Billing is pay-as-you-go through an Azure subscription, which only processes the payment, with no extra storage charges. 

Each site, mailbox, or OneDrive account can sit in only one policy, and a new policy takes about an hour to process and another to create its first restore points, with initial backups at roughly 15 minutes per 1,000 protection units.

To restore, you pick a restore point and roll a site or OneDrive account back, in place or to a new URL, or bring mailbox items back to their original folder or a new one. 

Say ransomware encrypts a finance team’s SharePoint site one afternoon: an admin picks the express restore point from that morning and rolls the site back, and Microsoft says a site under about 1 TB restores in under 20 minutes.

An in-place rollback overwrites everything saved after the restore point, though, including that afternoon’s legitimate work. Restoring to a new URL is slower but keeps the live site intact while you sort out what to keep.

Microsoft also adds guardrails around the backups themselves: email alerts to up to 20 recipients for potentially harmful actions, a fixed 90-day grace period after offboarding, and, as of October 2026, two-person approval before anyone can shorten offboarding deletion.

Native vs. third-party backup for Microsoft 365

The main difference between native and third-party backup for Microsoft 365 is where the copies live and how much of the tenant they cover. Microsoft’s service keeps three workloads inside your tenant’s trust boundary. Third-party tools vary, and the stronger ones store copies outside Microsoft 365 and add Teams and Entra ID.

By workload, the split looks like this:

Workload Native service What to look for in a third-party tool
Exchange Online Mailboxes and items, 10-minute restore points Item-level restore and search across deleted mail
OneDrive Accounts, files, and folders File and folder restore with permissions kept
SharePoint Sites, files, and folders Site, library, and file restore with sharing settings kept
Teams Channel files only (stored in SharePoint) Channel messages plus 1:1, group, and meeting chats
Entra ID Not covered Users, groups, roles, and app registrations

And where the copies sit and how long they stay:

Question Native service Third-party tool with its own vault
Where do backups live? Inside the Microsoft 365 trust boundary Outside the tenant, often in a region you pick
How long are they kept? Up to 2 years per policy Set by your own retention policy
Where can you restore? Same or new location, same tenant Original location or a separate folder or site
Who manages them? Admins in the same tenant A separate console with its own access controls
How is it billed? $0.15 per GB per month Per user or per GB, depending on the vendor

Entra ID has a native option of its own, outside the backup service. Microsoft Entra Backup and Recovery comes with Entra ID P1 or P2 licenses, takes one backup a day, and keeps seven days of history. That’s useful for reversing a bad change from yesterday, and short if the change happened two weeks ago.

Microsoft has closed several of these shortfalls quickly. File-level restore and the 2-year recovery window both arrived in 2026. What it still leaves out is in the workload table above and the limitations below.

The native service wins on restore point frequency and bulk rollback speed inside Microsoft 365. Microsoft quotes median rates of up to 1 to 3 TB an hour for up to 1,000 sites or mailboxes at a time.

A third-party copy wins when the threat reaches the tenant itself. Plenty of enterprises use both: Microsoft for fast in-tenant rollback, an outside copy for the worst day.

Where Microsoft’s backup works well and where it falls short

Within Microsoft 365, the native service does several things well:

  • Ten-minute restore points run across a full year for Exchange, a tight recovery point for mail.
  • Express restore points roll back large numbers of sites and OneDrive accounts in hours.
  • Restores are free, there’s no annual contract, and you pay only for content inside a policy.
  • Policies sit alongside the rest of your Microsoft 365 settings, with no extra vendor to onboard.

It also comes with clear limits:

  • Teams chats and Entra ID need a separate product.
  • Backups are managed by the same tenant’s admin roles as production, so an attacker with Global Admin rights is working in the same console that controls them.
  • Two years is the longest recovery window, which won’t cover multi-year archiving.
  • Online archives, recycle bins, and deleted items all count toward protected storage, so large tenants can see bigger bills than their usage reports suggest.

For most enterprises, it works best as one layer of a plan: strong for fast in-tenant rollback of the workloads it covers, and worth pairing with a second copy outside the tenant for everything it leaves out.

How to back up Microsoft 365

You back up Microsoft 365 natively by connecting pay-as-you-go billing and then creating a backup policy for each workload in the admin center. The steps below set up a SharePoint policy; OneDrive and Exchange policies follow the same flow from their own sections of the admin center.

Before you start, you’ll need the SharePoint Administrator or Global Administrator role, whichever is the lowest-privilege one that works, plus an Azure subscription where you’re an Owner or Contributor, a resource group, and a region.

  1. Set up pay-as-you-go billing. From the Billing node in the Microsoft 365 admin center, link your Azure subscription, resource group, and region.
  2. Go to Settings and select Microsoft 365 Backup from the list of products.
  3. In the SharePoint section, select Set up policy, review the overview page, and select Next.
  4. Choose how to add sites. You can upload a CSV of up to 50,000 sites, back up sites that match filters (site name or URL keywords, or last modified date), pick sites one by one, or protect every site with a full-workload policy (in preview).
  5. On the backup settings page, name the policy (20 characters max) and set the recovery window to 3 months, 6 months, 1 year, or 2 years.
  6. Review the policy and select Create policy. Restore points can take up to 15 minutes per 1,000 sites to appear.
  7. Add up to 20 people, distribution lists, or security groups to the backup notification list, so someone hears about potentially harmful actions right away.

Pick your recovery window carefully on day one. Shortening it later deletes older restore points once a 30-day grace period ends.

Microsoft’s service isn’t the only route. For a manual copy, Microsoft Purview eDiscovery can export mailbox content as PST files and SharePoint or OneDrive documents as copies of the original files.

That’s handy for a one-off snapshot before an employee leaves, but not for running a tenant’s backup, since there’s no backup schedule and no restore workflow.

Automated third-party tools usually connect through Microsoft Graph with tenant-wide admin consent, run on a schedule, and store copies in their own vault. That’s the route to look at if you need Teams chats, Entra ID, or a copy outside the tenant.

Best practices for backing up Microsoft 365

These are the practices we recommend for any enterprise tenant, whichever tools you use.

  1. Follow the 3-2-1 rule. Keep three copies of your data on two different types of storage, with one copy offsite. For SaaS data, “offsite” means outside the tenant and out of reach of the admin roles that manage it.
  2. Automate the schedule and the scope. Static lists leave new accounts unprotected. A policy built from a CSV last spring won’t include the OneDrive account created for this month’s new hire. Use filters, full-workload policies, or a tool that discovers new users, sites, and teams on its own.
  3. Match retention to what auditors and contracts expect. If your legal team needs mail recoverable for five years, a two-year recovery window leaves three years uncovered. Set retention per data type, and write it down in a backup retention policy so it survives staff changes.
  4. Keep one copy outside the tenant, and limit who can touch it. An immutable backup in a separate vault stays intact when a Microsoft 365 admin account is compromised. Inside the tenant, give backup rights to a small group and keep notifications on.
  5. Back up Teams and Entra ID too. Restoring a mailbox doesn’t help much if the user account, its group memberships, and its app permissions are gone. Teams chats hold decisions and approvals that never land in email.
  6. Test restores on a regular schedule. Restore a mailbox, a SharePoint site, and a Teams channel to an alternate location, then check permissions and timing. As AWS’s Mo Kamioner put it in our DynamoDB backup webinar, "It’s very important to not only have your data backed up, but have a plan."

How Eon protects Microsoft 365

Eon protects Microsoft 365 with daily backups of Exchange Online, OneDrive, SharePoint, and Teams, stored in an immutable, logically air-gapped vault outside your tenant in the region you choose. A compromised Microsoft 365 admin account has no path to that vault.

We built it for the case the native service can’t cover: the tenant itself is the thing under attack. Eon connects through Microsoft Entra ID with tenant-wide admin consent. Backup runs on read-only application permissions, and restores use a separate application with write access.

Teams coverage includes channel conversations (root messages, threaded replies, reactions, and inline images) plus 1:1, group, and meeting chats. You can restore a single reply, a thread, a channel, or a whole chat, and the messages keep their original sender and timestamp.

Entra ID protection covers users, groups, directory roles, administrative units, app registrations, service principals, and license assignments, along with the relationships between them. Restores run per object, so you can bring back a deleted group with its members and role assignments re-linked.

When ransomware hits OneDrive or SharePoint, Eon scans those backups and flags the last clean recovery point with no signs of encryption.

From there, granular recovery restores only what was affected: a single email, a folder, or a full mailbox, files and folders in OneDrive, or SharePoint sites, libraries, and single files with permissions and sensitivity labels intact. You can search content and metadata across current and deleted items before you restore.

Sensitive restores can require multi-party approval, and an AI agent can find the right recovery point and submit a restore through Eon’s MCP integration, within the signed-in user’s permissions.

Eon backs up the tenant once a day by default, so it won’t match Microsoft’s 10-minute restore points for mail. Ransomware scanning covers OneDrive and SharePoint backups, so Exchange mailboxes aren’t scanned the same way. 

Pricing is usage-based, per GB per month of backed-up data, with no seat tiers.

Does your only backup of Microsoft 365 live inside the tenant it protects?

Microsoft’s native service is a solid first layer. It rolls SharePoint, OneDrive, and Exchange back fast and bills only for what you protect, and it sits inside the admin center your team already uses. For a lot of tenants, it belongs in the plan.

What it misses is everything around it: Teams chats, Entra ID, retention past two years, and a copy that the tenant’s own admins can’t reach. A backup that sits behind the same admin login as production can end up as part of the incident.

Would your Microsoft 365 data survive a compromised Global Admin account? Book a demo and see how Eon keeps your backups in a logically air-gapped vault outside your tenant, with restores down to a single email or Teams reply.

Frequently asked questions

Does Microsoft 365 have built-in backup?

No, standard Microsoft 365 licenses don’t include a full backup. They include recycle bins, Exchange’s Recoverable Items folder, and version history, which recover recent deletions for a limited time. Microsoft sells point-in-time backup of SharePoint, OneDrive, and Exchange Online separately at $0.15 per GB per month.

How much does it cost to back up Microsoft 365 per month?

Microsoft charges $0.15 per GB per month of protected content, billed through Azure, and restores are free. Protecting 10 TB costs about $1,500 a month. Third-party tools price per user or per GB, so compare them against your own tenant’s data.

What is the best backup for Microsoft 365?

The best backup for Microsoft 365 covers Exchange, OneDrive, SharePoint, Teams, and Entra ID and keeps those copies outside your tenant, with restores down to a single item. Eon does this with daily backups in an immutable, logically air-gapped vault in the region you choose. Microsoft’s native service pairs well with it as a fast in-tenant layer.

Does Microsoft 365 back up Teams chats?

No. Microsoft’s native backup only covers Teams channel files stored in SharePoint sites. Teams chats and other content stored on Teams servers aren’t protected, so you need a third-party tool for them.

How long does Microsoft 365 keep deleted files and emails?

SharePoint and OneDrive keep deleted items for 93 days across both recycle bin stages. Exchange Online keeps permanently deleted mail in Recoverable Items for 14 days by default, and admins can raise that to 30. After that, you need a backup or a retention policy that keeps a copy.

FAQ

No items found.
Team Eon
Team Eon
>100% ROI in the first year

SoFi automated multi-region resilience and regulatory alignment across five AWS regions with Eon’s cloud-native platform, cutting recovery time from a day to minutes and achieving over 100% ROI.

Read case study
88% faster recovery, 35% savings

NETGEAR replaced its legacy backup provider with Eon's cloud-native platform, cutting a 10TB recovery from 24 hours to under three and reducing backup storage costs by 35% in under a week.

Read case study

Turn your backups into usable data

Eon turns your backups into instantly searchable, usable data so you can recover exactly what you need without delays.

  • Instantly search backup data with Global Search
  • Find any backup data with Global Search
  • Restore only what you need
See eon in action