Merge pull request #16854 from MicrosoftDocs/main

Taojunshen · web-flow · commit 690cc49ca12d · 2025-01-25T02:00:21.000+08:00
1/24/2025 AM Publish
diff --git a/azure-local/includes/azure-local-banner-22h2.md b/azure-local/includes/azure-local-banner-22h2.md
@@ -3,9 +3,9 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 11/18/2024
+ms.date: 01/24/2025
 ms.reviewer: alkohli
 ---
 
 > [!IMPORTANT]
-> Azure Stack HCI is now part of Azure Local. Product documentation renaming is in progress. However, older versions of Azure Stack HCI, for example 22H2 will continue to reference Azure Stack HCI and won't reflect the name change. [Learn more](https://aka.ms/azloc-promo).
+> Azure Stack HCI is now part of Azure Local. However, older versions of Azure Stack HCI, for example 22H2 will continue to reference Azure Stack HCI and won't reflect the name change. [Learn more](https://aka.ms/azloc-promo).
diff --git a/azure-local/migrate/media/migrate-hyperv-requirements/migrate-resource-providers.png b/azure-local/migrate/media/migrate-hyperv-requirements/migrate-resource-providers.png
diff --git a/azure-local/migrate/media/migrate-vmware-requirements/migrate-resource-providers.png b/azure-local/migrate/media/migrate-vmware-requirements/migrate-resource-providers.png
diff --git a/azure-local/migrate/migrate-faq.yml b/azure-local/migrate/migrate-faq.yml
@@ -8,6 +8,7 @@ metadata:
   ms.service: azure-local
   ms.date: 01/23/2025
 
+
 title: FAQ - Migration of Hyper-V and VMware VMs to Azure Local using Azure Migrate (preview)
 
 summary:
@@ -96,6 +97,10 @@ sections:
         
           Both Linux and Windows VMs that have secure boot enabled aren't supported in this release.
 
+          ### Can I use private endpoints with Azure Migrate for Azure Local migrations?
+          
+          Private endpoint connectivity is not currently supported for Azure Migrate projects configured for migrations to Azure Local.
+
           ### How do I enable guest management on my migrated VMs? 
           
           First, ensure that the target Azure Local that hosts the migrated VMs is updated to 2405.1. This version contains a fix for guest enablement of migrated VMs. Then, follow the instructions in [Enable Guest Management on Arc VMs](migrate-enable-guest-management.md).
@@ -104,10 +109,7 @@ sections:
           
           No, this is not a supported scenario with this release. Create a separate project for each source from which you wish to migrate.
 
-          ### Can I use private endpoints to connect to my Azure Migrate project?
-          
-          No, this is not a supported scenario with this release.
-
+        
           ## [VMware VMs only](#tab/vmware-vms)
           
           ### How many VMs can I replicate in parallel from VMware?
diff --git a/azure-local/migrate/migrate-hyperv-replicate.md b/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: 10/28/2024
+ms.date: 12/16/2024
 ms.author: alkohli
 ---
 
@@ -21,6 +21,8 @@ For more information on appliances for Azure Migrate and how to manage them, see
 
 For both the source and target appliance, make sure that your hardware has sufficient resource to support the creation of a Windows Server 2022 VM with 16 GB RAM, 80 GB of disk storage, 8 vCPUs, and an external virtual switch.
 
+Ensure all VMs that you wish to migrate are powered on and have [Hyper-V integration services](/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services) installed. Migration will fail if the VMs are not powered on and do not have Hyper-V integration services installed.
+
 ## Step 1: Create and configure the source appliance
 
 ### Generate the project key
@@ -47,6 +49,8 @@ After the appliance is configured, you start the VM discovery process.
 
 Wait until you have a green checkmark indicating discovery is finished, then go to the Azure portal to review VM inventory.
 
+Ensure that all VMs you want to migrate are powered on and have [Hyper-V integration services](/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services) installed before or during the discovery process.
+
 ## Step 2: Create and configure the target appliance
 
 ### Generate target appliance key
@@ -203,7 +207,7 @@ This step applies only if you downloaded the .zip file.
 1. On the **Specify intent** page:
     1. **What do you want to migrate** is automatically populated as **Servers or virtual machines (VM)**.
     1. Select **Azure Local** for **Where do you want to migrate to ?**
-    1. Select **HYper-V** for the **Virtualization type**.
+    1. Select **Hyper-V** for the **Virtualization type**.
     1. Select the source appliance as the **On-premises appliance** (source) used for discovery.
     1. When finished, select **Continue**.
 
diff --git a/azure-local/migrate/migrate-hyperv-requirements.md b/azure-local/migrate/migrate-hyperv-requirements.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: 10/31/2024
+ms.date: 12/12/2024
 ms.author: alkohli
 ---
 
@@ -56,6 +56,10 @@ For more information on Azure subscriptions and roles, see [Azure roles, Azure A
 |Tenant|Application administrator|
 |Subscription|Contributor, User Access Administrator|
 
+For any subscriptions hosting resources used in migration, such as Azure Migrate project subscriptions and target Azure Local instance subscriptions, the **Microsoft.DataReplication** resource provider must be registered. For more information, see [register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider-1).
+
+:::image type="content" source="./media/migrate-hyperv-requirements/migrate-resource-providers.png" alt-text="Screenshot showing Azure Local Docs Subscription page." lightbox="./media/migrate-hyperv-requirements/migrate-resource-providers.png":::
+
 ## Source Hyper-V requirements
 
 - Hyper-V Server is supported for both standalone server and cluster configuration.
diff --git a/azure-local/migrate/migrate-vmware-replicate.md b/azure-local/migrate/migrate-vmware-replicate.md
@@ -3,7 +3,7 @@ title: Discover and replicate VMware VMs for migration to Azure Local using Azur
 description: Learn the discovery and replication process for VMware VMs to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 10/28/2024
+ms.date: 12/16/2024
 ms.author: alkohli
 ---
 
@@ -21,6 +21,8 @@ For more information on appliances for Azure Migrate and how to manage them, see
 
 For both the source VMware vCenter Server and target Azure Local appliances, make sure that the underlying hardware has sufficient resources to support the creation of a Windows Server 2022 VM with a minimum of 16 GB RAM, 80 GB of disk storage (HDD), 8 vCPUs, and an external virtual switch.
 
+Ensure all VMs that you wish to migrate are powered on and have VMware tools installed. Migration will fail if the VMs are not powered on and do not have VMware tools installed.
+
 ## Step 1: Create and configure the source VMware appliance
 
 ### Generate the project key
@@ -132,6 +134,8 @@ The information table is updated and the status changes to **Validated**.
 
 Wait until you have a green checkmark indicating that the discovery is finished. The migration readiness checks are also completed successfully. After the discovery is complete, go to the Azure portal to review the VM inventory.
 
+Ensure that all VMs you want to migrate are powered on and have VMware tools installed before or during the discovery process.
+
 :::image type="content" source="./media/migrate-vmware-replicate/discovery-complete-1.png" alt-text="Screenshot showing that discovery is complete." lightbox="./media/migrate-vmware-replicate/discovery-complete-1.png":::
 
 ## Step 2: Create and configure the target appliance
diff --git a/azure-local/migrate/migrate-vmware-requirements.md b/azure-local/migrate/migrate-vmware-requirements.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: 10/28/2024
+ms.date: 12/12/2024
 ms.author: alkohli
 ms.custom: references_regions
 ---
@@ -57,6 +57,10 @@ For more information on Azure subscriptions and roles, see [Azure roles, Azure A
 |Tenant|Application administrator|
 |Subscription|Contributor, User Access Administrator|
 
+For any subscriptions hosting resources used in migration, such as Azure Migrate project subscriptions and target Azure Local instance subscriptions, the **Microsoft.DataReplication** resource provider must be registered. For more information, see [register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider-1).
+
+:::image type="content" source="./media/migrate-vmware-requirements/migrate-resource-providers.png" alt-text="Screenshot showing Azure Local Docs Subscription page." lightbox="./media/migrate-vmware-requirements/migrate-resource-providers.png":::
+
 ## Source VMware server requirements
 
 - The source VMware server used for migration should have sufficient resources to create a Windows Server 2022 VM with a minimum of 16 GB memory, 80 GB disk, and 8 vCPUs.
