Skip to content

Commit 4979efd

Browse files
author
Ankita Dutta
committed
new updates
1 parent 1274ac7 commit 4979efd

File tree

3 files changed

+37
-41
lines changed

3 files changed

+37
-41
lines changed

articles/virtual-machines/move-virtual-machines-regional-zonal-faq.md

Lines changed: 11 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -18,66 +18,46 @@ This article answers common questions about Azure single instance virtual machin
1818

1919
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).
2020

21+
> [!NOTE]
22+
> Azure China (China North 3) and Azure Govt (US Gov Virginia) are also supported.
23+
2124
### Where is the metadata stored?
2225

2326
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:
2427

2528
| Region group | Region | Metadata region |
2629
| --- | --- | ----|
27-
| **Americas** | centralus | eastus2 |
28-
| | centraluseuap | centraluseuap |
30+
| **Americas** | eastus2 | eastus2 |
2931
| | eastus | eastus2 |
30-
| | eastus2 | eastus2 |
31-
| | eastus2euap | eastus2euap |
32-
| | westus | eastus2 |
3332
| | westus2 | eastus2 |
34-
| | northcentralus | eastus2 |
3533
| | southcentralus | eastus2 |
36-
| | westcentralus | eastus2 |
3734
| | brazilsouth | brazilsouth |
38-
| | brazilus | brazilsouth |
3935
| | canadacentral | canadacentral |
40-
| | canadaeast | canadacentral |
41-
| | brazilsoutheast | brazilsouth |
4236
| | westus3 | eastus2 |
37+
||||
4338
| **Europe**| northeurope | northeurope |
4439
| | westeurope | northeurope |
45-
| | uknorth | uksouth |
46-
| | uksouth2 | uksouth |
4740
| | uksouth | uksouth |
48-
| | ukwest | uksouth |
4941
| | francecentral | francecentral |
50-
| | francesouth | francecentral |
5142
| | switzerlandnorth | switzerlandnorth |
52-
| | switzerlandwest | switzerlandnorth |
53-
| | germanynorth | germanywestcentral |
5443
| | germanywestcentral | germanywestcentral |
5544
| | norwayeast | norwayeast |
56-
| | norwaywest | norwayeast |
5745
| | swedencentral | swedencentral |
5846
| | polandcentral | polandcentral |
5947
| | spaincentral | northeurope |
6048
| | italynorth | northeurope |
61-
| | swedensouth | swedencentral |
62-
| **Middle East** | uaecentral | uaenorth |
63-
| | uaenorth | uaenorth |
49+
||||
50+
| **Middle East** | uaenorth | uaenorth |
6451
| | qatarcentral | qatarcentral |
65-
| **Asia Pacific** | japaneast | |
66-
| | japanwest | japaneast |
52+
||||
53+
| **Asia Pacific** | japaneast | japaneast |
6754
| | eastasia | southeastasia |
6855
| | southeastasia | southeastasia |
69-
| | australiasoutheast | australiaeast |
7056
| | australiaeast | australiaeast |
71-
| | westindia | centralindia |
72-
| | southindia | centralindia |
7357
| | centralindia | centralindia |
7458
| | koreacentral | koreacentral |
75-
| | koreasouth | koreacentral |
76-
| | jioindiawest | centralindia |
77-
| | jioindiacentral | centralindia |
78-
| | malaysiasouth | southeastasia |
59+
||||
7960
| **Africa** | southafricanorth | southeastasia |
80-
| | southafricawest | southeastasia |
8161

8262

8363
### Is the collected metadata encrypted?
@@ -139,7 +119,7 @@ Managed identity previously known as Managed Service Identity (MSI), is a featur
139119

140120
### Can I move my resources from Regional to Zonal and across subscriptions?
141121

142-
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.
122+
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.
143123

144124
### Are Azure Backup/DR, RBAC, Tags, Policies, and extensions on virtual machines supported?
145125

articles/virtual-machines/move-virtual-machines-regional-zonal-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ To select the VMs for the move, follow these steps:
4141
2. In the virtual machine resource pane, select **Availability + scaling** > **edit**.
4242
:::image type="content" source="./media/tutorial-move-regional-zonal/scaling-pane.png" alt-text="Screenshot of Availability + scaling pane.":::
4343

44-
Alternatively, in the **DemoTestVM1** overview plane, you can select **Availability + scale** > **Availability + scaling**.
44+
Alternatively, in the virtual machine overview plane, you can select **Availability + scale** > **Availability + scaling**.
4545
4646

4747

articles/virtual-machines/move-virtual-machines-regional-zonal-powershell.md

Lines changed: 25 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -481,7 +481,7 @@ Check whether the regional VMs you added have any dependencies on other resource
481481
482482
### Availability Zones VM SKU, Quota and Capacity validations
483483
484-
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 VM SKU is not available.
484+
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.
485485
486486
#### VM SKU not available
487487
@@ -526,20 +526,20 @@ To address the situations where the VM SKU is not found or there is a capacity i
526526
527527
1. Update virtual machine move resource object to new Zone or SKU as per the recommendations.
528528
529-
```azurepowershell
530-
$targetResourceSettingsObj.TargetVmSize = "Standard_DC1ds_v3"
531-
$targetResourceSettingsObj.TargetAvailabilityZone = "3"
532-
```
529+
```azurepowershell
530+
$targetResourceSettingsObj.TargetVmSize = "Standard_DC1ds_v3"
531+
$targetResourceSettingsObj.TargetAvailabilityZone = "3"
532+
```
533533
534534
1. Update virtual machine move resource
535535
536-
```azurepowershell
537-
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
538-
```
536+
```azurepowershell
537+
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
538+
```
539539
540540
1. Run resolve again
541541
542-
`Resolve-AzResourceMoverMoveCollectionDependency -ResourceGroupName "RegionToZone-DemoMCRG" -MoveCollectionName "RegionToZone-DemoMC"`
542+
`Resolve-AzResourceMoverMoveCollectionDependency -ResourceGroupName "RegionToZone-DemoMCRG" -MoveCollectionName "RegionToZone-DemoMC"`
543543
544544
### Insufficient Quota
545545
@@ -642,6 +642,22 @@ After the initial move, you must commit the move or discard it. **Commit** compl
642642

643643
---
644644

645+
## Remove a resource
646+
647+
You can remove a single resource or multiple resources from a `MoveCollection` using the following cmdlets:
648+
649+
1. Get a list of the move resources that are added to the move collection:
650+
`$list = Get-AzResourceMoverMoveResource -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>"`
651+
652+
1. Remove the move resources you found:
653+
`Invoke-AzResourceMoverBulkRemove -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>" -MoveResource $($list.Name)`
654+
655+
1. Remove the move collection:
656+
`Remove-AzResourceMoverMoveCollection -ResourceGroupName "<MoveCollectionResourceGroupName>" -MoveCollectionName "<MoveCollectionName>"`
657+
658+
> [!NOTE]
659+
> If you observe managed identities authorization issues, re-enable the managed identities access by following [these steps](#remove-a-resource) again.
660+
645661

646662
## Delete source regional VMs
647663

0 commit comments

Comments
 (0)