Microsoft Entra Connect Health frequently asked questions

To switch between different Microsoft Entra tenants, select the currently signed-in User Name on the upper-right corner, and then choose the appropriate account. If the account isn't listed here, select Sign out. Next, use the Global Administrator credentials of the directory that has Microsoft Entra ID P1 or P2 (P1 or P2) enabled to sign in.

The following table lists the roles and supported operating system versions.

Windows Server Core installations aren't supported.

The features provided by the service may differ based on the role and the operating system. All of the features may not be available, for all operating system versions. See the feature descriptions for details.

• The first Connect Health Agent requires at least one Microsoft Entra P1 or P2 license.
• Each additional registered agent requires 25 more Microsoft Entra P1 or P2 licenses.
• Agent count is equivalent to the total number of agents that are registered across all monitored roles (AD FS, Microsoft Entra Connect, and/or AD DS).
• Microsoft Entra Connect Health licensing doesn't require you to assign the license to specific users. You only need to have the requisite number of valid licenses.

Licensing information is also found on the Microsoft Entra pricing page.

Example:

Yes, all agents will get updated automatically when there's a new version of the agent.

No, automatic upgrade is mandatory. If you don't want the agent to be upgraded when a new version is released, you should uninstall the agent.

The impact of installing the Microsoft Entra Connect Health Agent, AD FS, web application proxy servers, Microsoft Entra Connect (sync) servers, domain controllers is minimal with respect to the CPU, memory consumption, network bandwidth, and storage.

The following numbers are an approximation:

• CPU consumption: ~1-5% increase.
• Memory consumption: Up to 10 % of the total system memory.

• Local buffer storage for Microsoft Entra Connect Health Agents: ~20 MB.
• For AD FS servers, we recommend that you provision a disk space of 1,024 MB (1 GB) for the AD FS audit channel for Microsoft Entra Connect Health Agents to process all the audit data before it is overwritten.

No. The installation of the agents will not require you to reboot the server. However, installation of some prerequisite steps might require a reboot of the server.

For example, installation of .NET 4.6.2 Framework may require a server reboot.

Yes. For ongoing operations, you can configure the Health Agent to use an HTTP proxy to forward outbound HTTP requests. Read more about configuring HTTP Proxy for Health Agents.

If you need to configure a proxy during agent registration, you might need to modify your Internet Explorer Proxy settings beforehand.

1. Open Internet Explorer > Settings > Internet Options > Connections > LAN Settings.
2. Select Use a Proxy Server for your LAN.
3. Select Advanced if you have different proxy ports for HTTP and HTTPS/Secure.

No. A mechanism to specify an arbitrary user name and password for Basic authentication isn't currently supported.

See the requirements section for the list of firewall ports and other connectivity requirements.

When you remove an agent from a server, the server isn't automatically removed from the Microsoft Entra Connect Health portal. If you manually remove an agent from a server or remove the server itself, you need to manually delete the server entry from the Microsoft Entra Connect Health portal. To delete monitored servers from Microsoft Entra Connect Health, you must have either Microsoft Entra Global Administrator account permissions or the Contributor role in Azure role-based access control.

You might reimage a server or create a new server with the same details (such as machine name). If you did not remove the already registered server from the Microsoft Entra Connect Health portal, and you installed the agent on the new server, you might see two entries with the same name.

In this case, manually delete the entry that belongs to the older server. The data for this server should be out of date.

No. Installation on Server Core isn't supported.

The health agent can fail to register due to the following possible reasons:

• The agent cannot communicate with the required endpoints because a firewall is blocking traffic. This issue is common on web application proxy servers. Make sure that you have allowed outbound communication to the required endpoints and ports. See the requirements section for details.
• Outbound communication is subjected to a TLS inspection by the network layer. This causes the certificate that the agent uses to be replaced by the inspection server/entity, and the steps to complete the agent registration fail.
• The user doesn't have access to perform the registration of the agent. Global admins have access by default. You can use Azure role-based access control (Azure RBAC) to delegate access to other users.

Microsoft Entra Connect Health generates the alert when it doesn't receive all the data points from the server in the last two hours. Read more.

No, auditing doesn't need to be enabled on the web application proxy servers.

Microsoft Entra Connect Health alerts get resolved on a success condition. Microsoft Entra Connect Health Agents detect and report the success conditions to the service periodically. For a few alerts, the suppression is time-based. In other words, if the same error condition isn't observed within 72 hours from alert generation, the alert is automatically resolved.

Microsoft Entra Connect Health for AD FS generates this alert when the Health Agent installed on an AD FS server fails to obtain a token as part of a synthetic transaction initiated by the Health Agent. The Health agent uses the local system context and attempts to get a token for a self relying party. This behavior is a catch-all test to ensure that AD FS is in a state of issuing tokens.

Most often this test fails because the Health Agent is unable to resolve the AD FS farm name. This state can happen if the AD FS servers are behind a network load balancers and the request gets initiated from a node that's behind the load balancer (as opposed to a regular client that is in front of the load balancer). This issue can be fixed by updating the "hosts" file located under "C:\Windows\System32\drivers\etc" to include the IP address of the AD FS server or a loopback IP address (127.0.0.1) for the AD FS farm name (such as sts.contoso.com). Adding the host file will short-circuit the network call, thus allowing the Health Agent to get the token.

Microsoft Entra Connect Health service scanned all the machines it monitors to ensure the required patches were installed. The email was sent to the tenant administrators if at least one machine did not have the critical patches. The following logic was used to make this determination.

1. Find all the hotfixes installed on the machine.
2. Check if at least one of the HotFixes from the defined list is present.
3. If Yes, the machine is protected. If Not, the machine is at risk for the attack.

You can use the following PowerShell script to perform this check manually. It implements the above logic.

Function CheckForMS17-010 ()
{
    $hotfixes = "KB3205409", "KB3210720", "KB3210721", "KB3212646", "KB3213986", "KB4012212", "KB4012213", "KB4012214", "KB4012215", "KB4012216", "KB4012217", "KB4012218", "KB4012220", "KB4012598", "KB4012606", "KB4013198", "KB4013389", "KB4013429", "KB4015217", "KB4015438", "KB4015546", "KB4015547", "KB4015548", "KB4015549", "KB4015550", "KB4015551", "KB4015552", "KB4015553", "KB4015554", "KB4016635", "KB4019213", "KB4019214", "KB4019215", "KB4019216", "KB4019263", "KB4019264", "KB4019472", "KB4015221", "KB4019474", "KB4015219", "KB4019473"

    #checks the computer it's run on if any of the listed hotfixes are present
    $hotfix = Get-HotFix -ComputerName $env:computername | Where-Object {$hotfixes -contains $_.HotfixID} | Select-Object -property "HotFixID"

    #confirms whether hotfix is found or not
    if (Get-HotFix | Where-Object {$hotfixes -contains $_.HotfixID})
    {
        "Found HotFix: " + $hotfix.HotFixID
    } else {
        "Didn't Find HotFix"
    }
}

CheckForMS17-010

Get-MsolDirSyncProvisioningError will only return DirSync provisioning errors. The Connect Health portal also shows other sync error types such as export errors. Read more about Microsoft Entra Connect Sync errors.

Please use the PowerShell cmdlet Get-AdfsProperties -AuditLevel to ensure audit logs aren't in disabled state. Read more about AD FS audit logs. Notice if there are advanced audit settings pushed to the AD FS server, any changes with auditpol.exe will be overwritten (event if Application Generated isn't configured). In this case, set the local security policy to log Application Generated failures and success.

The agent certification will be automatically renewed 6 months before its expiration date. If it isn't renewed, ensure the network connection of the agent is stable. Restart the agent services or update to the latest version may also solve the issue.

Related links

• Microsoft Entra Connect Health
• Microsoft Entra Connect Health Agent installation
• Microsoft Entra Connect Health operations
• Using Microsoft Entra Connect Health with AD FS
• Using Microsoft Entra Connect Health for sync
• Using Microsoft Entra Connect Health with AD DS
• Microsoft Entra Connect Health version history