Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | MENROLL_E_DEVICE_MANAGEMENTSERVICE_FAILED (0x80180014) | Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin | -> Event ID 75 |
| Affected build range | Windows 11 23H2 | ||
| Registry key involved | HKLM:\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot | Registry Editor | -> Contains failure details |
| Relevant service/endpoint URL | https://enterpriseregistration.windows.net, https://portal.manage.microsoft.com | ||
| Log line signature | Event ID 75 - MDM enrollment failed with 0x80180014 | Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin |
Log Files to Check
C:\Windows\Provisioning\Autopilot\AutopilotDDSZTDFile.jsonC:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\MdmDiagnostics.log
What This Error Actually Means
The error codeMENROLL_E_DEVICE_MANAGEMENTSERVICE_FAILED (0x80180014) signifies a failure during the Microsoft Intune MDM enrollment process for devices enrolling via Windows Autopilot. Specifically, this error occurs when the device is unable to establish communication with the Microsoft Enrollment Service or if there's an issue with the enrollment policy assigned to the device. This can be due to network issues, misconfigured policies, or mismatches between the device and Intune settings.
Affected Versions and Scope
This error primarily affects devices running Windows 11 23H2 that are attempting to enroll via Windows Autopilot into Microsoft Intune. It is not limited to a specific build but rather occurs across all builds of Windows 11 23H2 where Autopilot enrollment is attempted. Devices on other versions or configurations that do not use Windows Autopilot for initial setup will not encounter this error.Where To Look First: Logs and Event IDs
To diagnose the root cause, start by examining the following logs and event IDs: - **Event Viewer**: Navigate toApplications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. Here, look for events with ID 75 (MDM enrollment failed) and 76 (enrollment completed). Event ID 75 will contain the exact error message indicating the failure of MDM enrollment.
- **Autopilot Diagnostic Logs**: Review C:\Windows\Provisioning\Autopilot\AutopilotDDSZTDFile.json for any issues during the provisioning phase. Additionally, check C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\MdmDiagnostics.log to identify specific errors or failures encountered during MDM enrollment.
- **Registry Key**: Inspect the registry key at HKLM:\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot. This key contains session failure details that can provide insights into why the Autopilot process failed.
Root Causes
Mismatched MDM Authority Configuration
One common cause is a mismatch between the device's expected MDM authority and what has been configured in Intune. Ensure that the MDM authority setting in your tenant administration matches the intended enrollment method for Autopilot devices.Network Connectivity Issues
Another frequent issue stems from network connectivity problems preventing the device from reaching necessary endpoints likehttps://enterpriseregistration.windows.net and https://portal.manage.microsoft.com. Verify that these URLs are accessible from the affected devices.
Incorrect Autopilot Profile Assignment
The error can also occur if the device's Autopilot profile is incorrectly assigned or missing. Ensure that the deployment profiles in Intune correctly target Entra security groups containing the device to be enrolled.Fix Procedure
- Verify MDM Authority Configuration: - Navigate to the Microsoft Intune admin center > Tenant administration > MDM authority. - Confirm that the MDM authority is set to Intune.
- Check Network Connectivity:
- Ensure the device can reach both
https://enterpriseregistration.windows.netandhttps://portal.manage.microsoft.com. - Validate Autopilot Profile Assignment: - In the Intune admin center, go to Devices > Enroll devices > Windows enrollment > Deployment profiles. - Confirm that the correct profile is assigned to an Entra security group containing the device.
- Reset Device and Retry Enrollment: - Select the problematic device in the Intune admin center. - Choose "Wipe" followed by confirming the Autopilot reset process. This step can potentially break enrolled devices, proceed with caution.
Warning: The Wipe and Reset action will remove all data from the device. Ensure backups are in place before proceeding.
Error Code Variants
| Error Code | Description | Distinguishing Features |
|---|---|---|
MENROLL_E_DEVICE_MANAGEMENTSERVICE_FAILED (0x80180014) |
MDM enrollment failed due to service communication issues. | Error occurs during the MDM join phase, typically related to network or policy mismatches. |
MENROLL_E_DEVICE_PROFILE_NOT_FOUND (0x80180024) |
MDM enrollment failed due to missing deployment profile. | Error occurs if the device's Autopilot profile is not correctly assigned or does not exist in Intune. |
Verification
To verify that the issue has been resolved: - Use the PowerShell cmdletGet-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" to check if the device appears in Intune after attempting enrollment.
- Confirm that the event log at Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin no longer contains Event ID 75 with error code MENROLL_E_DEVICE_MANAGEMENTSERVICE_FAILED (0x80180014).
Prevention
To prevent recurrence of this issue, ensure that: - The MDM authority is correctly configured in the Intune admin center. - Network policies allow devices to reach necessary endpoints likehttps://enterpriseregistration.windows.net and https://portal.manage.microsoft.com.
- Autopilot deployment profiles are accurately assigned to Entra security groups containing the intended devices.
TIP: Use the PowerShell cmdlet Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to quickly retrieve recent MDM enrollment events for analysis.
MENROLL_E_DEVICE_MANAGEMENTSERVICE_FAILED (0x80180014) during Windows Autopilot enrollment.