Merge pull request #268708 from vamckMS/docs-editor/dedicated-hosts-how-to-1710200593

update-adh-how-to-page-reassign-2

Author: prmerger-automator[bot]

articles/virtual-machines/dedicated-hosts-how-to.md

@@ -220,7 +220,7 @@ If you would like to create a VM with ultra disks support, make sure the host gr
 1. For the size, select **Change size**. In the list of available sizes, choose one from the Esv3 series, like **Standard E2s v3**. You may need to clear the filter in order to see all of the available sizes.
 1. Complete the rest of the fields on the **Basics** tab as needed.
 1. If you want to specify which host to use for your VM, then at the top of the page, select the **Advanced** tab and in the **Host** section, select *myHostGroup* for **Host group** and *myHost* for the **Host**. Otherwise, your VM will automatically be placed on a host with capacity.
-	![Select host group and host](./media/dedicated-hosts-portal/advanced.png)
+    ![Select host group and host](./media/dedicated-hosts-portal/advanced.png)
 1. Leave the remaining defaults and then select the **Review + create** button at the bottom of the page.
 1. When you see the message that validation has passed, select **Create**.
 
@@ -328,13 +328,14 @@ If you want to manually choose which host to deploy the scale set to, add `--hos
 
 ---
 
-## Add an existing VM
+## Reassign an existing VM
 
-You can add an existing VM to a dedicated host, but the VM must first be Stop\Deallocated. Before you move a VM to a dedicated host, make sure that the VM configuration is supported:
+You can add reassign an existing multitenant VM or dedicated host VM to a different dedicated host, but the VM must first be Stop\Deallocated. Before you move a VM to a dedicated host, make sure that the VM configuration is supported:
 
 - The VM size must be in the same size family as the dedicated host. For example, if your dedicated host is DSv3, then the VM size could be Standard_D4s_v3, but it couldn't be a Standard_A4_v2.
 - The VM needs to be located in same region as the dedicated host.
-- The VM can't be part of a proximity placement group. Remove the VM from the proximity placement group before moving it to a dedicated host. For more information about this topic, see [Move a VM out of a proximity placement group](./windows/proximity-placement-groups.md#move-an-existing-vm-out-of-a-proximity-placement-group)
+- The VM can't be part of a proximity placement group. Remove the VM from the proximity placement group before moving it to a dedicated host. For more information about this topic, see [Move a VM out of a proximity placement group](./windows/proximity-placement-groups.md#move-an-existing-vm-out-of-a-proximity-placement-group).
+
 - The VM can't be in an availability set.
 - If the VM is in an availability zone, it must be the same availability zone as the host group. The availability zone settings for the VM and the host group must match.
 

articles/virtual-machines/sizes/migration-guides/dedicated-host-migration-guide.md

@@ -124,7 +124,7 @@ On Azure portal, go through the following steps:
 >[!NOTE] 
 > **Skip this step for automatically placed VMs and virtual machine scale set.** 
 
-Once the target Dedicated Host has been created and the VM has been stopped, [reassign the VM to the target Dedicated Host](../../dedicated-hosts-how-to.md#add-an-existing-vm).
+Once the target Dedicated Host has been created and the VM has been stopped, [reassign the VM to the target Dedicated Host](../../dedicated-hosts-how-to.md#reassign-an-existing-vm).
 
 #### Start the VM(s) or virtual machine scale set