AVD added notes to highlight incompatibility between autoscale and scaling scripts

Author: dknappettmsft

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

@@ -25,7 +25,7 @@ The autoscale feature (preview) lets you scale your Azure Virtual Desktop deploy
 > - Autoscale doesn't support Azure Virtual Desktop for Azure Stack HCI 
 > - Autoscale doesn't support scaling of ephemeral disks.
 > - Autoscale doesn't support scaling of generalized VMs.
-
+> - You can't use the autoscale feature and [scale session hosts using Azure Automation](set-up-scaling-script.md) on the same host pool. You must use one or the other.
 
 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.
 
@@ -103,20 +103,20 @@ To create and assign the custom role to your subscription with the Azure portal:
 
 4. On the **Permissions** tab, add the following permissions to the subscription you're assigning the role to:
 
-    ```azcopy
-   		"Microsoft.Insights/eventtypes/values/read"
-				 "Microsoft.Compute/virtualMachines/deallocate/action"
-				 "Microsoft.Compute/virtualMachines/restart/action"
-				 "Microsoft.Compute/virtualMachines/powerOff/action"
-				 "Microsoft.Compute/virtualMachines/start/action"
-				 "Microsoft.Compute/virtualMachines/read"
-				 "Microsoft.DesktopVirtualization/hostpools/read"
-				 "Microsoft.DesktopVirtualization/hostpools/write"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/read"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/write"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/delete"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/read"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/sendMessage/action"
+    ```
+   	"Microsoft.Insights/eventtypes/values/read"
+	"Microsoft.Compute/virtualMachines/deallocate/action"
+	"Microsoft.Compute/virtualMachines/restart/action"
+	"Microsoft.Compute/virtualMachines/powerOff/action"
+	"Microsoft.Compute/virtualMachines/start/action"
+	"Microsoft.Compute/virtualMachines/read"
+	"Microsoft.DesktopVirtualization/hostpools/read"
+	"Microsoft.DesktopVirtualization/hostpools/write"
+	"Microsoft.DesktopVirtualization/hostpools/sessionhosts/read"
+	"Microsoft.DesktopVirtualization/hostpools/sessionhosts/write"
+	"Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/delete"
+	"Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/read"
+	"Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/sendMessage/action"
     ```
 
 5. When you're finished, select **Ok**.

articles/virtual-desktop/set-up-scaling-script.md

@@ -13,6 +13,9 @@ You can reduce your total Azure Virtual Desktop deployment cost by scaling your
 
 In this article, you'll learn about the scaling tool built with the Azure Automation account and Azure Logic App that automatically scales session host VMs in your Azure Virtual Desktop environment. To learn how to use the scaling tool, skip ahead to [Prerequisites](#prerequisites).
 
+> [!NOTE]
+> You can't scale session hosts using Azure Automation and use the [autoscale feature](autoscale-scaling-plan.md) on the same host pool. You must use one or the other.
+
 ## How the scaling tool works
 
 The scaling tool provides a low-cost automation option for customers who want to optimize their session host VM costs.
@@ -21,7 +24,7 @@ You can use the scaling tool to:
 
 - Schedule VMs to start and stop based on peak and off-peak business hours.
 - Scale out VMs based on number of sessions per CPU core.
-- Scale in VMs during Off-Peak hours, leaving the minimum number of session host VMs running.
+- Scale in VMs during off-peak hours, leaving the minimum number of session host VMs running.
 
 The scaling tool uses a combination of an Azure Automation account, a PowerShell runbook, a webhook, and the Azure Logic App to function. When the tool runs, Azure Logic App calls a webhook to start the Azure Automation runbook. The runbook then creates a job.