Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Microsoft 365 device enrollment can fail with the message “Device management could not be enabled” when Windows cannot complete registration with Microsoft Entra ID, Intune, or the organization’s MDM service. The errors -2145833241, 80192EE7, and 0x80180002 often appear during Azure AD join, work or school account setup, or automatic Intune enrollment.
For device-management enrollment errors, Outbyte PC Repair can scan Windows settings and system elements for related configuration problems.
These errors are usually caused by configuration or connectivity problems rather than a damaged PC. Common causes include missing Intune licenses, disabled MDM enrollment scope, enrollment restrictions, device limit issues, stale work account connections, proxy or VPN interference, incorrect system time, or a device that is already joined or enrolled in another state.
Free tools Windows power users keep installed
One-click scans. No signup required.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Windows 11 Pro Upgrade, from Windows 11 Home (Digital Download) | $99.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The fixes involve checking both the user side and the admin side: confirming licensing, verifying Entra ID and Intune enrollment settings, removing old account links, checking device records, resolving network access problems, and then re-enrolling the device cleanly.
What the Error Means in Microsoft 365 Device Enrollment
The message “Device management could not be enabled” appears when Windows can add or recognize a Microsoft 365 work or school account, but cannot complete the management enrollment step. In a Microsoft 365 environment, that management layer is typically handled by Microsoft Intune through Microsoft Entra ID device registration or join. The sign-in may succeed, Outlook or Teams may still work, and the account may appear under Windows settings, but the device is not fully enrolled for policy, compliance, app deployment, or security configuration.
Popular on Amazon
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
The error codes -2145833241, 80192EE7, and 0x80180002 are commonly seen during this handoff between Windows, Entra ID, and Intune. They do not always point to a single broken component. Instead, they usually indicate that Windows attempted to register or enroll the device and was blocked by configuration, eligibility, connectivity, or an existing device state. This can happen during “Access work or school” setup, Entra ID join, automatic MDM enrollment, Windows Autopilot, or when opening a Microsoft 365 app that triggers account setup.
| Error code | Common meaning during enrollment | Typical area to check |
|---|---|---|
| -2145833241 | MDM enrollment did not complete after work account connection or Entra registration. | Intune licensing, MDM scope, existing enrollment, device join state. |
| 80192EE7 | Windows could not reach or resolve the required Microsoft enrollment service. | DNS, proxy, VPN, firewall, captive portal, TLS inspection, time sync. |
| 0x80180002 | The enrollment request was rejected or not allowed for the user or device. | Enrollment restrictions, device platform rules, device limit, tenant settings. |
For users, the most visible symptom is that Windows keeps asking to set up device management, fails after authentication, or shows the account as connected without the device becoming compliant. Company Portal may report that the device is not managed, Microsoft 365 apps may say the organization requires management, or access to Exchange, SharePoint, Teams, or OneDrive may be blocked by Conditional Access until enrollment is complete.
For administrators, the error usually means the device did not successfully move through the expected sequence: user authentication, device registration or join in Entra ID, MDM discovery, Intune enrollment, and policy check-in. A failure at any point can produce the same user-facing message. The fastest way to troubleshoot is to treat it as an enrollment chain problem rather than a simple password or app issue. Start by confirming the user is licensed for Intune, the tenant allows automatic MDM enrollment for that user, enrollment restrictions do not block the device, the user has not exceeded device limits, and the Windows device is not already joined or enrolled under a stale work account.
Check Microsoft Intune and Entra ID Licensing
Microsoft 365 device enrollment depends on the user having the right cloud services assigned before Windows can complete MDM enrollment. The error “Device management could not be enabled”, including codes such as -2145833241, 80192EE7, or 0x80180002, can appear when the sign-in account is valid for email or Office apps but is not licensed for Microsoft Intune, Entra ID features required by the tenant configuration, or automatic device management.
For users, the first check is simple: confirm that you are signing in with the correct work or school account. If your organization has mulle Microsoft 365 accounts, guest accounts, or recently renamed domains, enrollment may fail when Windows tries to register the device under an account that does not have Intune rights. Sign out of Office apps and the Microsoft Store if needed, then try again with the primary organizational account provided by your IT administrator.
Admin licensing checks
Admins should verify licensing in the Microsoft 365 admin center or Microsoft Entra admin center. Open the affected user account and review the assigned licenses and enabled service plans. The user typically needs an Intune-capable license, such as Microsoft Intune Plan 1, Microsoft 365 Business Premium, Enterprise Mobility + Security E3/E5, or a Microsoft 365 enterprise plan that includes Intune. If the tenant relies on Conditional Access, automatic enrollment, or advanced identity controls, confirm that the required Entra ID licensing is also present for the users and policies involved.
- Microsoft Intune: Required for mobile device management and Windows MDM enrollment.
- Microsoft Entra ID P1 or P2: May be required for Conditional Access, dynamic groups, and some automated access controls.
- Windows licensing: Windows Pro, Enterprise, Education, or Business editions are commonly used for Entra join and management scenarios.
- Service plan status: A license may be assigned, but the Intune service plan can still be disabled for that user.
If licensing was just assigned, wait a few minutes before retrying enrollment. In some tenants, license and service-plan changes can take longer to propagate across Microsoft 365, Entra ID, and Intune. After assigning the license, ask the user to restart the device, connect to a stable network, and attempt the work or school account connection again from Settings > Accounts > Access work or school.
Common licensing mismatches
| Symptom | What to check | Fix |
|---|---|---|
| User can access email but enrollment fails | Exchange or Office license exists, but no Intune license | Assign an Intune-included license or standalone Intune Plan 1 |
| Only some users fail enrollment | License assigned through a group with exclusions or errors | Check group-based licensing status and resolve assignment errors |
| Enrollment fails after a plan change | Old license removed before replacement services activated | Confirm the new license includes Intune and that the service plan is enabled |
| Conditional Access blocks setup | Policy requires compliant device before enrollment can complete | Adjust enrollment exclusions or bootstrap access policies for setup |
When group-based licensing is used, do not only check the license name on the user object. Open the license assignment details and look for processing errors, conflicting plans, or disabled services. A user may appear licensed at a glance while Intune is not actually enabled. Once the correct licenses are active, retry enrollment before moving on to MDM scope, enrollment restrictions, or device-limit troubleshooting.
Verify MDM User Scope and Enrollment Restrictions
If licensing is correct, the next place to check is whether the user is actually allowed to enroll the device into Microsoft Intune. In Microsoft 365 and Entra ID, the message “Device management could not be enabled” can appear when the user signs in with a valid work account, but the tenant’s MDM configuration does not target that user. This commonly affects new users, pilot groups, recently migrated tenants, or organizations where Intune enrollment is limited to a security group.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
In the Microsoft Intune admin center, an admin should review the automatic enrollment configuration. Go to Devices > Enroll devices > Automatic enrollment, then check the MDM user scope. If it is set to None, Windows devices will not automatically enroll in Intune. If it is set to Some, confirm that the affected user is a direct or effective member of the selected Entra ID group. If all eligible users should be enrolled, set the scope to All, then allow time for the setting to apply.
Also confirm that the MDM authority is set correctly for the tenant. For most Microsoft 365 environments, this should be Microsoft Intune. If the tenant was previously configured with another MDM provider or has legacy enrollment settings, Windows may attempt to enroll against the wrong management endpoint and return errors such as 80192EE7 or 0x80180002. After changing MDM scope or authority-related settings, ask the user to sign out and restart the PC before trying enrollment again.
Review enrollment restrictions
Enrollment restrictions can block a device even when the user has the correct license and is included in MDM scope. In the Intune admin center, open Devices > Enroll devices > Enrollment device platform restrictions. Check the default restriction and any custom restrictions assigned to the user or group. Make sure Windows enrollment is allowed, and confirm that the device type is not blocked.
- Windows platform: Windows enrollment must be permitted for the affected user.
- Personally owned devices: If the PC is not recognized as corporate-owned, a restriction blocking personal Windows devices can prevent enrollment.
- Minimum and maximum OS version: A device running an unsupported Windows build may be rejected.
- Priority order: If multiple restrictions apply, Intune uses the highest-priority matching policy.
Admins should also check Enrollment device limit restrictions. If the user has reached the allowed number of enrolled devices, enrollment can fail before management is enabled. This is especially common when users have replaced laptops, reinstalled Windows, or repeatedly attempted enrollment during troubleshooting. Increase the limit if appropriate, or remove stale device records from Intune and Entra ID before retrying.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchAfter making changes, do not immediately assume the device is still broken. Policy and group membership changes can take several minutes to propagate across Microsoft 365 services. Have the user disconnect any failed work account entry, restart Windows, and try again from Settings > Accounts > Access work or school using the same licensed account that is included in the MDM user scope.
Remove Old Work or School Account Connections
Stale work or school account connections are a common cause of “Device management could not be enabled” with errors such as -2145833241, 80192EE7, or 0x80180002. This often happens when a Windows device was previously joined to another Microsoft 365 tenant, enrolled in Intune under an old user, connected to a retired account, or partially removed from management. Windows may still hold workplace join records, cached authentication tokens, or an old MDM enrollment profile, causing the new enrollment attempt to fail.
Start by removing old account links from Windows. On the affected device, go to Settings > Accounts > Access work or school. Select any old organization account that should no longer manage the device, then choose Disconnect. If the device shows a connected account for the correct organization but enrollment keeps failing, disconnect it as well and add it back later. Restart the PC after removing the connection so Windows clears the associated sign-in and enrollment state.
Clean up saved credentials and cached sign-ins
After disconnecting the account, check for cached Microsoft 365 credentials that may be reused during enrollment. Open Control Panel > Credential Manager > Windows Credentials and remove entries related to the old tenant, such as MicrosoftOffice, ADAL, AzureAD, Intune, Workplace Join, or entries containing the previous user’s email address. If Office apps are signed in with an old account, open an Office app such as Word or Excel, go to File > Account, and sign out of accounts that should not be used on the device.
For a user-owned device, this cleanup is often enough. For a corporate-owned or previously managed device, an admin should also confirm that stale records have been removed from the cloud portals. In the Microsoft Intune admin center, check Devices for the affected computer and retire, wipe, or delete obsolete entries as appropriate. In the Microsoft Entra admin center, check the user’s devices and remove duplicate or outdated device objects if they are no longer valid. Leaving mulle stale records can cause Windows to associate the device with the wrong object during re-enrollment.
Commands for checking the current join state
On Windows, you can verify whether the device still thinks it is connected to Entra ID or workplace management. Open Command Prompt as the signed-in user or as administrator and run dsregcmd /status. Review fields such as AzureAdJoined, WorkplaceJoined, TenantName, and User State. If the tenant shown is not the current organization, the device still has old registration data that must be removed before enrollment will succeed.
- AzureAdJoined: YES means the device is joined to Microsoft Entra ID.
- WorkplaceJoined: YES means a work account registration exists.
- TenantName should match the organization that will manage the device.
- WamDefaultSet or token errors can indicate cached sign-in problems.
If the device must be completely removed from the old tenant, disconnect it through Access work or school first. If that is not possible, an administrator may need to remove the Entra device object and Intune device record, then have the user restart and sign in again. Avoid deleting device objects randomly in shared or production environments; confirm the serial number, device name, primary user, and last check-in time before removal.
Once the stale connections are gone, restart the computer and sign in with the intended Microsoft 365 work account. Return to Settings > Accounts > Access work or school, choose Connect, and complete the enrollment using the correct user. If the error changes or the device still cannot enroll, continue by checking device limits, join status, network access, and time synchronization before attempting another re-enrollment.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check Device Limits, Join Status, and Existing Enrollment
Microsoft 365 device enrollment can fail with errors such as -2145833241, 80192EE7, or 0x80180002 when the device or user account has already reached an enrollment boundary. Even when licensing and MDM scope are correct, Entra ID and Intune still check whether the user is allowed to register another device, whether the Windows device is already joined to a tenant, and whether an older MDM enrollment record is blocking the new one.
Start by checking the user’s device quota in the Microsoft Entra admin center. Go to Identity > Devices > Device settings and review Maximum number of devices per user. If the affected user already has that number of devices registered or joined, new enrollment can fail before Intune policy is applied. An admin can either increase the limit or remove stale devices from the user’s device list. For a single user, open the user object in Entra ID, review the Devices tab, and delete old Windows PCs, retired laptops, or duplicate entries that are no longer in use.
Next, confirm the local join state on the Windows device. Open Command Prompt as the signed-in user or as an administrator and run dsregcmd /status. Review the values under Device State. A healthy Microsoft 365 work device is usually either AzureAdJoined: YES for Entra joined devices, or DomainJoined: YES with AzureAdJoined: YES for hybrid joined devices. If you see unexpected combinations, such as a device joined to an old tenant, registered but not joined, or Workplace Joined remnants, clean-up may be required before trying enrollment again.
| Check | What to look for | Fix |
|---|---|---|
| User device limit | User has reached the maximum allowed devices | Remove stale devices or raise the Entra ID device limit |
| Join state | Device is joined or registered to the wrong tenant | Disconnect the account, leave the old tenant, then rejoin |
| Existing Intune record | Device already appears in Intune with an old or failed enrollment | Retire, delete, or clean up the duplicate device record |
| Hybrid join | AD and Entra ID objects do not match or sync is delayed | Check Entra Connect sync and wait for the device object to appear |
Admins should also check the Intune admin center under Devices > All devices. Search by device name, serial number, and primary user. If the same computer appears mulle times, or if it shows as retired, noncompliant, or enrollment failed, remove records that no longer represent the active device. For corporate-owned devices, also check Devices > Enrollment > Windows enrollment, especially if Autopilot is involved. A mismatched Autopilot registration can cause the device to enroll into the wrong profile or fail during setup.
Recommended Free Tools
For hybrid Entra ID joined devices, verify that the on-premises computer account is healthy and syncing correctly through Microsoft Entra Connect. If the computer was renamed, reimaged, moved between OUs, or restored from an old backup, Entra ID may contain duplicate or stale device objects. Make sure the OU containing the computer is in sync scope, then run a delta sync or wait for normal synchronization. After cleanup, restart the device and run dsregcmd /status again before attempting to connect the work or school account.
If the device is clearly associated with an old tenant or broken enrollment, disconnect it before re-enrolling. Go to Settings > Accounts > Access work or school, select the connected account, and choose Disconnect. Restart Windows, sign in with a local or domain account, and confirm that the old connection is gone. Once the Entra ID and Intune records are cleaned up and the device count is below the allowed limit, the next enrollment attempt has a much better chance of completing successfully.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix Network, Proxy, VPN, and Time Sync Issues
Microsoft 365 device enrollment depends on a stable connection to Microsoft Entra ID, Microsoft Intune, Windows Push Notification Services, and several authentication endpoints. If the device is behind a restrictive firewall, SSL-inspecting proxy, captive portal, or unstable VPN, Windows may fail to complete enrollment and show “Device management could not be enabled” with errors such as -2145833241, 80192EE7, or 0x80180002. These errors are common when the sign-in succeeds but the device cannot reach the required MDM discovery or enrollment services afterward.
Start by testing the enrollment from a simple network path. Disconnect from VPN, switch to a trusted home or mobile hotspot connection if allowed, and make sure the user can browse to Microsoft 365 services without repeated sign-in prompts. If the device is on a corporate network, ask the network team to verify that Microsoft cloud endpoints are not blocked, redirected, or modified by SSL inspection. Enrollment traffic should be allowed to reach Microsoft authentication and management services directly, especially endpoints used by login.microsoftonline.com, device.login.microsoftonline.com, enterpriseregistration.windows.net, and Intune enrollment services.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsNetwork checks for users
- Restart the PC and router, then try enrollment again on a stable connection.
- Temporarily disconnect from VPN unless your organization specifically requires it for enrollment.
- Avoid hotel, airport, school, or guest Wi-Fi networks that use captive portals or traffic filtering.
- Open Microsoft 365 in a browser and confirm the account can sign in without certificate warnings or proxy prompts.
- Disable third-party web filtering, antivirus web shield, or local proxy software for a test, if permitted by company policy.
Proxy configuration is another frequent cause. Windows enrollment may use system proxy settings rather than browser-only settings, so a browser working normally does not always prove that device registration can connect. On the affected PC, check Settings > Network & internet > Proxy and remove stale manual proxy entries if they are no longer used. Admins can also review WinHTTP proxy settings by running netsh winhttp show proxy in an elevated command prompt. If a proxy is required, it must allow authentication flows and device enrollment traffic without breaking TLS connections.
Time synchronization also matters because Entra ID authentication tokens and device certificates are time-sensitive. If the clock is off by several minutes, enrollment can fail even when licensing and MDM settings are correct. Go to Settings > Time & language > Date & time, enable Set time automatically and Set time zone automatically, then select Sync now. On domain-joined devices, confirm that the domain time source is healthy. After correcting network, proxy, VPN, and time settings, restart the device and attempt enrollment again from Settings > Accounts > Access work or school.
Re-enroll the Device in Microsoft 365
After licensing, Intune enrollment settings, device limits, account remnants, and network access have been corrected, the last step is to enroll the Windows device again. Re-enrollment forces Windows to request a fresh Microsoft 365 device registration, apply the current Microsoft Intune MDM policy, and rebuild the local management certificates that may have been left in a broken state after errors such as -2145833241, 80192EE7, or 0x80180002.
For a standard user-driven enrollment, open Settings > Accounts > Access work or school. If the old work or school connection is still listed, select it and choose Disconnect. Restart the PC, return to the same page, and choose Connect. Sign in with the affected Microsoft 365 work account, approve MFA if prompted, and allow Windows to register the device with Entra ID and enroll it into device management. If the organization requires full Entra ID join instead of simply adding a work account, choose Join this device to Microsoft Entra ID during the connection flow.
- Confirm the user has a valid Microsoft Intune or Microsoft 365 plan that includes device management.
- Make sure the user is included in the configured MDM user scope in Microsoft Entra ID.
- Remove stale work or school accounts from Windows before trying again.
- Restart the device to clear cached enrollment and authentication state.
- Connect the account again from Access work or school and complete MFA.
- Wait several minutes, then check that the device appears in the Intune admin center and Entra admin center.
If the normal Settings flow still fails, use the Company Portal app. Install or open Company Portal from the Microsoft Store, sign in with the user’s Microsoft 365 account, and follow the prompts to set up the device. Company Portal often provides clearer enrollment prompts and can trigger the Intune enrollment process when the built-in Windows flow has cached a failed attempt. Once complete, open Company Portal and confirm the device status shows as compliant or that required actions are listed.
Admins should also verify the server-side result after re-enrollment. In the Microsoft Intune admin center, go to Devices > Windows and search for the device name or user. Remove duplicate, stale, or retired records only after confirming which entry is current. In the Microsoft Entra admin center, check Devices for the join type and owner. A healthy setup usually shows the device as Microsoft Entra joined or registered, with MDM set to Microsoft Intune. If the device repeatedly creates new records but never becomes managed, review enrollment failure logs in Intune and confirm conditional access policies are not blocking registration.
For devices that remain stuck after mulle attempts, perform a deeper reset of the enrollment state. Disconnect the work account, delete the device record from Intune if it is stale, remove the old Entra device object if appropriate, restart, and then enroll again. On corporate-owned devices, an admin may prefer a clean Windows reset or Autopilot reset so the device returns to a known-good provisioning path. Once re-enrolled, run Settings > Accounts > Access work or school > Info > Sync to pull policies immediately and confirm the original “Device management could not be enabled” error no longer appears.
Frequently Asked Questions
What does “Device management could not be enabled” mean when adding a Microsoft 365 work account?
It usually means Windows could add or detect the work account, but could not complete MDM enrollment into Microsoft Intune or another configured management service. The common causes are missing Intune licensing, incorrect MDM user scope, enrollment restrictions, stale work account entries, device limit issues, or blocked connectivity to Microsoft enrollment endpoints.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How do I know if this is a user licensing problem or an Intune configuration problem?
First, confirm the affected user has a license that includes Intune, such as Microsoft 365 Business Premium, Enterprise Mobility + Security, or an Intune standalone license. If the license is valid, check the Microsoft Intune admin center and Entra admin center for MDM user scope, enrollment restrictions, and whether the user is allowed to enroll Windows devices.
Can old work or school accounts on the PC cause errors like 80192EE7 or 0x80180002?
Yes. Stale workplace joins, old Azure AD registrations, or a previous Intune enrollment can block a new enrollment attempt. On the device, go to Settings > Accounts > Access work or school, disconnect old work accounts, then check Entra ID and Intune for duplicate or obsolete device records before trying enrollment again.
What should I check if only one user or one device gets error -2145833241?
Check whether that user has reached the Entra ID or Intune device enrollment limit, and verify the device is not already joined or enrolled under another account. Run dsregcmd /status to review Azure AD join and workplace join state, then remove duplicate device objects from Entra ID or Intune if needed.
Can network settings cause Microsoft 365 device enrollment to fail?
Yes. VPNs, proxies, SSL inspection, restricted firewalls, incorrect DNS, and wrong system time can prevent Windows from reaching Microsoft enrollment services. Try enrollment from a trusted unrestricted network, temporarily disable VPN or proxy filtering where appropriate, confirm time sync is correct, and make sure Microsoft login, Entra ID, and Intune endpoints are reachable.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsBottom Line
“Device management could not be enabled” usually points to an enrollment blocker rather than a broken PC: missing Intune licensing, disabled MDM user scope, device limit issues, stale work account records, or network access to Microsoft enrollment endpoints. Start with the simple user-side fixes first, such as removing the work account, rebooting, checking connectivity, and trying enrollment again.
If the error persists, admins should verify Entra ID and Intune settings, confirm the user is licensed and allowed to enroll, review device limits and existing registrations, then clean up stale devices before re-enrolling. Once policy, licensing, and connectivity are corrected, the Microsoft 365 device enrollment should complete normally.

