Merge pull request #189307 from dknappettmsft/avd-peak-offpeak-definition

AVD scaling script - defined peak and off-peak hours

Author: PRMerger19

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

@@ -19,12 +19,18 @@ The scaling tool provides a low-cost automation option for customers who want to
 
 You can use the scaling tool to:
 
-- Schedule VMs to start and stop based on Peak and Off-Peak business hours.
+- 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.
 
 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.
 
+Peak and off-peak hours are defined as:
+
+| Peak  | Off-peak |
+|--|--|
+| The time when *maximum* user session concurrency is expected to be reached. | The time when  *minimum* user session concurrency is expected to be reached. |
+
 During peak usage time, the job checks the current number of sessions and the VM capacity of the current running session host for each host pool. It uses this information to calculate if the running session host VMs can support existing sessions based on the *SessionThresholdPerCPU* parameter defined for the **CreateOrUpdateAzLogicApp.ps1** file. If the session host VMs can't support existing sessions, the job starts additional session host VMs in the host pool.
 
 >[!NOTE]
@@ -63,10 +69,10 @@ Before you start setting up the scaling tool, make sure you have the following t
 
 The machine you use to deploy the tool must have:
 
-- Windows PowerShell 5.1 or later
-- The Microsoft Az PowerShell module
+- PowerShell 5.1 or later
+- The [Azure Az PowerShell module](/powershell/azure/new-azureps-module-az)
 
-If you have everything ready, then let's get started.
+If you have everything ready, let's get started.
 
 ## Create or update an Azure Automation account
 
@@ -75,7 +81,7 @@ If you have everything ready, then let's get started.
 
 First, you'll need an Azure Automation account to run the PowerShell runbook. The process this section describes is valid even if you have an existing Azure Automation account that you want to use to set up the PowerShell runbook. Here's how to set it up:
 
-1. Open Windows PowerShell.
+1. Open PowerShell.
 
 2. Run the following cmdlet to sign in to your Azure account.
 
@@ -152,7 +158,7 @@ To create a Run As account in your Azure Automation account:
 
 Finally, you'll need to create the Azure Logic App and set up an execution schedule for your new scaling tool. First, download and import the [Desktop Virtualization PowerShell module](powershell-module.md) to use in your PowerShell session if you haven't already.
 
-1. Open Windows PowerShell.
+1. Open PowerShell.
 
 2. Run the following cmdlet to sign in to your Azure account.
 
@@ -288,15 +294,15 @@ When you report an issue, you'll need to provide the following information to he
 
 If you decided to use Log Analytics, you can view all the log data in a custom log named **WVDTenantScale_CL** under **Custom Logs** in the **Logs** view of your Log Analytics Workspace. We've listed some sample queries you might find helpful.
 
-- To see all logs for a host pool, enter the following query
+- To see all logs for a host pool, enter the following query:
 
     ```Kusto
     WVDTenantScale_CL
     | where hostpoolName_s == "<host_pool_name>"
     | project TimeStampUTC = TimeGenerated, TimeStampLocal = TimeStamp_s, HostPool = hostpoolName_s, LineNumAndMessage = logmessage_s, AADTenantId = TenantId
     ```
 
-- To view the total number of currently running session host VMs and active user sessions in your host pool, enter the following query
+- To view the total number of currently running session host VMs and active user sessions in your host pool, enter the following query:
 
     ```Kusto
     WVDTenantScale_CL
@@ -307,7 +313,7 @@ If you decided to use Log Analytics, you can view all the log data in a custom l
     | project TimeStampUTC = TimeGenerated, TimeStampLocal = TimeStamp_s, HostPool = hostpoolName_s, LineNumAndMessage = logmessage_s, AADTenantId = TenantId
     ```
 
-- To view the status of all session host VMs in a host pool, enter the following query
+- To view the status of all session host VMs in a host pool, enter the following query:
 
     ```Kusto
     WVDTenantScale_CL
@@ -316,7 +322,7 @@ If you decided to use Log Analytics, you can view all the log data in a custom l
     | project TimeStampUTC = TimeGenerated, TimeStampLocal = TimeStamp_s, HostPool = hostpoolName_s, LineNumAndMessage = logmessage_s, AADTenantId = TenantId
     ```
 
-- To view any errors and warnings, enter the following query
+- To view any errors and warnings, enter the following query:
 
     ```Kusto
     WVDTenantScale_CL
@@ -326,4 +332,4 @@ If you decided to use Log Analytics, you can view all the log data in a custom l
 
 ## Report issues
 
-Issue reports for the scaling tool are currently being handled by Microsoft Support. When you make an issue report, make sure to follow the instructions in [Reporting issues](#reporting-issues). If you have feedback about the tool or want to request new features, open a GitHub issue labeled "4-WVD-scaling-tool" on the [RDS GitHub page](https://github.com/Azure/RDS-Templates/issues?q=is%3Aissue+is%3Aopen+label%3A4-WVD-scaling-tool).
+Issue reports for the scaling tool are currently being handled by Microsoft Support. When you make an issue report, make sure to follow the instructions in [Reporting issues](#reporting-issues). If you have feedback about the tool or want to request new features, open a GitHub issue labeled *4-WVD-scaling-tool* on the [RDS GitHub page](https://github.com/Azure/RDS-Templates/issues?q=is%3Aissue+is%3Aopen+label%3A4-WVD-scaling-tool).