Intune MDM enrollment for devices already Azure Ad /Entra joined

Last Updated on January 31, 2024 by rudyooms

This blog will show you a possible method to make sure that your existing Azure Ad / Entra Joined devices and not yet MDM / Intune enrolled, are going to be automatically enrolled into Intune.

I will divide this blog into multiple parts

  1. Introduction
  2. The Requirements
  3. Triggering the Enrollment
  4. Results
  5. Troubleshooting the Enrollment

1. Introduction

A lot of customers will start their cloud journey by making use of Azure Ad as their Identity Provider. Most of the time, Intune wasn’t yet part of that journey. But what if you want to make sure your devices are being managed and the devices are already enrolled into Azure/Entra but not into Intune?

Today I spent some time enrolling existing Azure Ad joined /Entra devices into Intune. These devices were Azure Ad joined but without MDM/Intune enabled or configured.

This company started off with only Microsoft 365 Business standard licenses. With this particular license, we will not have the possibility to enroll the devices into Intune.

So without the possibility to enroll devices into Intune, all of the devices were only Azure Ad Joined/ Entra joined. How are we going to make sure we can enroll those Entra joined-only devices into Intune?

When you want to enroll your existing Azure Ad joined device into Intune, there are multiple options available to make sure the device will be enrolled into MDM/Intune.

Microsoft is telling us, that the official supported method is using a provisioning package.

Bulk join a Windows device to Azure AD and Microsoft Endpoint Manager using a provisioning package – Microsoft Community Hub

I guess, there should be an easier way to do so? Before I am going to show you, the easy way, let’s take a look at the requirements first.

2. The Requirements

The first one is not necessarily a requirement but could make your life a lot easier. When we have a third-party remote management (RMM) tool installed on those devices, we will probably have the possibility to deploy some PowerShell script to those devices in system context. (at least our RMM tool has that option)

The system permissions are necessary because when enrolling an existing Azure Ad Joined device into Intune there is 1 major requirement. You will need to have the right privileges (local administrator) to perform that operation! Otherwise, you will end up with some nice errors.

If the permissions aren’t going to be an issue we still need to check out some other settings. To make sure users could enroll their device we need to configure the MDM scope in Intune. As shown below we made sure only users with a proper license (Business Premium) could enroll their device into MDM.

Please note: Before enrolling the device, also make sure there are no enrollment restrictions(Block Personal Devices) configured!

3. Triggering the Enrollment

When you don’t want to go through all the steps to create a provisioning package and end up as a grumpy old man we need to come up with a faster solution

If you aren’t deploying this script below with system context (RMM tool requirement) we need to download and use PSExec. (Sysinternal tools)

With Psexec -s we can start the enrollment that triggers the DeviceEnroller command with these arguments /c /AutoEnrollMDM in the System context (PSEXEC).

If you don’t execute this command in the system context you will notice a nice error mentioning: “Auto MDM ENroll: Device Credential (0x0), Failed (Access is denied). So please….use PSEXEC to kick off the enrollment if you are doing this on your own and not using an RMM tool.

Let’s continue with the script! As shown below, I am also making sure the MdmEnrollmentUrls are configured before we start the enrollment!

I got 2 PowerShell scripts.. one just doing its job and one with try/if/catch in it to make sure it catches the error it could run into

The simple one

# Set MDM Enrollment URL's

$key = 'SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\*'
$keyinfo = Get-Item "HKLM:\$key"
$url = $
$url = $url.Split("\")[-1]
$path = "HKLM:\SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\$url"

New-ItemProperty -LiteralPath $path -Name 'MdmEnrollmentUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;
New-ItemProperty -LiteralPath $path  -Name 'MdmTermsOfUseUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;
New-ItemProperty -LiteralPath $path -Name 'MdmComplianceUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;

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

The Improved One

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

    $keyinfo = Get-Item "HKLM:\$key"
    Write-Host "Tenant ID is not found!"
    exit 1001

$url = $
$url = $url.Split("\")[-1]
$path = "HKLM:\SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\$url"
if(!(Test-Path $path)){
    Write-Host "KEY $path not found!"
    exit 1001
        Get-ItemProperty $path -Name MdmEnrollmentUrl
        Write_Host "MDM Enrollment registry keys not found. Registering now..."
        New-ItemProperty -LiteralPath $path -Name 'MdmEnrollmentUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;
        New-ItemProperty -LiteralPath $path -Name 'MdmTermsOfUseUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;
        New-ItemProperty -LiteralPath $path -Name 'MdmComplianceUrl' -Value '' -PropertyType String -Force -ea SilentlyContinue;
    # Trigger AutoEnroll with the deviceenroller
            C:\Windows\system32\deviceenroller.exe /c /AutoEnrollMDM
            Write-Host "Device is performing the MDM enrollment!"
           exit 0
            Write-Host "Something went wrong (C:\Windows\system32\deviceenroller.exe)"
           exit 1001          

exit 0

The Scheduled Task One

Another option you can use if you don’t want to leverage PSExec because of some ASR rules/AV Blocking it. Besides it could be blocked, and it could create a lot of noise if you have an SIEM. If we want to enroll our existing device into Intune without using Psexec, we could also just create a scheduled task that will literally do the exact same thing.

As shown below, this script will create a scheduled task under system context and will trigger the deviceenroller.exe with the /c /AutoEnrollMDM parameters.

$triggers = @()

$triggers += New-ScheduledTaskTrigger -At (get-date) -Once -RepetitionInterval (New-TimeSpan -Minutes 1)

$User = "SYSTEM"

$Action = New-ScheduledTaskAction -Execute "%windir%\system32\deviceenroller.exe" -Argument "/c /AutoEnrollMDM"

$Null = Register-ScheduledTask -TaskName "TriggerEnrollment" -Trigger $triggers -User $User -Action $Action -Force
Start-ScheduledTask -TaskName "TriggerEnrollment"

4. Results:

When kicking off the PowerShell script (or the scheduled task) you will need to give it some time because sometimes it could take a bit longer before the device will be enrolled into Intune successfully. In the meantime, you could notice the error Auto MDM Enroll: Failed 0x8018002b (event 76) popping up in the DeviceManagement-Enterprise-Diagnostic event log.

After some time of waiting you will notice event 75 with the message that Auto MDM Enroll: Succeeded

For the people who don’t believe that this process will only take a few seconds, here you go

5. Troubleshooting the Enrollment

I removed this part from this blog because it was becoming too large and while becoming too large it was overshadowing the main part of the blog.

Please visit this blog if you are dealing with Intune Enrollment Errors or if you are missing the scheduled task to start the enrollment


When your devices are already enrolled in Azure Ad, it doesn’t mean you will need to reinstall the devices to make sure those devices are enrolled into Intune/MDM. Sometimes enrolling a device into Intune sounds easier than it is… hopefully, the troubleshooting part showed you how to deal with those kinds of situations!

Please Note: Wiping the device and enrolling it with Autopilot is the path you will need to take… but sometimes that path isn’t always available!

Two Paths GIFs - Get the best GIF on GIPHY

35 thoughts on “Intune MDM enrollment for devices already Azure Ad /Entra joined

  1. Hi,
    thanks for your tutorial!
    Do you mean Azure AD joined or registered?

    best regards

  2. how long does it take for the scheduled task to show up? How long on avg before it enrolls with Azure AD? Been waiting 4hrs and nothing on ether front. Running version 20H2

    1. Normally, when you configure this setting your already azure ad joined device will register itself in Intune. This setting will not join the device to azure.

  3. Thank you! I couldn’t find any mention of this on the setup or troubleshooting pages, unless I’d glazed over it.

    As soon as I set this GPO and triggered the scheduled task, the devices checked in to Intune as ‘Co-managed’. Also gave them a reboot to speed up the client, rather than waiting 240 minutes for the retry.

  4. On a computer that is currently Azure AD Joined if you put in place the registry key in this location: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\MDM
    The device will never create the scheduled task. As soon as I made the changed via Local Group Policy Editor the scheduled task gets made as soon as I run GPUpdate. Without the local GPEDIT not even the “EnterpriseMgmt” folder within scheduled task gets generated.

    Any thoughts on how to get around this so the change can be made with just a regedit? It would be a lifesaver for automating this,

    1. Replying to myself here. I may have found a PowerShell script to do this. The scheduled task has to be made. You can’t just flip the registry keys. I’ve not tested yet but here is a potential solution:

      1. What happens when you use C:\Windows\System32\deviceenroller.exe /c /AutoEnrollMDM from a system shell(psexec)

  5. Hey Rudy
    If users enrol as local admin… Will they keep local admin on the enrolled device?
    If so that seems like a big no no :o)
    Regards from Denmark

    1. Depends on what”you” configured in Intune πŸ™‚ , as you are enrolling a device into a mdm… so I assume you have your configuration profiles in place to make sure the user isn’t going to be an admin right?

  6. I end up with error “Auto MDM Enroll: Device Credential (0x0), Failed (Unknown Win32 Error code: 0x80180026)”
    Any idea ?
    Using psexec -i -s powershell.exe

  7. I had an issue with your powershell, for some reason the JoinInfo and TennantInfo in the registry wasn’t there. I think I didn’t wait long enough but I’m sure what actually populates that info.

  8. Is there any way to automatically enroll a not Azure Ad joined device to MDM only with a username/password combination? E.g., to run some scripts with an embedded username/password and MDM server enrollment URL.

  9. Rudy! You’re an awesome bro! I used your powershell script but the scheduled task never scheduled. I still successfully enrolled my AzureAD only clients in Intune within seconds using your Psexec method. Let’s go have a beer sometime on me πŸ™‚

  10. In many PCs don’t have enrollment task.
    After Option 3. PowerShell had error: “Reg key alredy exist.”
    Then gpupdate /force – Windows failed to apply the MDM Policy settings.
    How can fix this?

  11. Found an easier way enroll Azure AD Joined devices in Intune. I ran this as the logged in user who was a local admin rights, but it might not be a requirement.
    Go to Accounts > Access work or school > Enroll only in device management. Sign in using your work Microsoft credentials. Follow the bouncing ball. Done!
    The device gets registered in Intune as a personal device, which you can change in Properties to Corporate if you want.
    On the users device, it now shows connected to two Work accounts, one says “Connected to Contoso’s Azure AD” (this was when it was originally Azure AD Joined), and another that says Connected to Contoso for Mobile Device Management Only.

    1. Hi… Never said that, this option wasnt possible πŸ˜› (admin is required)
      But maybe not the best option…. as the certificate (mdm) could be stored in the user store

    2. Hello, I stumbled across this method as well. Only thing is my user profile is not there to log into,, the PC logs straight back into the Local admin account. Any ideas to get this test.user back?

  12. Can I just say thank you so much for this tutorial. I have wasted so much time on this and Microsoft’s documentation on this very subject sucks. It sucks like most of their documentation to be honest.

    This has managed to get the devices from Azure AD to Intune. Thanks again!!

  13. I combined both scripts and was able to enroll the computers almost instantly. Hope this helps others!

    # Create Registry Path for MDM AutoEnrollment
    $registryPath = “HKLM:\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\MDM”
    New-Item -Path $registryPath -Force

    # Add Registry Keys for AutoEnrollment
    $Name1 = “AutoEnrollMDM”
    $Name2 = “UseAADCredentialType”
    $value = “1”

    New-ItemProperty -Path $registryPath -Name $Name1 -Value $value -PropertyType DWORD -Force | Out-Null
    New-ItemProperty -Path $registryPath -Name $Name2 -Value $value -PropertyType DWORD -Force | Out-Null

    # Force Group Policy Update
    gpupdate /force

    # Speed up the process by configuring MdmEnrollmentUrl and other URLs, and then forcing device enrollment
    $key = ‘SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\*’
    $keyinfo = Get-Item “HKLM:\$key”
    $url = $
    $url = $url.Split(“\”)[-1]
    $path = “HKLM:\SYSTEM\CurrentControlSet\Control\CloudDomainJoin\TenantInfo\$url”

    New-ItemProperty -LiteralPath $path -Name ‘MdmEnrollmentUrl’ -Value ‘’ -PropertyType String -Force -ea SilentlyContinue
    New-ItemProperty -LiteralPath $path -Name ‘MdmTermsOfUseUrl’ -Value ‘’ -PropertyType String -Force -ea SilentlyContinue
    New-ItemProperty -LiteralPath $path -Name ‘MdmComplianceUrl’ -Value ‘’ -PropertyType String -Force -ea SilentlyContinue

    & C:\Windows\system32\deviceenroller.exe /c /AutoEnrollMDM

    1. Thanks… made me realize I needed to update the script in that blogpost with the one we are always using these days πŸ™‚

  14. After running this and enrollment is done in Intune what does happen with for example a Bitlocker policy? Does it actively apply this policy?

    1. When the device is enrolled, it will start syncing with intune and with it fetching the policies.. so the bitlocker policy will be downloaded and applied

  15. Not getting any errors, not seeing devices in Intune either. They are either Entra Joined or Registered. I was getting errors previously that the regkey did not exist under TenantInfo.. that went away but still no change.

    1. I assume you run that command in system context. Also its good to know that when there are lingering keys (enrollments), it will not work

  16. Thanks Rudy! You’ve helped me out so many times with your posts, you’re the best!

    Quick question. Anyone else that knows the answer feel free to jump in!

    I have a bunch of Azure Joined laptops in the field. I have successfully used PSexec in my tests to run PS on remote devices, but these devices are Azure AD Joined, and nothing i do PSexec wise is allowing me to get to them im guessing because they arent hybrid or domain joined. Is there any way of executing this script on them remotely?

    1. Hi..thanks

      If you dont have management over them (defender or an rmm tool) than it would become difficult as you will need to have some remote control on them

  17. I tried the code but that threw this error
    Auto MDM Enroll: Device Credential (0x0), Failed (Unknown Win32 Error code: 0xcaa10001)
    my device was a virtual machine running on the windows 10. And the device is azure AD joined as mentioned

  18. Thanks, this guide was so helpful! We found some of our computers had recently started vanishing from InTune but were still in Entra and AutoPilot.

    We used the scheduled task method to get them to reenrol into Intune.

    We noticed though that we were not seeing Event 76 in the event viewer so we had an extra step we had to before they would retry enrolling.

    In case anyone else is in this situation, the extra step was to remove a reg key from:


    When you look in there, you’ll see lots of keys (not for just InTune) but the one you are looking for has a lot of information on it compared to the others and contains the under DiscoveryServiceFullURL.

    Once you have located this key, you can delete it. You should then see Event 75 to show it has succeeded (or Event 76 if something else is stopping it…MFA in our case!)

    Hope that helps, and thanks again for the guide!

Leave a Reply

Your email address will not be published. Required fields are marked *

8  +  2  =