Skip to content

Commit 63ccc00

Browse files
committed
Added select azure regions
1 parent d35f7d4 commit 63ccc00

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/reliability/regions-overview.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,16 @@ Every region is contained within a single *geography* that serves as a fixed dat
2929
> [!NOTE]
3030
> Most regions are available to all Azure customers. However, some regions belong to *sovereign cloud* geographies, which are available to some customers in specific geographic areas with stringent data residency regulations. Sovereign cloud regions work the same way as other regions, however they're often limited in the services and features of services that they provide. For more examples of limited service availability in sovereign cloud regions, see [Compare Azure Government and global Azure](/azure/azure-government/compare-azure-government-global-azure)) or [Availability of services for Microsoft Azure operated by 21Vianet](/azure/reliability/sovereign-cloud-china).
3131
32+
## Select Azure regions
33+
34+
When you select Azure regions for your solution, consider the following factors:
35+
36+
- **Latency**. Select regions that are geographically close to your users to reduce latency. For example, if your users are in the United States, you might select a region in the United States or Canada.
37+
- **Availability zones**. Select regions that support availability zones to provide redundancy and fault isolation. Make sure that you spread your resources across multiple availability zones in the region.
38+
- **Multi-region**. Multi-region may be required for your workload, based on your business continuity planning. Some Azure services use region pairs to support geo-replication and geo-redundancy, while others use availability zones as their primary means of redundancy. Furthermore, many Azure services support geo-redundancy whether the regions are paired or not, and you can design a highly resilient solution whether you use paired regions, nonpaired regions, or a combination of both. To learn more about the approach for each service see [Reliability guides by service](./overview-reliability-guidance.md).
39+
40+
For more detailed information on how to select regions, see [Select Azure regions](/azure/cloud-adoption-framework/ready/azure-setup-guide/regions).
41+
3242
## List of regions
3343

3444
For a list of Azure regions, see [List of Azure regions](./regions-list.md). If you want more details on regions, including data residency and regulatory compliance, see the [Microsoft Datacenters Map](https://datacenters.microsoft.com/globe/explore/).

0 commit comments

Comments
 (0)