Azure Regions

Get highly available, fast and scalable Azure cloud services from Microsoft. You may choose from these Azure regions:

• Australia Central (Canberra)
• Australia East (New South Wales)
• Australia Southeast (Victoria)
• Brazil South (Sao Paulo State)
• Canada Central (Toronto)
• Canada East (Quebec City)
• Central India (Pune)
• Central US (Iowa)
• East Asia (Hong Kong)
• East US (Virginia)
• East US 2 (Virginia)
• France Central (Paris)
• France South (Marseille)
• Germany West Central (Frankfurt)
• Germany North (Berlin)
• Japan East (Tokyo, Saitama)
• Japan West (Osaka)
• Korea Central (Seoul)
• Korea South (Busan)
• North Central US (Illinois)
• North Europe (Ireland)
• Norway East (Oslo)
• Norway West (Stavanger)
• South Africa North (Johannesburg)
• South Central US (Texas)
• South India (Chennai)
• Southeast Asia (Singapore)
• Switzerland North (Zurich)
• Switzerland West (Geneva)
• UAE North (Dubai)
• UK South (London)
• UK West (Cardiff)
• West Central US (Wyoming)
• West Europe (Netherlands)
• West India (Mumbai)
• West US (California)
• West US 2 (Washington)

Microsoft Azure uses the concept of an “Azure Region” as opposed to an “Azure datacenter” for each Azure location. Each Azure Region consists of multiple buildings, or datacenters. Each Region is at least the size of a city block. Typically, your data is stored in more than one building within the Region. If there were to be some type of outage within a Region, odds are that with the built-in redundancy, your access will not be impacted. 

If you are going to replace your on-premises infrastructure, a closer Azure Region may be best for you so that the network latency between your physical location and Azure is at its lowest.  If you are keeping your on-premises infrastructure for the foreseeable future, and you want to leverage Azure as your DR location, consider an Azure Region farther away from your physical location to provide some geographic redundancy at a lower cost.