Microsoft Configuration Manager
FundamentalsAzure Virtual Desktop
In brief
The documentation now says Azure Virtual Desktop must be deployed in an Azure subscription associated with the same Entra ID tenant as Intune. The previous wording also referenced being in the same region.
What Intune admins need to know
Administrators should use the updated tenant and subscription wording when validating Azure Virtual Desktop deployments; this change is documentation clarification, not evidence of a new feature.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
Open full page diff →The comparison below shows only the changed extract. Open the full-page diff for complete context.
- Configuration Manager co-management.
- User self-enrollment via Microsoft Entra join.
- Microsoft Entra joined and enrolled in Intune by enabling Enroll the VM with Intune in the Azure portal.
UnderDeployed in an Azure subscription associated with the same Entra ID tenant as Intuneand in the same region.
For more information on Azure Virtual Desktop licensing requirements, see Licensing Azure Virtual Desktop.
@@ -23,7 +23,7 @@ For single-session, Intune supports Azure Virtual Desktop VMs that are: - [Configuration Manager co-management](/configmgr/comanage/overview). - [User self-enrollment via Microsoft Entra join](../device-enrollment/windows/guide.md#byod-user-enrollment). - Microsoft Entra joined and enrolled in Intune by enabling [Enroll the VM with Intune](/azure/virtual-desktop/deploy-azure-ad-joined-vm#deploy-azure-ad-joined-vms) in the Azure portal.-- Under the same tenant as Intune and in the same region.+- Deployed in an Azure subscription associated with the same Entra ID tenant as Intune For more information on Azure Virtual Desktop licensing requirements, see [Licensing Azure Virtual Desktop](/azure/virtual-desktop/licensing).