
IN THIS GUIDE
Could you recover the Microsoft 365 data your business depends on? If your answer rests on “Microsoft has it covered,” then there is likely a gap in your recovery plan.
Microsoft 365 runs your business. Emails, contracts, financial files, and project documents sit across Exchange Online, SharePoint, and OneDrive. Losing access to that information can interrupt work across the organization, even when the service itself is available.
A useful backup strategy starts with understanding what your current protection can recover. From there, you can decide how much data loss and downtime the business can tolerate, how long information must be kept, and how to control costs as it grows. This guide explains those decisions and what to look for in a third-party solution.
Where Microsoft 365’s built-in protection falls short
Microsoft 365 includes retention, versioning, and recovery tools that help with common data protection needs. Their limits matter when the business needs something more: older history, selective recovery, or coordinated restoration after a larger incident. A working service and a recoverable business record are different outcomes.
Microsoft’s backup documentation explains that version-based recovery does not scale well for large ransomware incidents and that legal holds are designed for preservation and export rather than mass restoration. That distinction is the starting point for understanding where additional backup can help. [2]
The question for IT is whether the protection in place matches the way the organization needs to recover. Keeping information somewhere is useful only if you can return it to the right people, in a usable form, when they need it.
The Shared Responsibility Model Explained
Who protects what? • Microsoft’s own guidance
“You’re responsible for your data, including data classification, data protection, encryption decisions, and compliance with data governance requirements.”
Source: Microsoft Learn: Shared responsibility in the cloud
Microsoft’s responsibility
Microsoft secures and maintains the cloud infrastructure, including datacenters, physical networks, and servers. For SaaS services, it also manages the operating systems and platform services.
Your organization’s responsibility
Your organization is responsible for its data, identities, access, and configurations. It must choose and configure protection that supports its recovery, retention, and governance requirements.
Having a Microsoft 365 subscription does not tell you whether you can recover the data you need after a particular incident. You need to check the protection in place and the restore options it gives you.
Being on Microsoft 365 doesn’t automatically mean your recovery needs are covered. Brian Gnos, Director of Sales Engineering and Professional Services at CrashPlan, explains what shared responsibility means for your organization and why it matters when critical data is deleted or compromised.
What does that gap put at risk?
Data loss affects more than the IT queue. A missing contract can hold up a sale or a legal review. Lost employee records can interrupt HR processes. An overwritten financial model can delay a close. These are the business consequences a backup strategy needs to address.
Accidental deletion and changes discovered too late
A file can be deleted or overwritten long before anyone realizes it is missing. By the time someone asks for it, the recovery history available through the tools you use may no longer reach far enough back. Retention policies, legal holds, and dedicated backup can affect what remains available, so the plan needs to account for when a loss might be discovered as well as when it occurs.
Ransomware and malicious changes at scale
After a widespread incident, the challenge is identifying clean data and returning people to work within the time the business can tolerate. Restoring an earlier version of one document is a different task from coordinating recovery across many users or sites. Your plan needs to support both everyday mistakes and larger disruptions.
Recovering data without disrupting unaffected work
Imagine a project folder is deleted on Monday, but nobody notices until Thursday. In the meantime, colleagues have continued working. A broad rollback could recover the missing folder while reversing legitimate changes. Granular recovery matters because the scope of the restore can affect people who were not part of the original incident.
“Couldn’t we just use the tools we already have?”
It is reasonable to look at the tools already available before adding another solution. The important distinction is what each tool was designed to do. Retention, synchronization, and recovery features can all contribute to protection, but relying on one as a complete backup plan can leave requirements unmet.
| The apparent backup plan | What it helps with | The gap to investigate |
|---|---|---|
| Recycle bins | Recovering supported, recently deleted items. | Recovery windows expire; items can also be purged. What preserves older losses? |
| Version history | Returning supported content to an earlier version. | History depends on settings. How will IT coordinate recovery at incident scale? |
| Whole-OneDrive or shared-library restore | Rolling supported content back to an earlier state. | The available history and rollback scope may not fit the incident or preserve newer work. |
| Retention policies and legal holds | Preserving content for governance or investigation. | Keeping a record does not by itself provide a fast way to restore a working environment. |
| Syncing or copying files elsewhere | Making content accessible or keeping another copy. | Sync can propagate damaging changes. A manual copy needs its own history, access controls, coverage, and tested restore process. |
Copying data somewhere else does not settle the recovery question. Can you still find the version you need, and can you trust it? If a compromised account can alter both the original and the recovery copy, the second location has not solved that access problem.
Use these tools for the purposes they serve, then identify the recovery requirements that remain. A third-party backup plan should address those gaps through suitable recovery history, restore options, and administrative controls. [2]
How to choose the right third-party Microsoft 365 backup solution
Once you have identified the need for additional backup, the next decision is which approach fits your organization. Start with your recovery gaps, turn them into requirements, compare the available architectures, and ask shortlisted providers to demonstrate the outcome. A long feature list cannot make that decision for you.
1. Map the data and workflows you cannot afford to lose
Start with the work the business cannot afford to interrupt. Identify the Exchange mailboxes, SharePoint sites, and OneDrive accounts that support it, along with the teams that depend on them. Finance may need reporting files back before a close; legal may need an earlier contract version; HR may need employee records during a transition. Those priorities should shape protection and recovery order.
Use that list when you speak with providers. Ask them to show how they would protect and restore those workloads, rather than accepting a general claim that they cover Microsoft 365.
2. Set recovery objectives before comparing backup schedules
Your recovery point objective (RPO) defines the maximum acceptable data loss, usually expressed as time. Your recovery time objective (RTO) defines the maximum acceptable downtime. Backup cadence influences the first; restore capacity and the recovery process influence the second. Set both around business priorities before comparing products.
During a financial close, getting the right spreadsheet back tomorrow may be too late. Measure the whole recovery process, including finding a clean recovery point, regaining access, and checking the restored content with users. A frequent backup schedule does not tell you how long those steps will take.
3. Shortlist providers by the recovery workflows you need
Choose a solution that supports the level of recovery the incident requires, from individual emails or documents to user accounts and SharePoint sites. Metadata, permissions, and sharing links can be important to getting people working again. A restore that leaves IT rebuilding that context still has an operational cost.
Coverage should be clear for each workload. For Exchange, consider emails, attachments, calendars, and contacts; for OneDrive and SharePoint, consider files, folders, libraries, and metadata. Confirm which Teams content a solution covers rather than assuming that one application label includes everything. [6]
Look for selective recovery for everyday losses and a way to restore larger workloads after a wider incident. If both are important to your organization, include both in the evaluation.
4. Compare security, governance, and storage architecture
A recovery copy needs protection of its own. Encryption in transit and at rest, role-based access, audit logs, and immutable or deletion-protected storage are important considerations. Separate recovery administration from everyday access where appropriate, so a compromised user or administrator account does not automatically become a compromised recovery plan.
Check governance alongside recovery.
Decide how long recovery history must remain usable, what legal preservation requires, and where data may be stored. Check how holds, search, exports, and deletion policies apply to backup copies as well as production content. A provider’s certifications can inform the evaluation; configuration and operating procedures still determine whether your organization’s requirements are met.
Work out what protection will cost as data grows.
Storage choice affects cost, residency, and control. Compare the available cloud or customer-managed destinations alongside licensing, data growth, retained versions, retrieval, and administration. A low initial price may look different after several years of growth, so use the same period and assumptions for each option.
Backup and archiving belong in the same strategy because the data you need to recover is not always the data people use every day. Backup preserves recovery points. Archiving changes how less active information is stored and accessed. Adding backup does not automatically reduce production storage, and retained copies can continue using capacity after content is archived. [5]
Explore how archiving for Microsoft 365 can fit into a broader recovery and storage strategy.
Explore Potential Savings
If inactive data is driving storage overage costs, use our Microsoft 365 storage savings calculator to estimate potential savings from archiving. Review the assumptions against your environment, including retained copies that may continue using capacity.
5. Run the same recovery exercise with each finalist
Give each finalist the same data and recovery scenario, with clear criteria for success. Include a selective restore that must preserve newer work, and a larger recovery if your organization needs it. Record the time taken, any missing context, and the work IT has to do manually.
Make sure the demonstration uses the configuration and storage you would buy. A result from a different setup may not tell you how your deployment would perform.
6. Confirm how you will operate and verify protection
Ask how your team will spot failed jobs, excluded content, and gaps in coverage. Check what happens when someone creates a new site or mailbox. A successful job is useful information, but you also need to know whether everything that should be protected was included.
Assign someone to investigate failures and confirm how to get help during a recovery. Schedule restore tests with business owners. Choose a solution your team can manage consistently and demonstrate that it meets the requirements you set.
How CrashPlan meets these requirements
Why choose CrashPlan for Microsoft 365 backup?
CrashPlan brings Microsoft 365 backup, recovery, and archiving together to help organizations protect business data and manage its growth. Our granular recovery, storage choices, and governance capabilities address the requirements outlined above. Microsoft 365 Backup Storage integration adds an option for supported larger-scale recovery.
Protect your critical sites and mailboxes
CrashPlan protects SharePoint, OneDrive, and Exchange Online, the services that hold much of the organization’s everyday work. Protection should cover the sites, accounts, and mailboxes your teams rely on, with recovery available at the scope they need.
Design recovery around your RPO and RTO
CrashPlan for Microsoft 365 supports configurable backup frequency and point-in-time recovery. CrashPlan also offers Microsoft 365 Backup Storage integration for supported large-scale mailbox, SharePoint site, and OneDrive account recovery. This is available as a standalone offering or paired with CrashPlan for Microsoft 365; confirm the proposed combination when evaluating scope and cost.
Recover individual items or larger assets
With CrashPlan, you can restore individual documents, folders, and emails, alongside broader recovery workflows. Supported restores preserve context such as metadata, permissions, and sharing links. Granular recovery gives IT a way to address affected content without an unnecessary full-environment restore.
Explore CrashPlan’s Microsoft 365 backup solution →
Bring security, governance, and storage into the same plan
CrashPlan provides encryption in transit and at rest, role-based access, retention, legal hold, and eDiscovery capabilities. Review those controls with your IT and governance teams against your access and preservation requirements.
For CrashPlan for Microsoft 365, storage options include CrashPlan cloud, or customer-provided storage. These destination choices are distinct from Microsoft 365 Backup Storage, where protected data stays within the Microsoft 365 data trust boundary. Integrated archiving can move supported less active content out of production storage while retaining access through file pointers.
Storage flexibility lets you weigh cost and control as data grows. Integrated archiving provides a way to manage inactive content alongside active recovery needs, while accounting for the retention and access requirements of the selected destination.
Manage backup and recovery day to day
CrashPlan provides a web console for backup, recovery, retention, and legal hold, with role-based access and centralized reporting. Self-service recovery offers another route for supported user restores. Validate coverage reporting, new-asset enrollment, failure notifications, and support arrangements for your deployment.
The aim is to give IT a practical way to recover business data, manage retention, and control storage costs as the environment grows.
Explore CrashPlan for Microsoft 365, Microsoft 365 archiving, and our security, privacy, and compliance resources.
Microsoft 365 backup and recovery FAQs
Can ransomware-encrypted data be recovered from backup?
Recovery depends on having a usable, clean recovery point from before the damaging changes. Keeping encrypted versions does not necessarily remove earlier healthy copies, but those copies must remain within the available history. Follow your incident response process to contain the compromise before returning restored data to use.
How quickly should we expect recovery?
Recovery time depends on what was affected, how much data must be restored, the restore method, and how long validation takes. Test your priority workloads against your RTO so you know what to expect from the proposed setup.
How frequently should backups run?
Set capture frequency around your acceptable data loss, then check how long that history stays available. A frequent schedule does not help with a late-discovered incident if every clean recovery point has already expired.
What are the key features to look for in a Microsoft 365 backup solution?
When evaluating third-party backup solutions for Microsoft 365, consider features like granular recovery options, automated backup schedules, integration with existing security measures, compliance reporting capabilities, and ease of use for both administrators and end users.
Protect your Microsoft 365 data with CrashPlan
Get a personalized demo of CrashPlan’s Microsoft 365 backup solution. See how you can back up and recover SharePoint, OneDrive, and Exchange Online data, with flexible storage options and integrated archiving.
Get a Microsoft 365 Backup Demo ↗Microsoft recovery details
SharePoint’s recycle-bin period is 93 days from the original deletion across both stages, subject to purge behavior. Microsoft also documents a limited support-assisted site-collection restore window of 14 days after actual deletion. Whole-OneDrive and shared-library rollback support changes within the preceding 30 days. Applicable retention policies, holds, and dedicated backup may provide other recovery paths. The linked Microsoft documentation explains scope and configuration. [4] [7] [8]
Sources and further reading
- Microsoft: Shared responsibility in the cloud
- Microsoft: Microsoft 365 Backup FAQ
- Microsoft: Microsoft 365 Backup overview
- Microsoft: SharePoint recycle-bin recovery
- Microsoft: Retention policies and labels
- Microsoft: Isolation and access control, including Teams storage
- Microsoft: Restore your OneDrive
- Microsoft: Restore a shared library
CrashPlan resources: CrashPlan: Microsoft 365 backup and archiving capabilities; CrashPlan: Microsoft 365 archiving
CrashPlan is the enterprise platform for resilient, secure, and cost-effective backup and recovery. Purpose-built to safeguard critical data across endpoints, servers, and SaaS applications, CrashPlan empowers organizations to maintain business continuity, meet compliance standards, and protect the ideas that drive growth—without disrupting end users. CrashPlan helps enterprises and institutions reduce storage costs with innovative storage strategies, like zero-cost backup to OneDrive, while maintaining control and visibility across their backup environment.
Privacy | Legal | Cookie Notice | Free Trial

