Intune: Windows Hello for Business

-

Windows Hello for Business has been around for some time as an alternative sign-in method and it allows a user gesture to sign-in instead of just using a password. There are many sign-in gestures available and depending on what is supported based on the hardware, one can configure a PIN, biometric or a fingerprint. For corporate devices, PIN is the most suited method and it is easily configurable on Intune managed devices. However, I will cover other settings in this blog as well.

Now Windows Hello for Business is Not Configured by default. So, in case you do not want to enable it for all your users (Remember this setting is a tenant wide setting) then you will need to atleast configure it to Disable for Intune to be able to manage the feature.

 


Once in place, one can then deploy a Windows Identity protection profile policy to devices of your choice to enable the feature along with the desired configuration.

Let’s begin

  1. Browse to Devices – Windows – Configuration profile.
  2. Click Create Profile.
  3. Choose Windows 10 and later as Platform
  4. Select Identity Protection as Profile type
  5. Click Create
  6. Give a name
  7. Configure Windows Hello for Business: Enable
  8. Minimum PIN length: <Minimum is 6, but you can enforce a lower value>
  9. Maximum PIN length: <Maximum length is 127 characters>
  10. Lowercase letters in PIN: Allowed
  11. Uppercase letters in PIN: Allowed
  12. Special characters in PIN: Allowed
  13. PIN expiration (days): <Default is 41 days>
  14. Remember PIN history: <Default is 5 reused>
  15. Enable PIN recovery: Enable
  16. Use a Trusted Platform Module (TPM): <You can enable this, I left it out for testing purposes>
  17. Allow biometric authentication: Enable
  18. Use enhanced anti-spoofing, when available: Enable
  19. Certificate for on-premise resources: Enable
  20. Use security keys for sign-in: Enable (This setting is available for Windows 10 1903 and later.)
  21. Assign it to a user or a device group.


User Experience

After a device has checked in with Intune, Windows Hello setup screen should show up in 15-20 minutes. If it doesn’t then it most certainly will show up after a reboot.

 


If you haven’t already confirmed your identity on the device, you’ll be prompted to do so. Once done, you should receive a text code.

 





User will be able to login using the newly setup PIN.

 




 

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){              ...
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from st...
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $P...
Read more