Skip to content

Commit 737495a

Browse files
committed
table
1 parent a67832d commit 737495a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/virtual-desktop/deploy-azure-virtual-desktop.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,12 +213,14 @@ Here's how to create a host pool using the Azure portal.
213213
| Resource group | This automatically defaults to the resource group you chose your host pool to be in on the *Basics* tab, but you can also select an alternative. |
214214
| Name prefix | Enter a name for your session hosts, for example **hp01-sh**.<br /><br />This value is used as the prefix for your session hosts. Each session host has a suffix of a hyphen and then a sequential number added to the end, for example **hp01-sh-0**.<br /><br />This name prefix can be a maximum of 11 characters and is used in the computer name in the operating system. The prefix and the suffix combined can be a maximum of 15 characters. Session host names must be unique. |
215215
| Virtual machine type | Select **Azure virtual machine**. |
216-
| Virtual machine location | Select **West US**, then select **Deploy to an Azure Extended Zone**. |
216+
| Virtual machine location | Select the Azure region where you want to deploy your session hosts. This must be the same region that your virtual network is in. Then select **Deploy to an Azure Extended Zone**. |
217217
| **Azure Extended Zones** | |
218218
| Azure Extended Zone | Select **Los Angeles**. |
219219
| Place the session host(s) behind an existing load balancing solution? | Check the box. This will show options for selecting a load balancer and a backend pool.|
220220
| Select a load balancer | Select an existing load balancer on the virtual network that the session hosts are being deployed to. |
221221
| Select a backend pool | Select a backend pool on the load balancer to that you want to place the sessions host(s) into. |
222+
| Availability options | Select from **[availability zones](../reliability/availability-zones-overview.md)**, **[availability set](../virtual-machines/availability-set-overview.md)**, or **No infrastructure dependency required**. If you select availability zones or availability set, complete the extra parameters that appear. |
223+
| Security type | Select from **Standard**, **[Trusted launch virtual machines](../virtual-machines/trusted-launch.md)**, or **[Confidential virtual machines](../confidential-computing/confidential-vm-overview.md)**.<br /><br />- If you select **Trusted launch virtual machines**, options for **secure boot** and **vTPM** are automatically selected.<br /><br />- If you select **Confidential virtual machines**, options for **secure boot**, **vTPM**, and **integrity monitoring** are automatically selected. You can't opt out of vTPM when using a confidential VM. |
222224
</details>
223225

224226

0 commit comments

Comments
 (0)