# Atlas Azure Regions Mapping > Source-anchored research for Atlas Azure Regions Mapping. Run status: COMPLETED. Parent: [MongoDB Atlas on Azure](https://llms-explorer.com/tree/mongodb-atlas-on-azure/) · 5 facets · 16 facts · page: https://llms-explorer.com/tree/atlas-azure-regions-mapping/ ## How it works - Microsoft warns that availability-zone support for a region does not guarantee support by every service. MongoDB states that Atlas automatically distributes dedicated cluster nodes across zones in supported regions and uses fault domains where zones are unavailable; clusters deployed before September 13, 2019 are not automatically redistributed when zones become available. (high confidence) (verified as of 2026-10-24) — [source](https://learn.microsoft.com/azure/reliability/availability-zones-region-support) - Some Atlas-listed Azure regions may require Azure subscription access approval for private networking resources. Microsoft separately identifies restricted regions and documents a region access request process; an Atlas mapping is not proof that a subscription can create resources there. (high confidence) (verified as of 2026-10-24) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) ## How-to and procedures - Use the region format documented for each operation: the Atlas cluster API uses Atlas Region values, whereas the Atlas CLI Azure private-endpoint creation example passes --region eastus. (high confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) ## Problems, failure modes and limitations - Atlas cluster configuration uses Atlas region identifiers alongside providerName=AZURE; Azure location strings cannot simply be substituted into these fields. (high confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) ## Comparisons and alternatives - Dedicated Search Node coverage differs from general Atlas cluster coverage: MongoDB lists US_WEST, US_WEST_CENTRAL, CANADA_EAST, UK_WEST and other Azure regions as unsupported for Search Nodes, and identifies ITALY_NORTH as available for low-CPU Search Nodes only. (low confidence) (verified as of 2026-10-24) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) ## Facts and statements - For clusters, Azure eastus maps to US_EAST, while eastus2 maps to US_EAST_2; both Azure locations are in Virginia. (high confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - The cluster table maps centralus to US_CENTRAL, westus to US_WEST, westus2 to US_WEST_2, and westus3 to US_WEST_3. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Online Archive Azure private-endpoint instructions list eastus2/US_EAST_2, brazilsouth/BRAZIL_SOUTH, and westeurope/EUROPE_WEST. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/online-archive/config-private-endpoint.md) - MongoDB states that every region in its supported-region table supports dedicated M10+ clusters, while Free and Flex clusters are supported only in some regions. A valid region mapping therefore does not establish availability for every cluster tier. (low confidence) (verified as of 2026-10-24) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Some higher-cost secondary DR regions require Azure subscription approval before private networking resources can be created there. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - A supported Atlas Azure region can temporarily lack instance capacity; documented remedies include another region, a larger tier, or waiting. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Microsoft documents Azure programmatic names and provides az account list-locations, Get-AzLocation, and the Resource Manager REST API as ways to retrieve them. These enumerate Azure regions; Atlas support must be checked against MongoDB's separate supported-region table. (high confidence) — [source](https://learn.microsoft.com/azure/reliability/availability-zones-region-support) - Atlas cluster configuration uses Atlas region identifiers. For Azure East US, the native name eastus maps to US_EAST; Pulumi demonstrates providerName="AZURE" with regionsConfigs[].regionName="US_EAST". (high confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Representative Americas mappings are centralus → US_CENTRAL, eastus2 → US_EAST_2, westus2 → US_WEST_2, westus3 → US_WEST_3, canadacentral → CANADA_CENTRAL, brazilsouth → BRAZIL_SOUTH, chilecentral → CHILE_CENTRAL, and mexicocentral → MEXICO_CENTRAL. (low confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Representative Europe mappings are northeurope → EUROPE_NORTH, westeurope → EUROPE_WEST, uksouth → UK_SOUTH, germanywestcentral → GERMANY_WEST_CENTRAL, polandcentral → POLAND_CENTRAL, and spaincentral → SPAIN_CENTRAL. (low confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/) - Representative Asia-Pacific, Africa and Middle East mappings are eastasia → ASIA_EAST, southeastasia → ASIA_SOUTH_EAST, centralindia → INDIA_CENTRAL, australiaeast → AUSTRALIA_EAST, japaneast → JAPAN_EAST, southafricanorth → SOUTH_AFRICA_NORTH, and uaenorth → UAE_NORTH. (low confidence) — [source](https://www.mongodb.com/docs/atlas/reference/microsoft-azure/)