Fingerprint sign-in not working

Harry 1 Reputation point
2022-05-06T02:18:48.217+00:00

I have deployed a policy from Intune to enable Biometric Login.
However, after setting up my Fingerprint on my Windows 10 device I am not getting a sign-in option using Fingerprint after shut down and re-boot. It shows only password option for sign-in.

When I login using password, and go to Sign-in options in Settings, the fingerprint setup is wiped off and it asks me for a fresh setup.

Event Viewer shows :
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
Cloud trust for on premise auth policy is enabled: Not Tested
User account has Cloud TGT: Not Tested

Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,707 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,298 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Crystal-MSFT 42,631 Reputation points Microsoft Vendor
    2022-05-06T07:17:17.577+00:00

    @Harry , For our issue, firstly, please ensure the Fingerprint sensor requirements are met on our devices.
    https://learn.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-biometrics-in-enterprise#where-is-windows-hello-data-stored

    Then try to enable windows Hello Fingerprint Login on the affected device manually to see if it can work.

    For the error in event view, it can be generated when no AAD user logging the device. After the policy is assigned to the device group, we can logged one user to sync and get the policy, and go to Settings > Accounts > Sign-in Options to set the fingerprint. Then restart the device to see if it can work.

    However, if it still failed, please collect the following information to clarify:

    1. How did we configure the configuration policy, Is it under Identity Protection? Could you get a screen shot of the detailed configuration?
    2. Please check the "Device status" to see if the policy is applied successfully.
    3. Please check if the policy is assigned to device group.

    Please try the above suggestion and if there's anything unclear, feel free to let us know.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Sebastian Cerazy 306 Reputation points
    2023-03-18T17:49:10.1833333+00:00

    It is total insanity!

    I have same maddening issue with Hello for Business

    Enroll (setup) fingerprint on Azure AD/Intune machine

    It works if I ie lock the session, it might even work after first reboot. Then never again. It either does not show as an option, of it shows, accepts fingerprint, but instantly requests PIN

    I can delete the fingerprint & set it up again, and the same will happen over & over.

    Same behaviour applies to Face recognition. And it is not specific hardware (so far tested on two separate Dell Latitude 7400 2-in-1 & Latitude 7420

    If I do use either face or fingerprint on NON Azure/Intune machine (with local login of Microsoft login), it ALWAYS work just fine (also tested on multiple hardware)

    So it is only Azure AD/Intune devices

    The policies are correct (otherwise it would never allow to login)

    Seb

    0 comments No comments