Skip to main content

Azure AD Connect Health: Latest Data is not Available in Azure Portal

I recently had to create a new Azure AD Connect server, and found that it was not able to report health status in the Azure Portal. After some troubleshooting/research, I was able to get the health status report working by registering the health agent on the server with Azure AD Health Services. Doing this involves running one PowerShell cmdlet on your AD Connect server and providing global administrator credentials.

First, let’s test the status of the agent communication:

If you do not receive any errors, that means the Azure AD Connect Health agent on your server is able to successfully communicate with the cloud service. Now, let’s register the agent:

You will be prompted for credentials. The credentials you provide need to be a global administrator account in your Azure AD tenant.

You should receive some output stating that the registration is successful (or it failed).

Now, just go back to the Azure Portal and refresh the page. The message stating that the “latest data is not available” should be gone.