Troubleshoot device redirections for Azure Virtual Desktop


This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects.

Use this article to resolve issues with device redirections in Azure Virtual Desktop.

WebAuthn redirection

If WebAuthn requests from the session aren't redirected to the local PC, check to make sure you've fulfilled the following requirements:

If you've answered "yes" to both of the earlier questions but still don't see the option to use Windows Hello for Business or security keys when accessing Azure AD resources, make sure you've enabled the FIDO2 security key method for the user account in Azure AD. To enable this method, follow the directions in Enable FIDO2 security key method.

If a user signs in to the session host with a single-factor credential like username and password, then tries to access an Azure AD resource that requires MFA, they may not be able to use Windows Hello for Business. The user should follow these instructions to authenticate properly:

  1. If the user isn't prompted for a user account, they should first sign out.
  2. On the account selection page, select Use another account.
  3. Next, choose Sign-in options at the bottom of the window.
  4. After that, select Sign in with Windows Hello or a security key. They should see an option to select Windows Hello or security authentication methods.

Provide feedback

Visit the Azure Virtual Desktop Tech Community to discuss the Azure Virtual Desktop service with the product team and active community members.

Next steps