Legacy Intune PC agent conflicts with automatic MDM enrollment

Likely causes

• This documented scenario applies to the legacy Intune PC agent. Validate the device state before changing tenant-wide enrollment scope.
• Enrollment scope, licensing, discovery, restriction, platform support, or device registration does not match the request.
• A previous workplace/MDM registration or enrollment limit is producing conflicting state.

Recommended fix

1. Confirm the legacy Intune PC software client is installed.
2. If the device should use modern MDM, uninstall the legacy Intune client before retrying.
3. Only disable the tenant's MDM automatic-enrollment scope if that is genuinely the intended management design.

Verify

1. Repeat the smallest operation that produced the failure.
2. Confirm a fresh success in the authoritative service log or admin center, not only in the client UI.
3. Record the new UTC timestamp and correlation/request ID so the retry can be distinguished from cached or older failures.

Escalate when

• The failure persists after the documented prerequisites and a new authentication/session attempt.
• Multiple users, apps, devices, or networks show the same error, suggesting tenant policy or service scope.
• You can provide the exact UTC time, tenant, application/resource, correlation or request ID, and sanitized logs.