Acronis Blog

How to back up Microsoft 365: a guide for homes and SMBs

Learn how to back up Microsoft 365 business or personal data, compare recovery approaches, and test mailbox, OneDrive, SharePoint and Teams recovery.

Listen to this article

0:00 / 0:00

How to back up Microsoft 365: a practical guide for individuals and SMBs

Backing up Microsoft 365 starts with identifying the account and information you need to recover. A personal Outlook or OneDrive account, a company's Exchange Online mailbox and a Word document saved only on a laptop require different protection methods.

For a business, a useful backup plan identifies the covered services, creates retained recovery points, protects backup administration and defines how authorized staff will restore information. For an individual, the immediate need may be recovering email, personal files or a computer after a mistake or device failure.

Does Microsoft 365 include backup?

Microsoft 365 has several recovery mechanisms, and Microsoft also offers a distinct Microsoft 365 Backup service. It is inaccurate to say Microsoft provides only availability or that no native backup option exists.

The native Backup service covers selected SharePoint sites, OneDrive accounts and Exchange Online mailboxes. It uses protection policies and has workload-specific recovery behavior and retention options. Evaluate its current documentation for your tenant rather than applying an older article's universal retention limit.

This does not mean every subscription, workload and item is automatically protected by an enabled backup policy. Determine what you have configured and what a recovery would require.

Backup, retention, synchronization and export

Mechanism
Main purpose
What to check before relying on it
Recycle bin or deleted-item recovery
Recover particular deleted content within applicable conditions
Workload, eligibility, permissions and expiration
Version history
Return supported content to an earlier version
Available history and administrator controls
Retention or legal hold
Preserve covered information for governance requirements
Scope, retrieval process and whether it supports the operational recovery you need
Synchronization
Keep selected working data aligned across locations
Whether unwanted changes or deletions propagate
Backup service
Retain recovery points with defined restoration workflows
Coverage, protection of recovery points and tested recovery behavior
Export
Produce a separate copy of selected information
Completeness, refresh process, storage security and reimport limitations

These mechanisms can coexist. A legal hold and a backup policy may serve different requirements, while a synchronized folder can provide convenient access without being an independent recovery strategy.

Choose the right route for your account

Microsoft 365 business tenant: identify the business workloads and evaluate a tenant-capable backup service, whether native, third-party or managed by a service provider.

Personal Microsoft account: use a solution that explicitly supports personal Outlook and OneDrive. Business-tenant instructions may not apply.

Desktop Office files: protect the actual location of Word, Excel and PowerPoint documents. If they are local files, include those folders in a device backup. See our Microsoft Office file backup guide.

If the next task is choosing software, use the separate Microsoft 365 backup software buying guide. An MSP designing a recurring service can use the Microsoft 365 BaaS guide.

How to back up a Microsoft 365 business tenant

1. Inventory the information and owners

List users, shared resources, sites and collaboration spaces. Identify the business owner for each important service and record which information would be difficult to recreate.

Map where the content resides. Email, personal work files, shared documents and collaboration messages may use different services even when users access them through one application. Do not assume backing up a Teams-associated site captures every Teams item.

Include lifecycle events in the inventory: new employees, departing employees, new sites, renamed groups and ownership changes. Decide who verifies that protection follows those changes.

2. Define the recovery requirements

Agree how much recent work could be lost and how quickly different services must become usable. These are recovery point and recovery time objectives. Distinguish a request to recover one email from restoring a large site after widespread unwanted changes.

Choose retention against the organization's needs, including delayed discovery of deletion or corruption. Have the responsible teams approve retention and disposal obligations. A product's maximum retention is not a universal business requirement.

3. Evaluate native and third-party approaches

Compare the same requirements for each option: workloads, item types, recovery destinations, metadata, retention, access boundaries, geography, scale and costs.

Examine where backup data and its administration depend on Microsoft services, the backup provider or your own infrastructure. A third-party brand does not automatically mean every component is independent of Microsoft, and a separate storage location does not guarantee availability during every outage.

Check whether the proposed service uses Microsoft 365 Backup Storage or another backup architecture. The distinction can affect the recovery workflow and storage boundary; it should be explained in the evaluation.

4. Authorize and configure the service

Use an authorized administrator to connect the correct organization and grant the documented permissions. Review the requested access, protect administrative identities and record who can change or remove protection.

Select the workloads and resources to protect. Configure schedules, retention, destinations and encryption where those settings are available. Check how new users or sites are included and what exceptions require manual handling.

Use the setup documentation for the selected product and current edition. A home-account dashboard, an old eDiscovery export and a business backup console are different workflows.

5. Verify the first backup and ongoing coverage

Wait for the initial protection process to complete, then inspect its result. Confirm that representative mailboxes, files and sites are present and that exclusions are intentional.

Assign an owner for failed jobs, authorization changes, capacity issues and newly unprotected resources. A summary showing successful jobs does not reveal resources that were never added to a policy.

6. Run representative restore tests

Recover a sample email and a file to an appropriate test destination. Where required, exercise a site or account restore and verify permissions, content and the behavior of changes made after the chosen recovery point.

Record what was restored, the recovery point used, elapsed time and anything that needed manual reconstruction. Check the outcome with the service owner. Repeat relevant tests after important product, tenant or policy changes.

Check Microsoft Teams coverage carefully

Teams protection is not a single yes-or-no feature. Ask separately about channel files, channel conversations, private chats, membership, meetings, notebooks and recovery destinations.

For example, the current Acronis Teams protection documentation states that private one-to-one and group chats are not backed up. Channel conversations cannot be restored into channels, although they can be downloaded as an HTML file. Other supported team components have their own recovery options.

Treat these as documented Acronis limits, not a claim about every vendor. Request an item-level support matrix for whichever product you select.

Personal Microsoft 365 backup with Acronis True Image

The Acronis True Image 2026 Windows guide documents backup of personal Outlook mailbox content and OneDrive files and folders. That workflow does not support Microsoft business accounts or shared and group mailboxes.

For a supported personal account:

  1. Open the Acronis Online Dashboard and sign in.
  2. Choose Resources, then Add, then Microsoft 365.
  3. Authenticate to the intended personal Microsoft account.
  4. Select the entire supported account, Outlook or OneDrive as the source.
  5. Review cleanup and encryption options, apply the settings and choose Run now.
  6. After completion, browse the recovery data and test a sample restore.

Confirm your subscription and use the documentation for your installed version. Protect any backup-encryption password so it remains available for recovery.

When is an email export useful?

An export can provide a portable copy for a specific task. It needs its own handling plan: who creates it, which information it includes, how it is protected and how it can be opened or imported later.

Do not treat a one-time mailbox export as a complete backup of a business tenant. It does not establish continuous coverage for SharePoint, OneDrive, Teams or future mailbox changes. An archive also needs an appropriate retrieval process rather than an assumption that any exported file supports a full service restore.

Plan recovery before an incident

Document who can approve a recovery and how to reach them if normal email is unavailable. Keep recovery instructions and privileged access procedures accessible through a separate authorized route.

Before a large restore, establish the cause of the incident and select an appropriate recovery point. Check overwrite behavior and recovery scope. After a suspected compromise, coordinate restoration with incident response so that compromised accounts or malicious activity do not undermine the restored service.

Common questions

Does OneDrive synchronization protect every Office document? It covers only the configured data and synchronization behavior. Check local folders, cloud-only content and available recovery history separately.

Can backup undo a data breach? Restoring data can help recover availability and integrity. It does not reverse disclosure of information already stolen.

Will backup work during a Microsoft outage? It depends on the operation and architecture. Accessing an existing export and restoring into a Microsoft service have different dependencies. Test the scenarios your plan requires.

How do I know the backup is working? Verify coverage, monitor failures and complete representative restore tests. Keep evidence that the recovered information is usable.

Written by

About Acronis

Acronis is a leader in AI-native cyber protection, unifying data protection, cybersecurity, IT operations and hybrid infrastructure to deliver business continuity, security and compliance with less cost and complexity. More than 21,000 service providers trust Acronis to protect over 750,000 businesses in 150 countries. Acronis is headquartered in Schaffhausen, Switzerland.