Regions for virtual machines in Azure
Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets
It is important to understand how and where your virtual machines (VMs) operate in Azure, along with your options to maximize performance, availability, and redundancy. This article provides you with an overview of the availability and redundancy features of Azure.
What are Azure regions?
Azure operates in multiple datacenters around the world. These datacenters are grouped in to geographic regions, giving you flexibility in choosing where to build your applications.
You create Azure resources in defined geographic regions like 'China East', 'China North', or 'China East 2'. You can review the list of regions and their locations. Within each region, multiple datacenters exist to provide for redundancy and availability. This approach gives you flexibility as you design applications to create VMs closest to your users and to meet any legal, compliance, or tax purposes.
Special Azure regions
Azure has some special regions that you may wish to use when building out your applications for compliance or legal purposes. These special regions include:
- China East and China North
- These regions are available through a unique partnership between Microsoft and 21Vianet, whereby Azure does not directly maintain the datacenters. See more about Microsoft Azure operated by 21Vianet.
Region pairs
Each Azure region is paired with another region within the same geography. This approach allows for the replication of resources, such as VM storage, across a geography that should reduce the likelihood of natural disasters, civil unrest, power outages, or physical network outages affecting both regions at once. Additional advantages of region pairs include:
In the event of a wider Azure outage, one region is prioritized out of every pair to help reduce the time to restore for applications.
Planned Azure updates are rolled out to paired regions one at a time to minimize downtime and risk of application outage.
Data continues to reside within the same geography as its pair for tax and law enforcement jurisdiction purposes.
Examples of region pairs include:
| Primary | Secondary |
|---|---|
| China North | China East |
| China North 2 | China East 2 |
You can see the full list of regional pairs here.
Feature availability
Some services or VM features are only available in certain regions, such as specific VM sizes or storage types. There are also some global Azure services that do not require you to select a particular region, such as Microsoft Entra ID, Traffic Manager, or Azure DNS. To assist you in designing your application environment, you can check the availability of Azure services across each region. You can also programmatically query the supported VM sizes and restrictions in each region.
Storage availability
Understanding Azure regions and geographies becomes important when you consider the available storage replication options. Depending on the storage type, you have different replication options.
Azure Managed Disks
- Locally redundant storage (LRS)
- Replicates your data three times within the region in which you created your storage account.
Storage account-based disks
- Locally redundant storage (LRS)
- Replicates your data three times within the region in which you created your storage account.
- Zone redundant storage (ZRS)
- Replicates your data three times across two to three facilities, either within a single region or across two regions.
- Geo-redundant storage (GRS)
- Replicates your data to a secondary region that is hundreds of miles away from the primary region.
- Read-access geo-redundant storage (RA-GRS)
- Replicates your data to a secondary region, as with GRS, but also then provides read-only access to the data in the secondary location.
The following table provides a quick overview of the differences between the storage replication types:
| Replication strategy | LRS | ZRS | GRS | RA-GRS |
|---|---|---|---|---|
| Data is replicated across multiple facilities. | No | Yes | Yes | Yes |
| Data can be read from the secondary location and from the primary location. | No | No | No | Yes |
| Number of copies of data maintained on separate nodes. | 3 | 3 | 6 | 6 |
You can read more about Azure Storage replication options here. For more information about managed disks, see Azure Managed Disks overview.
Next steps
For more information, see Azure regions.