Home › Microsoft Intune › 0x87D11388

Microsoft Intune · 0x87D11388 · Windows 11 23H2

Microsoft Intune Error 0x87D11388 Windows 11 23H2 MDM Enrollment Failure

MDM enrollment failed due to authority conflict or misconfiguration. Fix by verifying tenant settings and resolving conflicts.

Error Details

FactValueSourceNote
Exact error string0x87D11388 - MDM enrollment failed — MDM authority conflict or authority not configured in tenantWindows Event Log, Intune Management Portal-> Indicates a critical configuration issue
Affected OS build rangeWindows 11 23H2Microsoft Documentation-> Specific to this version of Windows
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\ClientWindows Registry Editor-> Contains Intune client configuration details
Relevant service/endpoint URLhttps://manage.microsoft.comIntune Management Portal-> Primary endpoint for MDM enrollment
Log line signature[MDM] Enrollment failed with error code 0x87D11388Windows Event Log (System)-> Identifies the specific failure in logs

Log Files to Check

What This Error Actually Means

The error code 0x87D11388 is a hexadecimal representation of a Windows system error that occurs during Microsoft Device Management (MDM) enrollment. Decoding the hex value, 0x87D11388 corresponds to a specific failure in the MDM enrollment workflow, typically indicating either an MDM authority conflict or an unconfigured MDM authority in the tenant. This error is raised by the Intune Management Extension (IntuneManagementExtension) service, which acts as the bridge between the Windows device and Microsoft Intune. The root cause often lies in misalignment between the device's expected MDM authority (e.g., Intune) and the tenant's configuration in Microsoft Entra ID (formerly Azure AD). The error is logged by the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider event source, which tracks enrollment and policy application failures.

Affected Versions and Scope

This error is explicitly tied to Windows 11 23H2 (OS build 22000.2189 or later). It does not affect earlier Windows 11 builds (e.g., 21H2 or 22H2) or Windows 10 devices unless they are manually configured with conflicting MDM policies. The scope is limited to tenants where the MDM authority is either not configured in Microsoft Entra ID or where a conflicting MDM provider (e.g., a third-party MDM or a previous enrollment) is already registered. Devices enrolled via Autopilot, hybrid Azure AD join, or co-management are particularly susceptible if the MDM authority is not explicitly set to Intune. Conversely, tenants using Intune as the sole MDM provider with no legacy configurations are unlikely to encounter this error.

Where To Look First: Logs and Event IDs

The primary log files to investigate are: - C:\Windows\System32\winevt\Logs\System.evtx - C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log In the System.evtx log, search for the exact log line: [MDM] Enrollment failed with error code 0x87D11388. This line is typically associated with Event IDs 60060 (enrollment failure) and 60061 (MDM policy application error). In the IntuneManagementExtension.log, look for entries containing Enrollment failed due to MDM authority conflict or MDM authority not configured in tenant. Use PowerShell to extract relevant logs: Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 Get-Content -Path "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log" | Select-String "0x87D11388"

Root Causes

1. MDM Authority Not Configured in Tenant

The tenant lacks an assigned MDM authority in Microsoft Entra ID. This is common in new tenants or those transitioning from on-premises MDM solutions. To verify, navigate to Entra admin center > Properties > MDM authority and check if it is set to Microsoft Intune.

2. MDM Authority Conflict

A device is already enrolled under a different MDM provider (e.g., SCCM, third-party MDM). This conflict prevents Intune from claiming authority. Use the following cmdlet to identify devices with conflicting enrollment types: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"

3. Registry Misconfiguration

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\Client contains incorrect or outdated MDM enrollment settings. Specifically, the EnrollmentMode or MDMAuthority values may be misconfigured. Use reg query HKLM\SOFTWARE\Microsoft\Intune\Client /v EnrollmentMode to inspect these values.

Fix Procedure

  1. Set MDM Authority in Tenant
    Navigate to Intune admin center > Devices > Enrollment > MDM authority. Set the authority to Microsoft Intune. This step is critical and may
    break existing devices enrolled under a different MDM provider
    .
  2. Remove Conflicting MDM Configurations
    Use PowerShell to remove existing MDM enrollment: Invoke-MgGraphRequest -Method DELETE -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/{deviceID}/unenroll"
  3. Update Registry Settings
    Modify the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\Client to set EnrollmentMode to MDM and MDMAuthority to Intune. Example: Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Intune\Client" -Name "EnrollmentMode" -Value "MDM"
  4. Deploy OMA-URI Policy
    Create a custom device configuration profile in Intune with the OMA-URI: ./Device/Vendor/MSFT/Enrollment/MDM and set the value to Intune.

Error Code Variants

Error CodeDescriptionDistinguishing Factor
0x87D11388MDM authority conflict or unconfiguredOccurs during enrollment initialization
0x87D11389MDM certificate validation failureLogs reference certificate chain errors
0x87D1138AMDM policy download timeoutAppears after enrollment succeeds but policy sync fails

Verification

After applying fixes, verify success by checking the System.evtx log for Event ID 60059 (enrollment success) and confirming the absence of 0x87D11388 in IntuneManagementExtension.log. In the Intune admin center > Devices > All devices, the device should show an Enrollment status of Enrolled with MDM authority: Intune. Use dsregcmd /status to confirm the MDM field displays Intune.

Prevention

To prevent recurrence, enforce a baseline device configuration policy in Intune that sets the MDM authority via OMA-URI and blocks manual enrollment. Additionally, configure Entra admin center > Properties > MDM authority to Microsoft Intune and enable device enrollment restrictions under Intune admin center > Devices > Enrollment > Windows enrollment. A
non-obvious shortcut
is to use PowerShell to audit enrollment modes across devices: Get-AutopilotDevice | Where-Object { $_.EnrollmentMode -ne "MDM" }

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.