Try re-registering the device by running the following commands in PowerShell:
dsregcmd /leave
dsregcmd /debug
Then, restart the device and attempt to join it again.
Verify that the devices can reach the necessary Azure AD endpoints, specifically the connectivity to the following URLs:
Test-NetConnection -ComputerName enterpriseregistration.windows.net -Port 443
Test-NetConnection -ComputerName login.microsoftonline.com -Port 443
Test-NetConnection -ComputerName device.login.microsoftonline.com -Port 443
Test-NetConnection -ComputerName autologon.microsoftazuread-sso.com -Port 443
You can use Test-NetConnection
in PowerShell for that.
Check that your firewall or proxy is not blocking traffic to the required endpoints.
Don't forget also to check your Group Policy settings the ones related to device registration and Windows Hello for Business.
The AzureADKerberos
objects should be created correctly. The krbtgt_AzureAD
user object should be disabled, which is expected.
Run the dsregcmd /status
command on a problematic device to get detailed information about the device registration status. Look for any errors or warnings in the output.
Check the Event Viewer logs on the device for any related errors. Look under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin
for any relevant entries.