Company devices indentified as personal - error 8018004

Temny Pan 6 Reputation points
2022-04-14T11:30:12.727+00:00

Hi,
I can't join any of our company devices into corporate Azure AD because of 8018004. We have our own AD but wish to use corporate SSO for authentication. What makes Azure AD to think the device is not part of company but "personal"?

Microsoft Security | Intune | Enrollment
Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} vote

2 answers

Sort by: Most helpful
  1. JamesTran-MSFT 36,911 Reputation points Microsoft Employee Moderator
    2022-04-14T21:34:14.343+00:00

    @Temny Pan
    Thank you for your post!

    From the error you received - Error 80180014, I was able to find some related issues and will share the solutions below to hopefully help point you in the right direction.

    Error Code 80180014:
    Mobile Device Management (MDM) server doesn't support this platform or version. For more info.
    193215-image.png

    In order to resolve this, can you follow the steps below. For more info - Your organization does not support this version of Windows.

    1. In the Microsoft Endpoint Manager admin center, chooses Devices > Enrollment restrictions > choose a device type restriction.
    2. Choose Properties > Edit (next to Platform settings) > Allow for Windows (MDM).
    3. Click Review + Save.

    Related Issues:
    Error 80180014 due to device restrictions for Windows Autopilot devices
    Error 80180014 when joining azure ad - YouTube
    Error Code 80180014

    If you're still having issues, can you share how you're trying to join your devices to Azure AD?
    Thank you for your time and patience throughout this issue.

    ----------

    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    1 person found this answer helpful.

  2. John Miller 0 Reputation points
    2023-08-23T21:40:28.4+00:00

    Is there an extended message like "this platform is not supported"?

    Type "tpm" and check your tpm settings under Device Security - is Secured Core On?

    I had some tpm related compliance scenarios and had to reset my bios to re-enable:
    Firmware Protection
    Memory Access Protections

    (These were disabled in the BIOS)

    Also ... after reenabling those there was an INTEL update via WUA that needed to be applied.

    0 comments No comments

Your answer

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