Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)
Domic V.
Microsoft Entra ID (Azure AD) hybrid join stuck on "Pending" state in dsregcmd /status
![](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(172.8, 82%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
Ronaldo Cristiano
20
Reputation points
We are currently deploying Hybrid Entra ID Join for our on-premises Active Directory environment. On affected client machines, the output of dsregcmd /status reports both AzureAdJoined : NO and EnterpriseJoined : NO. However, the device already appears in the Entra admin center, where its registration status remains stuck at "Pending."
What is the proper way to trigger or accelerate the synchronization process so the device can complete its Hybrid Entra ID registration successfully?
Windows for business | Windows 365 Business
Answer accepted by question author
![](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(284.8, 33%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDV%3C/text%3E%3C/svg%3E)
Domic Vo
23,805
Reputation points
Independent Advisor
1 additional answer
Sort by: Most helpful
-
Domic Vo 23,805 Reputation points Independent Advisor
2026-06-05T13:55:15.9+00:00 Hi Ronaldo Cristiano,
A "Pending" status means Microsoft Entra Connect has synced the on-premises computer object to the cloud, but the client hasn't completed its local cryptographic handshake. The device must generate a self-signed certificate, update its Active Directory attribute, and wait for Entra Connect to sync that change before final enrollment can succeed.
To force this process immediately, open an elevated PowerShell window on the client machine and run:
Start-ScheduledTask -TaskName "Automatic-Device-Join" -TaskPath "\Microsoft\Windows\Workplace Join\". This bypasses standard logon delays and forces the machine to attempt registration.Verify the status moments later by running
dsregcmd /statusto confirm that AzureAdJoined changes to YES. If it remains stuck, look for specific error codes in the Event Viewer under Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin.Domic V.