Registering devices with Intune for management and policy enforcement
If the device does not need organizational management, sign in again and choose No, this app only; if Intune management is required, the tenant administrator must validate the user’s license, enrollment scope, and applicable enrollment restrictions before retrying.
Error -2145833241 converts to 0x80192EE7. It indicates that the device-management enrollment stage failed, but the code alone does not establish whether licensing, policy, eligibility, or another enrollment condition caused it.
If only app access is required
For access to an individual app such as Outlook, Teams, or Edge without enrolling the PC:
- Go to Settings > Accounts > Access work or school.
- Select the work account, and then select Disconnect.
- Sign in to the app again.
- On the Entra account-registration prompt, select No, this app only.
This signs the user into that application without registering or activating management on the device. Selecting Yes allows Windows to continue into device registration and, when configured by the organization, device management. ^1^
If the PC must be managed by Intune
Send the error code and this checklist to the Intune administrator. The administrator needs the permissions required to view or change each setting.
- Verify licensing and enrollment eligibility
- Confirm the affected user has the required Intune license.
- For automatic Windows enrollment, Microsoft documents an Intune subscription and Microsoft Entra ID P1 or P2 as prerequisites. ^2^
- On the PC, open Settings > System > About and note the Windows edition. If this is an enrollment scenario that requires Pro or higher and the device runs Windows Home, upgrade the edition before retrying. Microsoft lists upgrading Windows Home to Pro or higher as a conditional enrollment resolution. ^3^
- Check automatic MDM enrollment
- In the Intune admin center, go to Devices > Device onboarding > Enrollment > Windows > Automatic Enrollment.
- Set MDM user scope to Some and include the affected user’s group, or set it to All.
- Retain the default MDM URLs.
- Set WIP user scope to None, or ensure the affected BYOD user is not included in both MDM and WIP scopes.
- Select Save. ^2^
- Check Windows and personal-device restrictions
- Go to Devices > Device onboarding > Enrollment > Device platform restriction > Windows restrictions.
- Open the restriction assigned to the user.
- Confirm MDM is Allow.
- If this is a personally owned PC, confirm Personally-owned is also Allow.
- Review assignments and restriction priority so the intended policy actually applies. ^4^
- Check the device limit
- Go to Devices > Enrollment, select the relevant platform tab, and open Device limit restriction.
- Compare the assigned limit with the user’s existing enrolled devices.
- Remove stale device records or assign a suitable higher limit if the user has reached it. ^5^
- If Microsoft Entra join is required
- In Microsoft Entra device settings, verify that the user is permitted to join devices.
- Restrict this permission to the required users or groups rather than broadening it unnecessarily.
After correcting the applicable setting, disconnect any incomplete work-account connection under Settings > Accounts > Access work or school, restart Windows, and enroll again.
Conditional hybrid-join check
If this is a domain-joined or Microsoft Entra hybrid-joined computer using Group Policy enrollment:
- Verify the policy Enable automatic MDM enrollment using default Microsoft Entra credentials is enabled and configured with User Credential.
- Confirm the policy applies to the computer.
- Run
dsregcmd /statusand inspect the join state. - Check Task Scheduler under Microsoft > Windows > EnterpriseMgmt for the enrollment task. ^6^
This branch does not apply to a normal personal-PC registration flow that is not domain or hybrid joined.
Diagnostics if configuration appears correct
An administrator can run Microsoft’s enrollment diagnostic:
- Open Microsoft 365 admin center > Show all > Support > Help & support.
- Enter Intune Windows enrollment.
- Supply the affected user when prompted, and select Run tests.
- Apply any reported correction, then rerun the test. ^7^
On the affected PC, collect a diagnostic package from an elevated Command Prompt:
mdmdiagnosticstool.exe -area "DeviceEnrollment;DeviceProvisioning;Autopilot" -zip "C:\Users\Public\Documents\MDMDiagReport.zip"
Also inspect Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. For automatic MDM enrollment specifically, event 75 indicates success and event 76 indicates failure; other enrollment methods should be investigated using the broader log and diagnostic package. ^8^ ^9^
If the diagnostic results and logs do not identify the failure, open a Microsoft support case and attach MDMDiagReport.zip, the enrollment timestamp, affected username, Windows edition/build, and enrollment method.
References
- Add Your Work or School Account to a Windows Device | Microsoft Support
- Set up automatic enrollment for Windows devices
- Windows user is not authorized to enroll
- Create device platform restrictions
- Create device limit restrictions in Intune
- Intune Autoenrollment not work for some Domain Joined Devices - Microsoft Q&A
- Troubleshooting device enrollment in Intune
- Diagnose MDM enrollment
- Collect MDM logs