Updates and fixes

Author: v-sreedevank

articles/migrate/common-questions-appliance.md

@@ -7,7 +7,7 @@ ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: conceptual
 ms.custom: engagement-fy24
-ms.date: 05/02/2024
+ms.date: 06/20/2024
 ---
 
 # Azure Migrate appliance: Common questions
@@ -110,6 +110,10 @@ A project can have multiple appliances registered to it. However, one appliance
 1. Select **Change** in the upper-right corner to choose your project.
 1. In the Azure Migrate project, select **Overview** from the Azure Migrate: Discovery & assessment.
 1. In **Overview**, select **Appliances** in left menu to see the appliances registered with the project and the connectivity status of the agents on the appliance.
+1. 
+## Can I change the Azure user account from the Azure Migrate appliance once registered with the project?
+If you registered the appliance to Migrate project using a particular user account, it cannot be changed. You can try re-registering the appliance with the new project using another user account via PowerShell script but it will break all the operations in the old project.
+
 
 ## Can the Azure Migrate appliance/Replication appliance connect to the same vCenter?
 

articles/migrate/how-to-scale-out-for-migration.md

@@ -6,7 +6,7 @@ ms.author: ajaypar
 ms.manager: roopesh.nair
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 03/12/2024
+ms.date: 06/20/2024
 ms.custom: engagement-fy24
 ---
 
@@ -155,6 +155,8 @@ In the configuration manager, select **Set up prerequisites**, and then complete
 
             `PS .\ExportConfigFiles.ps1 `
 
+    > [!Note] Install PowerShell 7.x in the appliance and execute the script ExportConfigFiles.ps1. The script execution is only supported with PowerShell 7.x. 
+
          1. Copy the zip file created by running the above commands to the scale-out appliance. The zip file contains configuration files needed to register the scale-out appliance.
 
          1. In the pop-up window opened in the previous step, select the location of the copied configuration zip file and click **Save**.

articles/migrate/toc.yml

@@ -186,7 +186,7 @@ items:
           href: prepare-for-agentless-migration.md
     - name: Hyper-V migration architecture
       href: hyper-v-migration-architecture.md
-    - name: VMware agent-based migration architecture
+    - name: VMware/Physical agent-based migration architecture
       href: agent-based-migration-architecture.md
     - name: Web apps migration support
       href: concepts-migration-webapps.md

articles/migrate/vmware/how-to-set-up-appliance-vmware.md

@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 04/19/2024
+ms.date: 06/20/2024
 ms.custom: vmware-scenario-422, engagement-fy23
 ---
 
@@ -35,6 +35,9 @@ To set up the appliance by using an OVA template, you'll complete these steps, w
 > [!NOTE]
 > OVA templates are not available for soverign clouds.
 
+> [!NOTE]
+> Do not clone or create a VM template out of an appliance deployed using OVA template. This scenario is unsupported and may result in deployment failures within the Migrate Service.
+
 1. Provide an appliance name and generate a project key in the portal.
 1. Download an OVA template file, and import it to vCenter Server. Verify that the OVA is secure.
 1. Create the appliance from the OVA file. Verify that the appliance can connect to Azure Migrate.