Merge pull request #200498 from vamckMS/adh-ultra-ssd-vk

Adh ultra ssd vk

Author: PRMerger18

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

@@ -11,6 +11,7 @@ ms.date: 09/01/2021
 ms.reviewer: mattmcinnes
 
 
+
 #Customer intent: As an IT administrator, I want to learn about more about using a dedicated host for my Azure virtual machines
 ---
 
@@ -24,18 +25,23 @@ This article guides you through how to create an Azure [dedicated host](dedicate
 ## Limitations
 
 - The sizes and hardware types available for dedicated hosts vary by region. Refer to the host [pricing page](https://aka.ms/ADHPricing) to learn more.
+- Not all Azure VM SKUs, regions and availability zones support ultra disks, for more information about this topic, see [Azure ultra disks](disks-enable-ultra-ssd.md) . Ultra disk support for dedicated hosts is currently in preview.
 - The fault domain count of the virtual machine scale set can't exceed the fault domain count of the host group.
 
 ## Create a host group
 
-A **host group** is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it. When planning for high availability, there are more options. You can use one or both of the following options with your dedicated hosts:
+A **host group** is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it. You can use one or both of the following options with your dedicated hosts to ensure high availability:
 - Span across multiple availability zones. In this case, you're required to have a host group in each of the zones you wish to use.
 - Span across multiple fault domains, which are mapped to physical racks.
 
 In either case, you need to provide the fault domain count for your host group. If you don't want to span fault domains in your group, use a fault domain count of 1.
 
 You can also decide to use both availability zones and fault domains.
 
+Enabling ultra disks (Preview) is a host group level setting and can't be changed after a host group is created.
+
+If you intend to use LSv2 or M series VMs, with ultra disks (Preview) on dedicated hosts, set host group's **Fault domain count** to **1**.
+
 ### [Portal](#tab/portal)
 
 In this example, we'll create a host group using one availability zone and two fault domains.
@@ -49,6 +55,7 @@ In this example, we'll create a host group using one availability zone and two f
 1. For **Host group name**, type *myHostGroup*.
 1. For **Location**, select **East US**.
 1. For **Availability Zone**, select **1**.
+1. Select **Enable Ultra SSD** (Preview) to use ultra disks with supported Virtual Machines.
 1. For **Fault domain count**, select **2**.
 1. Select **Automatic placement** to automatically assign VMs and scale set instances to an available host in this group.
 1. Select **Review + create** and then wait for validation.
@@ -64,6 +71,17 @@ Not all host SKUs are available in all regions, and availability zones. You can
 ```azurecli-interactive
 az vm list-skus -l eastus2  -r hostGroups/hosts  -o table
 ```
+You can also verify if a VM series supports ultra disks (Preview).
+
+```azurecli-interactive
+subscription="<mySubID>"
+# example value is southeastasia
+region="<myLocation>"
+# example value is Standard_E64s_v3
+vmSize="<myVMSize>"
+
+az vm list-skus --resource-type virtualMachines  --location $region --query "[?name=='$vmSize'].locationInfo[0].zoneDetails[0].Name" --subscription $subscription
+```
 
 In this example, we'll use [az vm host group create](/cli/azure/vm/host/group#az-vm-host-group-create) to create a host group using both availability zones and fault domains.
 
@@ -77,6 +95,8 @@ az vm host group create \
 
 Add the `--automatic-placement true` parameter to have your VMs and scale set instances automatically placed on hosts, within a host group. For more information, see [Manual vs. automatic placement](dedicated-hosts.md#manual-vs-automatic-placement).
 
+Add the `--ultra-ssd-enabled true` (Preview) parameter to enable creation of VMs that can support ultra disks.
+
 
 **Other examples**
 
@@ -99,6 +119,17 @@ az vm host group create \
    --platform-fault-domain-count 2
 ```
 
+The following code snippet uses [az vm host group create](/cli/azure/vm/host/group#az-vm-host-group-create) to create a host group that supports ultra disks (Preview) and auto placement of VMs enabled.
+
+```azurecli-interactive
+az vm host group create \
+   --name myFDHostGroup \
+   -g myDHResourceGroup \
+   -z 1 \
+   --ultra-ssd-enabled true \
+   --platform-fault-domain-count 2 \
+   --automatic-placement true 
+```
 ### [PowerShell](#tab/powershell)
 
 This example uses [New-AzHostGroup](/powershell/module/az.compute/new-azhostgroup) to create a host group in zone 1, with 2 fault domains.
@@ -110,15 +141,20 @@ $location = "EastUS"
 
 New-AzResourceGroup -Location $location -Name $rgName
 $hostGroup = New-AzHostGroup `
-   -Location $location `
    -Name myHostGroup `
-   -PlatformFaultDomain 2 `
    -ResourceGroupName $rgName `
-   -Zone 1
+   -Location $location `
+   -Zone 1 `
+   -EnableUltraSSD `
+   -PlatformFaultDomain 2 `
+   -SupportAutomaticPlacement true
 ```
 
+Add the `-SupportAutomaticPlacement true` parameter to have your VMs and scale set instances automatically placed on hosts, within a host group. For more information about this topic, see [Manual vs. automatic placement ](dedicated-hosts.md#manual-vs-automatic-placement).
+
+
+Add the `-EnableUltraSSD` (Preview) parameter to enable creation of VMs that can support ultra disks.
 
-Add the `-SupportAutomaticPlacement true` parameter to have your VMs and scale set instances automatically placed on hosts, within a host group. For more information, see [Manual vs. automatic placement](dedicated-hosts.md#manual-vs-automatic-placement).
 
 ---
 
@@ -177,6 +213,8 @@ $dHost = New-AzHost `
 
 Now create a VM on the host.
 
+If you would like to create a VM with ultra disks support, make sure the host group in which the VM will be placed is ultra SSD enabled (Preview). Once you've confirmed, create the VM in the same host group. See [Deploy an ultra disk](disks-enable-ultra-ssd.md#deploy-an-ultra-disk) for the steps to attach an ultra disk to a VM.
+
 ### [Portal](#tab/portal)
 
 1. Choose **Create a resource** in the upper left corner of the Azure portal.
@@ -301,7 +339,7 @@ You can add an existing VM to a dedicated host, but the VM must first be Stop\De
 
 - 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, 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.
 
@@ -330,7 +368,7 @@ az vm update - n myVM -g myResourceGroup --host myHost
 az vm start -n myVM -g myResourceGroup
 ```
 
-For automatically placed VMs, only update the host group. For more information, see [Manual vs. automatic placement](dedicated-hosts.md#manual-vs-automatic-placement).
+For automatically placed VMs, only update the host group. For more information about this topic, see [Manual vs. automatic placement](dedicated-hosts.md#manual-vs-automatic-placement).
 
 Replace the values with your own information.
 
@@ -402,7 +440,7 @@ az vm host get-instance-view \
    --name myHost
 ```
 
-The output will look similar to this:
+The output will look similar to the below example:
 
 ```json
 {
@@ -513,7 +551,7 @@ Get-AzHost `
    -InstanceView
 ```
 
-The output will look similar to this:
+The output will look similar to the below example:
 
 ```
 ResourceGroupName      : myDHResourceGroup
@@ -611,7 +649,7 @@ Once you've deleted all of your hosts, you may delete the host group using [az v
 az vm host group delete -g myDHResourceGroup --host-group myHostGroup
 ```
 
-You can also delete the entire resource group in a single command. This will delete all resources created in the group, including all of the VMs, hosts and host groups.
+You can also delete the entire resource group in a single command. The following command will delete all resources created in the group, including all of the VMs, hosts and host groups.
 
 ```azurecli-interactive
 az group delete -n myDHResourceGroup
@@ -638,7 +676,7 @@ Once you've deleted all of your hosts, you may delete the host group using [Remo
 Remove-AzHost -ResourceGroupName $rgName -Name myHost
 ```
 
-You can also delete the entire resource group in a single command using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup). This will delete all resources created in the group, including all of the VMs, hosts and host groups.
+You can also delete the entire resource group in a single command using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup). This following command will delete all resources created in the group, including all of the VMs, hosts and host groups.
 
 ```azurepowershell-interactive
 Remove-AzResourceGroup -Name $rgName
@@ -648,7 +686,7 @@ Remove-AzResourceGroup -Name $rgName
 
 ## Next steps
 
-- For more information, see the [Dedicated hosts](dedicated-hosts.md) overview.
+- For more information about this topic, see the [Dedicated hosts](dedicated-hosts.md) overview.
 
 - There's sample template, available at [Azure Quickstart Templates](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/vm-dedicated-hosts/README.md), which uses both zones and fault domains for maximum resiliency in a region.