ERROR CODE :80192EE7. Your account was not setup in device because device management could not be enabled.

Anonymous
2024-03-19T06:25:56+00:00

We're in the process of configuring a computer with a Microsoft Business Premium account. The computer currently has an administrator account under ****@ugafco.aero. Now, I'm attempting to add another account to Microsoft 365 (Office), specifically ****@ugafcoaero.onmicrosoft.com, which was provided by the admin for Business Premium. However, we're encountering error code 80192EE7. How can we troubleshoot and resolve this issue?![](https://learn-attachment.microsoft.com/api/attachments/03d933b9-4cac-49a7-a6ac-30992a96c348?platform=QnA

![](https://learn-attachment.microsoft.com/api/attachments/96637866-fc4c-466c-8b08-324f4fc5dd4c?platform=QnA

Microsoft 365 and Office | Install, redeem, activate | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-03-26T02:32:26+00:00

I called Microsoft and they told me it is a known issue Microsoft accidentally created when they deprecated and renamed WIP.

If you go into Azure and then type into the search 'wip' and select Mobility (MDM and WIP) and then click on Microsoft Intune

Under Windows Information Protection (WIP) user scope tick on the None radio button and then Save.

Was this answer helpful?

90+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2024-03-20T03:19:34+00:00

No, that's fine, this error is apparently more broadly applicable than I thought. We must have it for different reasons, and I think in your case it was an isolated incident, as opposed to what's suddenly happening here, which seems to be any account on any machine.

It's pretty interesting what the audit log in Azure AD shows for any attempt: https://portal.azure.com/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Audit

This sequence, in rapid succession:

-Add device

-Add registered users to device

-Add registered owner to device

-Update device

-Register device

-Delete device

-Unregister device

So, amusingly, it adds it, changes its mind, removes it, and then throws the error in question. I was surprised to see that it gets that far.

Was this answer helpful?

30+ people found this answer helpful.
0 comments

46 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-04-21T19:28:39+00:00

    I had the same problem. I had to change the MDM Users scope from All to Some and add the All Users group to get it to work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-04-19T15:28:11+00:00

    We ran into a user with this problem this morning. Her device was registered in Entra, but she was not connected under Work and School. When we tried to connect her, we got the same error as the OP.

    Solution: Or the steps we took that resolved the issue

    1. Remove the device from Entra
    2. Rebuild the links for MDM/MIPS under Intune Settings (we're not using Intune, but the setting was put there)
    3. Reboot the PC
    4. Flush DNS (IPCONFIG /FLUSHDNS)

    We were able to connect under Connect to Work and School and all office products that were failing loaded just fine.

    Hope this helps.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-04-10T17:54:02+00:00

    working through the same issue as OP. In my case, the root cause was having a compliance policy requiring Microsoft Defender Antimalware. There was some issue with a specific machine where the Defender Antimalware would not start and therefore stalled the Intune enablement. I changed it to "Not Configured" and then everything finished smoothly.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments