Merge pull request #271736 from sipastak/avd-start-vm-connect-cli

Start VM on Connect update powershell and add CLI

Author: Stacyrch140

articles/virtual-desktop/start-virtual-machine-connect.md

@@ -29,6 +29,7 @@ The time it takes for a user to connect to a session host VM that is powered off
 To use Start VM on Connect, make sure you follow these guidelines:
 
 - You can only configure Start VM on Connect on existing host pools. You can't enable it at the same time you create a new host pool.
+
 - The following Remote Desktop clients support Start VM on Connect:
     - The [Windows client](./users/connect-windows.md?toc=/azure/virtual-desktop/toc.json&bc=/azure/virtual-desktop/breadcrumb/toc.json) (version 1.2.2061 or later)
     - The [Web client](./users/connect-web.md?toc=/azure/virtual-desktop/toc.json&bc=/azure/virtual-desktop/breadcrumb/toc.json)
@@ -37,8 +38,13 @@ To use Start VM on Connect, make sure you follow these guidelines:
     - The [Android and Chrome OS client](./users/connect-android-chrome-os.md?toc=/azure/virtual-desktop/toc.json&bc=/azure/virtual-desktop/breadcrumb/toc.json) (version 10.0.10 or later)
     - The [Microsoft Store client](./users/connect-microsoft-store.md?toc=/azure/virtual-desktop/toc.json&bc=/azure/virtual-desktop/breadcrumb/toc.json) (version 10.2.2005.0 or later)
     - Thin clients listed in [Thin client support](./users/connect-thin-clients.md?toc=/azure/virtual-desktop/toc.json&bc=/azure/virtual-desktop/breadcrumb/toc.json)
+    
 - If you want to configure Start VM on Connect using PowerShell, you'll need to have [the Az.DesktopVirtualization PowerShell module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization) (version 2.1.0 or later) installed on the device you use to run the commands.
+
 - You must grant Azure Virtual Desktop access to power on session host VMs, check their status, and report diagnostic information. You must have the `Microsoft.Authorization/roleAssignments/write` permission on your subscriptions in order to assign the role-based access control (RBAC) role for the Azure Virtual Desktop service principal on those subscriptions. This is part of **User Access Administrator** and **Owner** built in roles.
+
+- The Azure account you use to configure Start VM on Connect must have the [Desktop Virtualization Host Pool Contributor](rbac.md#desktop-virtualization-host-pool-contributor) role assigned.
+
 - If you enable Start VM on Connect on a host pool, you must make sure that the host pool name, the names of the session hosts in that host pool, and the resource group name don't have non-ANSI characters. If their names contain non-ANSI characters, then Start VM on Connect won't work as expected.
 
 ## Assign the Desktop Virtualization Power On Contributor role with the Azure portal
@@ -53,7 +59,7 @@ To learn how to assign the *Desktop Virtualization Power On Contributor* role to
 
 Now that you've assigned the *Desktop Virtualization Power On Contributor* role to the service principal on your subscriptions, you can configure Start VM on Connect using the Azure portal or PowerShell.
 
-# [Portal](#tab/azure-portal)
+# [Azure portal](#tab/azure-portal)
 
 To configure Start VM on Connect using the Azure portal:
 
@@ -69,27 +75,13 @@ To configure Start VM on Connect using the Azure portal:
 
 2. Select **Save** to apply the settings.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 You need to make sure you have the names of the resource group and host pool you want to configure. To configure Start VM on Connect using PowerShell:
 
-1. Open a PowerShell prompt.
-
-1. Sign in to Azure using the `Connect-AzAccount` cmdlet. For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps)
-
-1. Find the name of the subscription that contains host pools and session host VMs you want to use with Start VM on Connect by listing all that are available to you:
+[!INCLUDE [include-cloud-shell-local-powershell](includes/include-cloud-shell-local-powershell.md)]
 
-   ```powershell
-   Get-AzSubscription
-   ```
-
-1. Change your current Azure session to use the subscription you identified in the previous step, replacing the value for `-SubscriptionName` with the name or ID of the subscription:
-
-   ```powershell
-   Set-AzContext -Subscription "<subscription name or id>"
-   ```
-
-1. To enable or disable Start VM on Connect, do one of the following steps:
+2. To enable or disable Start VM on Connect, do one of the following steps:
 
    1. To enable Start VM on Connect, run the following command, replacing the value for `-ResourceGroupName` and `-Name` with your values:
 
@@ -103,8 +95,36 @@ You need to make sure you have the names of the resource group and host pool you
       Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -StartVMOnConnect:$false
       ```
 
+# [Azure CLI](#tab/azure-cli)
+
+You need to make sure you have the names of the resource group and host pool you want to configure. To configure Start VM on Connect using
+
+[!INCLUDE [include-cloud-shell-local-cli](includes/include-cloud-shell-local-cli.md)]
+
+2. To enable or disable Start VM on Connect, do one of the following steps:
+    1. To enable Start VM on Connect, run the following command, replacing the value for `--resource-group` and `--name` with your values:
+    
+          ```azurecli
+          az desktopvirtualization hostpool update \
+               --resource-group $resourceGroupName \
+               --name $hostPoolName \
+               --start-vm-on-connect true
+          ```
+    
+    1. To disable Start VM on Connect, run the following command, replacing the value for `--resource-group` and `--name` with your values:
+    
+          ```azurecli
+          az desktopvirtualization hostpool update \
+               --resource-group $resourceGroupName \
+               --name $hostPoolName \
+               --start-vm-on-connect false
+          ```
+    
+
 ---
 
+
+
 >[!NOTE]
 >In pooled host pools, Start VM on Connect will start a VM every five minutes at most. If other users try to sign in during this five-minute period while there aren't any available resources, Start VM on Connect won't start a new VM. Instead, the users trying to sign in will receive an error message that says, "No resources available."