Password hash sync perpetual error

EcoInC 0 Reputation points
2024-06-27T21:20:25.6133333+00:00

After reinstalling the Azure AD Connect Sync and provisioning agent on an existing environment, the error:

Password hash sync

Status: NotRun

Last successful run: Never

Job Id :AD2AADPasswordHash.9e6de611bd014d65b1ba299e550a6ae8.c4599863-b31a-4327-bcfb-12430ddd6065

Keeps showing non stop. all services are Up and running on the on premise DC, Agent is healthy, FW rules are as set in documentation but releasing the Password hash sync error from "provisioning quarantine" into Healthy state only last 1 minute.

A ticket with Microsoft is already in place but after 3 days no answers. thoughts?

DC is a Win 2022 Server (Azure VM)

Azure AD Sync Agent is 2.3.8

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,121 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,278 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Fabio Andrade 725 Reputation points Microsoft Employee
    2024-06-27T23:46:29.2366667+00:00

    Hi @EcoInC

    Thanks for reaching out to Microsoft Q&A.

    Are you experiencing any issues to sync users or only with the passwords? Do you know if the Password Sync is failing for all the users?

    Please, run the AD Connect Troubleshooter (if you haven't yet) and select the password sync option and share the results in here

    https://video2.skills-academy.com/en-us/entra/identity/hybrid/connect/tshoot-connect-password-hash-synchronization#run-the-troubleshooting-task

    User's image

    Thanks,

    Fabio

    0 comments
  2. Neuvi Jiang 465 Reputation points Microsoft Vendor
    2024-06-28T08:15:52.06+00:00

    Hi EcoInC,

    Thank you for posting in the Q&A Forums.

    Check the status of the Azure AD Connect synchronization service:

    On the local server, open Services and see if the Azure AD Connect synchronization service (usually Microsoft Azure AD Sync) is running.

    Check the agent status:

    If you are using a Provisioning Agent, make sure it is running and there are no errors. You can view the status and logs of the agent in the Azure Portal.

    View the synchronization logs:

    Open Azure AD Connect, go to the Troubleshooting tab, and use the Synchronization Service Manager to view detailed error logs. This may provide clues as to why the PHS is not running.

    Check network connectivity:

    Ensure that the Azure AD Connect synchronization server has access to the endpoints and URLs required for Azure AD.You can verify network connectivity using the Azure AD Connect Health agent or a manual test.

    Check firewall and proxy settings:

    If you have firewalls or outbound proxies in your environment, make sure that they are not blocking the Azure AD Connect synchronization server from communicating with Azure AD.

    Check the Azure AD Connect configuration:

    Rerun the configuration in the Azure AD Connect wizard to ensure that all settings are correct, especially those related to PHS.

    Best regards

    NeuviJ

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments