Skip to content
Back to Blog

Azure Virtual Desktop PowerShell Cheat Sheet: Az.DesktopVirtualization Commands You Can Copy

D
Founder and CEO, Atlas AVD··Updated
Azure Virtual Desktop PowerShell Cheat Sheet: Az.DesktopVirtualization Commands You Can Copy

Azure Virtual Desktop (AVD) is managed from PowerShell with the Az.DesktopVirtualization module, whose cmdlets all start with AzWvd: Get-AzWvdHostPool, Update-AzWvdSessionHost, Get-AzWvdUserSession and so on. Install it with Install-Module Az.DesktopVirtualization, sign in with Connect-AzAccount, and every task in the Azure portal's Azure Virtual Desktop blade has a cmdlet. This cheat sheet gives a copyable block for each everyday job: host pools, session hosts, drain mode, user sessions, registration tokens, application groups and scaling plans.

The short version: Get-AzWvdSessionHost and Get-AzWvdUserSession return names as HostPool/SessionHost and HostPool/SessionHost/SessionId, so split on / before you pass them to another cmdlet. Drain mode is Update-AzWvdSessionHost -AllowNewSession:$false. Logging a user off is Remove-AzWvdUserSession, which removes the session, not the user. Remove-AzWvdSessionHost takes a host out of the pool but leaves the VM running and billing. Registration tokens last from 1 hour to 27 days, and a new one is New-AzWvdRegistrationInfo. Scaling plans need module 4.2.0 or later and the Desktop Virtualization Power On Off Contributor role at subscription scope.

Last updated 17 November 2026. Cmdlets and parameters are from the Az.DesktopVirtualization reference and Microsoft Learn as of November 2026, with each source linked below.

This guide is vendor-neutral until the section on where Atlas AVD fits. New to host pools, application groups and workspaces? What Is Azure Virtual Desktop? explains them first.


1. Set up: install the module and sign in

Run these once on a workstation, or skip them and use Azure Cloud Shell, which has the Az modules already installed (Use Azure PowerShell with Azure Virtual Desktop).

# Install or update the AVD module (Az.Accounts comes with it)
Install-Module -Name Az.DesktopVirtualization -Scope CurrentUser
Update-Module -Name Az.DesktopVirtualization

# Sign in and pick the subscription that holds your host pools
Connect-AzAccount
Set-AzContext -Subscription '<SubscriptionNameOrId>'

# GCC High and other Azure Government tenants
Connect-AzAccount -Environment AzureUSGovernment

# See every AVD cmdlet
Get-Command -Module Az.DesktopVirtualization

The examples below use splatting (@params) so each block stays readable and copies cleanly. Set these once per session and most blocks work as they are:

$rg   = '<ResourceGroupName>'
$pool = '<HostPoolName>'

2. Quick reference

TaskCmdletKey parameters
List host poolsGet-AzWvdHostPool-ResourceGroupName, -Name
Create a host poolNew-AzWvdHostPool-HostPoolType, -LoadBalancerType, -PreferredAppGroupType, -Location
Change a host poolUpdate-AzWvdHostPool-MaxSessionLimit, -LoadBalancerType, -StartVMOnConnect, -CustomRdpProperty
List session hostsGet-AzWvdSessionHost-HostPoolName, -Name
Drain a session hostUpdate-AzWvdSessionHost-AllowNewSession:$false
Remove a host from the poolRemove-AzWvdSessionHost-Name, -Force
List user sessionsGet-AzWvdUserSession-SessionHostName, -Filter
Message a userSend-AzWvdUserSessionMessage-UserSessionId, -MessageTitle, -MessageBody
Disconnect a userDisconnect-AzWvdUserSession-SessionHostName, -Id
Log a user offRemove-AzWvdUserSession-SessionHostName, -Id, -Force
Create a registration tokenNew-AzWvdRegistrationInfo-ExpirationTime
Read the current tokenGet-AzWvdHostPoolRegistrationToken-HostPoolName
Create an application groupNew-AzWvdApplicationGroup-ApplicationGroupType, -HostPoolArmPath
Publish a RemoteAppNew-AzWvdApplication-GroupName, -FilePath, -CommandLineSetting
Register a group in a workspaceUpdate-AzWvdWorkspace-ApplicationGroupReference
Assign usersNew-AzRoleAssignment-RoleDefinitionName 'Desktop Virtualization User'
Create a scaling planNew-AzWvdScalingPlan-HostPoolType, -TimeZone, -HostPoolReference
Add a scaling scheduleNew-AzWvdScalingPlanPooledSchedule-DaysOfWeek, ramp-up, peak, ramp-down and off-peak times

3. Host pools

# List every host pool in the subscription, with the settings you check most
Get-AzWvdHostPool |
    Select-Object Name, HostPoolType, LoadBalancerType, MaxSessionLimit, PreferredAppGroupType, StartVMOnConnect

# One host pool, every property
Get-AzWvdHostPool -ResourceGroupName $rg -Name $pool | Format-List *

Create a pooled host pool. -HostPoolType is Pooled or Personal, -LoadBalancerType is BreadthFirst or DepthFirst for pooled pools and Persistent for personal ones, and -PreferredAppGroupType is Desktop or RailApplications (RemoteApp). All four, plus -Location, are required (New-AzWvdHostPool).

$params = @{
    ResourceGroupName     = $rg
    Name                  = $pool
    Location              = 'eastus'
    HostPoolType          = 'Pooled'
    LoadBalancerType      = 'BreadthFirst'
    PreferredAppGroupType = 'Desktop'
    MaxSessionLimit       = 12
}
New-AzWvdHostPool @params

This creates only the host pool. Users see nothing until it has an application group registered in a workspace, which is section 7. Change settings on an existing pool with Update-AzWvdHostPool:

# Session limit and load balancing
Update-AzWvdHostPool -ResourceGroupName $rg -Name $pool -MaxSessionLimit 16 -LoadBalancerType 'DepthFirst'

# Turn on Start VM on Connect
Update-AzWvdHostPool -ResourceGroupName $rg -Name $pool -StartVMOnConnect:$true

# RDP properties replace the whole string, so read the current one first
(Get-AzWvdHostPool -ResourceGroupName $rg -Name $pool).CustomRdpProperty
Update-AzWvdHostPool -ResourceGroupName $rg -Name $pool -CustomRdpProperty 'drivestoredirect:s:;redirectclipboard:i:1;'

Set a real MaxSessionLimit before you use autoscale: Microsoft requires it, and the default (999999) makes depth-first load balancing pile every user on one host. The AVD sizing guide covers how to choose the number.


4. Session hosts and drain mode

# Every session host in a pool: status, sessions, drain state, agent
Get-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool |
    Select-Object Name, Status, Session, AllowNewSession, AgentVersion, LastHeartBeat, UpdateState

# Only hosts that aren't Available
Get-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool |
    Where-Object Status -ne 'Available' |
    Select-Object Name, Status, UpdateErrorMessage

Names come back as HostPool/SessionHost. Get-AzWvdSessionHost returns Name as hp01/hp01-sh-0.contoso.com, but every cmdlet that takes -Name or -SessionHostName wants only hp01-sh-0.contoso.com. Split on the slash:

$hosts = Get-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool
$hostNames = $hosts | ForEach-Object { $_.Name.Split('/')[-1] }

Drain mode stops a host accepting new sessions while users already on it keep working. It's the AllowNewSession property, set per host (Drain session hosts for maintenance):

# Turn drain mode on for one host
Update-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool -Name 'hp01-sh-0.contoso.com' -AllowNewSession:$false

# Turn it off again
Update-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool -Name 'hp01-sh-0.contoso.com' -AllowNewSession:$true

# Drain every host in the pool, for example before an image rollout
Get-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool | ForEach-Object {
    Update-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool -Name $_.Name.Split('/')[-1] -AllowNewSession:$false
}

# Which hosts are draining right now?
Get-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool |
    Where-Object AllowNewSession -eq $false |
    Select-Object Name, Session

Remove a host from the pool. Remove-AzWvdSessionHost deletes the session host object: the VM keeps running and keeps costing money until you delete it with Remove-AzVM. Microsoft's order is drain, sign everyone out, then remove the session host before you delete the VM, or the pool keeps a stale entry (host pool creation troubleshooting).

Remove-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool -Name 'hp01-sh-0.contoso.com'

# Add -Force to remove it while sessions are still listed
Remove-AzWvdSessionHost -ResourceGroupName $rg -HostPoolName $pool -Name 'hp01-sh-0.contoso.com' -Force

5. User sessions: list, message, disconnect, log off

# Every session in the pool
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool |
    Select-Object Name, UserPrincipalName, SessionState, ApplicationType, CreateTime

# Sessions on one host
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -SessionHostName 'hp01-sh-0.contoso.com'

# Disconnected sessions only (the filter supports userprincipalname and sessionstate)
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -Filter "sessionstate eq 'Disconnected'"

# Find one user
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -Filter "userprincipalname eq 'jane@contoso.com'"

A session's Name is HostPool/SessionHost/SessionId (Get-AzWvdUserSession). The last two parts are the -SessionHostName and -Id (alias -UserSessionId) the action cmdlets need. This helper turns a session into those parameters:

function Get-SessionTarget($s) {
    $parts = $s.Name.Split('/')
    @{ ResourceGroupName = $rg; HostPoolName = $parts[0]; SessionHostName = $parts[1]; Id = $parts[2] }
}

Send a message that pops up in the user's session (Send-AzWvdUserSessionMessage). Note it takes -UserSessionId, not -Id:

$params = @{
    ResourceGroupName = $rg
    HostPoolName      = $pool
    SessionHostName   = 'hp01-sh-0.contoso.com'
    UserSessionId     = '2'
    MessageTitle      = 'Maintenance tonight'
    MessageBody       = 'Please save your work and sign out by 6 PM.'
}
Send-AzWvdUserSessionMessage @params

# Message everyone on a host you're about to drain
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -SessionHostName 'hp01-sh-0.contoso.com' | ForEach-Object {
    $t = Get-SessionTarget $_
    Send-AzWvdUserSessionMessage -ResourceGroupName $rg -HostPoolName $t.HostPoolName -SessionHostName $t.SessionHostName -UserSessionId $t.Id -MessageTitle 'Maintenance' -MessageBody 'This desktop restarts in 15 minutes. Please save your work.'
}

Disconnect drops the connection but leaves the session and the user's apps running on the host, so they can reconnect and carry on. Log off with Remove-AzWvdUserSession ends the session, and anything unsaved is lost (Disconnect-AzWvdUserSession, Remove-AzWvdUserSession).

# Disconnect one session
Disconnect-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -SessionHostName 'hp01-sh-0.contoso.com' -Id 2

# Log one session off
Remove-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -SessionHostName 'hp01-sh-0.contoso.com' -Id 2

# Log off every disconnected session in the pool
Get-AzWvdUserSession -ResourceGroupName $rg -HostPoolName $pool -Filter "sessionstate eq 'Disconnected'" | ForEach-Object {
    $t = Get-SessionTarget $_
    Remove-AzWvdUserSession @t -Force
}

Logging off disconnected sessions by script works, but it's a patch. A session time limit policy (Set time limit for disconnected sessions) does the same job on the hosts without a scheduled script. Control AVD spend covers which limits to set.


6. Registration tokens

A registration token (Microsoft also calls it a registration key) lets a VM join a host pool. It's valid for the time you set, from 1 hour up to 27 days (Add session hosts to a host pool).

# Create a token valid for 24 hours. The format string matters: UTC, with seven decimal places
$params = @{
    ResourceGroupName = $rg
    HostPoolName      = $pool
    ExpirationTime    = $((Get-Date).ToUniversalTime().AddHours(24).ToString('yyyy-MM-ddTHH:mm:ss.fffffffZ'))
}
New-AzWvdRegistrationInfo @params

# Read the current token, for example to pass to the agent installer
(Get-AzWvdHostPoolRegistrationToken -ResourceGroupName $rg -HostPoolName $pool).Token

# Revoke it when the rollout is done
Remove-AzWvdRegistrationInfo -ResourceGroupName $rg -HostPoolName $pool

On a VM you built outside AVD, install the agent with the token, then the boot loader:

msiexec /i Microsoft.RDInfra.RDAgent.Installer-x64-<version>.msi /quiet REGISTRATIONTOKEN=<RegistrationToken>
msiexec /i Microsoft.RDInfra.RDAgentBootLoader.Installer-x64.msi /quiet

Pick a lifetime that covers your whole deployment window. Hosts provisioned after the token expires fail to register with EXPIRED_MACHINE_TOKEN. Separately, a host that stays powered off for more than 90 days lets its own machine token expire, so start it for at least 20 minutes every 90 days.


7. Application groups, workspaces and assignments

# The host pool's resource ID, which application groups reference
$hostPoolArmPath = (Get-AzWvdHostPool -ResourceGroupName $rg -Name $pool).Id

# Desktop application group
New-AzWvdApplicationGroup -ResourceGroupName $rg -Name "$pool-DAG" -Location 'eastus' -ApplicationGroupType 'Desktop' -HostPoolArmPath $hostPoolArmPath

# RemoteApp application group (pooled host pools only)
New-AzWvdApplicationGroup -ResourceGroupName $rg -Name "$pool-Apps" -Location 'eastus' -ApplicationGroupType 'RemoteApp' -HostPoolArmPath $hostPoolArmPath

Publish an app to a RemoteApp group. Get-AzWvdStartMenuItem lists what's on the Start menu of a running session host, so you can copy its path:

Get-AzWvdStartMenuItem -ResourceGroupName $rg -ApplicationGroupName "$pool-Apps" | Select-Object Name, FilePath

$params = @{
    ResourceGroupName  = $rg
    GroupName          = "$pool-Apps"
    Name               = 'Notepad'
    FilePath           = 'C:\Windows\System32\notepad.exe'
    IconPath           = 'C:\Windows\System32\notepad.exe'
    IconIndex          = 0
    CommandLineSetting = 'DoNotAllow'
    ShowInPortal       = $true
}
New-AzWvdApplication @params

Register the group in a workspace, then assign users. ApplicationGroupReference is the workspace's whole list, so keep the groups that are already there:

$ws = Get-AzWvdWorkspace -ResourceGroupName $rg -Name '<WorkspaceName>'
$appGroupPath = (Get-AzWvdApplicationGroup -ResourceGroupName $rg -Name "$pool-DAG").Id
Update-AzWvdWorkspace -ResourceGroupName $rg -Name $ws.Name -ApplicationGroupReference (@($ws.ApplicationGroupReference) + $appGroupPath | Select-Object -Unique)

# Assign an Entra group to the application group
$params = @{
    ObjectId           = (Get-AzADGroup -DisplayName 'AVD Users').Id
    ResourceName       = "$pool-DAG"
    ResourceGroupName  = $rg
    RoleDefinitionName = 'Desktop Virtualization User'
    ResourceType       = 'Microsoft.DesktopVirtualization/applicationGroups'
}
New-AzRoleAssignment @params

A user assigned to both a desktop group and a RemoteApp group on the same pool sees only the one set by the pool's preferred application group type. RemoteApp vs full desktop explains that rule and when to publish apps instead of a desktop.


8. Scaling plans (autoscale)

Before your first scaling plan, give the Azure Virtual Desktop service principal (or the host pool's managed identity) the Desktop Virtualization Power On Off Contributor role with the subscription as its scope. Assigned lower down, at a resource group or host pool, autoscale doesn't work properly. Creating plans from PowerShell needs Az.DesktopVirtualization 4.2.0 or later, and the plan must be in the same region as the host pool's metadata (Create and assign an autoscale scaling plan).

$hostPoolArmPath = (Get-AzWvdHostPool -ResourceGroupName $rg -Name $pool).Id

# 1. Create the plan and assign it to the pool
$params = @{
    ResourceGroupName = $rg
    Name              = 'sp-weekdays'
    Location          = 'eastus'
    HostPoolType      = 'Pooled'
    TimeZone          = 'Eastern Standard Time'
    HostPoolReference = @(@{ 'hostPoolArmPath' = $hostPoolArmPath; 'scalingPlanEnabled' = $true })
}
New-AzWvdScalingPlan @params

# 2. Add a weekday schedule
$params = @{
    ResourceGroupName              = $rg
    ScalingPlanName                = 'sp-weekdays'
    ScalingPlanScheduleName        = 'weekdays'
    DaysOfWeek                     = 'Monday','Tuesday','Wednesday','Thursday','Friday'
    RampUpStartTimeHour            = 7
    RampUpStartTimeMinute          = 0
    RampUpLoadBalancingAlgorithm   = 'BreadthFirst'
    RampUpMinimumHostsPct          = 20
    RampUpCapacityThresholdPct     = 60
    PeakStartTimeHour              = 9
    PeakStartTimeMinute            = 0
    PeakLoadBalancingAlgorithm     = 'DepthFirst'
    RampDownStartTimeHour          = 17
    RampDownStartTimeMinute        = 0
    RampDownLoadBalancingAlgorithm = 'DepthFirst'
    RampDownMinimumHostsPct        = 10
    RampDownCapacityThresholdPct   = 90
    RampDownForceLogoffUser        = $false
    RampDownStopHostsWhen          = 'ZeroSessions'
    RampDownWaitTimeMinute         = 30
    RampDownNotificationMessage    = 'Please save your work and sign out.'
    OffPeakStartTimeHour           = 20
    OffPeakStartTimeMinute         = 0
    OffPeakLoadBalancingAlgorithm  = 'DepthFirst'
}
New-AzWvdScalingPlanPooledSchedule @params

# 3. Check which pools the plan is assigned to, and whether it's enabled for each
(Get-AzWvdScalingPlan -ResourceGroupName $rg -Name 'sp-weekdays').HostPoolReference |
    Format-List HostPoolArmPath, ScalingPlanEnabled

To pause autoscale on a pool without deleting the plan, set scalingPlanEnabled to $false for that pool. Like a workspace's group list, -HostPoolReference is the plan's full list of pools:

Update-AzWvdScalingPlan -ResourceGroupName $rg -Name 'sp-weekdays' -HostPoolReference @(@{ 'hostPoolArmPath' = $hostPoolArmPath; 'scalingPlanEnabled' = $false })

Personal pools use New-AzWvdScalingPlanPersonalSchedule instead, with actions on disconnect and log off (deallocate or hibernate). Don't run a scaling plan and another scaling script or tool on the same pool: they fight, one starting hosts the other just stopped. Power management autoscale works in Azure Government; dynamic autoscale doesn't.


9. Mistakes that bite in scripts

MistakeWhat happensFix
Passing $_.Name from Get-AzWvdSessionHost straight to -NameNot found, because the name includes the pool$_.Name.Split('/')[-1]
Using -Id with Send-AzWvdUserSessionMessageParameter errorIt's -UserSessionId there; -Id elsewhere
A local-time ExpirationTimeToken expires hours early or late.ToUniversalTime() and the yyyy-MM-ddTHH:mm:ss.fffffffZ format
Remove-AzWvdSessionHost to "delete" a hostThe VM keeps running and billingAlso remove the VM, its disk and NIC
Deleting the VM firstA stale session host stays in the poolDrain, sign out, remove the session host, then the VM
Update-AzWvdWorkspace with only the new groupOther groups drop out of the workspacePass the existing list plus the new group
-CustomRdpProperty with one propertyEvery other RDP property is clearedRead the current string and edit it
Power On Off Contributor on a resource groupAutoscale doesn't start or stop hostsAssign it at subscription scope
Default MaxSessionLimit with autoscaleDepth-first piles everyone on one hostSet a real per-host limit
Running a script against the wrong subscriptionChanges land in another tenant or customerGet-AzContext before anything that writes

Top 10 Azure Virtual Desktop mistakes covers the design-level mistakes behind many of these, and AVD session host needs assistance covers what to do when Status isn't Available.


10. Where Atlas AVD fits

Atlas AVD runs in your own Azure subscription and puts the jobs in this cheat sheet in one console, for every host pool and every tenant you manage. Here's what that covers, and where PowerShell is still the tool.

Drain without a loop. Each host in a pool's Session Hosts table has a Maint. switch, which is drain mode: the host stops taking new sessions and users already on it keep working. Drain & Reclaim puts the hosts you select into maintenance mode and deletes each one once its users have signed out, or straight away if it's already idle. See Drain & Reclaim and Configuring Session Hosts.

User sessions across every pool. User Sessions lists every active and disconnected session across your host pools, live, with Send message, Disconnect and Log off on each row (Manage User Sessions). Send message and Disconnect need the session.assist permission, so the help desk can use them without being able to log users off.

No registration tokens to handle. When Atlas adds session hosts, it creates a registration token for the host pool itself, uses it to register the new VMs and checks that each one appears in the pool. There's no token to copy or expire mid-rollout.

Autoscale that won't fight a scaling plan. Atlas has its own autoscale engine. If an enabled Azure scaling plan is assigned to a host pool, Atlas autoscale stands down for that pool and won't let you turn it on there, so the two never start and stop the same hosts.

Scripts on session hosts. Run Script in the Session Hosts table and the Script Repository run PowerShell on the session hosts, which Az.DesktopVirtualization can't do.

PowerShell mode is for Microsoft 365, not AVD. PowerShell mode opens a PowerShell 7 terminal in your browser, already connected to Exchange Online, Security & Compliance and Microsoft Graph, with every command recorded in the audit log. It doesn't load Az.DesktopVirtualization, so run the cmdlets in this cheat sheet from Azure Cloud Shell or your own workstation.


FAQ

Which PowerShell module manages Azure Virtual Desktop?

Az.DesktopVirtualization, part of the Az PowerShell modules. Its cmdlets have AzWvd in their names, such as Get-AzWvdHostPool and Update-AzWvdSessionHost. Install it with Install-Module Az.DesktopVirtualization, or use Azure Cloud Shell, where it's already installed.

How do I put an AVD session host in drain mode with PowerShell?

Run Update-AzWvdSessionHost -ResourceGroupName <rg> -HostPoolName <pool> -Name <sessionhost> -AllowNewSession:$false. The host stops accepting new sessions, and users already on it keep working until they sign out. Set -AllowNewSession:$true to take it out of drain mode.

How do I log off a user from Azure Virtual Desktop with PowerShell?

Find the session with Get-AzWvdUserSession, then run Remove-AzWvdUserSession with the session host name and the session ID, the last two parts of the session's name. Use Disconnect-AzWvdUserSession instead if you want the user to be able to reconnect to their running apps.

How do I get an AVD registration token with PowerShell?

Create one with New-AzWvdRegistrationInfo and an -ExpirationTime between 1 hour and 27 days from now, in UTC. Read the current token with (Get-AzWvdHostPoolRegistrationToken -ResourceGroupName <rg> -HostPoolName <pool>).Token.

Why does Update-AzWvdSessionHost say the session host isn't found?

You probably passed the full name from Get-AzWvdSessionHost, which is the host pool name, a slash, then the session host name. The -Name parameter wants only the part after the slash, such as hp01-sh-0.contoso.com.

Does Remove-AzWvdSessionHost delete the virtual machine?

No. It removes the session host from the host pool, but the VM, its disks and its network interface stay in Azure and keep costing money. Delete them separately, after draining the host and signing everyone out.

Can I use these cmdlets in GCC High?

Yes. Sign in with Connect-AzAccount -Environment AzureUSGovernment and the same cmdlets work. Power management autoscale is available in Azure Government; dynamic autoscale isn't. Azure Virtual Desktop in GCC High covers the other differences.


Sources

Related Resources

Blog

Azure Virtual Desktop Fleet Management: Stop Managing AVD One Host at a Time

Host-by-host habits from the server-rack era stop working as AVD grows. How to run Azure Virtual Desktop session hosts as a fleet: desired state, the session host lifecycle, troubleshooting from the user, fleet monitoring, bulk operations, autoscaling, golden image rollouts, workload-aware density, Azure quota as an operational signal, and multi-tenant management for MSPs.

Read more
Blog

MSP Client Onboarding Checklist for Azure Virtual Desktop: Consent, Discovery, Baseline and Handover

A step-by-step MSP client onboarding checklist for Azure Virtual Desktop: 38 items in six phases, from kickoff and tenant consent through discovery, baseline and documentation to handover and the 30-day review. Each item has an owner and a "done when" test, and the whole list is a free Excel download.

Read more
Blog

How to Sell Azure Virtual Desktop to SMB Clients: Discovery Questions, Objections and a Pitch Outline

A practical guide for MSPs selling Azure Virtual Desktop to small and mid-sized clients: the trigger events that make AVD an easy yes, who to qualify out, twelve discovery questions, answers to the eight objections you'll hear, a 30-minute pitch outline, a pilot plan and a free ROI template to fill in with the client's own numbers.

Read more
Blog

Azure Virtual Desktop on Mac, iPad, Chromebook, Linux and Thin Clients: Which Client to Use and What Each One Can't Do

Every device can reach an Azure Virtual Desktop session, but not every device can bring the same things into it. Which client to install on a Mac, iPad, Android tablet, Chromebook, Linux PC or thin client, the browsers the web client supports, and a feature-by-platform table of what works where: Teams, monitors, printers, USB, smart cards, clipboard and screen capture protection.

Read more

Get the AVD health checklist

The checks that catch slow sign-ins, temporary profiles and surprise Azure bills, across session hosts, FSLogix, golden images and cost. Free, straight to your inbox.

No spam. Unsubscribe anytime.

Ready to put this into practice?

Atlas AVD automates the strategies in this article - cost optimization, scaling, governance, and more.

Start free, no credit card

Free forever for 1 tenant & 1 host pool on the Community plan, or 30 days of every feature.

Try the live demo, no signup

Copyable Az.DesktopVirtualization commands for the AVD jobs you do every week: host pools, session hosts, drain mode, user sessions (message, disconnect, log off), registration tokens, application groups and scaling plans, plus the naming and parameter traps that break scripts.

By David Smith, Founder and CEO, Atlas AVD, , updated