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-03-24T17:55:54+00:00

    Right, if that one is on "All" (and the URLs in that top section are filled in) you might see a message come up for some users about licensing requirements. It can be declined at that point, but if the goal for the org is simply a workplace join, you're best just keeping it on None so that the user isn't confused.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-03-23T11:09:59+00:00

    To make the devices entra id joined by using a unlicensed user it seems we have to set "MDM user scope: None"

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-03-22T14:36:51+00:00

    According to a user in the other thread, "Microsoft has confirmed to me from the opened ticket that there is a general problem.

    They are trying to fix it ASAP."

    That thread has also been updated now with a solution:

    Go here: https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Mobility

    Click "Mobility (MDM and WIP" on the left.

    Set "Windows Information Protection (WIP) user scope" to None

    Note: If you've never used this screen before, maybe because you don't use Intune, it may seem that you can't save changes. This is because it's missing the URLs. Click the two "Restore" blue links to address that. Now you will be able to Save.

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments