Intune MDM Error

Chase 1 Reputation point

Hi! Im trying to join a device to azure AD using the access work or school page, then by hitting connect, and "Join this device to azure AD" when im prompted to put in my credentials I do and then it shows my AAD to join. I hit join and then an error pops up that gives me the "Something went wrong" page and gives me the

Server Error code: 80180014
correlation id: not available

This does not happen to any of our organizations other devices, and I have done the exact same steps to prep the machine for intune that I do with each device.

Microsoft Intune Enrollment
Microsoft Intune Enrollment
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Enrollment: The process of requesting, receiving, and installing a certificate.
1,282 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,569 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,077 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Rahul Jindal [MVP] 9,391 Reputation points MVP

    Is the user allowed for AAD join?

    0 comments No comments

  2. Lu Dai-MSFT 28,366 Reputation points

    @Chase Thanks for posting in our Q&A.

    To clarify this issue, we appreciate your help to collect some information:

    1. Please make sure that the target user has an intune license.
    2. Please make sure that the target user has permissions to join devices to Azure AD.
    3. Please check if there is any enrollment device limit restrictions and enrollment device platform restrictions configured for windows devices under Devices > Enroll devices. Please make sure that this windows device meets these limit restrictions.
    4. Please check if the device has displayed in Azure AD portal. If yes, please delete it.

    Then it is suggested to re-enroll the device again and check if the enrollment is successful.

    If there is anything update, feel free to let us know.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

  3. Akshay-MSFT 16,921 Reputation points Microsoft Employee

    Hello @Chase ,

    Thanks for posting your query on Microsoft Q&A @Lu Dai-MSFT thanks for adding the relevant tag here. In order to troubleshoot the Azure AD join issues kindly try the following steps:

    • Run Device Registration Troubleshooter Tool on the impacted device and validate the issue. User will get the option to choose from below, once identified try collecting logs via suggested option:


    Run dsregcmd /status in CMD on the device to see if device is Azure AD joined to some other tenant.

    • If yes, then run dsregcmd /leave CMD on the device to remove the device join from existing tenant.
    • If no, then run dsregcmd /join and enter the credentials to get the devices joined to Azure AD.
    • To isolate the issue outside of Intune, kindly exclude the user from Intune AutoEnrollment scope and Conditional Access (If applied for hybrid AD join device). If join/registration works, this may need further investigation from Intune end. Probably a support ticket would help


    Let me know if you have any further queries in the comments section.

    Akshay Kaushik

    Please "Accept the answer" and "Upvote" if the suggestion works as per your business need. This will help us and others in the community as well.

  4. Chase 1 Reputation point

    I eventually found out that allowing personal devices to be enrolled into intune fixed the issue, but every other device I have has never had to do that before. Very confusing

    0 comments No comments