This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 74%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
We are running the free version of Microsoft Entra ID (f.k.a. Azure AD). We recently upgraded from Azure AD Connect version 2.1.1.0 to version 2.3.2.0. (now MS Entra Connect). When we were running version 2.1.1.0 it included MS Azure AD Connect Health agent for sync version 3.2.1823.12. During the upgrade, the installation of the MS Entra Connect Health agent failed. I'm assuming this is because the Health agent now requires at least a P1 license of MS Entra ID, which we do not have. Am I correct in this assumption, or am I missing something? Did MS really take away the Health agent from the free version? Do I have the option of reinstalling the Health agent version 3.2.1823.12 that was free?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Hi @Patty C
Yes you are right P1 license is required as mentioned in the table below. For more details you can refer the Following Microsoft article :
lists requirements for using Microsoft Entra Connect Health
Please don't forget to accept helpful answer
It is unfortunate that MS took away the Health agent! Do you know in which version of MS Entra Connect the Health agent was taken away? Do we have the option to use older version of the Health agent?
@Patty C •
By default the Microsoft Entra Connect Health agent for sync is installed automatically when you deploy Microsoft Entra Connect whatever the version.
If you don't have Microsoft Entra ID P1 or P2, you can't complete the configuration in the Microsoft Entra admin center. For more information, see the requirements.
Please don't forget to accept helpful answer
Before the upgrade, the following were listed under Programs & Features:
When the upgrade completed, I received the following message: Upgrade from Azure Active Directory Sync has finished successfully.
Installation failed for Microsoft Entra Connect Health Agent.
Programs & Feature now lists the following:
Notice there is no Health agent listed.
The following event is listed under Event Viewer:
Log Name: Application
Source: AzureADConnectHealthAgent Date: 1/26/2024 7:50:21 PM Event ID: 0 Task Category: None Level: Error Keywords: Classic User: N/A Computer: xxxxxxxxxx Description: Service cannot be started. Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Microsoft.Identity.Health.AgentV15.BootstrapClientAddOn.HealthAgentInstance", name = "(none)". Exception occurred while: Calling constructor Microsoft.Identity.Health.AgentV15.BootstrapClientAddOn.HeartbeatScheduler(Microsoft.Identity.Health.Agent.Common.Interfaces.IAadConnectHealthMonitorManager manager, Microsoft.Identity.Health.Agent.Monitors.Interfaces.IEnvironmentInfo envInfo, Microsoft.Identity.Health.Agent.Common.Utilities.IRegKeyFactory regKeyFactory, Microsoft.Identity.Health.Agent.Common.Utilities.IAgentIdentityProvider agentIdentityProvider, Microsoft.Identity.Health.AgentV15.BootstrapClientAddOn.HeartbeatClient.IAgentHeartbeatClient agentHeartbeatClient, Microsoft.Identity.Health.Agent.Common.Interfaces.IAgentVersionUtil agentVersionUtil, Microsoft.Identity.Health.Agent.Common.Logging.AadConnectHealthAgentFileComm fileComm). Exception is: InvalidOperationException - Missing valid 'TenantId' keyVa... I just want to know if all these behaviors are expected due to not having a P1 or P2 license or did I do something wrong?
You mentioned that not having a P1 or P2 license will not allow you to complete the configuration in the MS Entra Admin Center, which is on the cloud end, but these issues I'm experiencing are occurring in our on-premise Azure AD Connect server.
I ask because I did not experience any of these issues when I upgraded from Azure AD V1 to V2, and that was a more complex upgrade. Also, will these issues prevent the auto upgrade of Azure AD Connect in the future?
Hi @Patty C •
I ask because I did not experience any of these issues when I upgraded from Azure AD V1 to V2, and that was a more complex upgrade
It seems that the behavior of Health agent with new version has been changed when all ^prerequisites are not configured before . Sorry I don't have a tenant without licence to produce your issue.
In my opinion, this is a licensing problem, since the agent should be installed automatically with Entra Connect as indicated in the Microsoft articleand the error you shared with us :
Also, will these issues prevent the auto upgrade of Azure AD Connect in the future? The auto upgrade is another process the licence is not required as mentioned in Microsoft article:
Please don't forget to accept helpful answer
I appreciate your feedback. It is unfortunate that MS changed the licensing requirements for the Health agent, but if they are going to do that, the Health agent should not be automatically installed with MS Entra Connect. Those of us who use the free version of MS Entra ID should have a choice NOT to install a component that requires a license! I can't image we are the only company that now has to deal with the problem.