Merge pull request #214117 from v-ksreedevan/10Oct-TestReplicationLegacy

Content Freshness - Test replication

Author: PMEds28

articles/migrate/how-to-test-replicating-virtual-machines.md

@@ -1,11 +1,12 @@
 ---
-title: Tests migrate replicating virtual machines
+title: Test migrate replicating virtual machines
 description: Learn best practices for testing replicating virtual machines
 author: piyushdhore-microsoft 
 ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: how-to
-ms.date: 3/23/2022
+ms.date: 10/18/2022
+ms.custom: engagement-fy23
 ---
 
 
@@ -14,76 +15,76 @@ ms.date: 3/23/2022
 This article helps you understand how to test replicating virtual machines. Test migration provides a way to test and validate migrations prior to the actual migration.  
 
 
-
 ##  Prerequisites
 
-Before you get started, you need to perform the following steps:
+Before you get started, perform the following steps:
 
-- Create the Azure Migrate project.
-- Deploy the  appliance for your scenario and complete discovery of  virtual machines.
+- [Create](create-manage-projects.md) an Azure Migrate project.
+- Deploy the  appliance for your scenario and complete the discovery of virtual machines.
 - Configure replication for one or more virtual machines that are to be migrated.
+
 > [!IMPORTANT]
-> You'll need to have at least one replicating virtual machine in the project before you can perform test migration.
+> You'll need at least one replicating virtual machine in the project before you can test the migration.
 
-To learn how to perform the above, review the following tutorials based on your scenarios 
-- [Migrating VMware virtual machines to Azure with the agentless migration method](./tutorial-migrate-vmware.md).
-- [Migrating Hyper-V VMs to Azure with Azure Migrate Server Migration](./tutorial-migrate-hyper-v.md)
-- [Migrating machines as physical server to Azure with Azure Migrate.](./tutorial-migrate-physical-virtual-machines.md)
+Review the following tutorials based on your environment:
+- [Migrating VMware VMs with agentless migration](./tutorial-migrate-vmware.md).
+- [Migrating Hyper-V VMs to Azure](./tutorial-migrate-hyper-v.md).
+- [Migrating machines as physical servers to Azure](./tutorial-migrate-physical-virtual-machines.md)
 
 
 ## Setting up your test environment
 
-The requirements for a test environment can vary according to your needs. Azure Migrate gives customers complete flexibility to create their own test environment. An option to select the VNet is given  during test migration. You can customize the setting of this VNet to create a test environment  according to your need. 
+The requirements for a test environment can vary according to your needs. Azure Migrate provides customers complete flexibility to create their own test environment. An option to select the VNet is provided  during test migration. You can customize the setting of this VNet to create a test environment according to your requirement. 
 
 Furthermore, you can create 1:1 mapping between subnets of the VNet and Network Interface Cards (NICs) on VM, which gives more flexibility in creating the test environment.
 
 > [!Note]
 > Currently, the subnet selection feature is available only for agentless VMware migration scenario.
 
-The following logic is used for subnet selection for other scenarios (Migration from Hyper-V environment and physical server migration) 
+The following logic is used for subnet selection for other scenarios (Migration from Hyper-V environment and physical server migration).
 
 - If a target subnet (other than default) was specified as an input while enabling replication. Azure Migrate prioritizes using a subnet with the same name in the Virtual Network selected for the test migration.
 
 - If the subnet with the same name ins't found, then Azure Migrate selects the first subnet available alphabetically that isn't a Gateway/Application Gateway/Firewall/Bastion subnet. For example, 
 
     - Suppose the target VNet is VNet-alpha and target subnet is Subnet-alpha for a replicating VM. VNet-beta is selected during test migration for this VM, then -
-    - If VNet-beta has a subnet named   Subnet-alpha, that subnet would be chosen for test migration.
+    - If VNet-beta has a subnet named Subnet-alpha, that subnet would be chosen for test migration.
     - If VNet-beta doesn't have a Subnet-alpha, then the next alphabetically available subnet, suppose Subnet-beta, would be chosen if it isn't Gateway / Application Gateway / Firewall / Bastion subnet. 
 
-## Precautions to take selecting the test migration virtual network
+## Precautions to take while selecting the test migration virtual network
 
-The test environment boundaries would  depend on the network setting of the VNet you selected. The tested VM would behave exactly like it's supposed to run  after migration.  We don't recommend performing a test migration to a production virtual network.   Problems such as   duplicate VM or DNS entry changes can arise if the VNet selected for test migration has connections open to on premise VNet.
+The test environment boundaries would  depend on the network setting of the VNet you selected. The tested VM would behave exactly like it's supposed to run after migration. Performing a test migration to a production virtual network is not recommended. If the VNet selected for test migration has connections open to the on-premises VNet, it may cause issues like duplication of VM or DNS entry changes.
 
 
-## Selecting test migration VNet while enabling replication  (Agentless VMware migration)
+## Selecting test migration VNet while enabling replication (Agentless VMware migration)
 
- Select the VNet and subnet for test migration from the Target settings tab. These settings can be overridden later in Compute and Network tab of the replicating VM or while starting test migration of the replicating VM.
+ Select the VNet and subnet for test migration from the **Target settings** tab. These settings can be overridden later in the **Compute and Network** tab of the replicating VM or while starting test migration of the replicating VM.
 
 :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-during-start-replication-flow.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box.":::
 
-## Changing test migration   virtual network and subnet of a replicating machine (Agentless VMware migration)
+## Changing test migration virtual network and subnet of a replicating machine (Agentless VMware migration)
 
 You can change the VNet and subnet of a replicating machine by following the steps below.
 
 1. Select  the virtual machine from the list of currently replicating virtual machines
 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-1.png" alt-text="Screenshot shows the contents of replicating machine screen. It contains a list of replicating machine.":::
 
-2. Select on the Compute and Network option under the general heading.
+2. Select **Compute and Network** option under **General**.
 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-2.png" alt-text="Screenshot shows the location of network and compute option on the details page of replicating machine.":::
 
-3. Select the virtual network  under the Test migration column. It's important to select the VNet in this drop down for test migration to be able to select subnet for each Network Interface Card (NIC) in the following steps.
+3. Select the virtual network from the **Test migration** column. It's important to select the VNet in this drop down for test migration to be able to select subnet for each Network Interface Card (NIC) in the following steps.
 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-3.png" alt-text="Screenshot shows where to select VNet in replicating machine's network and compute options.":::
 
-4. Select on the Network Interface Card's name to check its settings. You can select the subnet for each of the Network Interface Card (NIC) of the VM.
+4. Select the NIC's name to check its settings. You can select the subnet for each of the NICs of the VM.
 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-4.png" alt-text="Screenshot shows how to select a subnet for each Network Interface Card of replicating machine in the network and compute options of replicating machine.":::
 
-5. To change the settings, select on the pencil  icon. Change the setting for the Network Interface Card (NIC) in the new form. Select OK. 
+5. To change the settings, select edit. Change the setting for the NIC in the new form. Select **OK**. 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-5.png" alt-text="Screenshot shows the content of the Network Interface Card page after clicking the pencil icon next to Network Interface Card's name in the network and compute screen.":::
 
-6. Select save. Changes aren't saved until you can see the colored square next to Network Interface Card's (NIC) name.
+6. Select **Save**. Changes aren't saved until you can see the colored square next to the NIC's name.
 
     :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-6.png" alt-text="Screenshot shows the network and compute options screen of replicating machine and highlights the save button.":::