You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/availability-zones/az-overview.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,12 @@ ms.custom: references_regions
14
14
15
15
Azure regions and availability zones are designed to help you achieve resiliency and reliability for your business-critical workloads. Azure maintains multiple geographies. These discrete demarcations define disaster recovery and data residency boundaries across one or multiple Azure regions. Maintaining many regions ensures customers are supported across the world.
16
16
17
+
## Regions
18
+
17
19
Each Azure region features datacenters deployed within a latency-defined perimeter. They're connected through a dedicated regional low-latency network. This design ensures that Azure services within any region offer the best possible performance and security.
18
20
21
+
## Availability zones
22
+
19
23
Azure *availability zones* are physically separate locations within each Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved because of redundancy and logical isolation of Azure services. To ensure resiliency, a minimum of three separate availability zones are present in all availability zone-enabled regions.
20
24
21
25
Azure availability zones are connected by a high-performance network with a round-trip latency of less than 2 ms. They help your data stay synchronized and accessible when things go wrong. Each zone is composed of one or more datacenters equipped with independent power, cooling, and networking infrastructure. Availability zones are designed so that if one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones.
@@ -30,7 +34,7 @@ You can build high availability into your application architecture by using Azur
30
34
31
35
Azure *availability zones-enabled services* are designed to provide the right level of resiliency and flexibility. They can be configured in two ways. They can be either *zone redundant*, with automatic replication across zones, or *zonal*, with instances pinned to a specific zone. You can also combine these approaches.
32
36
33
-
Some organizations require high availability of availability zones and protection from large-scale phenomena and regional disasters. Azure regions are designed to offer protection against localized disasters with availability zones and protection from regional or large geography disasters with disaster recovery, by making use of another region. To learn more about business continuity, disaster recovery, and cross-region replication, see [Cross-region replication in Azure](.../best-practices-availability-paired-regions.md).
37
+
Some organizations require high availability of availability zones and protection from large-scale phenomena and regional disasters. Azure regions are designed to offer protection against localized disasters with availability zones and protection from regional or large geography disasters with disaster recovery, by making use of another region. To learn more about business continuity, disaster recovery, and cross-region replication, see [Cross-region replication in Azure](../best-practices-availability-paired-regions.md).
34
38
35
39

Copy file name to clipboardExpand all lines: articles/availability-zones/az-region.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ In the Product Catalog, always-available services are listed as "non-regional" s
107
107
|[Azure App Service environments](../app-service/environment/zone-redundancy.md)||
108
108
|[Azure Active Directory Domain Services](../active-directory-domain-services/overview.md)||
109
109
|[Azure API Management](../api-management/zone-redundancy.md)||
110
-
|[Azure App Configuration](../azure-app-configuration/faq#how-does-app-configuration-ensure-high-data-availability.md)||
110
+
|[Azure App Configuration](../azure-app-configuration/faq.md#how-does-app-configuration-ensure-high-data-availability)||
111
111
|[Azure Bastion](../bastion/bastion-overview.md)||
112
112
|[Azure Batch](../batch/create-pool-availability-zones.md)||
113
113
|[Azure Cache for Redis](../azure-cache-for-redis/cache-high-availability.md)||
@@ -132,7 +132,7 @@ In the Product Catalog, always-available services are listed as "non-regional" s
132
132
|[Azure Web Application Firewall](../firewall/deploy-availability-zone-powershell.md)||
133
133
|[Azure Container Registry](../container-registry/zone-redundancy.md)||
134
134
|[Azure Event Grid](../event-grid/overview.md)||
135
-
|[Azure HD Insight](../hdinsight-use-availability-zones.md)||
135
+
|[Azure HD Insight](../hdinsight/hdinsight-use-availability-zones.md)||
136
136
|[Azure Network Watcher](../network-watcher/frequently-asked-questions.yml)||
137
137
| Network Watcher: [Traffic Analytics](../network-watcher/frequently-asked-questions.yml)||
138
138
|[Power BI Embedded](/power-bi/admin/service-admin-failover#what-does-high-availability)||
0 commit comments