Office 365 Backup Sizing Tool v2.6

analysisIf you have been following the CloudOasis blog, you will be aware of the Community WebApp called Office 365 Backup Sizing Tool. Two years ago I came up with the idea of using WebApp and manual entry to estimate the size of your Office 365 Backup for storage and compute.

Today, I’m pleased to announce the release of the new version of CloudOasis Office 365 Backup Sizing Tool, version 2.6. The new version delivers several enhancements and new features. In this blog post, I will list the new features added to version 2.6.

So let’s get started. The first step:

Manual Entry

Many requests were received requesting the addition of an option to manually provide the number of mailboxes, the size of the databases and so on. Finally, in version 2.6, I have added this option.  You can see this option by browsing to the Backup Sizing when you are using the online retrieval option:

Screen Shot 2020-04-02 at 10.29.03 am

Those without an Office 365 tenancy yet, and wish to estimate the backup size, costs and more, can choose the Manual entry from the main page:


Storage Cost Analysis

Officially, this becomes an integrated feature in the community edition now. This feature has been in test since version 2.5 and is now fully integrated into version 2.6. Storage costs based on the tenancy subscription RateCard offer ID pricing. After the RateCard pricing has been retrieved, the WebApp calculates the backup Blob Storage cost based on the required retention. The cost also includes the cost of the Azure APIs usage.

Screen Shot 2020-04-02 at 11.10.02 am

Azure Offer ID Pricing

Version 2.5 brought storage cost estimation based on Pay-As-You-Go. With version 2.6, I have added all the Azure offer IDs available, which help with retrieving the appropriate Azure Ratecard pricing, to better calculate the estimated pricing for each customer.

Screen Shot 2020-04-02 at 10.53.48 am

Compute Cost Analysis

To avoid a cloud cost shock, and to cover all the corners of the cloud cost analysis, version 2.6 also includes the cost of the compute required for hosting the backup infrastructure. After you estimate the storage size, the WebApp incorporates an intelligent algorithm to calculate the number of backup and proxies servers needed to protect and backup your Office 365. After the number of servers is calculated, the WebApp retrieves the cost of your Azure VM cost, as based on your VM size selection.

Screen Shot 2020-04-02 at 11.30.38 am

Last Note

I hope you find these new features and enhancements useful, and that you find them valuable when it comes to sizing and costing your Office 365 Backup solution. Also on this occasion, Now is the time to highlight several important points following many enquiries about the sizing tool; so, here we are:

  • CloudOasis Office 365 backup estimated tool is a community tool 
  • Designed and developed by CloudOasis as a community tool based on .Net
  • Hosted by CloudOasis on Azure Cloud
  • Costs of development and hosting carried by CloudOasis 
  • Using Microsoft Authentication best practice
  • No need for Admin user on Office 365 to be used; however, does require an Office 365 enabled user with at least a mailbox enabled
  • All data retrieval based on MS Graph APIs
  • No data stored locally. If you refresh the page, the tool retrieves the data again
  • Costs are calculated using Azure RateCard API
  • Compute Sizing is cross-referenced with the RateCard for costing

And finally, thank you for your support and feedback, and I hope you find this tool valuable. Please share this blog so that other users can benefit from the great new features.

11 thoughts on “Office 365 Backup Sizing Tool v2.6

  1. Thank you for adding clarification re: the account needed to run this tool, much appreciated

    No need for Admin user on Office 365 to be used; however, does require an Office 365 enabled user with at least a mailbox enabled

  2. hi, great tool! thanks.
    However, small request, can you put in the units (like TB, GB or %) where applicable? Makes it more readable

  3. Manual input gives me 17GB repository size fore 100 onedrives of 10 GB each with 5% changerate and 7days /6months retention. Bit sceptisch about that.

    • Hi Jeffery, Thanks for your feedback. The local storage requirement for the period you specified is: 30 GB. But if you wish to save the backup on Azure Blob storage then the size will be 17 GB (Cache 1 GB).

      • oh nevermind. i looked at “total size” wrong for an onedrive folder. i asumed it should have been multiplied by the number of drives, but it’s the sum of all drives you enter there off course. Need coffee 🙂

  4. This is a great tool thank you! Just to confirm – Where it gives me Local Repository and Object Storage values, is this displaying options for one or the other? i.e. if I purely use object storage my total required space will be less? Or do I need to factor both into my sizing estimates?

    • Hi James, thanks for your feedback. The estimation of Local and Object repositories can be found on the backup tab under Local and Object storage.

Leave a Reply