A lot of our customers are currently moving to Azure and we have noticed that they are always very surprised when we explain them that their current configuration does not meet the requirements to meet the Microsoft Azure SLA…
Indeed, as you may not know, if you deploy a Virtual Machine into Azure, then the 99.95% does not apply to you. If you go on Microsoft Azure SLA Web Site, you can find the following statement:
So if you don’t put more than one Virtual Machine instance into an Availability Set, you have no guarantee that you will have a 99.95% uptime if your Virtual Machine goes down.
That’s where CloudocKit comes into play. In CloudocKit, we check that your environment is conform to Microsoft best practices and that you have everything properly configured to have the 99.95% SLA.
Let’s have a look at an example. As you can see in the following example (screengrab extracted from an CloudocKitdocument), we have a Virtual Machine named armVM that has no Availability Set defined:
CloudocKit automatically add the following information in the document for this Virtual Machine:
As you can see, CloudocKit explains you why you do not have the 99.95% Azure SLA in your current configuration and also gives you a link on how to fix it: you have to add an additional Virtual Machine and configure the Availability Set appropriately.
So at the end of the day, sure it can cost you more if you follow the best practices but it will give you a highly available environment that meets the Azure SLA.