Password Hash Synchronization heartbeat was skipped in last 120 minutes

Debbie C 40 Reputation points
2024-03-04T20:50:19.01+00:00

Keep receiving the following error:

Password Hash Synchronization heartbeat was skipped in last 120 minutes

Password Hash Synchronization has not connected with Microsoft Entra ID in the last 120 minutes. As a result passwords will not be synchronized with Microsoft Entra ID. Please refer to: Troubleshoot Password Has Synchronization.

I have referred to the troubleshoot menu - the diagnostics all returned that everything was running fine. I have tried restarting the service, and tried unticking password sync in the Azure AD Connect wizard and then going back and ticking it again and that seems to have worked for a few hours, but we are now receiving the message again. Any ideas on how to fix this?

Microsoft Entra
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,852 questions
{count} votes

14 answers

Sort by: Most helpful
  1. Debbie C 40 Reputation points
    2024-03-06T22:05:18.26+00:00

    I lodged a support ticket with the Microsoft Entra/Azure support team and received an answer from them around an hour ago to say that Microsoft was aware of the issue and they believe it is now resolved. They said that the problem was "Due to a recent rollout of a design change of Microsoft Entra Connect Health agent, the agents installed in customer premises started getting throttled by Service"

    Hopefully these alerts stop coming now. I haven't received any alerts for just over 12 hours now, so it is looking promising.

    3 people found this answer helpful.
    0 comments No comments

  2. Nathan Harwood 10 Reputation points
    2024-03-04T21:57:21.3666667+00:00

    Started happening for us too around 5 days ago but when I run the diagnostics everything looks fine.

    Always seems to resolves automatically after two hours later only to receive the alert again between 6 and 24hrs later.

    I think the agent did an auto update recently to 2.3.6.0 so I have a feeling it may be related to that.

    2 people found this answer helpful.
    0 comments No comments

  3. Stefan Rheeder 10 Reputation points
    2024-03-05T03:53:49.6833333+00:00

    Seeing the same issue. Fixes itself. Started about a week ago.

    2 people found this answer helpful.
    0 comments No comments

  4. TBTim 10 Reputation points
    2024-03-06T03:10:21.5866667+00:00

    Just adding to the thread, we're seeing this across multiple environments and all showing the same self-resolution within a 2 hour time frame.

    2 people found this answer helpful.
    0 comments No comments

  5. Matt H 10 Reputation points
    2024-03-04T21:00:17.66+00:00

    I'm seeing the same issue. Not for the first time, but its happening daily now across two separate environments. Have logged with Microsoft, but I suspect that this is a wider issue.

    1 person found this answer helpful.
    0 comments No comments