Merge pull request #106987 from cynthn/49785

Fixes public PR: #49785

Author: megvanhuygen

articles/virtual-machines/linux/dedicated-hosts-portal.md

@@ -4,7 +4,8 @@ description: Deploy VMs to dedicated hosts using the Azure portal.
 author: cynthn
 ms.service: virtual-machines
 ms.topic: article
-ms.date: 01/09/2020
+ms.workload: infrastructure
+ms.date: 03/10/2020
 ms.author: cynthn
 
 #Customer intent: As an IT administrator, I want to learn about more about using a dedicated host for my Azure virtual machines
@@ -36,6 +37,26 @@ This article guides you through how to create an Azure [dedicated host](dedicate
 
 It will take a few minutes for your VM to be deployed.
 
+## Add an existing VM 
+
+You can add an exiting 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:
+
+- 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 could not 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, see [Move a VM out of a proximity placement group](https://docs.microsoft.com/azure/virtual-machines/windows/proximity-placement-groups#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.
+
+Move the VM to a dedicated host using the [portal](https://portal.azure.com).
+
+1. Open the page for the VM.
+1. Select **Stop** to stop\deallocate the VM.
+1. Select **Configuration** from the left menu.
+1. Select a host group and a host from the drop-down menus.
+1. When you are done, select **Save** at the top of the page.
+1. After the VM has been added to the host, select **Overview** from the left menu.
+1. At the top of the page, select **Start** to restart the VM.
+
 ## Next steps
 
 - For more information, see the [Dedicated hosts](dedicated-hosts.md) overview.

articles/virtual-machines/windows/dedicated-hosts-portal.md

@@ -1,16 +1,11 @@
 ---
-title: Deploy Azure dedicated hosts using the Azure portal 
-description: Deploy VMs to dedicated hosts using the Azure portal.
-services: virtual-machines-windows
+title: Deploy Azure dedicated hosts using the portal 
+description: Deploy VMs to dedicated hosts using the portal.
 author: cynthn
-manager: gwallace
-editor: tysonn
-tags: azure-resource-manager
 ms.service: virtual-machines-windows
 ms.topic: article
-ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure
-ms.date: 07/26/2019
+ms.date: 03/10/2020
 ms.author: cynthn
 
 #Customer intent: As an IT administrator, I want to learn about more about using a dedicated host for my Azure virtual machines
@@ -37,11 +32,30 @@ This article guides you through how to create an Azure [dedicated host](dedicate
 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**.
 
+## Add an existing VM 
+
+You can add an exiting 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:
+
+- 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 could not 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, see [Move a VM out of a proximity placement group](https://docs.microsoft.com/azure/virtual-machines/windows/proximity-placement-groups#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.
+
+Move the VM to a dedicated host using the [portal](https://portal.azure.com).
+
+1. Open the page for the VM.
+1. Select **Stop** to stop\deallocate the VM.
+1. Select **Configuration** from the left menu.
+1. Select a host group and a host from the drop-down menus.
+1. When you are done, select **Save** at the top of the page.
+1. After the VM has been added to the host, select **Overview** from the left menu.
+1. At the top of the page, select **Start** to restart the VM.
 
 ## Next steps
 
 - For more information, see the [Dedicated hosts](dedicated-hosts.md) overview. 
 
 - There is sample template, found [here](https://github.com/Azure/azure-quickstart-templates/blob/master/201-vm-dedicated-hosts/README.md), that uses both zones and fault domains for maximum resiliency in a region.
 
-- You can also deploy a dedicated host using [Azure PowerShell](dedicated-hosts-powershell.md).
+- You can also deploy a dedicated host using [Azure PowerShell](dedicated-hosts-powershell.md).

includes/virtual-machines-common-dedicated-hosts-portal.md

@@ -5,7 +5,7 @@
  author: cynthn
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 01/09/2020
+ ms.date: 03/10/2020
  ms.author: cynthn
  ms.custom: include file
 ---
@@ -31,8 +31,6 @@ In this example, we will create a host group using 1 availability zone and 2 fau
 1. Open the Azure [portal](https://portal.azure.com).
 1. Select **Create a resource** in the upper left corner.
 1. Search for **Host group** and then select **Host Groups** from the results.
-
-	![Host groups search result.](./media/virtual-machines-common-dedicated-hosts-portal/host-group.png)
 1. In the **Host Groups** page, select **Create**.
 1. Select the subscription you would like to use, and then select **Create new** to create a new resource group.
 1. Type *myDedicatedHostsRG* as the **Name** and then select **OK**.
@@ -41,8 +39,6 @@ In this example, we will create a host group using 1 availability zone and 2 fau
 1. For **Availability Zone**, select **1**.
 1. For **Fault domain count**, select **2**.
 1. Select **Review + create** and then wait for validation.
-
-	![Host group settings](./media/virtual-machines-common-dedicated-hosts-portal/host-group-settings.png)
 1. Once you see the **Validation passed** message, select **Create** to create the host group.
 
 It should only take a few moments to create the host group.
@@ -57,16 +53,12 @@ If you set a fault domain count for your host group, you will be asked to specif
 
 1. Select **Create a resource** in the upper left corner.
 1. Search for **Dedicated host** and then select **Dedicated hosts** from the results.
-
-	![Host groups search result.](./media/virtual-machines-common-dedicated-hosts-portal/host.png)
 1. In the **Dedicated Hosts** page, select **Create**.
 1. Select the subscription you would like to use.
 1. Select *myDedicatedHostsRG* as the **Resource group**.
 1. In **Instance details**, type *myHost* for the **Name** and select *East US* for the location.
-1. In **Hardware profile**, select *Standard Es3 family - Type 1* for the **Size family**, select *myHostGrup* for the **Host group** and then select *1* for the **Fault domain**. Leave the defaults for the rest of the fields.
+1. In **Hardware profile**, select *Standard Es3 family - Type 1* for the **Size family**, select *myHostGroup* for the **Host group** and then select *1* for the **Fault domain**. Leave the defaults for the rest of the fields.
 1. When you are done, select **Review + create** and wait for validation.
-
-	![Host settings](./media/virtual-machines-common-dedicated-hosts-portal/host-settings.png)
 1. Once you see the **Validation passed** message, select **Create** to create the host.