Backup vendors promote the idea that Microsoft (Office) 365 native recovery tools are cannot be used as viable backup options, and that organizations need third-party services to back up their Microsoft 365 data.
Afi is a developer of Microsoft 365 backup service, but we do not share this view.
We believe that native M365 recovery capabilities provide a powerful tool set that has advantages over third-party M365 backup services. Specifically, they enable continuous M365 data backup and are tightly integrated with M365 management tools and access roles.
Some organizations need a longer retention period than provied by the native M365 data recovery (~93 days) and they may use E3/E5 Compliance Center retention policies to achieve unlimited retention (only limited by their budget).
In this blog post we’ll discuss the main capabilities of Microsoft 365 retention policies, pros, cons and the cost of using compliance retention for Microsoft 365 backup. Check our other blog post if you want to learn more about Microsoft 365 backup & recovery for SharePoint or for Teams data.
Do others use native M365 backup & recovery tools?
44% Microsoft 365 users leverage native M365 data protection for their backup strategy, while 32% use a 3rd party M365 backup and 20% have no Microsoft 365 backup strategy at all.
This data is based on a survey of 102 of Microsoft 365 users conducted by Afi in Dec 2020 (the users don’t include Afi customers). These results are in line with with similar surveys by Gartner 1 and IDC2.
Only around 4% of organizations rely on Microsoft Compliance Center retention policies to backup their Microsoft 365 data, meaning that an organization is 10x+ times more likely to use standard M365 data recovery than Compliance Retention policies.
The main reason for the low adoption of Compliance Center retention policies is their low availability and cost. Compliance Center features are only included in the most senior E3 and E5 Microsoft 365 plans that account for 16% of all business Microsoft 365 seats. And even the organizations that have E3 and E5 licenses may not have them for all users when mixing multiple M365 subscriptions to use cheaper plans for non-executive or frontline workers.
If you have a Microsoft 365 business subscription ($12.5-$20 depending on the plan) and want to upgrade to E3/E5, your price will increase by $7.5/month/user or more. See section 3 for more details on Compaliance Center retention policies’ cost.
How Microsoft 365 Retention Policies Work
You can enable retention for most Microsoft 365 applications and their data types. Once a retention policy is on, it makes sure that the existing items (at the moment when the retention policy is created) and all new data remain in Microsoft 365 for a prescribed period of time.
If users or admins delete data, the retention policy will remove it from Microsoft 365 applications, but the items will still be accessible & searchable using Compliance eDiscovery and in the Preservation library.
- Versions are retained for libraries where it's enabled
- Folder structures can be recovered from eDiscovery
- Site looks/themes and related settings not retained
- SharePoint memebership permissions are not preserved
- Sharing and access permissions aren't preserved
- Messages (drafts, in-place archive) & attachments retained
- Entire mailbox (sub)folder structures is preserved
- Teams messages captured sent by user are retained
- Site looks/themes and related settings not retained
- Calendar items and tasks with no end date are not retained
- Chats and channel (private/public) messages are retained
- Message attachments aren't retained by default (you need to separately enable retention for SharePoint & user OneDrives)
You can enable retention policies for MS Groups, but they'll only retain SharePoint data linked to the groups. No user membership, permissions & other metadata is backed up by retention policies.
The retention policies preserve all email messages, including unsent drafts, messages moved to the trash bin, messages stored in the Archived folder as well as in the in-place archive.
Exchange data can be exported in a PST file or a set of individual messages using the eDiscovery admin interface. Administrators with eDiscovery permissions can also access deleted messages in Recoverable Items Exchanage folder.
Although Microsoft recommends enabling a separate retention policy to capture Teams data, the policy we enabled for Exchange mailboxes also captured a system folder TeamsMessagesData with all Teams channel and individual messages that the Exchange users sent (though not the messages they received).
SharePoint Online and OneDrive
Compliance retention helps retain files and list items and their versions. The versions are retained only if the versioning is enabled for the library/OneDrive.
The items can be exported offline in their original folder structure. If there is more than one version of a file (list), all of them will be exported (old versions will have "_vX" added to them where X is the version number).
How Standard Versioning Works With Retention
Retention policies are often described to retain all document/item versions created, but this is not 100% correct.
The retention policies rely on the standard SharePoint & OneDrive versioning mechanism to retain versions. Retention policies retain versions only if the standard versioning is enabled. By default, the versioning is turned on for Document Libraries and OneDrives and the number of retained versions is set to 500. No versions are retained for other data types (lists, web pages, etc) by default.
The standard versioning is available in all Microsoft 365 plans, but when it is used without the retention policies it is significantly limited by the fact that users can accidentally or intentionally delete file versions. When you enable the compliance retention you overcome this limitation as Microsoft 365 will not allow to delete versions while a relevant retention policy is on for the data (see Deletion flow for details on what happens to versions if you delete an entire file).
You can disable or enable versioning for each document library and list (one by one) when you create it or later. The settings allow to retain up to 50,000 versions for documents and lists. Admins can also disable versioning entirely (this is the default setting for lists).
Cost of Retention Policies
Retained data and versions do count towards your Microsoft 365 storage quota making it an important component of cost of using compliance retention as a backup option.
In our experience the additional storage consumption associated is most relevant for SharePoint and OneDrive data:
- OneDrive for Business storage is in theory unlimited in E3/E5 subscription plans. Once your users exceed 1TB you can request Microsoft support to increase/remove the limit. However, you cannot increase the limit for all users at once and instead have to address each user’s limit each time he/she reaches it in stages, following the Microsoft process which takes time if you have many users
- The total SharePoint limit (pooled across all SharePoint sites in your Microsoft 365 tenant) is set at 1TB + 10GB x number of M365 users in your tenant. Whenever you exceed the limit, you need delete data or purchase additional storage priced at $200/month/TB (when paid annually), or $250/month/TB (when paid monthly).
Storage limits are less relevant for Exchange online because E3/E5 plans include unlimited auto-expanding archiving and for Teams because most of Teams data is stored on SharePoint sites and user OneDrives.
How Much additional storage Retention generates in 1 year
Let's estimate the average storage requirements for using retention policies as a backup with 1 year history.
- In the example below the domain has 1,000 users and 6TB of data across all SharePoints (6 GB of SharePoint storage per user is the global average across all our customers)
- 1-year versioning is estimated to add +90% to the total storage (the assumptions related to the change rate and avg. number of versions per year are based on those metrics amount Afi customers)
- Retained deleted data will add 10% of storage
- As a result, the total storage will grow from 6TB to 12TB due to 1-year retention & versioning, slightly exceeding Microsoft 365 licensing limit (11TB).
Neglecting the small storage overage, 1-year retention only additional cost the user licenses upgrade. The incremental cost will depend on your current plan. If you have Business Premium licenses ($20/user/month), then the incremental cost to upgrage to E3 ($32/user/month) will be $12/user/month.
The cost of retention policies as backup?
Most organizations require 3+ years retention for backups. If you extend the retention policies period to 3 years, then the additional storage in example above will grow to approx. 24TB (using the same assumptions):
- the 24TB total storage will exceed Microsoft licensing limit by 13TB
- to accommodate the overage you can to purchase storage capacity
- Microsoft offers additional storage in chunks of 1TB priced at $200/month
- the total cost of additional storage will thus be $2,600/month (=$200*13TB)
- this translates into $2/user/month (based on 1,000 users in our example).
If you combine the $2/user/month in storage costs with the incremental price of E3 licenses ($12/user or more), then the total cost of using retention policies is $14/user/month. This is significantly more expensive than the price of third-party backup solutions (typically $1.5-5/user/month, depending on solution).
At the same time, if you already have Microsoft 365 E3 licenses then the incremental $2/user/month cost of storage is very close to the cost of a third party backup solution.
Backup & Recovery with Retention Policies
You can enable retention policies for the users that have E3/E5 licenses using the following steps:
- Go to http://compliance.microsoft.com/ -> Policies -> Retention
- Create a new policy and select the type of resources (or individual SharePoints/users/Teams that you’d like to apply it to
It may take up to a few hours for the policy to take effect. Once it is applied, the data will follow the retention cadence you specified in the policy and you can use the eDiscovery module to export it offline. If you need to recover data back to Microsoft 365, you will have to first download it offline and then upload it manually to the SharePoint/Exchange/OneDrive resources.
Check Microsoft documentation for detailed steps on how to enable and customize compliance retention policies.
All product names are trademarks or registered trademarks of their respective holders; use of them does not imply any affiliation with or endorsement by them.