Start VM on Connect is enabled on a personal pool. An authorized user’s assigned VM is deallocated, but the configured host-pool managed identity has no power-on permissions. Which role should be assigned at a scope containing that VM?

✓ Correct answer

• Desktop Virtualization Power On Contributor

The automation identity needs the documented Power On Contributor role to start existing eligible VMs. User entitlement and session operations are different permission categories. Option explanations: A. Desktop Virtualization Power On Contributor: This is the role specified for the feature’s supported automation identity. B. Virtual Machine User Login: This role concerns Windows VM sign-in where required, not automation power-on. C. Desktop Virtualization Session Host Operator: Session Host Operator supports host-management operations such as drain changes and removal, rather than the documented Start VM on Connect power role. D. Desktop Virtualization User Session Operator: User Session Operator manages sessions and does not supply VM power authorization. Sources: Configure Start VM on Connect — https://learn.microsoft.com/azure/virtual-desktop/start-virtual-machine-connect; Built-in Azure RBAC roles for Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/rbac; Assign Azure roles to AVD service principals and managed identities — https://learn.microsoft.com/en-us/azure/virtual-desktop/service-principal-assign-roles

Read the source reference