Locations & Regions

Locations & Regions

Locally uses its own region names rather than Azure's. This is a deliberate safety measure - you always know whether a deployment is targeting Locally or real Azure.

Built-in regions

Every Locally installation includes these regions, all within the Europe geography:

---

Custom regions

This is in preview behind a feature flag, so the Regions page only appears in the Locally Dashboard once the flag is on.

You can define your own region names to match your team's conventions - for example dublin, seattle, or even Azure's own names like westeurope if you prefer a 1:1 match with your production regions. This lets every developer work against a region layout that mirrors your production topology, without needing a live Azure environment.

---

Using an Azure environment's regions

This is in preview behind the same feature flag as custom regions.

Instead of naming regions yourself, you can point Locally at one of Azure's own environments. The Regions page in the Locally Dashboard has a Use Locations From selector - pick Azure Public, Azure China or Azure US Government instead of Locally, and it will serve that environment's regions. If your production topology sits in westeurope and northeurope, your local environment can use those same names.

The regions each environment provides:

Azure Public 59 regions

Region	CLI value
Australia Central	australiacentral
Australia Central 2	australiacentral2
Australia East	australiaeast
Australia Southeast	australiasoutheast
Austria East	austriaeast
Belgium Central	belgiumcentral
Brazil South	brazilsouth
Brazil Southeast	brazilsoutheast
Canada Central	canadacentral
Canada East	canadaeast
Central India	centralindia
Central US	centralus
Chile Central	chilecentral
Denmark East	denmarkeast
East Asia	eastasia
East US	eastus
East US 2	eastus2
France Central	francecentral
France South	francesouth
Germany North	germanynorth
Germany West Central	germanywestcentral
India South Central	indiasouthcentral
Indonesia Central	indonesiacentral
Israel Central	israelcentral
Italy North	italynorth
Japan East	japaneast
Japan West	japanwest
Jio India Central	jioindiacentral
Jio India West	jioindiawest
Korea Central	koreacentral
Korea South	koreasouth
Malaysia West	malaysiawest
Mexico Central	mexicocentral
New Zealand North	newzealandnorth
North Central US	northcentralus
North Europe	northeurope
Norway East	norwayeast
Norway West	norwaywest
Poland Central	polandcentral
Qatar Central	qatarcentral
South Africa North	southafricanorth
South Africa West	southafricawest
South Central US	southcentralus
South India	southindia
Southeast Asia	southeastasia
Spain Central	spaincentral
Sweden Central	swedencentral
Switzerland North	switzerlandnorth
Switzerland West	switzerlandwest
UAE Central	uaecentral
UAE North	uaenorth
UK South	uksouth
UK West	ukwest
West Central US	westcentralus
West Europe	westeurope
West India	westindia
West US	westus
West US 2	westus2
West US 3	westus3

Azure China 6 regions

Region	CLI value
China East	chinaeast
China East 2	chinaeast2
China East 3	chinaeast3
China North	chinanorth
China North 2	chinanorth2
China North 3	chinanorth3

Azure US Government 5 regions

Region	CLI value
US DoD Central	usdodcentral
US DoD East	usdodeast
US Gov Arizona	usgovarizona
US Gov Texas	usgovtexas
US Gov Virginia	usgovvirginia

---

Why not use Azure's region names?

Locally's regions don't exist in Azure, and Azure's regions don't exist in Locally. This creates a two-way safety net:

• Use an Azure region like westeurope against Locally → the request fails because the region isn't recognised.
• Use a Locally region like berlin against Azure → the request fails because Azure doesn't have that region.

Either way, a misconfigured deployment fails fast rather than silently hitting the wrong environment.

Using an Azure environment's regions gives up the first of those - westeurope becomes valid in both - which is why the prefix matters more once you do.