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
#Customer intent: As an engineer responsible for business continuity, I want to learn how to enable zone redundancy for my Azure API Management instances.
@@ -30,7 +30,7 @@ For more detailed information about reliability features of API Management, such
30
30
31
31
## Default availability zone support
32
32
33
-
When you create a new API Management instance in the **Premium** tier in a region that supports availability zones, or you [deploy API Management to a new region](api-management-howto-deploy-multi-region.md), API Management offers two types of availability zone support:
33
+
When you create a new API Management instance in the **Premium** tier in a region that supports availability zones, or you [deploy API Management to an additional region](api-management-howto-deploy-multi-region.md), API Management offers two types of availability zone support:
34
34
35
35
*Automatic*. Azure API Management offers automatic availability zone support when you don't specify which availability zones to use.
@@ -57,6 +57,8 @@ Azure API Management offers two types of availability zone support when you depl
57
57
58
58
-*Manual*. Azure API Management offers manual availability zone support when you explicitly specify which availability zones to use.
59
59
60
+
With availability zone support, Azure API Management replicates service components across zones for high availability. In the primary region, these components include the gateway (scale units), management plane, and developer portal. In secondary regions, only the gateway units are replicated. See [Multi-region support](#multi-region-support) for more information about secondary regions.
61
+
60
62
### Automatic availability zone support
61
63
62
64
With automatic availability zone support, you can choose either a single unit or multi-unit instance configuration to achieve zone-redundancy:
@@ -69,7 +71,7 @@ With automatic availability zone support, you can choose either a single unit or
69
71
70
72
If you want to explicitly select the availability zones to use, you can choose between zone-redundant and zonal configurations:
71
73
72
-
-*Zone-redundant*: Manually configure zone redundancy for an API Management instance in a supported region to provide redundancy for service components. In the primary region, these components include the gateway, management plane, and developer portal. In secondary regions, only the gateway is replicated. When you select two or more availability zones to use, Azure automatically replicates the service components across the selected zones.
74
+
-*Zone-redundant*: Manually configure zone redundancy for an API Management instance in a supported region to provide redundancy for service components. When you select two or more availability zones to use, Azure automatically replicates the service components across the selected zones.
73
75
74
76
-*Zonal*: The API Management service components are deployed in a single zone that you select within an Azure region. All of the units are placed into the same availability zone.
75
77
@@ -203,7 +205,7 @@ When adding a region, you configure:
203
205
204
206
- The number of units that region is to host.
205
207
206
-
-Optional [availability zone support](#availability-zone-support), if that region provides availability zones.
208
+
-[Availability zone support](#availability-zone-support), if that region provides availability zones.
207
209
208
210
-[Virtual network settings](/azure/api-management/virtual-network-concepts) in the added region, if networking is configured in the existing region or regions.
0 commit comments