Edit

Share via

Autoscale glossary for Azure Virtual Desktop

  • Article

This article is a list of definitions for key terms and concepts related to the autoscale feature for Azure Virtual Desktop.

Autoscale

Autoscale is Azure Virtual Desktop's native scaling service that scales session hosts up and down based on the capacity of the host pools and the scaling plan schedule you define.

Scaling method

The scaling method you choose defines how the scaling service manages the available capacity. There are two scaling methods you can choose from:

  • Power management autoscaling: powers on and off session hosts to adjust to the available capacity in a host pool. If you want to apply a scaling plan to a host pool with standard management, this is the option that you should use.

  • Dynamic autoscaling (preview): powers on and off session hosts and creates and deletes session hosts to adjust to the available capacity in a host pool. Dynamic autoscaling can only be used for pooled host pools with session host configuration.

Scaling tool

Azure Virtual Desktop’s scaling tool uses Azure Automation and Azure Logic Apps to scale the VMs in a host pool based on how many user sessions per CPU core there are during peak and off-peak hours.

Scaling plan

A scaling plan is an Azure Virtual Desktop Azure Resource Manager object that defines the schedules for scaling session hosts in a host pool. You can assign one scaling plan to multiple host pools. When creating a scaling plan, you have to choose between pooled or personal host pools. You can only assign the scaling plan to the host pools with the same type (pooled or personal). The scaling plan type can't be changed after it is created.

Schedule

Schedules are sub-resources of scaling plans. Scaling plans for pooled host pools have schedules that specify the start time, capacity threshold, minimum percentage of hosts, load-balancing algorithm, and other configuration settings for the different phases of the day. Scaling plans for personal host pools have schedules that specify the start time and what operation to perform based on user session state (signed out or disconnected) for the different phases of the day.

Ramp-up

The ramp-up phase of a scaling plan schedule is usually at the beginning of the work day, when users start to sign in and start their sessions. In this phase, the number of active user sessions usually increases at a rapid pace without reaching the maximum number of active sessions for the day yet.

Peak

The peak phase of a scaling plan schedule is when your host pool reaches the maximum number of active user sessions for the day. In this phase, the number of active sessions usually holds steady until the peak phase ends. New active user sessions can be established during this phase, but usually at a slower rate than the ramp-up phase.

Ramp-down

The ramp-down phase of a scaling plan schedule is usually at the end of the work day, when users start to sign out and end their sessions for the evening. In this phase, the number of active user sessions usually decreases rapidly.

Off-peak

The off-peak phase of the scaling plan schedule is when the host pool usually reaches the minimum number of active user sessions for the day. During this phase, there aren't usually many active users, but you may keep a small amount of resources on to accommodate users who work after the peak and ramp-down phases.

Available session host

Available session hosts are session hosts that have passed all Azure Virtual Desktop agent health checks and have VM objects that are powered on, making them available for users to establish user sessions on.

Capacity threshold

The capacity threshold is the percentage of a host pool's capacity that, when reached, triggers a scaling action to happen.

For example:

  • If the used host pool capacity is below the capacity threshold and autoscale can turn off or delete session hosts without going over the capacity threshold, then dynamic autoscaling turns off or deletes the session hosts.
  • If the used host pool capacity goes over the capacity threshold, then autoscale turns on or creates more session hosts until the used host pool capacity goes below the capacity threshold.

Available host pool capacity

Available host pool capacity is how many user sessions a host pool can host based on the number of available session hosts. The available host pool capacity is the host pool's maximum session limit multiplied by the number of available session hosts in the host pool.

In other words:

Host pool maximum session limit × number of available session hosts = available host pool capacity.

Used host pool capacity

The used host pool capacity is the amount of host pool capacity that's currently taken up by active and disconnected user sessions.

In other words:

The number of active and disconnected user sessions ÷ the host pool capacity = used host pool capacity.

Scaling action

Scaling actions are when autoscale turns VMs on or off.

Shut down

Autoscale for pooled and personal host pools shuts down VMs based on the defined schedule. When autoscale shuts down a VM, it deallocates and stops the VM, ensuring you aren't charged for the compute resources.

Minimum percentage of hosts

The minimum percentage of hosts is the lowest percentage of all session hosts in the host pool that must be turned on for each phase of the scaling plan schedule.

Active user session

A user session is considered "active" when the user signs in and connects to their RemoteApp or desktop resource.

Disconnected user session

A disconnected user session is an inactive session that the user hasn't signed out of yet. When a user closes the remote session window without signing out, the session becomes disconnected. When a user reconnects to their remote resources, they'll be redirected to their disconnected session on the session host they were working on. At this point, the disconnected session becomes an active session again.

Force log-off

A force log-off, or forced sign-out, is when the service ends an active user session or a disconnected user session without the user's consent.

Exclusion tag

An exclusion tag is a property of a scaling plan that's a tag name you can apply to VMs that you want to exclude from scaling actions. Autoscale only performs scaling actions on VMs without tag names that match the exclusion tag.

Next steps