FIDO2 login issues on Windows 11 Enterprise

Christian Schmittel 0 Reputation points
2023-01-24T09:35:46.4866667+00:00

Hello,

for testing purposes we have enabled FIDO2 Auth in Azure AD. Everything works except: if the notebook is connected to a docking station and the lid is closed, then users cannot log in with the YubicoKey.

When the notebook is connected to a docking station but the lid is open, everything works normally.

Is this a bug or should I consider it normal behaviour.

Attached are two clips:

Normal behaviour | Lid is open

Windows problem ... | lid is closed

Sometimes there is no error message at all.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
18,736 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Givary-MSFT 25,761 Reputation points Microsoft Employee
    2023-01-25T10:00:58.3066667+00:00

    @Christian Schmittel Thank you for reaching out to us, As far I am aware FIDO2 login with lid closed should work without any issues, further researching on this found a similar issue (with Dell laptop) in our knowledge base in the past where usb power management within the bios affected the state of the USB when the lid was closed, there was an advice from Yubico in that case where adjusting the BIOS setting ‘Enable lid switch’ to off and the FIDO2 device started functioning correctly with the lid closed. 

    Would suggest if you have any such setting in the bios do check or else contacting FIDO2 vendor should further help you in this issue.

    Let me know if you have any further questions, feel free to post back.

    Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.

    0 comments No comments

  2. Peter Kolarov 0 Reputation points
    2023-02-28T13:03:08.45+00:00

    Hello @Givary-MSFT

    I am seeing exactly the same issue as Christian above. This indeed appears as a Windows 11 bug as I have tested this on 3 different notebooks and external monitors from different OEMS including Microsoft Surface Book2, ThinkPad and Dell.

    Can you please look into it?