Bitwarden not supplying passkeys to Microsoft 365 logon

Which Bitwarden app is your issue or question about?

1 - Browser Extension

Bitwarden App Version

2026.8.0

Operating System

03 - Windows

Where is your vault hosted?

Bitwarden (default)

Attach a screenshot

Description

New profile for a client in Edge. Logged into profile with M365 account so synchronised. Bitwarden extension automatically added (as in sync’d profile). Logged in to extension. Then tried to logon to OneDrive which brings up this dialogue. Is it a web page or not? Never very clear. Anyway, no way to get Bitwarden to supply the previously saved passkey. Have to resort to password.

Is it because this logon isn’t really a web page and therefore the extension doesn’t spot it?

I’m not clear how the mechanism to supply passkeys works in a web browser, or passkeys in general! Still not 100% happy with this whole concept…

Later… once logged onto the M365 console, Bitwarden did supply the passkey correctly when I went into the security section of the account. So the passkey is correct. But that prompt was 100% a webpage.

I know that after my employer switched their 2FA provider from DUO to Microsoft, I was no longer able to use passkeys stored in Bitwarden for authentication. If I had to guess, this is a restriction imposed by Microsoft, out of Bitwarden’s control (it may even be related to the attestation issue described here).

I don’t know what the problem is, but I want to share what I’ve observed with my CONSUMER Microsoft account.

  1. All the login pages I’ve tried have been web pages, with a URL at the top of the browser’s Windows, which I don’t see on your screen.
  2. Entra ID admins can restrict the types of authenticators they’ll accept (1, 2, 3). The confusing thing in your case is that it does accept Bitwarden’s passkey when you go into your account’s security options.
  3. I don’t have an Entra account, but I do have an institutional DUO account. Mine also behaves inconsistently: passkey registration for Windows Hello is allowed, but I can’t use it. In my case, I think it’s a combination of the institution’s configuration and Duo’s inconsistent implementation. Maybe Microsoft has some inconsistency issues as well.
  4. As far as I know, passkeys in Windows require a browser component (i.e., a webpage), so they’re usually available in web browsers and apps that have web components, like Electron apps.

It is/was. Earlier this year, Microsoft introduced the possibility of using synced passkeys. If an admin had never futzed with passkey settings prior to March 2026, the “Default Passkey Profile” will be set to to device-bound and enforce attestation, and this will be used in the passkey “campaigns” Microsoft is currently imposing.

Microsoft does allow three “types”:

  • Device Bound with Attestation Enforced
  • Device Bound without Attestation
  • Synced without Attestation

In all three cases, one can optionally enumerate acceptable (or blocked) AAGUIDS. @Neuron5569 included relevant links in the preceding comment.

Just now, I used an account configured as “Synced without Attestation” and targeting AAGUID d548826e-79b4-db40-a3d8-11116f7e8349 (“Bitwarden”) solely using a passkey stored in Bitwarden.

Isn’t the actual issue here that OneDrive uses WAM to handle authentication, which is a wrapper round a browser and not the regular browser with extensions, so the Bitwarden Extension cannot intercept and respond to the passkey.

I believe there was an announcement about a beta version of the Bitwarden client that could hook windows passkey - I think this was still in beta?

What’s not clear is if the new beta client for layout includes this passkey beta feature or they are separate builds?

Yes, I suspect this is exactly the reason. The Microsoft 365 authentication dialogues are not web pages despite them looking a bit like them.

@TankBob Welcome to the forum!

Those are two separate builds, if we mean the same thing:

It matters which onedrive is being discussed. The web version (https://onedrive.live.com/login) should behave.

App (e.g. onedrive installed with add/remove programs) that use “embedded browsers” tend to have problems with any sorts of advanced authentication. @tankbob (welcome to the community!) is correct that lack of extensions in embedded browsers is a common cause, but I do believe there is more than just that as I have also seen them refuse passkeys stored in Hello, which does not require an extension.