A family of Microsoft products that enable users to capture, organize, and reuse notes electronically.
The behavior matches a sign-in/authentication problem specific to the passkey flow, not to the browsers or the Web Clipper extension itself. Context confirms:
- Passkey sign-in can fail or get stuck when the passkey on the device is no longer valid or is “orphaned.”
- Some sensitive or special sign-in flows still require a traditional password even if a passkey is normally used.
Based on the context, the most reliable workaround is to temporarily fall back to a password for the affected personal Microsoft 365 account, and clean up any invalid passkeys.
Try the following steps in order:
- Verify the account and sign-in method in a normal browser
- In a regular browser window (not the Web Clipper), go to the Microsoft account security page for the affected personal account (for example, via
account.microsoft.com→ Security). - Sign in using the same personal account that fails in Web Clipper.
- If prompted for a passkey and it fails or loops, choose an alternative sign-in method (password, SMS, email, etc.) if available.
- Ensure the account has a usable password Even when a passkey is used, the account still has (or can have) a password, and some flows require it.
- From the account’s security settings, go to the advanced security options.
- Use the “Change password” or “Create password” option to set a password for this account.
- This password can be used only for verification/sign-in when needed; it does not disable the passkey.
- Clean up invalid or orphaned passkeys If the passkey on the device is no longer valid with Microsoft Entra ID / Microsoft account, sign-in can fail in embedded dialogs (like Web Clipper’s popup).
- In the account’s security info page, review the list of registered passkeys or security keys.
- Remove any passkeys that no longer apply (old devices, keys, or entries that no longer work).
- If the passkey on the current device is orphaned, remove it from the device/passkey authenticator and then re-register a new passkey for this account.
- Re-register a fresh passkey
- After cleanup, add a new passkey for the affected personal account from the security info page.
- Complete the registration on the same device where Web Clipper is used.
- Test sign-in again in a full browser
- In the same browser where Web Clipper is installed, sign out of the personal account if it is signed in.
- Sign back in using the new password first (not the passkey) to ensure the session is clean and working.
- Retry OneNote Web Clipper sign-in
- Open the Web Clipper sign-in dialog.
- If it offers passkey and still loops, choose an alternative sign-in method (password or code) for this account instead of passkey.
- Once signed in successfully with password, the extension should work even if the account also has a passkey configured.
If the issue persists across all browsers even after password creation and passkey cleanup, it is likely a service-side regression in how the Web Clipper’s embedded sign-in window handles passkeys. In that case, use the password-based sign-in as a workaround and contact Microsoft support with details of:
- That the same account signs in fine in a full browser.
- That other accounts (work and personal without passkey) work in Web Clipper.
- That the issue reproduces across multiple browsers and after cache/extension reset.
References: