Merge pull request #16825 from v-sissondan/rebrand-23h2-migrate

Remove 23H2 references - Azure Migrate

Author: denrea

azure-local/migrate/migrate-cluster-new-hardware.md

@@ -3,7 +3,7 @@ title: Migrate to Azure Local on new hardware
 description: Learn how to migrate to Azure Local on new hardware 
 author: alkohli 
 ms.topic: how-to 
-ms.date: 01/16/2025 
+ms.date: 02/03/2025 
 ms.author: alkohli 
 ms.reviewer: alkohli 
 ---
@@ -85,7 +85,7 @@ Regardless of the OS version a VM may be running on, the minimum VM version supp
 
 For VMs on Windows Server 2012 R2 or later, update all VMs to the latest VM version supported on the source hardware first before running the Robocopy migration script. This ensures all VMs are at least at version 5.0 for a successful VM import.
 
-For VMs on Windows Server 2008 SP1, Windows Server 2008 R2-SP1, and Windows 2012, the VM version will be less than version 5.0. These VMs also use an .xml file for configuration instead of an .vcmx file. As such, a direct import of the VM to Azure Local is not supported. In these cases, you have two options, as detailed in [Migrating older VMs](#migrating-older-vms).
+For VMs on Windows Server 2008 SP1, Windows Server 2008 R2-SP1, and Windows 2012, the VM version will be less than version 5.0. These VMs also use an .xml file for configuration instead of a .vcmx file. As such, a direct import of the VM to Azure Local is not supported. In these cases, you have two options, as detailed in [Migrating older VMs](#migrating-older-vms).
 
 ### Updating the VM version
 

azure-local/migrate/migrate-cluster-same-hardware.md

@@ -3,18 +3,18 @@ title: Migrate to Azure Local on same hardware
 description: Learn how to migrate a system to Azure Local on the same hardware
 author: alkohli 
 ms.topic: how-to 
-ms.date: 01/16/2025
+ms.date: 02/03/2025
 ms.author: alkohli 
 ms.reviewer: kerimha 
 ---
 
 # Migrate to Azure Local on same hardware
 
-> Applies to: Azure Local 2311.2 and later; Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2008 R2
+> Applies to: Azure Local 2311.2 and later; Azure Stack HCI, version 22H2; Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2008 R2
 
 [!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
 
-This topic describes how to migrate a Windows Server failover cluster to Azure Local using your existing machine hardware. This process installs the new operating system for Azure Local and retains your existing system settings and storage, and imports your VMs.
+This topic describes how to migrate a Windows Server failover cluster to Azure Local using your existing machine hardware. This process installs the new operating system for Azure Local and retains your existing system settings and storage, and imports your virtual machines (VMs).
 
 The following diagram depicts migrating your Windows Server cluster in-place using the same machine hardware. After shutting down your system, Azure Local is installed, storage is reattached, and your VMs are imported and made highly available (HA).
 
@@ -23,7 +23,7 @@ The following diagram depicts migrating your Windows Server cluster in-place usi
 To migrate your VMs to new Azure Local hardware, see [Migrate to Azure Local on new hardware](migrate-cluster-new-hardware.md).
 
 > [!NOTE]
-> Migrating stretched clusters is not covered in this article.
+> Migrating stretched clusters isn't covered in this article.
 
 ## Before you begin
 
@@ -40,7 +40,7 @@ There are several requirements and things to consider before you begin migration
 - Shut down your system VMs, offline CSVs, offline storage pools, and the system service.
 - Disable the Cluster Name Object (CNO) (it's reused later) and:
     - Check that the CNO has Create Object rights to its own Organizational Unit (OU)
-    - Check that the block inherited policy has been set on the OU
+    - Check that the block inherited policy is set on the OU
     - Set the required policy for Azure Local on this OU
 
 ## VM version support and update
@@ -60,7 +60,7 @@ Regardless of the OS version a VM may be running on, the minimum VM version supp
 |Windows Server 2022| |
 |Azure Local|9.0|
 
-For VMs on Windows Server 2008 SP1, Windows Server 2008 R2-SP1, and Windows 2012 systems, direct migration to Azure Local is not supported. In these cases, you have two options:
+For VMs on Windows Server 2008 SP1, Windows Server 2008 R2-SP1, and Windows 2012 systems, direct migration to Azure Local isn't supported. In these cases, you have two options:
 
 - Migrate these VMs to Windows Server 2012 R2 or later first, update the VM version, then begin the migration process.
 
@@ -111,11 +111,11 @@ If using Windows Admin Center to create the Azure Local instance, the Create Clu
 For detailed information on how to create the system, see [Create an Azure Local instance using Windows Admin Center](../deploy/create-cluster.md).
 
 > [!IMPORTANT]
-> Skip step **4.1 Clean drives** in the Create system wizard. Otherwise you will delete your existing VMs and storage.
+> Skip step **4.1 Clean drives** in the Create system wizard. Otherwise you'll delete your existing VMs and storage.
 
 1. Start the Create Cluster wizard. When you get to **Step 4: Storage**:
 
-1. Skip step **4.1 Clean drives**. Don't do this.
+1. Skip step **4.1 Clean drives**. Don't do this operation.
 
 1. Step away from the wizard.
 
@@ -144,7 +144,7 @@ Install-WindowsFeature -Name Hyper-V, Failover-Clustering, FS-Data-Deduplication
 For more information on how to create the system using PowerShell, see [Create an Azure Local instance using Windows PowerShell](../deploy/create-cluster-powershell.md).
 
 > [!NOTE]
-> Re-use the same name for the previously disabled Cluster Name Object.
+> Reuse the same name for the previously disabled Cluster Name Object.
 
 1. Run the cmdlet to create the system:
 
@@ -161,11 +161,11 @@ For more information on how to create the system using PowerShell, see [Create a
 1. If migrating from Windows Server 2016, this also creates a new `ClusterperformanceHistory` ReFS volume and assigns it to the SDDC Cluster Resource Group.
 
     > [!NOTE]
-    > If a storage pool shows Minority Disk errors (viewable in Cluster Manager), re-run the `Enable-ClusterS2D -verbose` cmdlet.
+    > If a storage pool shows Minority Disk errors (viewable in Cluster Manager), rerun the `Enable-ClusterS2D -verbose` cmdlet.
 
-1. Using Cluster Manager, enable every CSV except the `ClusterperformanceHistory` volume, which is a ReFS volume (make sure this is not an ReFS CSV).
+1. Using Cluster Manager, enable every CSV except the `ClusterperformanceHistory` volume, which is a ReFS volume (make sure this isn't an ReFS CSV).
 
-1. If migrating from Windows Server 2019, re-run the `Enable-ClusterS2D -verbose` cmdlet. This associates the `ClusterperformanceHistory` ReFS volume with the SDDC Cluster Resource Group.
+1. If migrating from Windows Server 2019, rerun the `Enable-ClusterS2D -verbose` cmdlet. This associates the `ClusterperformanceHistory` ReFS volume with the SDDC Cluster Resource Group.
 
 1. Determine your current storage pool name and version by running the cmdlet:
 
@@ -203,7 +203,7 @@ For more information on how to create the system using PowerShell, see [Create a
     ```
 
     > [!NOTE]
-    > `ClusterFunctionalLevel` is automatically set to `10` and does not require updating due to new the operating system and cluster creation.
+    > `ClusterFunctionalLevel` is automatically set to `10` and doesn't require updating due to new the operating system and cluster creation.
 
 1. Update your storage pool as follows:
 
@@ -215,7 +215,7 @@ For more information on how to create the system using PowerShell, see [Create a
 
 If migrating from Windows Server 2016, Resilient File System (ReFS) volumes are supported, but such volumes don't benefit from performance enhancements in Azure Local from using mirror-accelerated parity (MAP) volumes. This enhancement requires a new ReFS volume to be created using the PowerShell `New-Volume` cmdlet.
 
-For Windows Server 2016 MAP volumes, ReFS compaction wasn't available, so re-attaching these volumes is OK but will be less performant compared to creating a new MAP volume in an Azure Local instance.
+For Windows Server 2016 MAP volumes, ReFS compaction wasn't available, so reattaching these volumes is OK but will be less performant compared to creating a new MAP volume in an Azure Local instance.
 
 ## Import the VMs
 

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

@@ -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: 10/29/2024
+ms.date: 02/03/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -12,7 +12,7 @@ ms.reviewer: alkohli
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
-This article describes how to enable guest management after migration for Arc virtual machines (VMs) running on Azure Local, version 23H2.
+This article describes how to enable guest management after migration for Arc virtual machines (VMs) running on Azure Local.
 
 For more information on other scenarios, see [Manage Arc VMs on Azure Local](../manage/manage-arc-virtual-machines.md).
 
@@ -26,7 +26,7 @@ Before you begin, complete the following:
 
 - You have access to a deployed and registered Azure Local instance, with an Arc Resource Bridge and custom location configured.
 
-- Your system is running Azure Local, version 23H2, release 2405 or later.
+- Your system is running Azure Local release 2405 or later.
 
 - Azure CLI is installed on the Azure Local instance. For instructions, see [Install the Azure CLI for Windows](/cli/azure/install-azure-cli-windows?tabs=azure-cli).
 

azure-local/migrate/migrate-faq.yml

@@ -12,7 +12,7 @@ metadata:
 title: FAQ - Migration of Hyper-V and VMware VMs to Azure Local using Azure Migrate (preview)
 
 summary:
-  The Azure Migrate based solution enables you to migrate VMs from Hyper-V and VMware to an Azure Local, version 23H2 instance.  This FAQ answers questions you might have about the migration of a VM from a Hyper-V or a VMware VM to an Azure Local instance using Azure Migrate.
+  The Azure Migrate based solution enables you to migrate VMs from Hyper-V and VMware to an Azure Local instance.  This FAQ answers questions you might have about the migration of a VM from a Hyper-V or a VMware VM to an Azure Local instance using Azure Migrate.
 
   Tabs have questions about **VMware and Hyper-V VMs**, **VMware VMs only**, and **Hyper-V VMs only**.
 
@@ -32,7 +32,7 @@ sections:
           
           Run `winrm quickconfig` to add `winrm` access through firewall as this doesn't happen automatically.
 
-          After you replicate and migrate the VM, set the VM version to the latest supported version on the target. For Azure Local, version 22H2, it's version 10.
+          After you replicate and migrate the VM, set the VM version to the latest supported version on the target. For Azure Stack HCI, version 22H2, it's version 10.
           
           > [!NOTE]
           > Migration is a one-way process and can't be reversed. The VM version can't be downgraded.

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: 12/12/2024
+ms.date: 02/03/2025
 ms.author: alkohli
 ---
 
@@ -24,7 +24,7 @@ The following operating systems (OS) are supported for the source appliance, tar
 |---------|---------|
 |Source environment     |Hyper-V on Windows Server 2022<br>Hyper-V on Windows Server 2019<br>Hyper-V on Windows Server 2016<br>Hyper-V on Windows Server 2012 R2         |
 |Source appliance     |Windows Server 2022        |
-|Target environment     |Azure Local, version 23H2         |
+|Target environment     |Azure Local 2311.2 or later         |
 |Target appliance     |Windows Server 2022         |
 |Guest VM (Windows)    |Windows Server 2022<br>Windows Server 2019<br>Windows Server 2016<br>Windows Server 2012 R2<br>Windows Server 2008 R2*       |
 |Guest VM (Linux) | Red Hat Linux 6.x, 7.x<br>Ubuntu Server and Pro. 18.x<br>CentOS 7.x <br>SUSE Linux Enterprise 12.x<br>Debian 9.x |
@@ -76,9 +76,9 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 ## Target Azure Local requirements
 
-- The target operating system for your Azure Local instance must be running version 23H2.
+- The target system must be running Azure Local.
 
-- An Arc Resource Bridge must exist on the Azure Local, version 23H2 system for migration. The Arc Resource Bridge is automatically created during the deployment. To verify that an Arc Resource Bridge exists on your Azure Local system, see [Deploy using Azure portal](../deploy/deploy-via-portal.md).  
+- An Arc Resource Bridge must exist on the Azure Local system for migration. The Arc Resource Bridge is automatically created during the deployment. To verify that an Arc Resource Bridge exists on your Azure Local system, see [Deploy using Azure portal](../deploy/deploy-via-portal.md).  
 
 - Ensure that a logical network is configured on your Arc Resource Bridge. For more information, see [Create a logical network](../manage/create-logical-networks.md).
 

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: 12/12/2024
+ms.date: 02/03/2025
 ms.author: alkohli
 ms.custom: references_regions
 ---
@@ -25,7 +25,7 @@ The following operating systems (OSs) are supported for the VMware source applia
 |---------|---------|
 |Source environment     |VMware vCenter Server version 8.0 <br>VMware vCenter Server version 7.0 <br> VMware vCenter Server version 6.7</br><br>VMware vCenter Server version 6.5         |
 |Source appliance     |Windows Server 2022          |
-|Target environment     |Azure Local, version 23H2         |
+|Target environment     |Azure Local 2311.2 or later         |
 |Target appliance     |Windows Server 2022         |
 |Guest VM (Windows)    |Windows Server 2022<br>Windows Server 2019<br>Windows Server 2016<br>Windows Server 2012 R2<br>Windows Server 2008 R2*       |
 |Guest VM (Linux)     | Red Hat Linux 6.x, 7.x<br>Ubuntu Server and Pro. 18.x<br>CentOS 7.x<br>SUSE Linux Enterprise 12.x<br>Debian 9.x        |
@@ -73,9 +73,9 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 ## Target Azure Local system requirements
 
-- The target OS must be version 23H2 for Azure Local.
+- The target system must be running Azure Local.
 
-- An Arc Resource Bridge must exist on Azure Local, version 23H2 for migration. The Arc Resource Bridge is automatically created during the deployment. To verify that an Arc Resource Bridge exists on your Azure Local system, see [Deploy using Azure portal](../deploy/deploy-via-portal.md).  
+- An Arc Resource Bridge must exist on Azure Local for migration. The Arc Resource Bridge is automatically created during the deployment. To verify that an Arc Resource Bridge exists on your Azure Local system, see [Deploy using Azure portal](../deploy/deploy-via-portal.md).  
 
 - Make sure that a logical network is configured on your Arc Resource Bridge. For more information, see [Create a logical network](../manage/create-logical-networks.md).
 

azure-local/migrate/migration-options-overview.md

@@ -27,11 +27,11 @@ To migrate VM workloads and their data to your Azure Local instance, several opt
 
 First party migration options are provided by Microsoft. These options are built into the Azure Local platform and are available to you at no additional cost. The following first party migration options are available:
 
-- [Azure Migrate](./migration-azure-migrate-overview.md). This option is only available on systems running Azure Local, version 23H2.
+- [Azure Migrate](./migration-azure-migrate-overview.md). This option is only available on systems running Azure Local.
     - [For Hyper-V VMs](./migration-azure-migrate-overview.md).
     - [For VMware VMs](./migration-azure-migrate-vmware-overview.md).
 
-- System Center Virtual Machine Manager (SCVMM). These options are only available on systems running Azure Local, version 22H2.
+- System Center Virtual Machine Manager (SCVMM). These options are only available on systems running Azure Stack HCI, version 22H2.
     - [For Hyper-V VMs](/system-center/vmm/deploy-manage-azure-stack-hci?view=sc-vmm-2022&preserve-view=true#step-8-migrate-vms-from-windows-server-to-azure-stack-hci-cluster)
     - [For VMware VMs](/system-center/vmm/deploy-manage-azure-stack-hci?view=sc-vmm-2022&preserve-view=true#step-9-migrate-vmware-workloads-to-azure-stack-hci-cluster-using-scvmm)
 
@@ -47,7 +47,7 @@ Third party migration options are provided by Microsoft partners. These options
 
 ## Manual migration options
 
-Manual migration options are provided by Microsoft. These options are available to you at no additional cost. These options are available only on systems running Azure Local, version 22H2. 
+Manual migration options are provided by Microsoft. These options are available to you at no additional cost. These options are available only on systems running Azure Stack HCI, version 22H2.
 
 The following manual migration options are available: