Test-AzureADConnectHealthConnectivity is not recognized

Andreas 1,301 Reputation points
2024-03-06T07:40:19.1566667+00:00

Hi,

We have a hybrid setup with Entra ID connect installed on our Windows Server 2022 domain controller. The sync service is running fine, and i cannot see any issues. Today we got a email notifying us about Health service data is not up to date.

We have check that the services are running, we have rebooted the server.

User's image

I was going to try the Test-AzureADConnectHealthConnectivity, but this command I cannot seem to find. I have imported AzureAD, but still no command. Is there another module I need to import ?

/R

Andreas

Microsoft Entra
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,759 questions
{count} votes

Accepted answer
  1. Timmerman, Michiel 140 Reputation points
    2024-03-06T08:52:15.2666667+00:00

    Seems to be a more global issue as we have it here too. Not much to do about until Microsoft fixes the issue.

    The module is located in C:\Program Files\Microsoft Azure AD Connect Health Agent\Modules, so import it from there to run the command(s).

    Import-Module "C:\Program Files\Microsoft Azure AD Connect Health Agent\Modules\AdHealthConfiguration\AdHealthConfiguration.psd1"

    13 people found this answer helpful.

16 additional answers

Sort by: Most helpful
  1. T.Wunderlich 0 Reputation points
    2024-03-06T09:55:45.1666667+00:00

    Same here Germany

    Test-AzureADConnectHealthConnectivity -Role Sync was successfull.

    0 comments No comments

  2. Hugo Santos 0 Reputation points
    2024-03-06T09:57:58.47+00:00

    User's image

    It seems to be working but the alert remains under Azure.

    User's image


  3. Veres, József 0 Reputation points
    2024-03-06T10:09:30.5366667+00:00

    Same issue for me. Agent unhealthy and ps commands gone.

    0 comments No comments

  4. Spöri, Marco 0 Reputation points
    2024-03-06T10:39:28.32+00:00

    Seems like MS mitigated the issue now. No more active warnings in Azure for me