Mar 12 2020 01:51 PM
Mar 12 2020 01:51 PM
I'm looking for some clarification on the behaviour around Windows Hello for Business after Hybrid Azure AD joining Windows 10 devices.
I recently enabled HAADJ in AAD Connect. As expected first of all, the devices acquire a userCertificate attribute as part of the WorkplaceJoin schedule task, sync to AzureAD as part on the next AADConnect sync cycle and show up in the Azure AD tenant as a HAAD device.
The issue I encounter is with the Windows Hello for Business prompt. When a synced user logs in, they're prompted to setup a Windows Hello for Business PIN. You can skip the process and continue but every subsequent login ask you to set-up a PIN which you can sync.
The devices are HAADJ but not enrolled into Intune for MDM.
In the AzureAD Portal under Microsoft Intune\Device Enrollment\Windows Enrollment\Windows Hello for Business, it was set as Not Configured. I also changed this to Disabled, but the users still get the prompt.
I only way forward I'm finding to deal with this is by setting the settings “Use Windows Hello for Business” under "User Configuration\Administrative Templates\Windows Components\Windows Hello for Business” to Disabled. It was previously set to Not Configured. This stops the setup PIN prompt coming up after login, however, notifications still appear in the notification area after login saying that The system is configured to use Windows Hello for Business, Click here to setup you PIN.
I do not get this behaviour in other environments where I have HAADJ configured, with seemingly the same settings.
End goal is wanting to retain HAADJ but disable all the prompts for setting up Windows Hello for Business. Any ideas?
Mar 20 2020 04:18 AM
Managed to shed some light on this.
In short, ignore the WHFB settings in InTune unless the device is MDM enrolled and managed by InTune. Essentially this was the associated to a group policy via AD on premises which was already in place for the AD forest/domain.
There was a COMPUTER GP in place which set "Computer Configuration\Administrative Templates\Windows Components\Windows Hello for Business” to Enabled. I imagine that somebody switched it to enabled thinking that would be nice to have.
After enabling HAADJ, a device was becoming hybrid joined, and the subsequent login (from a synced AD user) resulted in a WHFB Set-Up PIN prompt.
If the "Computer Configuration\Administrative Templates\Windows Components\Windows Hello for Business” setting been set to Not Configured, this wouldn't have arisen as an issue.
As a note, once we had set the "User Configuration\Administrative Templates\Windows Components\Windows Hello for Business” to Disabled, that took priority over the Computer Configuration policy and the WHFB prompt didn't show.
So lesson learnt is to check those GP settings in an AD on premises prior to mass syncing devices to be Hybrid Azure AD Joined.