Merge pull request #184621 from sefriend/autoscale-doc-updates

Autoscale doc updates

Author: AnnaMHuff

articles/virtual-desktop/autoscale-faq.yml

@@ -19,7 +19,7 @@ sections:
       - question: |
          How do I configure the autoscale feature so I run zero session hosts after working hours?
         answer: |
-         Ramp-down mode always uses the lowest possible number of session hosts. However, if there are existing user sessions, the lowest number of usable session hosts won't be zero. Configure a time limit policy to sign out all disconnected users to avoid having usable session hosts after hours.
+         Ramp-down mode always uses the lowest possible number of session hosts. However, if there are existing user sessions, the lowest number of usable session hosts won't be zero. To configure the time limit policy to sign out all disconnected users to avoid having usable session hosts after hours, go to **Local Computer Policy** > **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Remote Desktop Services** > **Remote Desktop Session Host** > **Session Time Limits** > **Set time limit for disconnected sessions**.
 
       - question: |
          Does autoscale create or delete virtual machines (VMs) based on service load?
@@ -74,9 +74,9 @@ sections:
       - question: |
          Can the autoscale feature turn off all the VMs in a host pool, or does it need to keep at least a few VMs on to work properly?
         answer: |
-         The autoscale feature can turn off all the VMs in a host pool if the minimum percentage of hosts is set to **0%** and there are no user sessions on the session host.
-      
+         The autoscale feature can turn off all VMs in a host pool if the minimum percentage of hosts is set to **0%** and there are no user sessions on the session hosts in the host pool.
+
       - question: |
          How many VMs need to be in a host pool for the autoscale feature to work properly?
         answer: |
-         At least 1.
+         At least one.

articles/virtual-desktop/autoscale-scaling-plan.md

@@ -23,7 +23,8 @@ The autoscale feature (preview) lets you scale your Azure Virtual Desktop deploy
 >[!NOTE]
 > - Azure Virtual Desktop (classic) doesn't support the autoscale feature. 
 > - Autoscale doesn't support Azure Virtual Desktop for Azure Stack HCI 
-> - Autsoscale doesn't support scaling of ephemeral disks.
+> - Autoscale doesn't support scaling of ephemeral disks.
+> - Autoscale doesn't support scaling of generalized VMs.
 
 
 For best results, we recommend using autoscale with VMs you deployed with Azure Virtual Desktop Azure Resource Manager templates or first-party tools from Microsoft.
@@ -123,7 +124,7 @@ To assign the custom role to grant access:
 
 2. Select the role you just created and continue to the next screen.
 
-3. Select **+Select members**. In the search bar, enter and select **Windows Virtual Desktop**, as shown in the following screenshot. When you have a Azure Virtual Desktop (classic) deployment and an Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects, you will see two apps with the same name. Select them both.
+3. Select **+Select members**. In the search bar, enter and select **Windows Virtual Desktop**, as shown in the following screenshot. When you have an Azure Virtual Desktop (classic) deployment and an Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects, you will see two apps with the same name. Select them both.
 
     > [!div class="mx-imgBorder"]
     > ![A screenshot of the add role assignment menu. The Select field is highlighted in red, with the user entering "Windows Virtual Desktop" into the search field.](media/search-for-role.png)
@@ -179,7 +180,7 @@ To create a scaling plan:
 
 8. For **Time zone**, select the time zone you'll use with your plan.
 
-9. In **Exclusion tags**, enter tags for VMs you don't want to include in scaling operations. For example, you might want to tag VMs that are set to drain mode so that autoscale doesn't override drain mode during maintenance.
+9. In **Exclusion tags**, enter a tag name for VMs you don't want to include in scaling operations. For example, you might want to tag VMs that are set to drain mode so that autoscale doesn't override drain mode during maintenance using the exclusion tag "excludeFromScaling". If you've set "excludeFromScaling" as the tag name field on any of the VMs in the host pool, the autoscale feature won't start, stop, or change the drain mode of those particular VMs.
         
     >[!NOTE]
     >- Though an exclusion tag will exclude the tagged VM from power management scaling operations, tagged VMs will still be considered as part of the calculation of the minimum percentage of hosts.