Merge pull request #17020 from v-sissondan/migrate-feb-updates

Migrate Feb updates

Author: JamesJBarnett

azure-local/migrate/media/migrate-maintain-ip-addresses/connected-devices.png

@@ -3,7 +3,7 @@ title: Enable guest management for migrated VMs (preview)
 description: Learn how to enable guest management for migrated VMs (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 02/03/2025
+ms.date: 02/10/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -41,18 +41,23 @@ Before you begin, complete the following:
     - To verify the installation and check that the **stack-hci-vm** version is 1.1.5 or later:
 
         ```azurecli
-        PS C:\Users\AzureStackAdminD> az version
+        PS C:\Users\AzureStackAdminD> az -version
         {
-            "azure-cli": ”2.60.0”,
-            "azure-cli-core": ”2.60.0”,
+            "azure-cli": "2.68.0",
+            "azure-cli-core": "2.68.0",
             "azure-cli-telemetry": "1.1.0",
             "extensions": {
-                "aksarc": ‘1. 2.20" ,
-                "arcappliance": "1.1.1", 
-                "connectedk8s": "1.6. 2‘ ,
+                "aksarc": "1.2.23",
+                "arcappliance": "1.3.1", 
+                "connectedk8s": "1.10.5",
                 "customlocation": "0.1.3",
-                "k8s-extension": "1.4. 5" ,
-                "stack-hci-vm": "1.1.8"
+                "k8s-extension": "1.6.3",
+                "stack-hci-vm": "1.5.0",
+                            },
+            "dependencies": {
+                "msal": "1.31.1",
+                "azure-mgmt-resource": "23.1.1",
+                            },
         }
         ```
 

azure-local/migrate/migrate-enable-guest-management.md

@@ -6,7 +6,7 @@ metadata:
   author: alkohli
   ms.author: alkohli
   ms.service: azure-local
-  ms.date: 01/23/2025
+  ms.date: 02/10/2025
 
 
 title: FAQ - Migration of Hyper-V and VMware VMs to Azure Local using Azure Migrate (preview)
@@ -109,6 +109,12 @@ sections:
           
           No, this is not a supported scenario with this release. Create a separate project for each source from which you wish to migrate.
 
+          ### I have the Azure Connected Machine Agent deployed on my source VM(s) that I wish to migrate. Do I need to uninstall the agent on my VM(s) before migration?
+
+          Yes, you must uninstall the Azure Connected Machine Agent from your source VMs before migration. [Follow the steps to uninstall the agent](/azure/azure-arc/servers/manage-agent?tabs=windows#uninstall-the-agent). Not doing so will result in unsupported behavior.
+
+          When the VM is migrated, it will be created as a native Azure Arc virtual machine in the Azure Local instance. Removing the Azure Connected Machine Agent from the source VMs before migration ensures that the migrated VM is the only valid projection of the virtual machine in Azure.
+
         
           ## [VMware VMs only](#tab/vmware-vms)
           

azure-local/migrate/migrate-faq.yml

@@ -3,7 +3,7 @@ title: Discover and replicate Hyper-V VMs for migration to Azure Local using Azu
 description: Learn the discovery and replication process for Hyper-V VMs to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 12/16/2024
+ms.date: 02/10/2025
 ms.author: alkohli
 ---
 

azure-local/migrate/migrate-hyperv-replicate.md

@@ -3,7 +3,7 @@ title: Review requirements for Hyper-V VM migration to Azure Local using Azure M
 description: Learn the system requirements for Hyper-V migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 02/03/2025
+ms.date: 02/10/2025
 ms.author: alkohli
 ---
 
@@ -74,6 +74,8 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 - Before you begin, for all Windows VMs, bring all the disks online and persist the drive letter. For more information, see how to [configure a SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy) to bring the disks online.
 
+- Verify that none of the VMs you plan to migrate have the Azure Connected Machine Agent installed. For more information, see [FAQ](migrate-faq.yml).
+
 ## Target Azure Local requirements
 
 - The target system must be running Azure Local.

azure-local/migrate/migrate-hyperv-requirements.md

@@ -3,7 +3,7 @@ title: Maintain static IP addresses during migration (preview)
 description: Learn how to maintain static IP addresses for VMs during migration.
 author: alkohli
 ms.topic: how-to
-ms.date: 01/23/2025
+ms.date: 02/10/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -51,12 +51,16 @@ To migrate VMs with static IPs from the source system (Hyper-V or VMware), follo
 
 1. Ensure the preparation script is run on the source VM by an account with administrator privileges to create scheduled tasks.
 
-### Prepare target VMs for IP migration
+### Prepare target Azure Local instance and logical network
 
-On the target system, provision a static Azure Arc logical network to support the migration. This setup requires defining the IP address space, gateway address, DNS servers, and optionally an IP pool range.
+On the target Azure Local instance, provision a static Azure Arc logical network to support the migration. This setup requires defining the IP address space, gateway address, DNS servers, and optionally an IP pool range.
 
 For detailed guidance on creating and configuring static or dynamic Azure Arc logical networks, see [Create logical networks for Azure Local](../manage/create-logical-networks.md?tabs=azurecli).
 
+Ensure that the static IP addresses you plan to migrate are available in the static logical network and not assigned to another VM. If an IP address is already in use, the migration will fail with the error: "The address is already in use." To avoid this, go to the target static logical network, check which IP addresses are in use, and remove any NICs assigned to the static IPs you want to migrate.
+
+:::image type="content" source="./media/migrate-maintain-ip-addresses/connected-devices.png" alt-text="Screenshot of Connected Devices page." lightbox="./media/migrate-maintain-ip-addresses/connected-devices.png":::
+
 ### (Optional) Prepare to deploy IP migration at scale using group policy
 
 To use this method, you need domain administrator privileges and access to the Group Policy Editor. Additionally, one of the following conditions must be met:

azure-local/migrate/migrate-maintain-ip-addresses.md

@@ -3,7 +3,7 @@ title: Review requirements for VMware VM migration to Azure Local using Azure Mi
 description: Learn the system requirements for VMware migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 02/03/2025
+ms.date: 02/10/2025
 ms.author: alkohli
 ms.custom: references_regions
 ---
@@ -71,6 +71,8 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 - The VMware source environment must be able to initiate a network connection with the target Azure Local instance, either by being on the same on-premises network or by using a VPN.
 
+- Verify that none of the VMs you plan to migrate have the Azure Connected Machine Agent installed. For more information, see [FAQ](migrate-faq.yml).
+
 ## Target Azure Local system requirements
 
 - The target system must be running Azure Local.