Merge pull request #267825 from anaharris-ms/az-toc-update

Reliability: AZ Migration TOC update

Author: JamesJBarnett

articles/reliability/TOC.yml

@@ -22,24 +22,52 @@
         href: migrate-app-configuration.md
       - name: Azure Application Gateway
         href: migrate-app-gateway-v2.md
+      - name: Azure App Service
+        href: reliability-app-service.md#availability-zone-migration
       - name: Azure Functions
         href: migrate-functions.md
       - name: Azure Cache for Redis
         href: migrate-cache-redis.md
       - name: Azure AI Search
         href: migrate-search-service.md
+      - name: Azure Backup
+        href: migrate-recovery-services-vault.md
+      - name: Azure Batch
+        href: reliability-batch.md#availability-zone-migration
+      - name: Azure Container Apps
+        href: reliability-azure-container-apps.md#availability-zone-migration
       - name: Azure Container instances
         href: migrate-container-instances.md
+      - name: Azure Container Registry
+        href: /azure/container-registry/zone-redundancy?toc=/azure/reliability
+      - name: Azure Cosmos DB
+        href: /azure/cosmos-db/high-availability?toc=/azure/reliability
       - name: Azure Database for MySQL - Flexible Server
         href: migrate-database-mysql-flex.md
+      - name: Azure Database for PostgreSQL
+        href: /azure/postgresql/flexible-server/how-to-manage-high-availability-portal#enable-high-availability-during-server-creation
+      - name: Azure Elastic SAN
+        href: reliability-elastic-san.md#availability-zone-migration
+      - name: Azure Functions
+        href: reliability-functions.md#availability-zone-migration
+      - name: Azure HDInsight
+        href: reliability-hdinsight.md#availability-zone-migration
+      - name: Azure Key Vault
+        href: /azure/key-vault/general/disaster-recovery-guidance?toc=/azure/reliability
+      - name: Azure Kubernetes Service
+        href: /azure/aks/availability-zones?toc=/azure/reliability
       - name: Azure Load Balancer 
         href: migrate-load-balancer.md
       - name: Azure Log Analytics workspaces
         href: migrate-monitor-log-analytics.md
+      - name: Azure Logic Apps
+        href: /azure/logic-apps/set-up-zone-redundancy-availability-zones?tabs=standard&toc=/azure/reliability
       - name: Azure Recovery Services vault
         href: migrate-recovery-services-vault.md
       - name: Azure Service Fabric
         href: migrate-service-fabric.md
+      - name: Azure Service Bus
+        href: /azure/service-bus-messaging/service-bus-geo-dr#availability-zones?toc=/azure/reliability
       - name: Azure SQL Database
         href: migrate-sql-database.md
       - name: Azure Storage accounts

articles/reliability/availability-zones-migration-overview.md

@@ -46,8 +46,18 @@ The table below lists each product that offers migration guidance and/or informa
 | [Azure Cache for Redis](migrate-cache-redis.md)|
 | [Azure AI Search](migrate-search-service.md)|
 | [Azure Container Instances](migrate-container-instances.md)|
+| [Azure Container Registry](/azure/container-registry/zone-redundancy?toc=/azure/reliability) |
+| [Azure Cosmos DB](/azure/cosmos-db/high-availability?toc=/azure/reliability) |
 | [Azure Database for MySQL - Flexible Server](migrate-database-mysql-flex.md)|
+| [Azure Database for PostgreSQL](/azure/postgresql/flexible-server/how-to-manage-high-availability-portal#enable-high-availability-during-server-creation)|
+| [Azure Elastic SAN](reliability-elastic-san.md#availability-zone-migration)|
+| [Azure Functions](reliability-functions.md#availability-zone-migration)|
+| [Azure HDInsight](reliability-hdinsight.md#availability-zone-migration)|
+| [Azure Key Vault](/azure/key-vault/general/disaster-recovery-guidance?toc=/azure/reliability)|
+| [Azure Kubernetes Service](/azure/aks/availability-zones?toc=/azure/reliability)|
+| [Azure Logic Apps](/azure/logic-apps/set-up-zone-redundancy-availability-zones?tabs=standard&toc=/azure/reliability)|
 | [Azure Monitor: Log Analytics](migrate-monitor-log-analytics.md)|
+| [Azure Service Bus](/azure/service-bus-messaging/service-bus-geo-dr#availability-zones?toc=/azure/reliability)|
 | [Azure SQL Managed Instance](migrate-sql-managed-instance.md)|
 
 

articles/reliability/reliability-azure-container-apps.md

@@ -213,7 +213,7 @@ You should still use safe deployment techniques such as [blue-green deployment](
 
 If you have enabled [session affinity](../container-apps/sticky-sessions.md), and a zone goes down, clients for that zone are routed to new replicas because the previous replicas are no longer available. Any state associated with the previous replicas is lost.
 
-### Availability zone redeployment and migration
+### Availability zone migration
 
 To take advantage of availability zones, enable zone redundancy as you create the Container Apps environment. The environment must include a virtual network with an available subnet. You can't migrate an existing Container Apps environment from nonavailability zone support to availability zone support.
 

articles/reliability/reliability-batch.md

@@ -58,7 +58,7 @@ Azure Batch account doesn't reallocate or create new nodes to compensate for nod
 To prepare for a possible availability zone failure, you should over-provision capacity of service to ensure that the solution can tolerate 1/3 loss of capacity and continue to function without degraded performance during zone-wide outages. Since the platform spreads VMs across three zones and you need to account for at least the failure of one zone, multiply peak workload instance count by a factor of zones/(zones-1), or 3/2. For example, if your typical peak workload requires four instances, you should provision six instances: (2/3 * 6 instances) = 4 instances.
 
 
-### Availability zone redeployment and migration
+### Availability zone migration
 
 You can't migrate an existing Batch pool to availability zone support. If you wish to recreate your Batch pool across availability zones, see [Create an Azure Batch pool across availability zones](/azure/batch/create-pool-availability-zones).
 

articles/reliability/reliability-elastic-san.md

@@ -39,7 +39,7 @@ If you deployed an LRS elastic SAN, you may need to deploy a new SAN, using snap
 
 The latency differences between an elastic SAN on LRS and an elastic SAN on ZRS isn't particularly high. However, for workloads sensitive to latency spikes, consider an elastic SAN on LRS since it offers the lowest latency.
 
-### Availability zone redeployment and migration
+### Availability zone migration
 
 To migrate an elastic SAN on LRs to ZRS, you must snapshot your elastic SAN's volumes, export them to managed disk snapshots, deploy an elastic SAN on ZRS, and then create volumes on the SAN on ZRS using those disk snapshots. To learn how to use snapshots (preview), see [Snapshot Azure Elastic SAN volumes (preview)](../storage/elastic-san/elastic-san-snapshots.md).
 

articles/reliability/reliability-functions.md

@@ -146,7 +146,7 @@ To learn more about these templates, see [Automate resource deployment in Azure
 
 After the zone-redundant plan is created and deployed, any function app hosted on your new plan is considered zone-redundant.
 
-### Migrate your function app to a zone-redundant plan
+### Availability zone migration
 
 Azure Function Apps currently doesn't support in-place migration of existing function apps instances. For information on how to migrate the public multitenant Premium plan from non-availability zone to availability zone support, see [Migrate App Service to availability zone support](../reliability/migrate-functions.md).
 

articles/reliability/reliability-hdinsight.md

@@ -97,7 +97,7 @@ When the HDInsight cluster is ready, you can check the location to see which ava
 
 You can scale up an HDInsight cluster with more worker nodes. The newly added worker nodes will be placed in the same availability zone of this cluster. 
 
-### Availability zone redeployment
+### Availability zone migration
 
 Azure HDInsight clusters currently doesn't support in-place migration of existing cluster instances to availability zone support. However, you can choose to [recreate your cluster](#create-an-hdinsight-cluster-using-availability-zone), and choose a different availability zone or region during the cluster creation. A secondary standby cluster in a different region and a different availability zone can be used in disaster recovery scenarios.