Skip to content
StrikeOps

Password Hash Sync Disabled in a Hybrid Tenant

LowTypical severity Cloud and Microsoft 365

01Description

The tenant synchronized users from on-premises Active Directory with Microsoft Entra Connect, but password hash synchronization was not enabled. Users authenticated through federation or pass-through authentication only.

02Impact

Microsoft's leaked credentials detection compares hashes of credentials found in breach dumps and criminal forums with synchronized password hashes, so without password hash sync the organization does not learn when users' passwords appear in leaks. Without it, the tenant also has no fallback authentication method if the on-premises federation or pass-through agents fail, which can turn an on-premises outage or ransomware incident into a full Microsoft 365 outage.

03Severity

Typically

Low

Typically Low. Low by default. Raise to Medium where the organization relies on federation or pass-through authentication with no cloud fallback, or where leaked credential detection is a stated control.

04How to verify

  1. 1In the Entra admin center, open Identity > Hybrid management > Microsoft Entra Connect > Connect Sync and check the status of Password Hash Sync.
  2. 2Review the Microsoft Entra Connect configuration on the sync server to confirm the selected user sign-in method.
  3. 3Check whether any leaked credentials risk detections have ever been raised in Identity Protection for synchronized users.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Enable password hash synchronization in Microsoft Entra Connect, even where federation or pass-through authentication remains the primary sign-in method.
  2. 2Document the decision and the process to switch sign-in methods during an on-premises outage.
  3. 3Configure risk-based Conditional Access to act on leaked credentials detections where the tenant has Entra ID P2.
  4. 4Consider Microsoft Entra Password Protection to block known weak and banned passwords in on-premises Active Directory.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo