Split the zone pivot articles

Author: BanoFarha

articles/migrate/how-to-upgrade-windows.md

@@ -27,7 +27,7 @@ This article describes how to upgrade Windows Server OS while migrating to Azure
 - To upgrade from Windows Server 2008 or 2008 R2, ensure you have Microsoft .NET Framework 4 installed on your machine. This is available by default in Windows Server 2008 SP2 and Windows Server 2008 R2 SP1.
 - Disable antivirus and anti-spyware software and firewalls. These types of software can conflict with the upgrade process. Re-enable antivirus and anti-spyware software and firewalls after the upgrade is completed.  
 - Ensure that your VM has the capability of adding another data disk as this feature requires the addition of an extra data disk temporarily for a seamless upgrade experience. 
-- For Private Endpoint enabled Azure Migrate projects, follow [these](migrate-servers-to-azure-using-private-link.md?pivots=agentlessvmware#replicate-vms) steps before initiating any Test migration/Migration with OS upgrade.  
+- For Private Endpoint enabled Azure Migrate projects, follow [these](migrate-vmware-servers-to-azure-using-private-link.md?pivots=agentlessvmware#replicate-vms) steps before initiating any Test migration/Migration with OS upgrade.  
 
 
 > [!NOTE]

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

@@ -1,5 +1,5 @@
 ---
-title: Migrate servers to Azure by using Private Link
+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.
 author: vijain
 ms.author: vijain
@@ -10,24 +10,17 @@ ms.date: 12/14/2022
 ms.custom: engagement-fy23
 ---
 
-# Migrate servers to Azure using Private Link
+# Migrate Hyper-V servers to Azure using Private Link
 
 This article describes how to use Azure Migrate to migrate servers over a private network by using [Azure Private Link](../private-link/private-endpoint-overview.md). You can use the [Migration and modernization](migrate-services-overview.md) tool to connect privately and securely to Azure Migrate over an Azure ExpressRoute private peering or a site-to-site (S2S) VPN connection by using Private Link. 
 
-## Next steps 
-
- - [Migrate VMs](tutorial-migrate-vmware.md#migrate-vms)
- - Complete the [migration process](tutorial-migrate-vmware.md#complete-the-migration).
- - Review the [post-migration best practices](tutorial-migrate-vmware.md#post-migration-best-practices). 
-
-
 This article shows you how to [migrate on-premises Hyper-V VMs to Azure](tutorial-migrate-hyper-v.md), using the [Migration and modernization](migrate-services-overview.md) tool, with agentless migration. You can also migrate using agent-based migration.  
 
 ## Set up the replication provider for migration 
 
 The following diagram illustrates the agentless migration workflow with private endpoints by using the Migration and modernization tool. 
 
- ![Diagram that shows replication architecture.](./media/how-to-use-azure-migrate-with-private-endpoints/replication-architecture.png)
+:::image type="content" source="./media/how-to-use-azure-migrate-with-private-endpoints/replication-architecture.png" alt-text="Diagram that shows replication architecture." lightbox="./media/how-to-use-azure-migrate-with-private-endpoints/replication-architecture.png":::
 
 For migrating Hyper-V VMs, the Migration and modernization tool installs software providers (Microsoft Azure Site Recovery provider and Microsoft Azure Recovery Service agent) on Hyper-V Hosts or cluster nodes.  
 1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization**, select **Discover**. 
@@ -46,7 +39,7 @@ For migrating Hyper-V VMs, the Migration and modernization tool installs softwar
     - The key is valid for five days after you generate it. 
 1. Copy the provider setup file and registration key file to each Hyper-V host (or cluster node) running VMs you want to replicate. 
 > [!Note]
->Before you register the replication provider, ensure that the vault's private link FQDNs are reachable from the machine that hosts the replication provider. Additional DNS configuration may be required for the on-premises replication appliance to resolve the private link FQDNs to their private IP addresses. Learn more about [how to verify network connectivity](./troubleshoot-network-connectivity.md#verify-dns-resolution) 
+>Before you register the replication provider, ensure that the vault's private link FQDNs are reachable from the machine that hosts the replication provider. Additional DNS configuration can be required for the on-premises replication appliance to resolve the private link FQDNs to their private IP addresses. Learn more about [how to verify network connectivity](./troubleshoot-network-connectivity.md#verify-dns-resolution) 
 
 Next, follow these instructions to [install and register the replication provider](tutorial-migrate-hyper-v.md#install-and-register-the-provider). 
 

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

@@ -1,5 +1,5 @@
 ---
-title: Migrate servers to Azure by using Private Link
+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.
 author: vijain
 ms.author: vijain
@@ -10,7 +10,7 @@ ms.date: 12/14/2022
 ms.custom: engagement-fy23
 ---
 
-# Migrate servers to Azure using Private Link
+# Migrate agentless servers to Azure using Private Link
 
 This article describes how to use Azure Migrate to migrate servers over a private network by using [Azure Private Link](../private-link/private-endpoint-overview.md). You can use the [Migration and modernization](migrate-services-overview.md) tool to connect privately and securely to Azure Migrate over an Azure ExpressRoute private peering or a site-to-site (S2S) VPN connection by using Private Link. 
 
@@ -31,7 +31,7 @@ The tool uses a replication appliance to replicate your servers to Azure. Follow
     - By default, Azure Migrate automatically creates a private DNS zone and adds DNS A records for the Recovery Services vault microservices. The private DNS is then linked to the private endpoint virtual network.
 
 >[!Note]
-> Before you register the replication appliance, ensure that the vault's private link FQDNs are reachable from the machine that hosts the replication appliance. Additional DNS configuration may be required for the on-premises replication appliance to resolve the private link FQDNs to their private IP addresses. Learn more about [how to verify network connectivity](./troubleshoot-network-connectivity.md#verify-dns-resolution). 
+> Before you register the replication appliance, ensure that the vault's private link FQDNs are reachable from the machine that hosts the replication appliance. Additional DNS configuration can be required for the on-premises replication appliance to resolve the private link FQDNs to their private IP addresses. Learn more about [how to verify network connectivity](./troubleshoot-network-connectivity.md#verify-dns-resolution). 
 
 After you verify the connectivity, download the appliance setup and key file, run the installation process, and register the appliance to Azure Migrate. Learn more about how to [set up the replication appliance](./tutorial-migrate-physical-virtual-machines.md#prepare-a-machine-for-the-replication-appliance). After you set up the replication appliance, follow these instructions to [install the mobility service](./tutorial-migrate-physical-virtual-machines.md#install-the-mobility-service-agent) on the machines you want to migrate.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Migrate servers to Azure by using Private Link
+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.
 author: vijain
 ms.author: vijain
@@ -10,7 +10,7 @@ ms.date: 12/14/2022
 ms.custom: engagement-fy23
 ---
 
-# Migrate servers to Azure using Private Link
+# Migrate VMware servers to Azure using Private Link
 
 This article describes how to use Azure Migrate to migrate servers over a private network by using [Azure Private Link](../private-link/private-endpoint-overview.md). You can use the [Migration and modernization](migrate-services-overview.md) tool to connect privately and securely to Azure Migrate over an Azure ExpressRoute private peering or a site-to-site (S2S) VPN connection by using Private Link. 
 
@@ -36,7 +36,7 @@ After setting up the appliance and completing discovery, you can begin replicati
 
 The following diagram illustrates the agentless replication workflow with private endpoints by using the Migration and modernization tool.
 
-![Diagram that shows agentless replication architecture.](./media/how-to-use-azure-migrate-with-private-endpoints/agentless-replication-architecture.png)
+:::image type="content" source="./media/how-to-use-azure-migrate-with-private-endpoints/agentless-replication-architecture.png" alt-text="Diagram that shows agentless replication architecture." lightbox="./media/how-to-use-azure-migrate-with-private-endpoints/agentless-replication-architecture.png":::
 
 Enable replication as follows:
 1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization** > **Migration tools**, select **Replicate**. 

articles/migrate/troubleshoot-upgrade.md

@@ -44,7 +44,7 @@ Add the target VNET into the firewall in the storage account that you select i
 
 1. Go to **Networking** > **Firewall and Virtual Networks** > **Public Network Access – Enabled from selected Virtual Network and IP address** > **Virtual Network** > Add existing Virtual Network and add your target VNET. Then proceed with the Test Migration/Migration.    
 
-2. Perform the initial replication by following [these](migrate-servers-to-azure-using-private-link.md?pivots=agentlessvmware#replicate-vms) steps.  
+2. Perform the initial replication by following [these](migrate-vmware-servers-to-azure-using-private-link.md?pivots=agentlessvmware#replicate-vms) steps.  
 
 ## Server is migrated without OS upgrade with status “Completed with errors”  
 

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-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).
 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-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).
 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-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).
 
 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-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)
 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.