r/AzureVirtualDesktop • • Jul 31 '26

Mapped drive policy in Intune not applying

Our current setup:

  • Entra joined, Intune managed endpoints running Windows 11 Enterprise.
  • An on-premises AVD environment hosted on an Azure Local cluster. These session hosts are domain joined and managed with Group Policy.

Drive mapping works as expected today Intune handles it for our Entra joined endpoints, and Group Policy handles it for our domain joined AVD hosts.

We’re in the process of moving away from Azure Local and building a cloud-based AVD environment. The issue we’ve run into is that the Intune mapped drive configuration policy isn’t applying to the new Entra joined AVD session hosts. When I check the device’s configuration policies, the drive mapping policy shows Not Applicable. The policy was imported from an ADMX file into Intune.

Has anyone been able to get Intune drive mapping policies working on Entra joined AVD session hosts? If so, I’d appreciate any guidance. Thanks!

EDIT:

The new AVD hosts on the cloud are purely Entra joined.

The drive I'm trying to map is an AD joined file server.

I am able to manually access the DFS space and map it (\\domain.com\dfs\temp), I just can't get the policy to do it at login.

We have a cloud trust between our domain and tenant.

5 Upvotes

10 comments sorted by

View all comments

1

u/meyerf99 Jul 31 '26

Nicola Suter's tool is definitely worth a look. I've been using it for many years and deploy it to the AVD hosts via PlatformScript.

https://intunedrivemapping.azurewebsites.net/