Password hash synchronization
Reviewed 2026-11-10
An Entra Connect option that extends directory synchronization so users sign in to Entra ID and Microsoft 365 with their on-premises Active Directory password. One of the options when moving Microsoft 365 off Okta. Keep identity, access policy and resource permission separate. Check the source before choosing a control for your applications.
How it works
An Entra Connect option that extends directory synchronization so users sign in to Entra ID and Microsoft 365 with their on-premises Active Directory password. One of the options when moving Microsoft 365 off Okta.
Identify the actor, the resource and the decision this term describes. Record which system makes that decision and which system enforces it.
A sign-in event, a policy decision and an application permission are not interchangeable. Test the relevant boundary rather than relying on a product label.
What Okta and Entra ID call it
An Entra Connect option that extends directory synchronization so users sign in to Entra ID and Microsoft 365 with their on-premises Active Directory password. One of the options when moving Microsoft 365 off Okta.
Use the linked comparison to locate the relevant product scope. Do not infer a vendor capability from a similar name alone.
Example
Consider an application access review as an illustrative exercise, not a customer story. Identify the person or service involved, the resource requested and the evidence needed.
Locate where password hash synchronization affects that decision. Ask what would change if the identity, device or permission changed.
Write down the expected result before testing. Keep the observation separate from a vendor's description of the feature.