Cannot Join Device to Azure Ad - States Device is already enrolled

Question

Cannot Join Device to Azure Ad - States Device is already enrolled

RandSol 41

Hello,

I am a member of an MSP that recently took over a client running Azure AD. We are attempting to join our first new PC (Win10)to Azure AD by going through Settings>Accounts> Join Work. I am using a support account to authenticate with a Business PRemium license (Intune included).

However, we receive an error that the device is already enrolled. I can confirm that the device is not in Azure AD nor is it showing in Endpoint Manager. I'm not sure where else it could be but any advice would be appreciated to get the new PC joined and enrolled.

Thank you!

YesMan 0 Reputation points

2023-03-25T09:16:49.15+00:00

I have seen this error as well. Sometimes it takes at least a few attempts (restarts) to get it going. Seems to be related to poor internet or Wi-Fi connections. Not a great solution, but it seems to work.
Nathan 0 Reputation points

2023-05-10T04:26:51.1633333+00:00

Hi guys, I got this issue Enroll in Azure AD with error 8018000a, and I found the solutions:

on Windows setting, use: "Reset this pc", after that computer reset, you will be able to join Azure AD. I tested on 2 PCs.
Nathyn Luke 10 Reputation points

2023-08-09T05:21:46.7066667+00:00

I came across this and used the solution found here "https://jocha.se/blog/tech/azure-ad-mdm-intune-error-8018000a" but took it one step further to work out exactly which registry item required deleting and why.

The Why: Because the device was previously MAM enrolled and pointing to https://wip.mam.manage.microsoft.com/Enroll

When Intune is configured you switch off the MAM policy so devices can enroll via MDM

The key that requires deleting is the GUID that points to

https://wip.mam.manage.microsoft.com/Enroll

I have tested this across 10 devices and just deleting that item works.

I don't think there is any issue with deleting all the other keys other than context etc as they are possibly just failed enrollments.
Jon Mercer 1,026 Reputation points

2023-08-09T17:34:10+00:00

@Nathyn Luke did you have to search manually through each key or did a search work to find the specific key?
Nathyn Luke 10 Reputation points

2023-08-10T00:20:43.4133333+00:00

Hey Jon, I actually performed the remediation remotely via a rmm tool. I'd imagine you could search using

https://wip.mam.manage.microsoft.com/Enroll

and delete the key located under __HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments
__
If it worked I'd imagine it would be pretty straightforward to script to remediate a bunch of machines.

Accepted answer

7 additional answers

Your answer

YesMan 0 Reputation points

2023-03-25T09:16:49.15+00:00

I have seen this error as well. Sometimes it takes at least a few attempts (restarts) to get it going. Seems to be related to poor internet or Wi-Fi connections. Not a great solution, but it seems to work.
Nathan 0 Reputation points

2023-05-10T04:26:51.1633333+00:00

Hi guys, I got this issue Enroll in Azure AD with error 8018000a, and I found the solutions:

on Windows setting, use: "Reset this pc", after that computer reset, you will be able to join Azure AD. I tested on 2 PCs.
Nathyn Luke 10 Reputation points

2023-08-09T05:21:46.7066667+00:00

I came across this and used the solution found here "https://jocha.se/blog/tech/azure-ad-mdm-intune-error-8018000a" but took it one step further to work out exactly which registry item required deleting and why.

The Why: Because the device was previously MAM enrolled and pointing to https://wip.mam.manage.microsoft.com/Enroll

When Intune is configured you switch off the MAM policy so devices can enroll via MDM

The key that requires deleting is the GUID that points to

https://wip.mam.manage.microsoft.com/Enroll

I have tested this across 10 devices and just deleting that item works.

I don't think there is any issue with deleting all the other keys other than context etc as they are possibly just failed enrollments.
Jon Mercer 1,026 Reputation points

2023-08-09T17:34:10+00:00

@Nathyn Luke did you have to search manually through each key or did a search work to find the specific key?
Nathyn Luke 10 Reputation points

2023-08-10T00:20:43.4133333+00:00

Hey Jon, I actually performed the remediation remotely via a rmm tool. I'd imagine you could search using

https://wip.mam.manage.microsoft.com/Enroll

and delete the key located under __HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments
__
If it worked I'd imagine it would be pretty straightforward to script to remediate a bunch of machines.

Answer 1

Crystal-MSFT 54,031 Microsoft External Staff

@RandSol , For our issue, we can try to delete all GUIDs under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments to see if it can be enrolled.
Note: Make sure to NOT delete Context, Ownership, Status and ValidNodePaths.

The following link for the reference:
https://jocha.se/blog/tech/azure-ad-mdm-intune-error-8018000a
Note: Non-Microsoft link, just for the reference.

Hope it can help.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Jon Mercer 1,026 Reputation points

2022-11-30T19:37:37.277+00:00

This worked for me also. Would think after nearly 2 years, Microsoft would have fixed this issue, which in my case was dropping a system from the domain, that was also on Azure AD through Azure AD Connect. Until I deleted the GUID keys (all but 2 deleted) I was getting the same error. It has been an issue since Azure AD came out when trying to migrate an AD joined system to Azure.
Kerfisstjóri Reykjahlíðarskóla 0 Reputation points

2023-03-09T10:00:53.4533333+00:00

Worked perfectly!
Christopher Van Scoy 0 Reputation points

2023-04-05T00:45:59.98+00:00

Thank You! This worked super smoothly! I was adding the Admin computer, and was worried for a little bit there!
Sumith Bogela 0 Reputation points

2023-08-13T11:11:51.5833333+00:00

thanks a lot, it is working.
Abdullah Ollivierre 0 Reputation points

2023-08-21T14:14:15.4166667+00:00

Yes this is the solution! a small pro tip, to find the proper GUID under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments it will be the GUID that has DeviceEnroller, DMClient, Poll and Push. so if you rename the parent folder which is the GUID to say by adding .old and then close regedit and then try again from OOBE/ ms-settings then you should be able to enroll.

Answer 2

Marnix Sommen 0

Thank you! It worked perfectly for me as well.

Answer 3

Nathan 0

Hi guys, I got this issue Enroll in Azure AD with error 8018000a, and I found the solutions:

on Windows setting, use: "Reset this pc", after that computer reset, you will be able to join Azure AD. I tested on 2 PCs.

Jon Mercer 1,026 Reputation points

2023-05-10T15:29:24.78+00:00

Would that be the reset this pc, that does a clean install of the OS, or something else?
RaKu 41 Reputation points

2025-07-29T12:50:23.6433333+00:00

did not work for me any other fix?

Answer 4

RaKu 41

did not work for me any other fix?

Share via

Cannot Join Device to Azure Ad - States Device is already enrolled

7 additional answers

Your answer