Enable passwordless security key sign in to Windows 10 devices (preview)
This document focuses on enabling FIDO2 security key based passwordless authentication with Windows 10 devices. At the end of this article, you will be able to sign in to both web-based applications and your Azure AD joined Windows 10 devices with your Azure AD account using a FIDO2 security key.
- Azure Multi-Factor Authentication
- Combined security information registration preview
- Compatible FIDO2 security keys
- WebAuthN requires Windows 10 version 1809 or higher
- Azure AD joined devices require Windows 10 version 1809 or higher
- Microsoft Intune (Optional)
- Provisioning package (Optional)
- Windows Server Active Directory Domain Services (AD DS) domain-joined (on-premises only devices) deployment not supported.
- RDP, VDI, and Citrix scenarios are not supported using security key.
- S/MIME is not supported using security key.
- “Run as“ is not supported using security key.
- Log in to a server using security key is not supported.
- If you have not used your security key to sign in to your device while online, you will not be able to use it to sign in or unlock offline.
- Signing in or unlocking a Windows 10 device with a security key containing multiple Azure AD accounts. This scenario will utilize the last account added to the security key. WebAuthN will allow users to choose the account they wish to use.
Prepare devices for preview
Azure AD joined devices that you will be piloting with must be running Windows 10 version 1809 or higher. The best experience is on Windows 10 version 1903 or higher.
Enable security keys for Windows sign-in
Organizations may choose to use one or more of the following methods to enable the use of security keys for Windows sign-in based on their organization's requirements.
Enable with Intune
- Sign in to the Azure portal.
- Browse to Microsoft Intune > Device enrollment > Windows enrollment > Windows Hello for Business > Properties.
- Under Settings set Use security keys for sign-in to Enabled.
Configuration of security keys for sign-in, is not dependent on configuring Windows Hello for Business.
Targeted Intune deployment
To target specific device groups to enable the credential provider, use the following custom settings via Intune.
- Sign in to the Azure portal.
- Browse to Microsoft Intune > Device configuration > Profiles > Create profile.
- Configure the new profile with the following settings
- Name: Security Keys for Windows Sign-In
- Description: Enables FIDO Security Keys to be used during Windows Sign In
- Platform: Windows 10 and later
- Profile type: Custom
- Custom OMA-URI Settings:
- Name: Turn on FIDO Security Keys for Windows Sign-In
- OMA-URI: ./Device/Vendor/MSFT/PassportForWork/SecurityKey/UseSecurityKeyForSignin
- Data Type: Integer
- Value: 1
- This policy can be assigned to specific users, devices, or groups. More information can be found in the article Assign user and device profiles in Microsoft Intune.
Enable with a provisioning package
For devices not managed by Intune, a provisioning package can be installed to enable the functionality. The Windows Configuration Designer app can be installed from the Microsoft Store.
- Launch the Windows Configuration Designer.
- Select File > New project.
- Give your project a name and take note of the path where your project is created.
- Select Next.
- Leave Provisioning package selected as the Selected project workflow and select Next.
- Select All Windows desktop editions under Choose which settings to view and configure and select Next.
- Select Finish.
- In your newly created project, browse to Runtime settings > WindowsHelloForBusiness > SecurityKeys > UseSecurityKeyForSignIn.
- Set UseSecurityKeyForSignIn to Enabled.
- Select Export > Provisioning package
- Leave the defaults in the Build window under Describe the provisioning package and select Next.
- Leave the defaults in the Build window under Select security details for the provisioning package and select Next.
- Take note of or change the path in the Build windows under Select where to save the provisioning package and select Next.
- Select Build on the Build the provisioning package page.
- Save the two files created (ppkg and cat) to a location where you can apply them to machines later.
- Follow the guidance in the article Apply a provisioning package, to apply the provisioning package you created.
Devices running Windows 10 Version 1809 must also enable shared PC mode (EnableSharedPCMode). Information about enabling this funtionality can be found in the article, Set up a shared or guest PC with Windows 10.
Sign in to Windows with a FIDO2 security key
In the example below a user Bala Sandhu has already provisioned their FIDO2 security key using the steps in the previous article, Enable passwordless security key sign in. Bala can choose the security key credential provider from the Windows 10 lock screen and insert the security key to sign into Windows.
Manage security key biometric, PIN, or reset security key
- Windows 10 version 1903 or higher
- Users can open Windows Settings on their device > Accounts > Security Key
- Users can change their PIN, update biometrics, or reset their security key
Troubleshooting and feedback
If you would like to share feedback or encounter issues while previewing this feature, please share via the Windows Feedback Hub app.
- Launch Feedback Hub and make sure you're signed in.
- Submit feedback under the following categorization:
- Category: Security and Privacy
- Subcategory: FIDO
- To capture logs, use the option: Recreate my Problem
Frequently asked questions
Does this work in my on-premises environment?
This feature does not work for a pure on-premises Active Directory Domain Services (AD DS) environment.
My organization requires two factor authentication to access resources, what can I do to support this requirement?
Security keys come in a variety of form factors. Please contact the device manufacturer of interest to discuss how their devices can be enabled with a PIN or biometric as a second factor.
Can admins set up security keys?
We are working on this capability for general availability (GA) of this feature.
Where can I go to find compliant security keys?
What do I do if I lose my security key?
You can remove keys from the Azure portal, by navigating to the security info page and removing the security key.