In this guide
Version history, the recycle bin, retention and backup are different tools. The first three help with specific scenarios within the service. A backup and restore policy defines which data is protected, for how long, which restore points exist, who can restore it and how quickly operations can resume after an error, deletion or attack.
Why there is confusion
Microsoft 365 includes many retention and recovery capabilities. OneDrive and SharePoint have version history and recycle bins, while Exchange and compliance features have their own retention mechanisms. These functions are useful, but should not all be treated as equivalent to an independently designed backup strategy.
The right question is “Which scenario do we need to recover from, to what point in time, and how quickly?”
What each mechanism does
- Version history: helps you return to previous versions of a file when the service and those versions remain available.
- Recycle bin: helps recover recently deleted content within the service’s limits.
- Retention: applies retention and deletion rules for specific business or regulatory needs.
- Backup/restore: organises restore points, protection scope, the restoration process and recovery targets. Microsoft now also offers Microsoft 365 Backup for supported workloads such as Exchange, OneDrive and SharePoint, alongside other solutions available on the market.
Design backup around restoration
A backup job showing “successful” does not prove that the business can recover. Define who checks jobs, who can request a restore, which versions must be retained and how restoration is verified.
For critical data, restore testing is part of the protection service, rather than an optional step after installation.
Frequently asked questions
Is OneDrive sync a backup?
Not on its own. Synchronisation keeps copies of data in multiple locations, but can also synchronise errors or deletions. Recovery depends on the available versions, retention and backup mechanisms.
Do I need a separate backup if I have retention policies?
It depends on the recovery targets. Retention and backup serve different needs and should be assessed separately.
What should I test?
At a minimum, recovery of a representative file or folder, mailbox or another supported workload, including the time and steps needed until the user confirms the result.
Related services and guides
Discuss your next step with UniLoud
Tell us which Microsoft 365 data you consider critical and how far back you may need to restore it. We will design a backup and restore policy with measurable targets.
