Hello Parthasarathi Panda
Thanks for contacting MS Q&A. I will be able to help you with resolving your issues.
The key thing to understand is that “Health service data is not up to date” is a data‐freshness alert raised by the Connect Health agent, not an object-level sync error. That’s why:
It doesn’t show up under the Sync errors blade. The Sync errors page only surfaces object-level failures (duplicate attributes, validation failures, federated domain changes, etc.) in the synchronization engine itself
Docs - https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-health-sync
The “Health service data isn’t up to date” alert has two severities: Warning: Some data types haven’t arrived in the last two hours—no e-mail is sent. Error: No data has arrived in the last two hours: This does generate an email to your configured recipients.
You saw the Warning state, which, by design, does not trigger the built-in notification e-mail.
Docs - https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-health-data-freshness
To receive the alerts: • You’ll need to build your own Azure Monitor alert on the Connect Health metric (for example, on “SyncDataFreshness” or the heartbeat metric) and point it at Action Groups of your choice or If you only care when the service is completely stale, leave the built-in notifications on, and you’ll get an e-mail when it escalates to Error.
That should explain why you didn’t see it under Sync Errors and why the initial warning didn’t generate mail.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Siri