Skip to content

Commit fdf6f39

Browse files
author
gitName
committed
wip
1 parent 85de260 commit fdf6f39

File tree

4 files changed

+7
-16
lines changed

4 files changed

+7
-16
lines changed

articles/reliability/overview-reliability-guidance.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ This section provides links to reliability guidance for many Azure services. Eac
4242
|Azure Application Gateway (V2)||[Autoscaling and High Availability](../application-gateway/application-gateway-autoscaling-zone-redundant.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
4343
|Azure Application Gateway for Containers| [Reliability in Azure Application Gateway for Containers](reliability-app-gateway-containers.md ) ||
4444
|Azure API for FHIR®||[Disaster recovery for Azure API for FHIR](../healthcare-apis/azure-api-for-fhir/disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
45-
|Azure API Management||[Ensure API Management availability and reliability](../api-management/high-availability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) </p>[How to implement disaster recovery using service backup and restore](../api-management/api-management-howto-disaster-recovery-backup-restore.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
4645
|Azure App Service| [Reliability in Azure App Service](reliability-app-service.md)||
4746
|Azure Backup| [Reliability in Azure Backup](reliability-backup.md)||
4847
|Azure Batch| [Reliability in Azure Batch](reliability-batch.md)||

articles/reliability/reliability-api-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ You must use the Premium (classic) tier to configure availability zone support.
8989

9090
To determine the number of units that provide your required gateway performance, use [capacity metrics](/azure/api-management/api-management-capacity) and your own testing. For more information about scaling and upgrading your service instance, see [Upgrade and scale an Azure API Management instance](/azure/api-management/upgrade-and-scale).
9191

92-
- **Autoscaling:** If you manually configure availability zones on an API Management instance that's configured with autoscaling, you might need to adjust your autoscale settings after configuration. In this case, the number of API Management units in autoscale rules and limits must be a multiple of the number of zones. U you simply default to the automatic availability zone support, you don't need to adjust your autoscale settings.
92+
- **Autoscaling:** If you manually configure availability zones on an API Management instance that's configured with autoscaling, you might need to adjust your autoscale settings after configuration. In this case, the number of API Management units in autoscale rules and limits must be a multiple of the number of zones. If you simply default to the automatic availability zone support, you don't need to adjust your autoscale settings.
9393

9494
- **IP address requirements:** When you're enabling availability zone support on an API Management instance that's deployed in an external or internal virtual network, currently you must specify a public IP address resource for the instance to use. In an internal virtual network, the public IP address is used only for management operations, not for API requests. [Learn more about IP addresses of API Management](../api-management/api-management-howto-ip-addresses.md).
9595

@@ -107,7 +107,7 @@ Regardless of your availability zone configuration, if you add more units, it in
107107

108108
[!INCLUDE [Availability zone numbering](./includes/reliability-availability-zone-numbering-include.md)]
109109

110-
When you change availability zone configuration, changes can take 15 to 45 minutes to apply. The API Management gateway can continue to handle API requests during this time.
110+
When you change availability zone configuration, changes can take 15 to 45 minutes (or longer) to apply. The API Management gateway can continue to handle API requests during this time.
111111

112112
Changing the availability zone configuration triggers a public and private [IP address change](../api-management/api-management-howto-ip-addresses.md#changes-to-ip-addresses).
113113

includes/api-management-az-notes.md

Lines changed: 0 additions & 13 deletions
This file was deleted.

redirects/.openpublishing.redirection.api-management.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/api-management/high-availability.md",
5+
"redirect_url": "/azure/reliability/reliability-api-management",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/api-management/diagnostic-logs-reference.md",
510
"redirect_url": "/rest/api/apimanagement/diagnostic/create-or-update",

0 commit comments

Comments
 (0)