I recently detailed how to
I thought it was about time to take a look at the cost of Microsoft 365 Backup to see how it compares to other offerings.
The interesting thing is that billing is a little different from other third party solution. Microsoft 365 Backup is based on storage not on users. This makes direct comparison hard, so let me just focus on Microsoft 365 Backup is billed for now.
If you take a look at the Microsoft 365 Backup site you’ll see that at this point in time the service is billed at US$0.15 per GB per month. That is no matter what the data is whether, SharePoint, Exchange, OneDrive for Business. Data is data and the backup cost is per GB per month.
You’ll find this from Microsoft:
Pricing model for Microsoft 365 Backup (Preview)
in which you need to note:
there is also a Microsoft 365 Backup pricing spreadsheet here:
https://aka.ms/M365BackupCalculator
but bottom line is to add up all your data storage and multiple by US$0.15, right? Not so quick. Per the documentation:
The size of protected content is equal to the cumulative size of the mailboxes being protected plus the size of the SharePoint sites and OneDrive accounts being protected (that is, the size of the live OneDrive accounts and SharePoint sites as display in the live sites’ usage reports) plus the size of any deleted/versioned content held for restore during the protection period.
Let’s say that I have 1,024GB (1TB) of total data I wanted backed up across SharePoint, Exchange and ODFB. That is relatively easy to determine via the usage reporting tools in Microsoft 365. Where it becomes more challenging is determining the deleted data capacity.What exactly is that?
After some digging, in essence, deleted data is data that has been purged from the service. For example, deleted data is data that was backed up in the SharePoint Online recycle bin that has now expired the standard retention period of 93 days and is no longer in SharePoint Online. Thus, deleted data, is largely, data that no longer resides in the service but has been backed up inside the service at some stage. Ok, but how will I know what that is? That’s a challenge. I can’t find an easy way of determining that. Maybe we’ll see that soon in Microsoft 365 Backup as I think we need to have it, otherwise knowing the costs becomes challenging.
For now, let’s say that the deleted data is exactly the same as my source data inside the services currently being backed up. Thus, if I have 1TB of live data to be backed up, let’s assume the total amount being sent to Microsoft 365 Backup is 2TB. Thus, the cost of this would be:
2,048 GB x US$0.15 = US$307.20 per month
If I assume say 30 users in that tenant of that size then I get roughly US$10 per month per user. I’m taking this as the high end benchmark for SMB in terms of tenant size. I’m just trying to get an average benchmark price with these numbers. That figure is around US$10 per user per month for Microsoft 365 Backup (with plenty of assumptions I admit, but you got to start somewhere)
I appreciate this is all very subjective but upon first glimpse, but looking at a few example tenants around the place and doing the same sort of calculations, I found that, at the very least, Microsoft 365 Backup seems to be comparable to the pricing of third party products on a purely economic basis, which I found interesting.
Of course, price isn’t the only measure of product value and the more live and deleted data you have as well as the longer you retain that data the more expensive it becomes with Microsoft 365 Backup. However, interestingly, Microsoft 365 Backup is pretty cost effective for smaller environments, that is, typically those in SMB. The challenge is that most competitive products are a flat fee per month per user (like a Microsoft 365 Business Premium license is), whereas Microsoft 365 Backup is a consumption based (Azure) fee (i.e. you pay for what you use). That leads to variable costs which many people don’t favour. But, remember with Microsoft 365 Backup your overall backup cost could be much lower as well. It all depends on what you use.
It is still early days for Microsoft 365 Backup and I remind you that it is still in preview at the moment. I’ll take a look a feature comparisons to third party services in an upcoming article but I found it interesting that Microsoft 365 Backup has taken a different approach to pricing that could work well in SMB, but I’ll take a closer look at the feature set in an upcoming article and hopefully present a better picture of how you should be considering Microsoft 365 Backup.
For me, that fact that it generally seems to be price competitive in SMB environments is a plus (aka in the ballpark). Not definitive, I grant you to replace what might be in place with other solutions from third parties, but still it is a good start in the comparison journey.
I’ll have more to share soon on what I’ve found and how I believe Microsoft 365 Backup can work in SMB.
CIAOPS 