Hi @Mobu ,
If you are receiving the "heartbeat skipped" alert, even if the issue is not present anymore, please check the application event viewer logs and try to understand if the heartbeat is really not present for the time that the alert was raised. This event should be present with a 663 ID and with a “Password hash synchronization manager is alive and running”.
If you don’t see these events present, you know that you have an issue and you need to troubleshoot this from a PHS perspective but if you have the 663 events and you still have the alert, this is likely caused by a bug on the Health agent.
The engineering team is aware of this and is deploying a fix for it. But if you want to solve this with the current version, please do the following:
1st – Run in PS:
- Get-process -name "Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup" | Stop-Process -force
- Restart-service AzureADConnectHealthSyncMonitor
2nd – The issue should now be fixed and the error cleaned from the Azure portal.
[https://learn.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-password-hash-synchronization#no-passwords-are-synchronized-manual-troubleshooting-steps
If you still face the issue after trying these steps, let me know and we can troubleshoot further.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions.