Look at these guys! They are so happy, they have gotten their Yubikey’s and are ready for some Passwordless Authentication with Windows 10.
In March I posted a blog post about using Yubikey with Azure AD – https://alven.tech/yubico-with-azure-ad-mfa/, So this post is a follow-up since Microsoft has now support for passwordless and Fido2 with Windows 10 (still only preview).
In his post, I will go through the steps regarding configuring passwordless in Intune, Azure AD and Windows 10 with Yubico.
For the purpose of this guide, I will use Windows 10 version 1903 since it has more capabilities in the Policies like users can change their PIN, update biometrics, or reset their security key, and does not require tool from Yubico.
Quick FAQs Passwordless with Windows 10
- Still Only Public Preview
- Working from Windows 10 1809, however, 1903 is recommended for testing.
- Azure AD (MFA) must be configured
- Combined registration required
- FIDO2 key like Yubikeys or other from MS documentation.
- Supports WebAuthN in Edge Only
- The FIDO2 “Key restriction policies” do not work yet.
- FIDO2 support for AAD Hybrid Joined is not supported yet. MS working on support for Hybrid ( Hopefully supported beginning of Q1 2020)
Step 1) Enable Windows Hello for Business
Go to https://devicemanagement.microsoft.com
Choose the Windows Hello for Business settings in Intune. Change the Use Security keys for sign-in to “Enabled“
If you haven’t configured Windows Hello for Business. You will need to enable this setting as well.
Windows Hello is a topic by itself, so I recommend reading the documentation from Microsoft, if you need to look into the different settings and scenarios like Hybrid, Cloud only or on-premise https://docs.microsoft.com/nb-no/windows/security/identity-protection/hello-for-business/hello-planning-guide
Step 2) Intune OMA-URI for Security Key
Create the OMA-URI settings in Intune – Device Configuration – Profiles – Create Profile and Add Custom OMA-URI for Windows 10.
“Name it whatever you want”
“Name it whatever you like”
If you think is strange this OMA-URI setting is called Passport for Work, it’s just the old name before it was named Windows Hello for Business.
I will now add the Profile to my Pilot target group.
Step 3) Enable combined registration experience
Now let’s go back to Azure AD – https://aad.portal.azure.com
Azure AD Manage section – User settings and choose the Manage user feature preview settings
Change it to, Users can use preview settings to select the group for your Pilot users.
Step 4) Enable new passwordless authentication methods
Back to Azure AD Security section – https://aad.portal.azure.com AAD – Auth methods. Authentication method Policy (preview) blade.
Choose the ” Click here to Enable users for the enhanced registration preview”. If its not already enabled.
Add your user target group and save.
Next, go to Methods and Enable FIDO2 Security Key.
The Enforce key restriction is not supported by Microsoft yet . Will be before GA.
Step 5) Add the FIDO key to the user profile
Go to the https://myprofile.microsoft.com
Add FIDO key to user account with the user account in the Security Info tab on the left side.
If you this message. You will have to wait or verify your user’s group permissions.
It took some time for me before the feature was enabled for the user in Azure AD.
Step 6) Testing Passwordless with yubikey’s on Windows 10
We are now ready to test on a Windows 10 Version 1903 Computer.
I can see that the OMA-URI has pushed the policy with login option.
Just need to add my Yubikey, Add my Yubikey PIN and Tap the Yubikey to login like the screenshot below.
Version 1903 gives a better user experience since 1809, however, from an end-user perspective I don’t think the dongle is for everyone. But this improves security and there are multiple use cases for this in the filed, so it’s not strange that Microsoft is pushing to improves Passwordless Experience throughout 2019. When the big players like Apple and Google adding Fido into the Android and iOS devices, the journey to test Passwordless this is even more exciting. WebAuthn also has a lot of potentials and this will expand with browsers capabilities.
In my lab, the next step is still to have a device with NFC so that I could test this functionality.