Health service not up to date

Amy E. Case 0 Reputation points
2026-05-08T14:34:03.4166667+00:00

I am getting this and don't know what is wrong. We have been running for months with no issues.

The Microsoft Entra Connect Health Service is not receiving the latest data from the server(s) listed above. This may be due to connectivity issues or data collection issues on the server itself.

The latest data received by the Microsoft Entra Connect Health Service is older than 2 hours. The server specific Alert Details blade indicates the type of data that is not up to date. If a server has not uploaded any data for 30 consecutive days, it will be marked as disabled. See more details at Microsoft Entra Connect Health data retention policy.

Azure Health Data Services
Azure Health Data Services

An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.

0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-05-08T14:34:29.08+00:00

    The alert indicates that Microsoft Entra Connect Health hasn't received complete data from one or more on-premises Health agents in the last two hours. This is typically caused by connectivity or agent/service issues.

    To troubleshoot and resolve it, follow these steps:

    1. Verify the alert details
      • In the Azure portal, go to Microsoft Entra Connect Health.
      • Open the relevant service (Sync, AD DS, or AD FS) and select Alerts.
      • Open the Health service data isn't up to date alert and then select the Server Name.
      • Review Alert Details and Data Type Details to see which data types are missing and from which agent/service.
    2. Check agent versions and services
      • Ensure the latest Microsoft Entra Connect Health agents are installed on the affected servers (Sync, AD DS, AD FS as applicable).
      • On each affected server, open Services and confirm all relevant Microsoft Entra Connect Health services are Running (for example, for AD FS there should be two Health services; for Sync/AD DS see the table in the documentation).
    3. Validate prerequisites and connectivity
      • Confirm all requirements for Microsoft Entra Connect Health are met (firewall, TLS, permissions, etc.).
      • If an HTTP proxy is used, ensure it is configured for the Health agents as documented.
      • Run the connectivity test on the affected server:
             Test-MicrosoftEntraConnectHealthConnectivity -Role ADFS
        
        or use -Role Sync or -Role ADDS depending on the service. If this fails, fix the reported connectivity issues (network, firewall, proxy, TLS inspection).
    4. Check for registration and endpoint issues
      • If the agent cannot register or communicate:
        • Ensure outbound communication to required endpoints and ports is allowed.
        • Verify there is no TLS inspection replacing certificates on outbound traffic.
        • Ensure the account registering the agent has appropriate permissions (for example, Global Administrator or delegated via Azure RBAC).
    5. Consider data retention behavior
      • If a server has an active Health service data is not up to date error for more than 30 consecutive days, it will be disabled and no longer shown in the Connect Health portal.
      • To re-enable such a server, uninstall and then reinstall the Health agent on that server.
    6. Understand alert behavior
      • Warning: Health Service received only partial data types in the last two hours (no email notification).
      • Error: Health Service received no data types in the last two hours (email notification is sent).
      • Alerts resolve automatically when agents successfully send complete data again, or are suppressed if the error condition is not seen for 72 hours.

    If these steps are followed and connectivity plus agent health are restored, the alert should clear automatically once fresh data is uploaded.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator
    2026-05-08T15:15:11.2966667+00:00

    Hello Amy E. Case,

    This alert indicates that the Microsoft Entra Connect Health agent on the listed server is not uploading data to the service. This is usually due to the agent service being stopped, connectivity issues (proxy/firewall blocking outbound HTTPS on port 443), or an agent registration problem.

    Please check that the Microsoft Entra Connect Health Agent and Updater services are running on the server and restart them. Also verify outbound connectivity and TLS 1.2 is enabled.

    If the status does not update after restarting the services, reinstall or repair the Entra Connect Health agent, which typically resolves stale data upload issues.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.