Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Availability options for Azure Virtual Machines description: Learn about the availability options for running virtual machines in Azure author: mimckitt ms.author: mimckitt ms.service: azure-virtual-machines ms.topic: concept-article ms.date: 12/05/2025 ms.reviewer: wwilliams ms.update-cycle: 1095-days # Customer intent: "As an IT manager, I want to understand the availability options for virtual machines in the cloud, so that I can ensure the resilience and uptime of our applications and data during outages." --- # Availability options for Azure Virtual Machines **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets This article provides an overview of the availability options for Azure virtual machines (VMs). ## Availability zones [Availability zones](/azure/reliability/availability-zones-overview?context=/azure/virtual-machines/context/context) expands the level of control you have to maintain the availability of the applications and data on your VMs. An Availability Zone is a physically separate zone, within an Azure region. There are three Availability Zones per supported Azure region. Each Availability Zone has a distinct power source, network, and cooling. By designing your solutions to use replicated VMs in zones, you can protect your apps and data from the loss of a data center. If one zone is compromised, then replicated apps and data are instantly available in another zone. > [!NOTE] > Regional resources may or may not exist in an Availability zone, and there is no insight into what physical or logical zone a regional resource is in. A failure in any of the availability zones in a region has the potential to bring down a regional VM. ## Virtual Machines Scale Sets [Azure virtual machine scale sets](flexible-virtual-machine-scale-sets.md) let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide high availability to your applications, and allow you to centrally manage, configure, and update many VMs. There is no cost for the scale set itself, you only pay for each VM instance that you create. Virtual machines in a scale set can also be deployed into multiple availability zones, a single availability zone, or regionally. Availability zone deployment options may differ based on the [orchestration mode](../virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md?context=/azure/virtual-machines/context/context). ## Availability sets An [availability set](availability-set-overview.md) is a logical grouping of VMs that allows Azure to understand how your application is built to provide for redundancy and availability. We recommended that two or more VMs are created within an availability set to provide for a highly available application and to meet the [99.95% Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/). There is no cost for the Availability Set itself, you only pay for each VM instance that you create. ## Load balancer Combine the [Azure Load Balancer](/azure/load-balancer/load-balancer-overview) with availability zones and scale sets to get the most application resiliency. The Azure Load Balancer distributes traffic between multiple virtual machines. For our Standard tier virtual machines, the Azure Load Balancer is included. Not all virtual machine tiers include the Azure Load Balancer. For more information about load balancing your virtual machines, see the Load Balancer quickstarts using the [CLI](/azure/load-balancer/quickstart-load-balancer-standard-public-cli) or [PowerShell](/azure/load-balancer/quickstart-load-balancer-standard-public-powershell). ## Azure Storage redundancy Azure Storage always stores multiple copies of your data so that it is protected from planned and unplanned events, including transient hardware failures, network or power outages, and massive natural disasters. Redundancy ensures that your storage account meets its availability and durability targets even in the face of failures. When deciding which redundancy option is best for your scenario, consider the tradeoffs between lower costs and higher availability. The factors that help determine which redundancy option you should choose include: - How your data is replicated in the primary region - Whether your data is replicated to a second region that is geographically distant to the primary region, to protect against regional disasters - Whether your application requires read access to the replicated data in the secondary region if the primary region becomes unavailable for any reason For more information, see [Azure Storage redundancy](/azure/storage/common/storage-redundancy) ## Azure Site Recovery As an organization you need to adopt a business continuity and disaster recovery (BCDR) strategy that keeps your data safe, and your apps and workloads online, when planned and unplanned outages occur. [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) helps ensure business continuity by keeping business apps and workloads running during outages. Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to secondary location, and access apps from there. After the primary location is running again, you can fail back to it. Site Recovery can manage replication for: - Azure VMs replicating between Azure regions. - On-premises VMs, Azure Stack VMs, and physical servers. ## Next steps - [Create a virtual machine in an availability zone](./linux/create-cli-availability-zone.md) - [Create a virtual machine in an availability set](./linux/tutorial-availability-sets.md) - [Create a virtual machine scale set](../virtual-machine-scale-sets/quick-create-portal.md)