How to configure Start VM on Connect for personal and pooled host pools
Partner · Neutral partner: Nerdio
By Mirko Peters ·
Assign the Desktop Virtualization Power On Contributor role to the Azure Virtual Desktop service principal or a managed identity, then set Start VM on connect to Yes in the host pool's properties. Test with a deallocated host and add a deallocation mechanism, because the feature only starts VMs.
To configure Start VM on Connect, give the Azure Virtual Desktop service principal (or a managed identity on the host pool) the Desktop Virtualization Power On Contributor role, then set Start VM on connect to Yes in the host pool's properties. The steps are the same for personal and pooled host pools; what differs is what you test. Learn last updated the main page on 1 September 2026.
Key points
- Two things are required: a role assignment that lets Azure Virtual Desktop power on the VMs, and the Start VM on connect setting on an existing host pool.
- The role is Desktop Virtualization Power On Contributor, assigned to the AVD service principal or a host pool managed identity at a scope containing the pool and its VMs.
- Names of the host pool, its session hosts and the resource group may contain only ANSI characters.
- The setting is per host pool, so test on one pool first. Set it in the portal, PowerShell or Azure CLI; Learn says to configure it on an existing host pool, not during creation.
- Test a deallocated host for each pool type you run, and plan separately what deallocates the VMs afterwards.
How the feature behaves, why it saves cost and what the pooled start rules mean are in "Start VM on Connect in Azure Virtual Desktop: how it saves cost". This article is the procedure.
Prerequisites
From Learn's configuration page:
- An existing host pool that is associated with an application group and a workspace.
- An Azure account with the Desktop Virtualization Host Pool Contributor role, which Learn lists for configuring the setting.
- A test user assigned to a desktop or application in the application group, with Windows App or the Remote Desktop app on a local device.
- Names of the host pool, its session hosts and the resource group that contain only ANSI characters.
- For PowerShell or CLI: the
Az.DesktopVirtualizationmodule or thedesktopvirtualizationAzure CLI extension, or Azure Cloud Shell.
For the role assignment itself you need permission to create it. Learn's autoscale page, which describes the same kind of assignment, names Microsoft.Authorization/roleAssignments/write and says Owner and User Access Administrator include it. The Start VM on Connect page does not state this permission, so check what your own account has.
Step 1: assign the Power On Contributor role
Learn says this assignment allows Azure Virtual Desktop to power on VMs, check their status and report diagnostic information. The role description on the RBAC page is "used to allow the Azure Virtual Desktop Resource Provider to start virtual machines". Assign Desktop Virtualization Power On Contributor to either the Azure Virtual Desktop service principal or a managed identity assigned to the host pool, for every host pool and set of session host VMs you want to use with the feature.
Scope. Learn's tip says subscription scope is recommended for environments with several host pools or a subscription dedicated to Azure Virtual Desktop, because one assignment covers everything. Lower scopes also work, as long as the assignment scope contains the target session host VMs. Learn calls older guidance that anything below the subscription breaks the feature technically incorrect. Do not carry this over to autoscale: for its own role, Desktop Virtualization Power On Off Contributor, Learn says the subscription is the assignable scope, and that assigning it at any lower level, such as the resource group, host pool or VM, prevents autoscale from working properly.
Service principal in the Azure portal (Learn's service principal page):
- Open Microsoft Entra ID. On Overview, use Search your tenant and enter the application ID
9cdead84-a844-4324-93f2-b2e6bb768d07. - Select the enterprise application named Azure Virtual Desktop or Windows Virtual Desktop. Note its name and object ID.
- Search for Subscriptions and select the target subscription.
- Select Access control (IAM), then + Add, then Add role assignment.
- Select Desktop Virtualization Power On Contributor and Next.
- Set Assign access to to Microsoft Entra user, group, or service principal, select Select members, enter the application name and select it. If two entries share the name, select both, then remove the one whose object ID does not match the one you noted.
- Select Next, then Review + assign.
Managed identity alternative. Learn lists Start VM on Connect among the features that can use a managed identity on a host pool. Learn's "What's new in Azure Virtual Desktop" lists "Managed identity support is now generally available" under September 2026, and says that in a future service update, host pools configured with a session host configuration will require a managed identity to add session hosts. Learn's managed identity page says this replaces reliance on the Azure Virtual Desktop service principal for those host pools; it does not say this about Start VM on Connect itself. A system-assigned identity is tied to the host pool; a user-assigned identity is an independent resource. Learn's managed identity page (September 2026) gives these portal steps:
- Search for Azure Virtual Desktop, select Host pools, then select the host pool.
- Select Identity and select Assign a Managed Identity.
- Choose System assigned managed identity, or User assigned managed identity and then the subscription and the existing identity.
- Select Save.
You need Desktop Virtualization Host Pool Contributor at the host pool scope or higher; for a user-assigned identity you also need Managed Identity Operator at the identity's scope or higher. Then assign Desktop Virtualization Power On Contributor to that identity at a scope that contains the host pool and its session host VMs, using Azure's general role assignment steps. Learn's Start VM on Connect page does not give separate steps for that assignment, so confirm the result in Access control (IAM). For Azure Local session hosts, Learn's managed identity page adds that the host pool's identity needs Reader access on the resource group that holds the session hosts. Both the service principal and a managed identity are documented options for this role assignment; because Learn says a managed identity will be required for host pools with a session host configuration, plan for it if you create or update such pools.
Step 2: enable Start VM on connect
In the Azure portal (Learn's steps):
- Search for Azure Virtual Desktop and select it.
- Select Host pools, then the host pool.
- Select Properties.
- In the configuration section, set Start VM on connect to Yes, or No to disable it.
- Select Save.
The setting applies to the one host pool you edit, so repeat the steps for each pool.
Azure PowerShell and Azure CLI. Learn's configuration page gives commands for both directions. Replace the placeholders with your resource group and host pool names.
Azure PowerShell, enable and disable:
Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -StartVMOnConnect:$true
Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -StartVMOnConnect:$false
Azure CLI, enable and disable:
az desktopvirtualization hostpool update --resource-group $resourceGroupName --name $hostPoolName --start-vm-on-connect true
az desktopvirtualization hostpool update --resource-group $resourceGroupName --name $hostPoolName --start-vm-on-connect false
The Update-AzWvdHostPool reference describes -StartVMOnConnect as "The flag to turn on/off StartVMOnConnect feature". The CLI reference says --start-vm-on-connect accepts 0, 1, f, false, n, no, t, true, y and yes, and that the extension needs Azure CLI 2.55.0 or later. Both commands change an existing host pool, which is the route Learn describes. The create commands list the same parameter in their references, but Learn's configuration page only describes setting it on existing host pools.
Step 3: test each pool type
Deallocate a session host first, so the test starts from a powered-off VM. Learn's FAQ says shutting down from the Start menu does not deallocate it.
Personal host pool. Assign a test user to a session host, or use an unassigned host if the pool uses automatic assignment (see personal host pools). Deallocate that VM, then connect as the test user with Windows App. Learn says the client tells the user that a VM is being powered on. Expect the connection to take longer than usual, because the VM must boot.
Pooled host pool. Deallocate all session hosts and check the maximum session limit. Connect as the first test user; one VM should start. Fill it to its limit with test sessions and connect once more to see the next VM start. Learn says that for pooled host pools Start VM on Connect starts a VM every five minutes at most, so wait at least five minutes after the first start before the connection that should start the second VM. If a user connects inside that window and no resources are available, no new VM starts and the user gets No resources available; Learn tells them to wait a few minutes and try again. That is expected behavior, not a misconfiguration. The wider pooled start rules are in the explainer article, and a low session limit keeps the test short.
Step 4: decide what deallocates the VMs
Start VM on Connect does not turn VMs off. Learn's FAQ says VMs are not deallocated when users stop using them and that signing users out does not deallocate them. It points to autoscale for pooled and personal host pools, and the ramp-up tab of a personal scaling plan schedule has its own Start VM on Connect option, which Learn highly recommends enabling if you choose not to start session hosts during ramp-up. The Start VM on Connect page does not explain how that option relates to the host pool property, so check both after you enable the feature.
Without autoscale, the FAQ (page dated 20 June 2025) describes a two-part approach. First, on the VM, open the Group Policy Editor and go to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits. Set Set time limit for disconnected sessions to Enabled, then select End a disconnected session with a limit greater than five minutes, because a low limit can end sessions when a network connection drops for a while. Second, deallocate the VMs with Azure automation scripts.
Settings at a glance
| Item | Value |
|---|---|
| Portal setting | Start VM on connect under host pool Properties |
| Scope of the setting | One host pool |
| Role for the service principal or managed identity | Desktop Virtualization Power On Contributor |
| Role for the person who changes the setting | Desktop Virtualization Host Pool Contributor |
| Where it works | Session hosts on Azure and on Azure Local, personal or pooled |
Troubleshooting
- VM does not power on. Learn says to check the health of the VM first. Then review Azure Virtual Desktop logs in Log Analytics, note the exact error name and use Insights for suggestions.
- Direct RDP does not start the VM. This is expected, per Learn.
- Second connection starts no VM. On a pooled host pool, this is expected if less than five minutes passed since the last start; Learn says users then get No resources available.
- Own checklist, not from Learn. If the role assignment looks right but nothing starts, confirm that the assignment scope contains the VM, that the assignment names the service principal whose object ID you noted in step 1, and that the host pool, session host and resource group names contain only ANSI characters, which Learn lists as a prerequisite.
Sources
- Microsoft Learn: Configure Start VM on Connect
- Microsoft Learn: Start VM on Connect FAQ
- Microsoft Learn: Configure managed identity in Azure Virtual Desktop
- Microsoft Learn: What's new in Azure Virtual Desktop (September 2026)
- Microsoft Learn: Assign Azure RBAC roles or Microsoft Entra roles to the Azure Virtual Desktop service principals
- Microsoft Learn: Azure RBAC roles for Azure Virtual Desktop (rbac page)
- Microsoft Learn: Create and assign an autoscale scaling plan
- Microsoft Learn: Autoscale scaling plans and schedules
- Microsoft Learn: Update-AzWvdHostPool
- Microsoft Learn: az desktopvirtualization hostpool
FAQ
Which role does Start VM on Connect need, and who gets it?
Microsoft Learn says to assign the Desktop Virtualization Power On Contributor role to the Azure Virtual Desktop service principal, or to a managed identity assigned to the host pool, at a scope that contains the host pool and the session host VMs. The person who configures the setting needs the Desktop Virtualization Host Pool Contributor role.
Can I enable it when I create the host pool?
Learn's configuration page says no: you can only configure Start VM on Connect on existing host pools, which are associated with an application group and a workspace. Create the host pool first, then open its properties.
Does the setting start VMs that I connect to by RDP directly?
No. Learn says that connecting to a powered-off session host outside the Azure Virtual Desktop service, for example by IP address or name, does not start the VM.