Split the zone pivot articles

Author: BanoFarha

articles/migrate/migrate-hyperv-servers-to-azure-using-private-link.md

@@ -1,6 +1,6 @@
 ---
 title: Migrate Hyper-V servers to Azure by using Private Link
-description: Use Azure Migrate with private endpoints for migrations by using ExpressRoute private peering or VPN connections.
+description: Use Azure Migrate with private endpoints to migrate on-premises Hyper-V VMs to Azure.
 author: vijain
 ms.author: vijain
 zone_pivot_groups: migrate-agentlessvmware-hyperv-agentbased

articles/migrate/migrate-servers-to-azure-using-private-link.md

@@ -1,6 +1,6 @@
 ---
 title: Migrate agentless servers to Azure by using Private Link
-description: Use Azure Migrate with private endpoints for migrations by using ExpressRoute private peering or VPN connections.
+description: Use Azure Migrate to migrate servers over a private network by using Azure Private Link.
 author: vijain
 ms.author: vijain
 zone_pivot_groups: migrate-agentlessvmware-hyperv-agentbased
@@ -53,7 +53,7 @@ Now, select machines for replication and migration.
 1. In **Virtual network**, select the Azure VNet/subnet for the migrated  Azure VMs. 
 1. In **Cache storage account**, use the dropdown list to select a storage account to replicate over a private link.  
 
-1. Next, [**create a private endpoint for the storage account**](migrate-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1) and [**grant permissions to the Recovery Services vault managed identity**](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault) to access the storage account required by Azure Migrate. This is mandatory before you proceed.   
+1. Next, [**create a private endpoint for the storage account**](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account) and [**grant permissions to the Recovery Services vault managed identity**](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault) to access the storage account required by Azure Migrate. This is mandatory before you proceed.   
 
     - Ensure that the server hosting the replication appliance has network connectivity to the storage accounts via the private endpoints before you proceed. Learn how to [verify network connectivity](./troubleshoot-network-connectivity.md#verify-dns-resolution).     
 

articles/migrate/migrate-vmware-servers-to-azure-using-private-link.md

@@ -1,6 +1,6 @@
 ---
 title: Migrate VMware servers to Azure by using Private Link
-description: Use Azure Migrate with private endpoints for migrations by using ExpressRoute private peering or VPN connections.
+description: Use Azure Migrate with private endpoints to migrate on-premises VMware VMs to Azure.
 author: vijain
 ms.author: vijain
 zone_pivot_groups: migrate-agentlessvmware-hyperv-agentbased

articles/migrate/tutorial-migrate-aws-virtual-machines.md

@@ -225,7 +225,7 @@ A Mobility service agent must be preinstalled on the source AWS VMs to be migrat
     > [!NOTE]
     >
     > - If you selected private endpoint as the connectivity method for the Azure Migrate project, grant the Recovery Services vault access to the cache storage account. [Learn more](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault).
-    > - To replicate by using Azure ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1).
+    > - To replicate by using Azure ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account).
 1. In **Availability options**, select:
     -  **Availability Zone**: Pins the migrated machine to a specific availability zone in the region. Use this option to distribute servers that form a multinode application tier across availability zones. If you select this option, you need to specify the availability zone to use for each of the selected machines on the **Compute** tab. This option is only available if the target region selected for the migration supports availability zones.
     -  **Availability Set**: Places the migrated machine in an availability set. The target resource group that was selected must have one or more availability sets in order to use this option.

articles/migrate/tutorial-migrate-gcp-virtual-machines.md

@@ -216,7 +216,7 @@ A Mobility service agent must be preinstalled on the source GCP VMs to be migrat
     > [!NOTE]
     >
     > - If you selected private endpoint as the connectivity method for the Azure Migrate project, grant the Recovery Services vault access to the cache storage account. [Learn more](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault).
-    > - To replicate using ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1).
+    > - To replicate using ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account).
 1. In **Availability options**, select:
     -  **Availability Zone**: Pins the migrated machine to a specific availability zone in the region. Use this option to distribute servers that form a multinode application tier across availability zones. If you select this option, you need to specify the availability zone to use for each of the selected machines on the **Compute** tab. This option is only available if the target region selected for the migration supports availability zones.
     -  **Availability Set**: Place the migrated machine in an availability set. The target resource group that was selected must have one or more availability sets in order to use this option.

articles/migrate/tutorial-migrate-physical-virtual-machines.md

@@ -205,7 +205,7 @@ Now, select machines for migration.
 
     >[!NOTE]
     > - If you selected private endpoint as the connectivity method for the Azure Migrate project, grant the Recovery Services vault access to the cache storage account. [Learn more](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault).
-    > - To replicate by using Azure ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1).
+    > - To replicate by using Azure ExpressRoute with private peering, create a private endpoint for the cache storage account. [Learn more](migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account).
 
 1. In **Availability options**, select:
     -  **Availability Zone**: Pins the migrated machine to a specific availability zone in the region. Use this option to distribute servers that form a multinode application tier across availability zones. If you select this option, you need to specify the availability zone to use for each of the selected machines on the **Compute** tab. This option is only available if the target region selected for the migration supports availability zones.

articles/migrate/vmware/tutorial-migrate-vmware-agent.md

@@ -259,7 +259,7 @@ Select VMs for migration.
     > [!NOTE]
     >
     > - If you selected private endpoint as the connectivity method for the Azure Migrate project, grant the Recovery Services vault access to the cache storage account. [**Learn more**](../migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault)
-    > - To replicate using ExpressRoute with private peering, create a private endpoint for the cache storage account. [**Learn more**](../migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1)
+    > - To replicate using ExpressRoute with private peering, create a private endpoint for the cache storage account. [**Learn more**](../migrate-vmware-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account)
 13. In **Availability options**, select:
     -  Availability Zone to pin the migrated machine to a specific Availability Zone in the region. Use this option to distribute servers that form a multi-node application tier across Availability Zones. If you select this option, you'll need to specify the Availability Zone to use for each of the selected machine in the Compute tab. This option is only available if the target region selected for the migration supports Availability Zones
     -  Availability Set to place the migrated machine in an Availability Set. The target Resource Group that was selected must have one or more availability sets in order to use this option.