Merge pull request #18543 from v-sissondan/migrate-san-policy

Migrate updates for target appliance

Author: prmerger-automator[bot]

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

@@ -3,7 +3,7 @@ title: Prerequisites for Hyper-V VM migration to Azure Local using Azure Migrate
 description: Learn prerequisites for Hyper-V migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 05/14/2025
+ms.date: 07/25/2025
 ms.author: alkohli
 ---
 
@@ -23,7 +23,7 @@ The following list contains the prerequisites that must be met to migrate Hyper-
 |--|--|--|
 |Open required firewall ports.|source, target|**3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **5985, 5986** – Inbound and outbound connections on port 5985 (WinRM) to communicate from appliance to host. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance.|
 |Allow required URLs |source, <br> target |[URL access](/azure/migrate/migrate-appliance#url-access) and <br> **\*.siterecovery.azure.com** |
-|Configure SAN policy on Windows VMs.|source|[Configure SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy).|
+|Configure SAN/disks policy on VMs. |source|[Configure SAN/disks policy](migrate-troubleshoot.md#disks-on-migrated-vms-are-offline).|
 |Deploy, configure and register an Azure Local instance.|target|[Create and register an Azure Local instance](../deploy/deployment-introduction.md).|
 | Verify a successful deployment. | target | [Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment). |
 |Verify and make a note of the custom location created during deployment on Azure Local.|target|[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment).|

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

@@ -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: 04/08/2025
+ms.date: 07/25/2025
 ms.author: alkohli
 ---
 
@@ -93,75 +93,54 @@ Under **Step 2: Download Azure Migrate appliance**, select either **.VHD** or **
 
 This step applies only if you downloaded the .VHD zipped file. 
 
-Check that the zipped file is secure, before you deploy it.
+1. Check that the zipped file is secure, before you deploy it. 
 
-1. On the machine where you downloaded the file, open an administrator command window.
-1. Run the following command to generate the hash for the VHD.
-    
-    ```powershell    
-    C:\>Get-FileHash -Path <file_location> -Algorithm <Hashing Algorithm>
-    ```
+1. On the machine where you downloaded the file, open an administrator PowerShell window. 
 
-    Here's an example output.
+1. Run the following command to generate the hash for the VHD. 
 
-    ```output
-    C:\>Get-FileHash -Path ./AzureMigrateAppliance_v3.20.09.25.zip -Algorithm SHA256
+    ```powershell
+    C:\>Get-FileHash -Path <Path to downloaded VHD zip>  -Algorithm SHA256
     ```
 
-1. Verify the latest appliance versions and hash values for Azure public cloud:
-
+1. Verify the latest appliance versions and hash values: 
     
     |**Scenario**  |**Download**  |**SHA256**  |
     |---------|---------|---------|
     |Azure Local appliance     |Latest version: `https://go.microsoft.com/fwlink/?linkid=2246416`         |6ae1144b026efb2650f5e11c007a457c351a752f942c2db827dd2903f468dccb         |
 
-
-1. Extract the zip file to a folder.
+1. Extract the zipped file to a folder. 
 
 Now you can install the appliance using the .VHD file.
 
-1. On a Hyper-V server (this could be your source server), go to the Hyper-V Manager. Select **Hyper-V Manager > Connect to server**. 
-
-1. On the **Select Computer** dialog box, select **Another computer**. Browse to the Azure Local machine, and then select **OK**.
-
-1. Map the drive on your Azure Local machine where you downloaded the VHD. Connect to this drive using File Explorer. Verify that you can access the location where the VHD was downloaded on your Azure Local machine.
-
-1. On your Hyper-V server, from the **Actions** pane, select **Import Virtual Machine**. This starts a wizard. Go through the steps of the wizard. Accept the defaults except on the following:
+1. Using local tools, such as Hyper-V Manager or Failover Cluster, install the target appliance from the downloaded .VHD file on your Azure Local instance. 
 
-    1. On the **Locate Folder** page, point to the folder that has the VHD (folder name is AzureMigrateAppliance.zip) that you downloaded on your Azure Local machine.
-    1. On the **Connect Network** page, select a switch from the dropdown list for **Connection**. Create a VM using the VHD you downloaded, then start and sign into the VM. Make sure the VM has access to the internet.
-    1. Finally review the settings and select **Finish**.
-
-1. In the Hyper-V Manager, under **Virtual Machines**, you see the VM your created. Select and start the VM.
-
-1. Once the VM starts, accept the license terms and conditions. On the **Customize settings** page, provide and confirm a password for the administrator account and then select **Finish**.
-
-1. After the VM has started up, sign in to the VM as an administrator. Enter the password you provided in the previous step.
-
-1. Open **Azure Migrate Target Appliance Configuration Manager** shortcut from the desktop.
+1. Once the VM has finished provisioning and has booted, open the **Azure Migrate Target Appliance Configuration Manager** shortcut from the desktop. 
 
 #### Install using a script (.zip file)
 
-This step applies only if you downloaded the .zip file.
-
-1. Using **Hyper-V Manager**, create a standalone (non-HA) VM on the target Azure Local machine running on Windows Server 2022 with 80 GB (min) disk storage, 16 GB (min) memory, and 8 virtual processors. Make sure that the VM has access to the internet.
+This step applies to using a .zip file.
 
-1. In  **Hyper-V Manager**, select the host.
+1. Create a VM in Azure Local with the following configuration: 
+    - Operating system: Windows Server 2022 
+    - vCPU: 8 
+    - Disk: >80 GB 
+    - Memory: 16 GB 
 
-1. Under **Hyper-V settings**, select **Enhanced Session Mode Policy** and ensure **Allow enhanced session mode** is enabled. For more information, see [Turn on enhanced session mode on a Hyper-V host](/windows-server/virtualization/hyper-v/learn-more/use-local-resources-on-hyper-v-virtual-machine-with-vmconnect#turn-on-enhanced-session-mode-on-a-hyper-v-host).
+1. Once the VM is created, sign into the VM as an administrator. 
 
-1. Sign into the VM as an administrator.
+1. You can download the appliance from a .zip file. Under  **Step 2: Download and install the target appliance**, select **.zip**, and then select  **Download**. 
 
-1. Copy and paste the downloaded .zip file to the VM virtual disk that you created and extract it as needed.
+1. Copy the downloaded zip file to the new VM that you created on the Azure Local instance. Extract the zip to a folder and go where the `AzureMigrateInstaller.ps1` PowerShell script resides in the extracted folder. 
 
-1. As an administrator, run the following PowerShell script from the folder of the extracted files to install the target appliance:
+1. Open a PowerShell window as an administrator and run the following:
 
-    ```PowerShell
-    Set-ExecutionPolicy -ExecutionPolicy Unrestricted
+    ```powershell
+    Set-ExecutionPolicy -ExecutionPolicy Unrestricted 
     .\AzureMigrateInstaller.ps1 -Scenario AzureStackHCI -Cloud Public -PrivateEndpoint:$false
-    ```
+    ``` 
 
-1. Restart and sign into the VM.
+1. Restart the VM after the installation is complete. Sign in to the VM. 
 
 ### Register the target appliance
 

azure-local/migrate/migrate-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot issues when migrating VMs to Azure Local using Azure Migrate
 description: Learn about how to troubleshoot issues when migrating Windows VMs to your Azure Local instance using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 07/10/2025
+ms.date: 07/25/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.custom: linux-related-content
@@ -283,17 +283,33 @@ The component fails to fetch the disk properties from the source Hyper-V host. T
 
 **Root cause**
 
-The disks on the migrated Windows VMs may not come online.
+The disks on the migrated Windows VMs and Linux VMs may not come online. 
 
-Migration creates a new VHD/VHDX, which results in a new disk for the Windows OS on the migrated VM. The OS sees this as a new drive and applies SAN policy. The OS will then not make the disk online as it is considered a shared disk.
+Migration creates a new VHD/VHDX, which results in a new disk for the OS on the migrated VM.  
+
+For Windows VMs, the OS sees this as a new drive and applies storage area network (SAN) policy. The OS will then not make the disk online as it is considered a shared disk. 
 
 **Recommended resolution** 
 
-To work around this issue, choose one of the following options: 
+**For Windows VMs**
+
+To ensure that all migrated disks come online, set the SAN policy to **OnlineAll**. 
+
+Configure this setting manually as follows: 
+
+1. On the on-premises virtual machine (not the host server) prior to migration, open an elevated command prompt. 
+
+1. Enter **diskpart**. 
+
+1. Enter **SAN**. If the drive letter of the guest operating system isn't maintained,  **Offline All**  or  **Offline Shared**  is returned. 
+
+1. At the **DISKPART** prompt, enter  **SAN Policy=OnlineAll**. This setting ensures that disks are brought online, and it ensures that you can read and write to both disks. 
+
+1. During migration, you can verify that the disks are brought online. 
 
-- Set SAN policy as `OnlineAll` for migrated Windows VMs. Reboot the VMs. This should bring all the disks online. For detailed instructions, see how to [Configure a SAN policy to bring disks online](/azure/migrate/prepare-for-migration#configure-san-policy).
+**For Linux VMs**
 
-- Manually bring the drives online on migrated VMs.
+Update **fstab** entries to use persistent volume identifiers prior to migration.  
 
 ### Migration fails with unable to delete snapshot error
 

azure-local/migrate/migrate-vmware-prerequisites.md

@@ -3,7 +3,7 @@ title: Prerequisites for VMware VM migration to Azure Local using Azure Migrate
 description: Learn prerequisites for VMware migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 05/14/2025
+ms.date: 07/25/2025
 ms.author: alkohli
 ---
 
@@ -24,7 +24,7 @@ The following list contains the prerequisites that must be met to migrate VMware
 |Open required VMware firewall ports.|source| **3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **443** – Inbound and outbound connections on port 443 to communicate with Azure Migrate services orchestrating replication and migration, and to allow the appliance to communicate with vCenter Server. <br> **902** – Inbound and outbound connections on port 902 for the appliance to replicate data from snapshots of ESXi hosts and send heartbeat traffic to vCenter. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance.|
 |Open required Hyper-V firewall ports.|target|**3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance. <br> **5985, 5986** – Inbound and outbound connections on port 5985 (WinRM) to communicate from appliance to host.|
 |Allow required URLs |source, <br> target |[URL access](/azure/migrate/migrate-appliance#url-access) and <br> **\*.siterecovery.azure.com** |
-|Configure SAN policy on VMware VMs.|source|[Configure SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy).|
+|Configure SAN/disks policy on VMs. |source|[Configure SAN/disks policy](migrate-troubleshoot.md#disks-on-migrated-vms-are-offline).|
 |Deploy, configure, and register an Azure Local instance.|target|[Create and register an Azure Local instance](../deploy/deployment-introduction.md).|
 | Verify a successful deployment. | target | [Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment). |
 |Verify and make a note of the custom location created during deployment on the Azure Local system.|target|[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment).|