Welcome to Microsoft Q&A Forum!
Thank you for providing detailed information about the issue.
Based on the behavior you described, yes, this can be related to Hybrid Microsoft Entra ID (Azure AD) Join, but a failure during the key registration phase is not necessarily caused by Hybrid Join alone.
In the Windows Hello for Business (WHfB) provisioning process, the user has already completed identity verification and PIN creation by the time key registration occurs. At this stage, Windows generates a public/private key pair and attempts to register the public key with Microsoft Entra ID. If the key cannot be registered successfully, provisioning stops and Windows Hello for Business enrollment cannot be completed. This indicates that the failure occurs after key generation, when Windows is communicating with the identity provider to complete credential registration. I recommend checking the following areas
1.Verify device registration status
Run the following command:
dsregcmd /status
For a Hybrid Microsoft Entra ID joined device, verify that the output shows:
- DomainJoined : YES
- AzureAdJoined : YES (or Hybrid Joined state)
- AzureAdPrt : YES
Windows Hello for Business provisioning depends on successful device registration. If the device is not properly hybrid joined or does not have a valid Primary Refresh Token (PRT), key registration may fail.
2.Review Event Logs
Check the following logs for errors occurring during provisioning:
- Applications and Services Logs -> Microsoft -> Windows -> User Device Registration
- Applications and Services Logs -> Microsoft -> Windows -> HelloForBusiness
These logs often provide the specific error code or failure reason that can help identify the root cause.
3.Validate connectivity to Microsoft Entra registration services
Ensure the affected device can access the required registration endpoints:
- enterpriseregistration.windows.net
- device.login.microsoftonline.com
- login.microsoftonline.com
Proxy, firewall, SSL inspection, or network connectivity issues can prevent the key registration process from completing successfully.
Reference: Configure Microsoft Entra hybrid join - Microsoft Entra ID | Microsoft Learn)
4.Verify Hybrid Join and WHfB prerequisites
For Hybrid deployments, please ensure:
- Microsoft Entra Connect synchronization is healthy.
- The device appears correctly in Microsoft Entra ID.
- Time synchronization is accurate.
- TPM is functioning correctly.
- Conditional Access or MFA policies are not blocking device registration.
For further information, please visit: Troubleshoot Microsoft Entra hybrid joined devices - Microsoft Entra ID | Microsoft Learn
I hope this helps clarify the issue, if this answer was helpful, please Accept the Answer.
Thank you for choosing Microsoft Q&A to raise your concern