What is the difference between the internal name and display name?

The internal name (like eastus or westeurope) is the lowercase code used in CLI, ARM templates and APIs. The display name (East US, West Europe) is the human-readable label shown in the Azure portal. They map one to one.

What is an Azure paired region?

Most Azure regions are paired with another region in the same geography for platform-managed replication and sequential update rollout. For example East US pairs with West US, so geo-redundant storage replicates between them automatically.

Do all Azure regions support availability zones?

No. Availability zones are physically separate data centres within a region, and only a subset of regions support them. Zone support is required for zone-redundant services and the highest single-region SLAs.

Why do some regions have no pair?

Newer regions and some single-region geographies (such as certain Asian or government regions) are not paired. For those you must design cross-region redundancy yourself rather than relying on the platform pairing.

How are Azure regions grouped into geographies?

A geography is a data-residency and compliance boundary that contains one or more regions, like United States or Europe. Geographies ensure data-residency and compliance requirements are honoured within market or sovereign boundaries.

Azure Region Codes Reference

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Azure region codes reference

An Azure region is a set of data centres in a defined geography, deployed within a latency-defined perimeter. Choosing one affects latency, cost, data residency and which services are available. This reference maps each Azure region’s internal name (used in CLI and ARM) to its display name, geography, availability-zone support and paired region for replication.

How it works

Azure uses two identifiers per region: a lowercase internal name (eastus, westeurope) for automation, and a display name (East US, West Europe) for the portal. Regions belong to a geography — a compliance and data-residency boundary.

Most regions have a paired region in the same geography. Azure uses pairs to:

replicate geo-redundant storage automatically,
roll out planned platform updates one region of a pair at a time,
prioritise recovery of one region in a pair during a broad outage.

Availability zones are isolated data centres inside a region; only zone-enabled regions support zone-redundant deployments.

Tips and notes

Use the internal name in az CLI, ARM/Bicep templates and Terraform.
Prefer zone-enabled regions for production workloads needing high single-region SLAs.
Check the paired region when designing geo-redundant storage and DR.
Some newer regions have no pair — plan cross-region redundancy manually there.