M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Managed identity for Azure Virtual Desktop

Concept

Managed identities for Azure Virtual Desktop remove the need to grant permissions to the service principal. They apply to session host configuration, autoscale and Start VM on Connect. Generally available since September 2026.

✦ CONCEPTManaged identity forAzure Virtual DesktopM365.FM
Title graphic: Managed identity for Azure Virtual Desktop (Concept)

Relationships

Managed identity for Azure Virtual Desktop is part of Azure Virtual Desktop. Managed identity for Azure Virtual Desktop is closely related to Host pool (Azure Virtual Desktop) and Azure Autoscale.

Description

A managed identity can be assigned to an Azure Virtual Desktop host pool so that host pool features perform Azure Resource Manager operations on virtual machines, key vaults and virtual networks in the subscription. This removes the need to grant permissions to the Azure Virtual Desktop service principal and a system-assigned identity is tied directly to its host pool, while a user-assigned identity is a standalone resource that several host pools can use. Learn describes two types: a system-assigned identity, which Azure deletes together with its metadata when it is removed, and a user-assigned identity, where removal only ends the association and leaves the identity's permissions unchanged.

The supported features are session host configuration and update, autoscale, Start VM on Connect and Azure Virtual Desktop for Azure Local. Learn's What's new lists under September 2026 that managed identity support is now generally available, without a specific day. The same entry announces that in a future service update, host pools with a session host configuration will require a managed identity to add session hosts. An earlier What's new entry from August 2025 also mentions permissions that are assigned automatically based on session host configuration parameters and support for key vaults with public access disabled that allow trusted Microsoft services.

Setting it up requires the Desktop Virtualization Host Pool Contributor role at the host pool scope or higher, and for a user-assigned identity also the Managed Identity Operator role at the identity's scope or higher. One exception is documented: app attach with Azure Files and session hosts joined to Microsoft Entra ID still uses the service principal approach.

TypeConcept
KindFeature
DocumentationManaged identity for Azure Virtual Desktop – Microsoft Learn learn.microsoft.com

Articles about Managed identity for Azure Virtual Desktop (1)

Articles in which Managed identity for Azure Virtual Desktop is a topic:

Relationship map of Managed identity for Azure Virtual Desktop: linked topics

Related topics in brief

Topics linked to Managed identity for Azure Virtual Desktop, each briefly explained:

All relationships of Managed identity for Azure Virtual Desktop, grouped by type of relationship:

Part of

Offerings of which Managed identity for Azure Virtual Desktop is a part:

Related to

Topics related to Managed identity for Azure Virtual Desktop:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Community members with expertise in Managed identity for Azure Virtual Desktop:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: