Share via

Intune does not enroll after Entra Cloud Device Join

Manuel Anderson 0 Reputation points
2026-03-12T17:37:59.25+00:00

Hello Community,

i have a view Devices that i could join after Entra Cloud Rollout via Script to Intune to Join. After Joining to Intune i see that the device is visible in Entra as managed Device and Also in Intune as a Device.

Only on Joining Entra it is only visible to Entra, so with a script like that for a example: https://github.com/CalvinWorst/Intune-Enrollment/blob/main/AutoEnrollMDM.ps1 i can join the device to Intune.

But i have a problem there is no article or otherwise helping of AI how to fix that Intune is not be able to communicate with the device. That means i can see device but the device is not be able to talk to Intune.

The Device Informations in Intune are empty. There are many Ideas and troubleshooting searching the web as well as deleting the registry keys so it is possible to onboard with the script again.

But everything i tried is not possible.

I know it is a Windows 10 Device and the PC is 10 Years old, just to know but this should not be the problem in it´s scenario. The Devices has also never have been in Active Directory or any other cases. So alle devices i have are happy but only one device not.

Today as well i left the organisation and the device was not visible in Entra and deleted the Registry keys and joint again, but there was automatic rollout as well the script again did not work.

Is there Any Idea by the experts i don´t know?

May someone can help me?

Thank you really much


Moved from Microsoft 365 and Office | Other

Microsoft Security | Intune | Configuration

2 answers

Sort by: Most helpful
  1. Manuel Anderson 0 Reputation points
    2026-04-07T23:10:38.6266667+00:00

    So thank you for your answer and Sorry for my late response. Well The script above works fully fine with the most devices if you delete the delete the intune registry keys. But only one device actually is saying to me, it could not find the registry key. If i restore the registry key it is missing an another key. So only issues and issues.

    So my idea is now to rollout the device complet new because there is no other way to join the device to intune after rollout in Entra.

    Or das you @Anonymous as a Microsoft Employee have an other idea if you only have issues in rollout again because of missing registry keys? So the rollout is not possible anymore?

    Well it´s so funny because at all other devices i delete the same registry keys without issues.

    0 comments No comments

  2. Manuel Anderson 0 Reputation points
    2026-04-07T23:03:15.89+00:00

    https://call4cloud.nl/enroll-existing-entra-azure-intune/

    Set MDM Enrollment URL's $key = 'SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo*' $keyinfo = Get-

    Item "HKLM:$key" $url = $keyinfo.name $url = $url.Split("")[-1] $path = "HKLM:\SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\$url" New-ItemProperty -LiteralPath $path -Name 'MdmEnrollmentUrl' -Value 'https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc' -PropertyType String -Force -ea SilentlyContinue; New-ItemProperty -LiteralPath $path -Name 'MdmTermsOfUseUrl' -Value 'https://portal.manage.microsoft.com/TermsofUse.aspx' -PropertyType String -Force -ea SilentlyContinue;

    New-ItemProperty -LiteralPath $path -Name 'MdmComplianceUrl' -Value 'https://portal.manage.microsoft.com/?portalAction=Compliance' -PropertyType String -Force -ea SilentlyContinue;

    Trigger AutoEnroll C:\Windows\system32\deviceenroller.exe /c /AutoEnrollMDM

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.