Device management could not be enabled

Morten Fly 0 Reputation points
2025-12-03T18:34:46.15+00:00

This used to work very well but 6-12 months ago something has changed so we now keep getting this error when signing in to an Office account on a new device:

[Moderator note: personal info removed] 

Previously you could sign in to i.e. OneDrive or at least Outlook and then Windows would re-use the credentials when you opened the other programs (Teams, Office 365 a.o.).

But now the user has to sign in to OneDrive, Outlook, Office 365, Teams a.o. individually.

Any idea what has changed and how we can make it work again?

Here are some screenshots from step 1 and 2:

Office activations part 1

Office activations part 2

And then eventually the first image with the error message will show.

It is the same error that shows no matter which application we activate.

And of course we only do this when the laptop/desktop is online and connected to our domain/network.

Any ideas?

/Morten

Microsoft 365 and Office | Install, redeem, activate | For business | Windows
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Chris Duong 5,165 Reputation points Microsoft External Staff Moderator
    2025-12-03T21:04:20.41+00:00

    Hi @Morten Fly,  

    Welcome to the Microsoft Q&A forum.    

    Thank you for contacting us regarding the sign-in issue you are experiencing on new devices and the error message “Device management could not be enabled.” I appreciate the detailed screenshots and description you provided. After reviewing the information, here is an explanation of the root cause and recommended steps to resolve the problem: 

    The behavior you are experiencing is that Windows/Office now requires devices to be enrolled in MDM/Intune for Single Sign-On (SSO), and the error “Device management could not be enabled” (0x80192EE7) occurs when device registration fails due to issues such as enrollment configuration, licensing, policy scope, or network restrictions. 

     

    Here are my recommendations, which I hope will be helpful to you. If you don’t have admin permissions, please contact your IT administrator:       

    1/ Confirm if device management is required: 

    • If your organization does not require device management, when prompted: 
      • Select “No, this app only” instead of “Yes”. 
      • This allows sign-in for the app without attempting device enrollment, avoiding the error. 
    • If your organization uses Intune, proceed with the steps below. 

    2/ Check MDM/Intune configuration: 

    In Microsoft Intune admin center

    1. Navigate to: Devices → Windows → Windows enrollment → Automatic enrollment 
    2. Configure: 
      • MDM user scope → Set to All or Some (include affected users). 
      • MAM user scope → Configure if applicable. 
      • Windows Information Protection (WIP) user scope → Set to None temporarily to rule out conflicts. (Note: WIP is deprecated; consider migrating to Microsoft Purview Information Protection.)
    3. If incorrect or blank, click Restore default MDM URLs. 
    4. User's image
    5. Confirm the user has a valid Microsoft 365/Intune license assigned. 

    3/ Verify network connectivity: 

    • The device must resolve and access: "https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc"
    • Test with nslookup enrollment.manage.microsoft.com and verify no firewall or proxy blocks. 
    • If using VPN or corporate proxy, ensure Microsoft endpoints are whitelisted. 

    4/ Clear sign-in cache on the device: 

    • Close all Office apps, Teams, and OneDrive. 
    • Delete these folders:  

    C:\Users<username>\AppData\Local\Microsoft\IdentityCache  

    C:\Users<username>\AppData\Local\Microsoft\OneAuth  

    • Restart the device and sign in again. 

     

    For more details, you can refer to these Microsoft's article:  

    5/ Contact Microsoft Support    

    If this issue is urgent and directly impacting your team’s productivity, I strongly recommend reaching out to your IT department and asking them to open a support ticket with Microsoft Technical Support through the Microsoft 365 Admin Center. They have access to system-level diagnostics and can investigate the problem more thoroughly. At the very least, they can provide the most effective workaround to ensure your experience remains smooth and secure.   

        

    We kindly ask for your understanding that, as moderators, we do not have access to the administrative tools or permissions required to investigate or modify these configurations. We also do not have the capability to initiate remote sessions for direct assistance. Our role is to guide users to the appropriate resources and support channels.      

      

    I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, feel free to share them in the comments on this post so I can continue to assist you.  

    I look forward to hearing your thoughts on this.  


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".   

    Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic. 


Your answer

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