Skip to content

Commit cc30865

Browse files
committed
edits
1 parent 0b749c8 commit cc30865

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/availability-zones/migrate-api-mgt.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,6 @@ In this article, we'll take you through the different options for availability z
5252

5353
* If your API Management instance is deployed (injected) in a [Azure virtual network (VNet)](../api-management/api-management-using-with-vnet.md), check the version of the [compute platform](../api-management/compute-infrastructure.md) (stv1 or stv2) that hosts the service.
5454

55-
> [!NOTE]
56-
> If you've configured [autoscaling](../api-management/api-management-howto-autoscale.md) for your API Management instance in the primary location, you may need to adjust your autoscale settings after enabling zone redundancy. The number of API Management units in autoscale rules and limits must be a multiple of the number of zones.
57-
5855
## Downtime requirements
5956

6057
There are no downtime requirements for any of the migration options.

0 commit comments

Comments
 (0)