About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A user changes their password at their Windows desktop. Hours later Outlook on the web and Teams still accept only the old one. Or a new starter is created in Active Directory and cannot sign in to Microsoft 365 at all.
If your Microsoft 365 sign-in uses password hash synchronisation through Microsoft Entra Connect Sync, the password is supposed to arrive within minutes. Microsoft says the process runs every two minutes and cannot be changed (Microsoft Learn, Implement password hash synchronization). If it has not arrived, something specific has stopped it.
What you see
- An on-premises password change does not work in Microsoft 365, and the old password still does.
- A new user gets "Your account or password is incorrect".
- On the Entra Connect server, the Application log (source "Directory Synchronization") shows events 611, 652 or 655, which Microsoft lists as signs of a connectivity problem, and names the affected forest (Microsoft Learn, Troubleshoot password hash synchronization).
- Event 654 (the heartbeat, logged every 30 minutes when nothing is pending) is missing.
The first question is whether it is every user or one user. Microsoft's troubleshooting splits the same way.
Why it happens
When no passwords sync, Microsoft's checks point to:
- Password hash sync is not enabled in the tenant, or on the Active Directory connector.
- The Entra Connect server is in staging mode. A staging server does not sync any passwords.
- The AD DS connector account has the wrong username or password, or lacks the two rights it needs at the root of every domain: Replicate Directory Changes and Replicate Directory Changes All. Express installs set these; custom installs have to be set by hand.
- The Entra Connect server cannot reach the domain controllers, or cannot reach Microsoft Entra ID.
- The server is locked down to FIPS mode, which disables the MD5 function password hash sync relies on for its local exchange with domain controllers (Microsoft Learn, Implement password hash synchronization).
When one user does not sync:
- "User must change password at next logon" is ticked. Without the temporary-password feature, that password is not synced.
- The user is not in sync scope (an OU or attribute filter), or has not yet been exported to Entra ID.
- No sync rule with password sync enabled applies to the object.
How to prove the cause
Work on the Entra Connect server, in PowerShell opened with Run as administrator. Microsoft's steps start with Set-ExecutionPolicy RemoteSigned; check your organisation's policy before changing the execution policy.
1. Use the built-in troubleshooter (version 1.1.614.0 or later). Start the Entra Connect wizard, go to Additional Tasks > Troubleshoot > Launch, then Troubleshoot password hash synchronization, and pick either "does not work at all" or "isn't synchronized for a specific user account".
For all users, it checks: the feature is enabled in the tenant, the server is not in staging mode, each connector has password sync enabled, heartbeat events in the last three hours, each domain is reachable, and the connector account's name, password and rights.
For one user, it follows the object through the Active Directory connector space, the metaverse and the Entra connector space, checks the sync rules, and shows the result of the last password sync attempt.
2. Or use the diagnostic cmdlet (version 1.1.524.0 or later):
Import-Module ADSyncDiagnostics
Invoke-ADSyncDiagnostics -PasswordSync
For one user:
Invoke-ADSyncDiagnostics -PasswordSync -ADConnectorName "<AD connector name>" -DistinguishedName "<user DN>"
3. Read the object's password sync log by hand. In Synchronization Service Manager, open Connectors, select the Active Directory connector, Search Connector Space, search by the user's DN, open Properties, then Log. Microsoft's status values include:
| Status | Meaning |
|---|---|
| Success | Password synced |
| FilteredByTarget | User must change password at next logon; not synced |
| NoTargetConnection | No object in the metaverse or the Entra connector space |
| SourceConnectorNotPresent | Not found in the on-premises connector space |
| TargetNotExportedToDirectory | Not yet exported to Entra ID |
An empty log means Entra Connect cannot read the password hash from Active Directory; Microsoft sends you back to the connectivity and rights checks. Results are kept for seven days by default.
4. Check the connector account's rights. In Synchronization Service Manager, open the Active Directory connector's Properties > Connect to Active Directory Forest to see the account. Then confirm it has Replicate Directory Changes and Replicate Directory Changes All at the root of every domain in the forest.
The fix
Fix what the check found:
- Staging mode: password sync only runs on the active server. Confirm which server should be active before changing anything.
- Feature or channel not enabled: Microsoft's manual step is to run the wizard, choose Customize synchronization options, untick password sync, finish, then run it again and tick it back on.
- Connector account: correct the password, or grant the two replication rights at each domain root.
- Domain controllers unreachable: in Synchronization Service Manager, Configure Directory Partitions, tick Only use preferred domain controllers and list ones Entra Connect can reach. Restart the ADSync service to apply it. The same list is used for import and export.
- One user with "must change password at next logon": ask the user to sign in and change the password on-premises. To sync temporary passwords instead, Entra Connect 2.0.3.0 or later with the ForcePasswordChangeOnLogon feature is required. Microsoft says to use that feature only when self-service password reset and password writeback are on.
- User out of scope or not exported: fix the filtering rules, then run Apply and verify changes so the user appears in Entra Connect.
- FIPS lockdown: Microsoft documents a change to
miiserver.exe.configto allow MD5 for this service. Microsoft also warns that editing that file can cause sync failures after upgrading to versions 2.5.190.0 and 2.6.1.0, so read its known-issue note first.
If nothing else is found and there is still no heartbeat, Microsoft gives a script to trigger a full sync of all passwords, and says to run it only once; if it is needed again, something else is wrong.
How to confirm the fix
- Event 654 appears again in the Application log at least every 30 minutes, or
Invoke-ADSyncDiagnostics -PasswordSyncreports no errors. - The user's password sync Log shows Success with a recent time.
- The user signs in to Microsoft 365 with the new password. An existing session is not affected by the change; Microsoft notes the new password is needed the next time the service asks for sign-in.
What to watch afterwards
- Events 611, 652, 655 on the Entra Connect server. Microsoft also suggests making the Application log larger so password sync events are not overwritten.
- Connector account changes. Resetting its password or tidying its group memberships can stop password sync for a whole forest.
- New domain controllers if you use a preferred list.
- Account expiry. Microsoft notes
accountExpiresis not synced, so an expired Active Directory account stays active in Entra ID unless it is also disabled.
Read next
Related articles you may want next.
- TroubleshootingEntra Connect Sync Errors: Duplicate Attributes, Soft and Hard Match ConflictsClassify Entra Connect export errors (AttributeValueMustBeUnique, InvalidSoftMatch, InvalidHardMatch, LargeObject), fix the source object on-premises and verify on the next cycle.Read article
- Backup & RecoveryHybrid identity during recovery: cloud sign-in and on-premises applicationsHow password hash, pass-through and federation change which directory must be up before users can sign in during a recovery.Read article
- CloudEntra ID Conditional Access: tenant lockout, break-glass accounts and how to test policy safelyHow Conditional Access locks administrators out, how to build emergency accounts that work under mandatory MFA, and a safe order for testing policy.Read article
Risks and limits
- The full password sync script is a recovery step, not routine maintenance. Microsoft says to contact Microsoft support if it has to be repeated.
- By default synced users' cloud passwords are set never to expire. Turning on Microsoft's cloud password policy for synced users changes that, and a full password sync then clears custom password policies that had to be set by hand.
- This article covers password hash synchronisation only. Pass-through authentication and federation sign in differently.
Sources
- Microsoft Learn, "Troubleshoot password hash synchronization with Microsoft Entra Connect Sync", last updated 18 July 2025: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/tshoot-connect-password-hash-synchronization
- Microsoft Learn, "Implement password hash synchronization with Microsoft Entra Connect Sync", last updated 3 December 2025: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-password-hash-synchronization
Next step
The Entra Connect server records each password sync step in its own logs, so the cause can be read rather than guessed. NetLeverage has looked after business servers since 2002. If passwords are not reaching Microsoft 365, talk to us through managed support with the troubleshooter's output and any 611, 652 or 655 events.
This article was originally published on .