Skip to main content

Azure VM Availability SLA

This post is focusing on the availability SLA of Azure Virtual Machines. You might think that there is not so much to say about it, even so, the reality is different.
Let me ask you a simple question when you talk about availability and Azure Virtual Machines:
  1. When do you have 99.9% availability?
  2. When do you have 99.95% availability?

Case 1: Single VM
When there is only one instance of VM, the SLA guaranty us minimum 99.9% availability. There are no actions that you can take to improve this value. Remember that this is the minimum value that is guaranteed. This value means that the real value can be higher than 99.9%.

Case 2: Two or more VMs in the same Availability Set
When there are two or more VMs in the same Availability Set, you have the availability SLA to 99.95%. This value means that:
  • The availability of the two or more VMs combined is at least 99.95%. 
  • On the other hand, this does not mean that for each VM the availability is 99.95%. Per node the availability can be lower but combined, you get 99.95%.

Case 3: Single VM inside a Scale Set
When you have only one VM in a Scale Set, the same SLA is offered as for a Single VM – 99.9%. Having a single, VM inside a VM does not offer additional VM availability.

Case 4: Two or more VMs on a Scale Set with at least Two Fault Domains
Having at least two VMs inside at least two fault domains guaranty us an availability SLA at 99.95%.

Things to consider
There is no increased availability offered if you have only one VM as a single VM or inside a Scale Set (99.9%). Inside a Scale Set, if you have two VMs inside the same Fault Domain the SLA for availability remains the same as for one VM (99.9%). It is required to have multiple VMs inside different Fault Domain or inside an Availability Set to get 99.95% availability.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...