Merge pull request #274367 from ankitaduttaMSFT/rz-ga

RZ GA

Author: v-dirichards

articles/reliability/migrate-vm.md

@@ -123,9 +123,6 @@ Now that you have migrated your data to ZRS managed disks or zonal managed disks
 This section details how to move single instance Azure virtual machines from a Regional configuration to a target [Availability Zone](../reliability/availability-zones-overview.md) within the same Azure region.
 
 
-> [!IMPORTANT]
-> Regional to zonal move of single instance VM(s) configuration is currently in *Public Preview*.
-
 ###  Key benefits of regional to zonal move
 
 The benefits of a regional to zonal move are:

articles/virtual-machines/media/tutorial-move-regional-zonal/availability-scaling-home.png

@@ -1,31 +1,64 @@
 ---
-title: FAQ - Move Azure single instance Virtual Machines from regional to zonal availability zones
+title: FAQ - Move Azure single instance Virtual Machines from regional to zonal availability zones 
 description: FAQs for single instance Azure virtual machines from a regional configuration to a target Availability Zone within the same Azure region.
 author: ankitaduttaMSFT
 ms.service: virtual-machines
 ms.topic: article
-ms.date: 09/25/2023
+ms.date: 05/06/2024
 ms.author: ankitadutta
 ---
 
 # Frequently asked questions - Move Azure single instance virtual machines from regional to zonal target availability zones
 
 This article answers common questions about Azure single instance virtual machines - regional to zonal move.
 
-> [!IMPORTANT]
-> Regional to zonal move of single instance VM(s) configuration is currently in *Public Preview*.
-
 ## Regional to zonal move
 
 ### Can I move virtual machine(s) in all Azure regions?
 
-Currently, you can move virtual machine(s) across all public regions that are supported by Availability Zones. Learn more about the availability zone service and regional support.
+Currently, you can move virtual machine(s) across all public regions that are supported by Availability Zones. Learn more about the [availability zone service and regional support](../reliability/availability-zones-service-support.md#azure-regions-with-availability-zone-support).
+
+> [!NOTE]
+> Azure China (China North 3) and Azure Govt (US Gov Virginia) are also supported.
 
 ### Where is the metadata stored?
 
-The metadata associated with the move is stored in an Azure Cosmos DB database located in either the East US2 or North Europe regions and in Azure Blob storage in a Microsoft subscription.
+The service doesn't retain any customer data, and all data remains within the source virtual machine region. The following table shows the mapping between the virtual machine region and metadata region:
+
+| Region group | Region | Metadata region |
+| --- | --- | ----|
+| **Americas** | eastus2 | eastus2 |
+| | eastus | eastus2 |
+| | westus2 | eastus2 |
+| | southcentralus | eastus2 |
+| | brazilsouth | brazilsouth |
+| | canadacentral | canadacentral |
+| | westus3 | eastus2 |
+||||
+| **Europe**| northeurope | northeurope |
+| | westeurope | northeurope |
+| | uksouth | uksouth |
+| | francecentral | francecentral |
+| | switzerlandnorth | switzerlandnorth |
+| | germanywestcentral | germanywestcentral |
+| | norwayeast | norwayeast |
+| | swedencentral | swedencentral |
+| | polandcentral | polandcentral |
+| | spaincentral | northeurope |
+| | italynorth | northeurope |
+||||
+| **Middle East** | uaenorth | uaenorth |
+| | qatarcentral | qatarcentral |
+||||
+| **Asia Pacific** | japaneast | japaneast |
+| | eastasia | southeastasia |
+| | southeastasia | southeastasia |
+| | australiaeast | australiaeast |
+| | centralindia | centralindia |
+| | koreacentral | koreacentral |
+||||
+| **Africa** | southafricanorth | southeastasia |
 
-Although the coverage will eventually extend to other regions, this doesn't restrict you from moving virtual machines to other regions. The service doesn't retain any customer data, and no customer data goes outside of the source virtual machine region.
 
 ### Is the collected metadata encrypted?
 
@@ -86,7 +119,7 @@ Managed identity previously known as Managed Service Identity (MSI), is a featur
 
 ### Can I move my resources from Regional to Zonal and across subscriptions?
 
-You can use Azure Resource Manager to move virtual machines from a regional to a zonal deployment within the same subscription, and then move them across subscriptions.
+You can use virtual machine Regional to Zonal Move capability to move virtual machines from a regional to a zonal deployment within the same subscription and then use Azure Resource Manager to move them across subscriptions.
 
 ### Are Azure Backup/DR, RBAC, Tags, Policies, and extensions on virtual machines supported?
 
@@ -100,9 +133,11 @@ Customer data isn't stored during the move. The system only stores metadata info
 
 When you select **Move**, the following steps are performed on the source virtual machines:
 
-1.	The source virtual machines are stopped and left intact in their original configuration.
+1.	The source virtual machines are stopped and left intact in their original configuration. 
+    > [!NOTE]
+    > Stopping the VMs could lead to a brief downtime.
 2.	Virtual machine restore points of the source virtual machine are taken. These restore points contain a disk restore point for each of the attached disks and a disk restore point consists of a snapshot of an individual managed disk.
-3.	Using these restore points, a new virtual machine with its associated disks (a copy of the source) is created in the zonal configuration.
+3.	Using these restore points, a new virtual machine with its associated disks (a copy of the source VM) is created in the zonal configuration.
 4.	After the move is complete, you can choose to delete the source virtual machines.
 
 

articles/virtual-machines/media/tutorial-move-regional-zonal/availability-scaling.png

@@ -1,5 +1,5 @@
 ---
-title: Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones
+title: Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones 
 description: Learn how to move single instance Azure virtual machines from a regional configuration to a target Availability Zone within the same Azure region.
 author: ankitaduttaMSFT
 ms.service: virtual-machines
@@ -8,12 +8,11 @@ ms.date: 09/25/2023
 ms.author: ankitadutta
 ---
 
-# Move Azure single instance VMs from regional to zonal target availability zones
+# Move Azure single instance VMs from regional to zonal target availability zones 
 
 This article provides information on how to move Azure single instance Virtual Machines (VMs) from a regional to a zonal configuration within the same Azure region.
 
-> [!IMPORTANT]
-> Regional to zonal move of single instance VM(s) configuration is currently in *Public Preview*.
+
 ## Prerequisites
 
 Ensure the following before you begin:
@@ -38,16 +37,13 @@ To select the VMs you want to move from Regional to Zonal configuration within s
 
 To select the VMs for the move, follow these steps: 
 
-1.	On the [Azure portal](https://ms.portal.azure.com/#home), select the VM. In this tutorial, we're using **DemoTestVM1** as an example.
-    
-    :::image type="content" source="./media/tutorial-move-regional-zonal/demo-test-machine.png" alt-text="Screenshot of demo virtual machine."::: 
- 
-2.	In the DemoTestVM1 resource pane, select **Availability + scaling** > **edit**. 
-    :::image type="content" source="./media/tutorial-move-regional-zonal/availability-scaling.png" alt-text="Screenshot of Availability + scaling option."::: 
+1.	On the [Azure portal](https://ms.portal.azure.com/#home), select the VM. 
+2.	In the virtual machine resource pane, select **Availability + scaling** > **edit**. 
+    :::image type="content" source="./media/tutorial-move-regional-zonal/scaling-pane.png" alt-text="Screenshot of Availability + scaling pane.":::  
+
+    Alternatively, in the virtual machine overview plane, you can select **Availability + scale** > **Availability + scaling**.
+        
 
-    Alternatively, in the **DemoTestVM1** overview plane, you can select **Availability + scale** > **Availability + scaling**.
-        :::image type="content" source="./media/tutorial-move-regional-zonal/scaling-pane.png" alt-text="Screenshot of Availability + scaling pane."::: 
-    
 
 ### Select the target availability zones
 

articles/virtual-machines/media/tutorial-move-regional-zonal/demo-test-machine.png

@@ -1,26 +1,24 @@
 ---
-title: Move Azure single instance Virtual Machines from regional to zonal availability zones using PowerShell and CLI
+title: Move Azure single instance Virtual Machines from regional to zonal availability zones using PowerShell and CLI 
 description: Move single instance Azure virtual machines from a regional configuration to a target Availability Zone within the same Azure region using PowerShell and CLI.
 author: ankitaduttaMSFT
 ms.service: virtual-machines
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ms.topic: tutorial
-ms.date: 09/25/2023
+ms.date: 06/10/2024
 ms.author: ankitadutta
 ---
 
-# Move a virtual machine in an availability zone using Azure PowerShell and CLI
+# Move a virtual machine in an availability zone using Azure PowerShell and CLI 
 
 This article details using Azure PowerShell and CLI cmdlets to move Azure single instance VMs from regional to zonal availability zones. An [availability zone](../availability-zones/az-overview.md) is a physically separate zone in an Azure region. Use availability zones to protect your apps and data from an unlikely failure or loss of an entire data center.
 
 To use an availability zone, create your virtual machine in a [supported Azure region](../availability-zones/az-region.md).
 
-> [!IMPORTANT]
-> Regional to zonal move of single instance VM(s) configuration is currently in *Public Preview*.
 
 ## Prerequisites
 
-Verify the following requirements:
+Verify the following requirements before you start the move process:
 
 | Requirement | Description |
 | --- | --- |
@@ -422,9 +420,10 @@ Check whether the regional VMs you added have any dependencies on other resource
     AdditionalInfo :
     Code           :
     Detail         :
+    EndTime        : 
     EndTime        : 9/8/2023 6:52:14 AM
-    Id             : /subscriptions/<Subscription-id>/resourceGroups/RegionToZone-DemoMCRG/providers/Microsoft.Migrate/moveCollections/RegionToZone-DemoMC/o
-                     perations/bc68354b-ec1f-44cb-92ab-fb3b4ad90229
+
+    Id             : /subscriptions/<Subscription-id>/resourceGroups/RegionToZone-DemoMCRG/providers/Microsoft.Migrate/moveCollections/RegionToZone-DemoMC/operations/bc68354b-ec1f-44cb-92ab-fb3b4ad90229
     Message        :
     Name           : bc68354b-ec1f-44cb-92ab-fb3b4ad90229
     Property       : Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.Models.Any
@@ -480,6 +479,75 @@ Check whether the regional VMs you added have any dependencies on other resource
 
 1. To remove resources from the resource collection, follow these [instructions](../resource-mover/remove-move-resources.md).
     
+### Availability Zones VM SKU, Quota and Capacity validations
+
+Azure provides recommendations when the selected Availability Zone doesn't have the virtual machine SKU, or when there is not enough Quota or Capacity available. Here are some examples of these recommendations and the actions that should be taken if the virtual machine SKU is not available.
+
+#### VM SKU not available
+
+When the source virtual machine size `Standard_DC1ds_v3` isn't available in the selected availability zone `1`.
+
+**Recommended Action**: Choose a different virtual machine size in the same availability zone or select a different availability zone with corresponding recommended VM size.
+
+**Recommendations**:
+
+- SKU: Standard_DC1ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC2ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC4ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC1s_v3, Zones: [ 2 ]
+- SKU: Standard_D2ds_v5, Zones: [ 2, 3 ]
+- SKU: Standard_D2as_v4, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2s_v3, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2as_v5, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2s_v5, Zones: [ 2, 3 ]
+
+
+### Capacity recommendations
+
+Capacity recommendations for the current selection virtual machine size `Standard_DC1ds_v3` in the selected availability zone `1`.
+
+**Recommended Action:** To increase the likelihood of a successful deployment, Azure has identified other recommended virtual machine sizes and zones. To deploy seamlessly, choose a different VM size in the same availability zone or a different availability zone with corresponding virtual machine size.
+
+**Recommendations**:
+
+- SKU: Standard_DC1ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC2ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC4ds_v3, Zones: [ 2 ]
+- SKU: Standard_DC1s_v3, Zones: [ 2 ]
+- SKU: Standard_D2ds_v5, Zones: [ 2, 3 ]
+- SKU: Standard_D2as_v4, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2s_v3, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2as_v5, Zones: [ 1, 2, 3 ]
+- SKU: Standard_D2s_v5, Zones: [ 2, 3 ]
+
+### Address the recommendations
+
+To address the situations where the VM SKU is not found or there is a capacity issue, update the move resource and then run resolve again. Here is an example for reference:
+
+1. Update virtual machine move resource object to new Zone or SKU as per the recommendations.
+
+    ```azurepowershell
+    $targetResourceSettingsObj.TargetVmSize = "Standard_DC1ds_v3"
+    $targetResourceSettingsObj.TargetAvailabilityZone = "3"
+    ```
+
+1. Update virtual machine move resource
+
+    ```azurepowershell
+    Add-AzResourceMoverMoveResource -ResourceGroupName "RegionToZone-DemoMCRG" -MoveCollectionName "RegionToZone-DemoMC" -SourceId "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.Compute/virtualMachines/vmtwo" -Name "demoVM-MoveResource2" -ResourceSetting $targetResourceSettingsObj
+    ```
+
+1. Run resolve again
+
+    `Resolve-AzResourceMoverMoveCollectionDependency -ResourceGroupName "RegionToZone-DemoMCRG" -MoveCollectionName "RegionToZone-DemoMC"`
+
+### Insufficient Quota
+
+Selected virtual machine can't be moved to availability zone due to insufficient quota.
+
+**Recommended Action:** In-sufficient quota found. Refer to link and contact [support](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits).
+
+
 
 ## Initiate move of VM resources
 
@@ -574,6 +642,22 @@ After the initial move, you must commit the move or discard it. **Commit** compl
 
   ---
 
+## Remove a resource
+
+You can remove a single resource or multiple resources from a `MoveCollection` using the following cmdlets:
+ 
+1.  Get a list of the move resources that are added to the move collection:
+    `$list = Get-AzResourceMoverMoveResource -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>"`
+ 
+1. Remove the move resources you found:
+    `Invoke-AzResourceMoverBulkRemove -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>" -MoveResource $($list.Name)`
+ 
+1. Remove the move collection:
+    `Remove-AzResourceMoverMoveCollection -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>"`
+
+> [!NOTE]
+> If you observe managed identities authorization issues, re-enable the managed identities access by following [these steps](#grant-access-to-the-managed-identity) again.
+
 
 ## Delete source regional VMs