Two symptoms, two paths
At fictional North Workshop, Leah is missing from Microsoft 365, while Malik exists in Entra but cannot sign in after a password change. Trace Leah’s object from AD. For Malik, confirm the target identity and sign-in method before suspecting password hash sync. If the account exists in Entra and only Outlook fails, check Exchange provisioning and licensing separately.
1. Confirm the server, version and scope
This guide covers Entra Connect Sync and its ADSync service; Cloud Sync uses a different agent. Check whether one account, one OU, one forest or the entire tenant is affected, and record the last success in UTC. Run the reads in Windows PowerShell on the Connect server with the required local permissions. Connect Health requires Entra ID P1 or P2; local history is useful without Health. Check installer prerequisites and supported releases: Microsoft requires version 2.6.84.0 or later and application-based authentication by April 7, 2027. Verify Windows Server, .NET, SQL and outbound connectivity for the selected version.
# Collect evidence only
Get-Service ADSync
Import-Module ADSync
Get-ADSyncScheduler | Select-Object SyncCycleEnabled,StagingModeEnabled,SchedulerSuspended,SyncCycleInProgress,NextSyncCycleStartTimeInUTC2. Missing user: trace the last visible point
With RSAT and an account allowed to read AD, confirm DN and UPN on a relevant DC. An excluded OU or an unreplicated change can explain a missing import. In Synchronization Service Manager, read Operations: AD import, synchronization, then Entra export. Find the DN in the AD connector space, check the metaverse link and follow the Entra connector space. Missing imports, metaverse filtering and export failures require different fixes. Staging prepares changes without exporting. If export succeeds, find the object in the correct tenant and check whether an unverified UPN suffix explains a different name.
# Collect evidence only
Get-ADUser -Identity 'lea.pilote' -Server 'dc01.atelier.example' -Properties proxyAddresses,pwdLastSet |
Select-Object DistinguishedName,ObjectGUID,UserPrincipalName,Enabled,proxyAddresses,pwdLastSet3. Export failure: establish ownership before correcting it
For a UPN or proxyAddresses conflict, compare on-premises and cloud objects, including recoverable deleted objects and other relevant recipient types. Confirm address ownership and source anchor mapping. Do not delete a user or change the Immutable ID simply to clear an error. Correct the value in its authoritative source, then confirm export and the expected Entra object ID. Reports and logs contain identifiers: retain excerpts in the restricted incident record.
4. Passwords: diagnose the PHS channel separately
An object delta cycle does not force password hash synchronization. Confirm the actual sign-in method: PHS, pass-through authentication (PTA) or federation. PHS may be enabled as a fallback without serving current sign-ins. On the active server, verify PHS for the tenant and connector; the troubleshooting wizard separates one-object from widespread failures. Application event 654 is an idle channel heartbeat, not proof that Malik’s password change succeeded. For a whole forest, check DC reachability, replication errors and the connector account’s delegated replication permissions. Do not grant it domain administrator rights. For one user, compare pwdLastSet on relevant DCs and confirm the object is already synchronized.
# Collect evidence only
Get-WinEvent -FilterHashtable @{LogName='Application'; Id=654; StartTime=(Get-Date).AddHours(-3)} -MaxEvents 50 |
Select-Object TimeCreated,ProviderName,Id,Message5. Changes: pilot, evidence and rollback
Export configuration and record the original value before any intervention. Correct an approved attribute for a pilot account and observe the next cycle; requesting a delta on the active server is an action that can export unrelated pending changes. For a filter or rule change, inspect pending exports and deletions in staging before cutover; keep only one active server and preserve accidental-deletion protection. Stop if scope or volume differs from the plan. Restore the original configuration and attribute value as appropriate; exported deletions require separate recovery. Do not try to restore an old password: use the approved reset process if needed.
6. Validate the object, then sign-in
For Leah, verify the expected Entra object and the affected Microsoft 365 service. For Malik, use a dedicated pilot account and a fresh browser session to validate an authorized password change. Compare time, authentication method and failure reason in Entra sign-in logs: MFA or Conditional Access denial does not prove a PHS failure. Record the cause, the restored stage and pilot results. A hybrid identity review can help when multiple forests or custom rules complicate diagnosis.