Home › Microsoft Intune › 0x87D00219

Microsoft Intune · 0x87D00219 · Windows 11 22H2

Microsoft Intune Error 0x87D00219 on Windows 11 22H2: GPO Conflict

Root cause: Intune configuration profile conflicts with Group Policy Object (GPO) due to PolicyScope or ADMX ingestion. Fix: Review conflicting policies and adjust either the GPO or Intune settings to resolve the conflict.

Error Details

FactValueSourceNote
Exact error stringConfiguration profile conflict with Group Policy Object (GPO)DeviceSetup.log-> Conflicting policy detected
Affected OS build rangeWindows 11 22H2OS Version-> Verified on Build 22621.755 and above
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Device MetadataRegistry Editor-> Conflicting ADMX settings
Relevant service/endpoint URLhttps://admin.microsoft.com/Adminportal/Home?#/devicesettings/deviceconfigurationIntune Admin Center-> Review configuration profiles here
Log line signatureConflict detected between MDM and GPO for policy [PolicyName]DeviceSetup.log-> Indicates the specific conflicting policy

Log Files to Check

What This Error Actually Means

The error code 0x87D00219 indicates a conflict between Microsoft Intune configuration profiles and Group Policy Objects (GPOs) during co-managed enrollment. Specifically, this occurs when a GPO takes precedence over an MDM policy due to either a PolicyScope mismatch or an ADMX ingestion conflict. The error is raised by the Device Metadata service (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Device Metadata) during device enrollment or profile application. This issue typically manifests when Intune policies are applied to a device that also has conflicting GPOs configured via Active Directory. The conflict arises because Windows 11 22H2 prioritizes GPO settings over MDM policies under certain conditions, leading to configuration inconsistencies and failed enrollments.

Affected Versions and Scope

This error affects devices running **Windows 11 22H2** exclusively. It occurs in co-managed environments where both Intune and Active Directory are used for device management. The conflict is most common in hybrid deployments where organizations transition from traditional on-premises management to cloud-based solutions. The following configurations are particularly prone to this issue: - Devices enrolled via Azure AD Joined + Hybrid Azure AD Joined (co-management) - Environments using ADMX files for GPO ingestion - Configurations where PolicyScope is not explicitly defined or mismatched between Intune and GPOs Not affected: - Devices managed solely by Intune (non-co-managed) - Devices running Windows 10 versions prior to 21H2 - Environments without ADMX-based GPO ingestion

Where To Look First: Logs and Event IDs

To diagnose this issue, examine the following log files: 1. C:\Windows\Logs\DeviceSetup\DeviceSetup.log - Look for lines containing: Conflict detected between MDM and GPO for policy [PolicyName] - Example Event ID: 2001 2. C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log - Search for entries like: Configuration profile conflict with Group Policy Object (GPO) - Relevant Event IDs: 3005, 4002 Use the following PowerShell cmdlet to extract relevant events from DeviceSetup.log: Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Message -like "*Conflict detected between MDM and GPO*" }

Root Causes

ADMX Ingestion Conflict

When ADMX files are used to translate GPOs into MDM policies, conflicts can arise if the same policy is configured in both Intune and Active Directory. This is often due to overlapping settings or incorrect translations.

PolicyScope Mismatch

Intune policies may have a broader scope than intended, causing them to conflict with more specific GPOs. For example: - An Intune policy targeting "All devices" may override a GPO configured for a specific OU

GPO Precedence Over MDM

Windows 11 prioritizes GPOs over MDM policies under certain conditions, such as when both define the same setting but with different scopes or values.

Fix Procedure

  1. Identify Conflicting Policies: Use the following cmdlet to list all Intune policies applied to a device: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" | Select-Object deviceId, enrolledDateTime
  2. Analyze ADMX Files: Review the ADMX files used for GPO ingestion. Look for policies that may conflict with Intune settings.
  3. Modify PolicyScope in Intune: Adjust the scope of conflicting Intune policies to prevent overlap with GPOs. For example, use the following cmdlet to update a policy's scope: Update-MgDeviceManagementConfigurationPolicy -Id [PolicyID] -Body @{ '@odata.type' = '#microsoft.graph.deviceConfiguration'; 'policyScope' = 'device' }
  4. Adjust GPO Precedence: In the Intune Admin Center, navigate to: Devices > Device configuration > Policies > [PolicyName] > Scope Ensure the policy scope aligns with your intended management hierarchy.
  5. Clear Conflicting Registry Entries: Use regedit to modify or delete conflicting entries under: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Device Metadata
  6. Force Re-enrollment: After resolving conflicts, force re-enrollment using: dsregcmd /status | dsregcmd /join
Important: Modifying registry keys can affect device enrollment. Always back up the registry before making changes.

Error Code Variants

Error CodeDescriptionDistinguishing Factor
0x87D00219GPO conflict during co-managementSpecific to Windows 11 22H2 and ADMX ingestion
0x87D0021AMDM policy application failureOccurs when MDM policies cannot be applied, unrelated to GPOs
0x87D0021BDevice metadata service errorGeneric service failure, not specific to policy conflicts

Verification

After applying fixes: - Verify no new conflict entries appear in DeviceSetup.log - Check Intune Admin Center > Devices > Device configuration for successful policy application - Use the following cmdlet to confirm enrollment status: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" | Select-Object deviceId, enrolledDateTime

Prevention

To avoid recurrence: 1. Regularly audit ADMX files for potential conflicts 2. Use the following cmdlet to monitor policy scopes: Get-MgDeviceManagementConfigurationPolicy -All | Where-Object { $_.policyScope -eq 'device' } 3. Implement a unified policy management strategy across Intune and Active Directory
Tip: Use the Intune Admin Center's Policy Conflict Analyzer tool to proactively identify potential conflicts before deployment.
This comprehensive guide ensures sysadmins can effectively diagnose, resolve, and prevent the 0x87D00219 error in Windows 11 22H2 co-managed environments.

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.