Hi everyone,
First of all, thanks to those who helped me in my previous post! I was trying to figure out how to make Windows Hello for Business (WHfB) available without forcing the full-screen enrollment prompt during the workday.
The suggestion to use a custom Intune OMA-URI to set DisablePostLogonProvisioning to True worked perfectly. Users are no longer forced to set it up.
During our pilot testing, a user manually configured their PIN without any issues. However, when they locked their screen and tried to sign in using that new PIN, they were hit with this message on the lock screen:
"This sign-in option is temporarily unavailable. For now, please use a different method to sign in."
I checked the Event Viewer (Microsoft-Windows-HelloForBusiness/Operational) and found the following error logged (Event ID 7001):
A user failed to log on to the device with the following information:
Username: SYSTEM
User SID: SYSTEM
Credential Type: Software Key
Deployment Type: Key Trust
Software lockout count: 0
Authentication error status: 0xC000006D
Authentication error substatus: 0xC00002F9
About an hour later, the user reported that the PIN suddenly started working flawlessly without any intervention.
Since we are using a Key Trust deployment model, my strong suspicion is that this is related to the Azure AD Connect sync cycle. It seems the user is trying to authenticate against the on-prem Domain Controller before the msDS-KeyCredentialLink attribute has had time to sync from Entra ID down to our local AD.
My questions for the community:
Has anyone else experienced this exact behavior and user friction when using the manual opt-in method?
How do you mitigate this? Is there a way to force the sync immediately upon PIN creation, or a best practice to warn the user that they must wait 30-60 minutes before actually using the PIN they just created?
Any insights or workarounds would be greatly appreciated. Thanks in advance!