New Update Bitwarden adds support for passkey login on Windows 11

Brownie2019

Level 23
Thread author
Verified
Well-known
Forum Veteran
Mar 9, 2019
969
4,663
2,168
Germany
Bitwarden announced support for logging into Windows 11 devices using passkeys stored in the manager's vault, enabling phishing-resistant authentication.
The new feature is available for all plans, including the free tier, and allows logging into Windows by selecting the security key option and scanning a QR code with a mobile device to confirm access to the passkey stored in the Bitwarden encrypted vault.
Bitwarden is an open-source password and secrets manager that can store account passwords, passkeys, API keys, credit card details, identity data, and private notes.
To use the new feature, there are three required conditions:
Have Entra ID–joined devices
FIDO2 security key sign-in is enabled
Have a registered Entra ID passkey stored in their Bitwarden vault
“Windows now supports industry-standard passkeys secured in the Bitwarden vault, enabling passwordless authentication during sign-in,” Bitwarden says in a press release.
“Users can choose to log in with a passkey stored in the Bitwarden vault, allowing Windows to authenticate using cryptographic credentials rather than passwords, without transmitting shared secrets.”
Bitwarden acts as the passkey provider in the Windows authentication flow, storing the credential in the user’s synced vault rather than binding it to a single device. This also allows recovery using other devices in case of losing the phone.
More importantly, by removing password entry from the login process and using cryptographic challenges signed with private keys stored in the vault, the risk of credential exposure to phishing drops dramatically.
Bitwarden states that Microsoft will roll out passkey login on Windows this month, and it depends on the Microsoft Entra ID configuration.
In November 2025, Microsoft announced the introduction of a passkey provider API on Windows 11, allowing third-party apps like Bitwarden and 1Password to store and manage passkeys for websites and apps on the OS.
The latest announcement extends this further, to a more fundamental authentication layer, that of the OS itself.
 
Last edited by a moderator:
This is a meaningful step forward for passwordless Windows sign-in, but it is important to read it as “Windows 11 + Microsoft Entra ID (work/school) scenarios” rather than a general “everyone can now sign into any Windows PC with Bitwarden.”

What this enables (in plain terms)

Bitwarden can act as a third-party passkey provider during Windows 11 sign-in, so the cryptographic credential (passkey) is stored in your Bitwarden vault and can be used across devices (depending on your organization’s Entra ID setup and Microsoft’s rollout).

The flow described (select “security key,” scan a QR code with a phone) is consistent with passkey/FIDO-style authentication where the phone confirms use of the credential without typing a password.

Key limitations / requirements (the important part)
  • This is tied to Microsoft Entra ID and Entra ID–joined devices. For most home users signing into Windows with a personal Microsoft account, this may not apply (or may not apply yet).
  • Your tenant must allow FIDO2 security key sign-in and have the right policies configured (often via Authentication Methods + Conditional Access).
  • You need an Entra ID passkey registered and stored in Bitwarden (so it’s not “turn it on and it works” — there is enrollment and admin policy behind it).
  • It also depends on Microsoft’s phased rollout in Windows, so availability can vary by build/channel and tenant configuration.

Security impact (what it helps, and what it does not)
  • Helps strongly against phishing and credential replay: there is no password being typed into a prompt that can be stolen, and the cryptographic challenge-response is origin-bound in passkey/FIDO designs.
  • Does not “solve” local compromise: if the endpoint is already compromised (malware, remote access trojan, malicious admin tools, etc.), an attacker may still be able to act in the user’s session or interfere with sign-in.
  • Your Bitwarden vault becomes more security-critical: vault protection (strong master password, 2FA, device security, and careful recovery options) matters even more when the vault is part of OS sign-in.

Practical advice for admins before enabling broadly
  • Pilot first: test with a small group and documented break-glass/fallback sign-in method (especially for remote users).
  • Review Conditional Access and Authentication Methods policies so you do not accidentally lock out users who lose a phone or cannot access Bitwarden temporarily.
  • Require strong protection for vault access (2FA for Bitwarden, device screen lock/biometrics, and sensible session timeout policies).
  • Document the recovery process clearly (lost phone, new phone, offline/low-connectivity situations).

Note on the dates mentioned

I can’t verify the “November 2025” timing in the quoted excerpt without checking Microsoft’s original announcement, but Microsoft has been actively building Windows support for third-party passkey providers; the important takeaway is the capability and its dependency on Windows/Entra ID policy and rollout, not the exact month stated in a news summary.

Sources
 
  • Like
Reactions: Jonny Quest
The direction is very positive: stronger security and less dependence on passwords. The key point is that, for now, these improvements are mainly designed for corporate environments and are not yet available to the average home user. Hopefully they will soon extend to everyday use, because the benefit would be huge. 🔐🏢🏠