Skip to main content
Compliance & Syncdecimal -2016281112

Fix Intune Error 0x87D1FDE8: Intune sent a setting and the response did not match what it expected (Remediation failed). Often cosmetic, but a real failure if the setting is not applied.

Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.

Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx

Folder: C:\Windows\System32\winevt\Logs\

Also check: IntuneManagementExtension.log

Root causes

  • A custom OMA-URI setting where the device returns formatted XML that differs from the XML in the policy, so Intune reads the mismatch as a failure.
  • A known issue with a specific policy type where the setting is applied but reported as errored until the next check-in.
  • The setting genuinely failed to apply because the CSP rejected the value or the OS does not support it.

Step-by-step remediation

  1. Open the profile in Intune and find the setting that reports Error. Note the device and the time of the last check-in.
  2. Sync the device and see whether the error clears. A known reporting issue goes away at the next check-in.
  3. On the device open the DeviceManagement-Enterprise-Diagnostics-Provider Admin log and look for the CSP result for that setting.
  4. Check the setting is actually in effect (registry key, CSP value or behavior). If it is, the report is cosmetic.
  5. If the setting is not applied, correct the value or data type. For custom OMA-URI VPN profiles, use the built-in VPN profile type if one exists.

For the full diagnosis around this error, read Intune Compliance Policy Not Evaluating: End-to-End Troubleshooting Checklist.

Tighten the rollout around it

Enrollment and compliance errors usually trace back to rollout design and device permissions. See how the endpoint privilege management tools compare, and plan the next ring with a tested runbook.

Compare Intune endpoint privilege management tools

Other Compliance & Sync errors with their own runbooks.

Search all 21 error codes