This Microsoft Azure Regions Interactive Map shows the locations of each of the Microsoft Azure cloud regions plotted on a map. The map code is built using the Azure Maps Web SDK

Disclaimer: This is an unofficial map of Azure Regions and is not endorsed by or affiliated with Microsoft. The official Azure region data may differ from what is displayed here.

This map was last updated October 11, 2023 with the latest list of Azure Regions.

Frequently Asked Questions

How many Azure Regions and Datacenters are there?

As of 2023, Microsoft Azure consists of 60 regions, 200 datacenters, 190 points of presence, and over 175,000 miles of terrestrial and subsea fiber worldwide, which connects the Internet at strategic global edge points of presence.

Source: https://datacenters.microsoft.com/

What is an Azure Region? Is it a single datacenter?

An Azure Region, in the context of the Microsoft Azure cloud, is not a single datacenter but a geographical area or location where Microsoft has multiple datacenters. These datacenters are strategically located within a region to provide redundancy, scalability, and high availability for Azure services and resources. In fact, most of the Azure regions are made up of 3 or more seprate data centers.

Each Azure Region consists of one or more datacenter buildings, also known as Availability Zones, which are typically located close to each other to minimize latency and provide data redundancy. The Azure regions that include Availability Zone support (which is almost all, if not all of them now) when configuring a Virtual Machines hosting will be comprised of at least 3 data centers; as each Availability Zone is a separate data center. These datacenters within a region are interconnected directly to each other through high-speed networks.

The main reasons for having multiple datacenters within an Azure Region include:

  • Redundancy
    Multiple datacenters within a region ensure that if one datacenter experiences issues, services and data can be quickly moved to another datacenter, minimizing downtime.
  • High Availability
    Azure services and resources deployed within a region can leverage the redundant infrastructure to provide high availability and fault tolerance.
  • Data Residency and Compliance
    Some organizations have specific requirements about the geographical location of their data. Azure Regions allow customers to choose a region that aligns with their data residency and compliance needs.
  • Low Latency
    By having datacenters close to each other within a region, Azure can minimize network latency and provide faster response times for services.

Azure offers multiple regions across the world, and customers can choose the region that best meets their needs when deploying their applications and data. It’s essential to consider the location of the Azure Region when designing your Azure architecture, as it can impact factors such as data latency, data sovereignty, and disaster recovery planning.

What’s the source of this Azure Region location data?

The following Azure CLI commands were used to retrieve the Latitude / Longitude (geocode) coordinates of each of the Microsoft Azure Regions (or locations):

# Azure CLI 2.0
az account list-locations > azure_regions.json

# Azure CLI 1.0
azure location list --json > azure_regions.json

This Azure CLI command will output a JSON file containing the Azure Region data. This JSON file is pulled directly into this app for display.

Additional data has been manually compiled / generated to include non-Public Cloud regions / locations; such as Germany, China, and the US Gov / DoD as well.

All geocode locations for Azure Regions are estimates. They do not represent the actual physical location for specific data centers.

More specifically, Here’s the command used to generate the JSON of Azure Regions that is displayed on the map:

az account list-locations -o json --query "[].{displayName:displayName,latitude:metadata.latitude,longitude:metadata.longitude,name:name}" > azure_regions.json

The data generated is in the following format with just the data needed by the JavaScript that generates the above map:

    "displayName": "East US",
    "latitude": "37.3719",
    "longitude": "-79.8164",
    "name": "eastus"

How accurate are the points / geocodes?

The accuracy is basically to the general geographic region where the Azure Regions are located. Microsoft doesn’t disclose the actual location or street address of the physical datacenters for security reasons. Much of the data on this map is taken directly from the geocode that Microsoft publishes for the datacenters. Other data (such as Germany, China, and US Gov / DoD) just point to the City or Region that Microsoft has indicated the region is in.

Microsoft MVP

Chris Pietschmann is a Microsoft MVP, HashiCorp Ambassador, and Microsoft Certified Trainer (MCT) with 20+ years of experience designing and building Cloud & Enterprise systems. He has worked with companies of all sizes from startups to large enterprises. He has a passion for technology and sharing what he learns with others to help enable them to learn faster and be more productive.
HashiCorp Ambassador Microsoft Certified Trainer (MCT) Microsoft Certified: Azure Solutions Architect