DMEDP Event 813

Likely causes

• Windows recorded an MDM PolicyManager operation for an integer setting. The policy name, area, scope, enrollment identifier, integer value, and result provide the useful evidence.
• The decisive details are usually in the event payload and adjacent DMEDP events, not the event ID by itself.
• Assignment, enrollment, scope, CSP applicability, and service response must be correlated at the same UTC timestamp.

Recommended fix

1. Read the policy name, area, integer value, scope, and result in Event Details.
2. Match the policy name to the Intune configuration profile.
3. Check CSP applicability for Windows edition, version, and scope.

Verify

1. Trigger a manual sync or repeat the original enrollment/policy operation.
2. Confirm a new event shows success or a different actionable result.
3. Verify the device state in Intune or the target MDM service after the client reports success.

Escalate when

• The same event repeats after the configuration and prerequisites are corrected.
• The server reports success but the Windows event stream shows a persistent failure, or vice versa.
• You have exported the event payload, adjacent events, MDM diagnostic report, device build, and UTC timeline.