update toc

Author: anaharris-ms

articles/api-management/TOC.yml

@@ -68,6 +68,10 @@
         href: self-hosted-gateway-overview.md
       - name: Networking
         href: virtual-network-concepts.md
+      - name: Resiliency
+        items: 
+            - name: Migrate to availability zone support
+              href: ../availability-zones/migrate-api-mgt.md
       - name: Security
         items:
             - name: Security controls by Azure Policy

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

@@ -89,7 +89,7 @@ Use this option to migrate an existing location of your API Management instance
 
 Use this option to migrate an existing location of your API Management instance to availability zones when it is currently injected (deployed) in a virtual network. The following steps are needed when the API Management instance is currently hosted on the stv1 platform. Migrating to availability zones will also migrate the instance to the stv2 platform.
 
-1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](api-management/api-management-using-with-vnet?tabs=stv2#prerequisites).
+1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](../api-management/api-management-using-with-vnet?tabs=stv2#prerequisites).
 
 1.	In the Azure portal, navigate to your API Management service.
 
@@ -110,7 +110,7 @@ Use this option to migrate an existing location of your API Management instance
 
 Use this option to migrate an existing location of your API Management instance to availability zones when it is currently injected (deployed) in a virtual network. The following steps are used when the API Management instance is already hosted on the stv2 platform.
 
-1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
+1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
 
 1.	In the Azure portal, navigate to your API Management service.
 
@@ -130,7 +130,7 @@ Use this option to migrate an existing location of your API Management instance
 
 Use this option to add a new location to your API Management instance and enable availability zones in that location. 
 
-If your API Management instance is deployed in a virtual network in the primary location, ensure that you set up a [virtual network](api-management/api-management-using-with-vnet.md?tabs=stv2), subnet, and public IP address in any new location where you plan to enable zone redundancy.
+If your API Management instance is deployed in a virtual network in the primary location, ensure that you set up a [virtual network](../api-management/api-management-using-with-vnet.md?tabs=stv2), subnet, and public IP address in any new location where you plan to enable zone redundancy.
 
 1.	In the Azure portal, navigate to your API Management service.
 
@@ -140,7 +140,7 @@ If your API Management instance is deployed in a virtual network in the primary
 
 1.	In **Availability zones**, select one or more zones. The number of units selected must be distributed evenly across the availability zones. For example, if you selected 3 units, select 3 zones so that each zone hosts one unit.
 
-1. If your API Management instance is deployed in a [virtual network](api-management/api-management-using-with-vnet.md?tabs=stv2), select the virtual network, subnet, and public IP address that are available in the location. 
+1. If your API Management instance is deployed in a [virtual network](../api-management/api-management-using-with-vnet.md?tabs=stv2), select the virtual network, subnet, and public IP address that are available in the location. 
 
 1. Select **Add**, and then select **Save**.