Skip to main content
AdminSignal
Compliance & Syncdecimal -2147012710

Fix Intune Error 0x80072F9A: The manual sync could not start. If the TPM was reset, the device lost its Entra identity and must be re-enrolled.

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: Microsoft-Windows-User Device Registration%4Admin.evtx

Root causes

  • The TPM was reset to factory settings, which removed the device identity stored in it.
  • The device record was deleted in Intune or Entra ID while the device still believed it was enrolled.
  • A broken Entra registration after a hardware or motherboard change.

Step-by-step remediation

  1. On the device run dsregcmd /status and check AzureAdJoined, and for the MDM section confirm the MDM URLs are present.
  2. Check Settings > Accounts > Access work or school and look for the work account and its Info > Sync result.
  3. Open the DeviceManagement-Enterprise-Diagnostics-Provider Admin log for the enrollment or sync error that follows the attempt.
  4. If the TPM was cleared or the identity is lost, re-enroll the device: remove the work account, delete stale device records, then enroll again.
  5. After re-enrollment, sync and confirm the device reports compliance within the next check-in.

For the full diagnosis around this error, read Intune device not syncing.

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

Related Error Codes in This Category

Other Compliance & Sync errors with their own runbooks.

Search all 21 error codes