Authentication issues when running Entra Connect Health troubleshooter

Question

Trying to run an Entra Connect Health troubleshooter to resolve a duplicate attribute error. The objects both belong to the same user, one in on-prem AD and one in Entra. There is a troubleshooter to update the source anchor to point it to the right location, but when I run it, I get this error:

Additional information from the call to get a token: Extension: Microsoft_Azure_ADHybridHealth Resource: self Details: The extension 'Microsoft_Azure_ADHybridHealth' has not defined the resource access for resource 'self' in the extension's configuration, or in the portal's configuration. Please follow the instructions at https://aka.ms/portalfx/resourceaccess to add your new resource.

The account I'm running it with has Owner permissions to Entra Connect Health. The link they share seems to be for third-party extensions, not first party Microsoft extensions.

I'm sure I'm missing something obvious, but I'm fairly new to Azure and don't know where to look.

Answer 1

Hi @patrick healy

Thank you for reaching Microsoft Q&A Forum!

I Understand that you are unable to run the Entra Connect Health, and you are getting an error.
This might be issue with the connectivity could you please check the Outbound connectivity to Azure service endpoints.
please try to restart the Entra Connect Health agent and see if the issue is fixed.

In order to install the Connect Health for Sync Agent, you need to be a Global Administrator. To activate the agent, you need to reinstall the agent using a global administrator account.

check the Requirements of Microsoft Entra Connect Health download the latest version of Microsoft Entra Connect and install. make sure .NET 4.6.2 Framework is installed.

Hope this helps. Do let us know if you any further queries by responding in the comments section.

Thanks,

Akhilesh.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Hello @Patrick Healy,

I have received an update from my engineering team regarding this issue. They have developed a fix, which is scheduled to be released into production by the end of the second week of January 2025.

If you continue to experience the issue after the second week of January, please feel free to update us here, and I will proactively look into it.

If this information was helpful, kindly click "Accept Answer." This helps us and others in the community as well.

Thanks,
Raja Pothuraju.