Error with azure Virtual Desktop - quickstart or manual creation - neither connects to intune

Thank you for your patience and for sharing the detailed information so far.

Based on what you’ve described, the Azure Virtual Desktop session hosts are being created successfully and users are able to connect, which confirms the AVD deployment itself is working as expected. However, the issue is that these machines are not appearing in Microsoft Intune, which indicates that the automatic MDM (Intune) enrollment is not completing, even though the devices are Microsoft Entra ID joined.

From similar cases, this behavior is typically related to enrollment configuration, licensing, or policy scope rather than a delay in sync.

To help us narrow this down, could you please confirm the following from your side:

• Do the users signing into these session hosts have a valid license that includes Intune (such as Microsoft 365 E3/E5 or EMS)?
• In Microsoft Entra ID → Mobility (MDM and MAM) → Microsoft Intune, what is the MDM user scope currently set to (All or specific group)?
• On one of the affected session hosts, could you run dsregcmd /status and share the output (specifically looking for AzureAdJoined = YES and whether an MDM URL is present)?
• Are the devices visible under Entra ID → Devices, even though they are not showing in Intune?
• Is the issue happening with all newly created session hosts or only a subset?
• Are you using only the Quickstart deployment, or any custom image, policies, or GPOs as part of the setup?
• Do you have any Conditional Access or device restriction policies that might impact device enrollment?

Additionally, please review the following Microsoft documentation which outlines the expected behavior and prerequisites for Intune enrollment with AVD:

https://dotnet.territoriali.olinfo.it/en-us/intune/intune-service/enrollment/windows-enroll

https://dotnet.territoriali.olinfo.it/en-us/intune/intune-service/fundamentals/azure-virtual-desktop-multi-session

Great questions.

1. Users have E3 + Defender endpoint P2 license
2. MDM user scope is set to ALL

+----------------------------------------------------------------------+

| Device State |

+----------------------------------------------------------------------+

         AzureAdJoined : YES

      EnterpriseJoined : NO

          DomainJoined : NO

       Virtual Desktop : NOT SET

           Device Name : vmaqs26*********

+----------------------------------------------------------------------+

| Tenant Details |

+----------------------------------------------------------------------+

                MdmUrl : https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc

4. Yes, appears under 'Devices' in Entra ID but not in intune
5. All session hosts be it quickstart or manual creation
6. Have tried quickstart + manual, quickstart seems to be only one that works currently if I create a manual session host we can't connect to it even when replicating the quickstart setup
7. All conditional access except for the 4 default in microsoft set to report only but none affect device enrolment, there is also no restrictions in place under enrolment either

Note, intune enrolment is working fine for other devices, ie win11 virtual machine on local desktop enrolled perfectly fine, as did a workspace 365 enterprise workstation (however this enrolled but can't actually connect to that device for some reason)

Mario Zuppini

Thank you for the reply.

We have shared the link via private message. Please create a support ticket so that we can transfer it to the appropriate support team.

Thank you