How To Fix Microsoft Passkey Sign-In Not Working (2026)
You try to sign in to your Microsoft account with a passkey, and you get “Something went wrong” or “No passkeys available.”
Most passkey errors come down to a missing screen lock, Bluetooth, an old software version or a passkey that was deleted.
This guide follows Microsoft’s passkey troubleshooting page and its passkey setup and management pages.
Quick answer: match the message to the fix
| Message | Cause Microsoft lists | Fix |
|---|---|---|
| Something went wrong | Duplicate passkey, timeout, Bluetooth off or old software | Retry in time, turn on Bluetooth, update the OS and browser |
| No passkeys available | Screen lock is turned off | Turn on a screen lock |
| This passkey can no longer be used | Passkey deleted, or PIN or biometrics changed | Set up a new passkey |
| Sign in another way | Passkey no longer valid on that device | Use another method, then delete old passkeys |
Fix “Something went wrong”
Credential managers allow only one passkey per website, app or service, so adding the same passkey twice can cause this error.
A synced credential manager already lets you sign in on any device, so you do not need a duplicate.
- Retry within the time limit, because a sign-in that times out fails.
- Turn on Bluetooth on both devices, keep them in range and connect both to the internet.
- If Bluetooth hangs while you register a USB security key, cancel and refresh the sign-in page.
- Check that your Windows, macOS, mobile OS and browser are current.
Fix “No passkeys available”
Synced passkeys do not appear when the device screen lock is disabled.
Turn on a screen lock, because passkeys need a face, fingerprint or PIN check.
Fix a QR code that does not appear
The QR code for an iPhone, iPad or Android device needs Bluetooth on both the sign-in device and the device that holds the passkey.
The two devices must be in range and online, but they do not have to be on the same network.
An organization can block Bluetooth cross-device sign-in, and in that case an admin has to change the policy.
Fix “This passkey can no longer be used”
Microsoft ties this message to a passkey that was deleted from the account or device, or to a changed PIN or biometric method.
- Set up a new passkey.
- On your phone, open the authenticator app and find passkeys that no longer apply.
- Delete the old ones.
Fix “Sign in another way”
This message means the passkey is no longer valid on that device.
Pick one of the other sign-in methods offered, then check your account for passkeys that no longer apply and delete them.
Android Work profile and security key problems
If you see “We couldn’t sign you in” on an Android Work profile, the passkey was probably saved in the Personal profile.
Recreate the passkey in the Work profile, and do not scan the sign-up QR code with the Personal profile’s camera app.
If an external security key is not found, unplug it, plug it back in and respond promptly.
Device-bound or synced: why it matters
A device-bound passkey lives only on the device where you created it and does not sync.
A synced passkey is saved in a credential manager, so it follows you to your other devices.
| Type | If you lose the device |
|---|---|
| Device-bound | You lose the passkey unless you have another recovery method |
| Synced | Sign in to your credential manager account on the new device |
Microsoft suggests saving to a synced manager, or creating passkeys on your other devices as a backup if you save locally.
Create a new passkey for your account
- Sign in to Advanced Security Options at account.live.com/proofs/manage.
- Select Add a new way to sign in or verify.
- Select Face, Fingerprint, PIN, or Security Key.
- Follow the instructions on your device.
- Select Continue or Create to use the suggested save location, or choose Change or Save another way.
| Save location | What it does |
|---|---|
| Password manager | Syncs the passkey across devices, such as Microsoft Password Manager or iCloud Keychain |
| Phone or tablet | Scan the QR code, or use the scan button in Microsoft Authenticator |
| Security key | Stores the passkey on a physical key |
| Windows Hello | Saves it only on that Windows device |
Check the system requirements
Old software is one of the causes Microsoft lists for passkey errors, so compare your devices with its requirements.
| Item | Minimum Microsoft lists |
|---|---|
| Windows | Windows 10 or newer |
| macOS | Ventura or newer |
| iOS | 16 or newer (17 or newer for passkeys in Microsoft Authenticator) |
| Android | 9 or newer (14 or newer for passkeys in Microsoft Authenticator) |
| Browsers | Edge 109, Safari 16 or Chrome 109 or newer |
Work or school accounts can use passkeys only if the organization supports them, and some Windows options need Windows 11.
To check your Windows version, open Settings, select System and then About.
Edge creates passkeys automatically
If a passkey appeared without you adding one, Microsoft Edge may have created it through its automatic upgrade setting.
In Edge, open Settings, then Passwords and autofill, then Microsoft Password Manager, then More settings.
Turn Automatically upgrade to passkeys on or off there, and note that automatically created passkeys are saved in Microsoft Password Manager.
Your organization’s IT admin may disable Windows storage and synced backup for passkeys, which can also explain missing options on a work device.
Manage or remove old passkeys
On Windows, open Settings and select Accounts then Passkeys, and use the more icon to delete one.
For passkeys on your account, go to account.live.com/proofs/manage, expand a passkey and choose Rename or Remove.
Add new sign-in info before removing a passkey, because a passkey scheduled for removal cannot be used to sign in.
When you changed phones
Create and save a new passkey on the new device before you delete the old one.
Our guide on moving Microsoft Authenticator to a new phone covers the app side.
Still locked out?
Use Microsoft’s sign-in helper, or open Contact Microsoft Support and select Get Help.
Agents cannot send password reset links or change account details, so see what to do when a security code does not arrive and how to handle a locked account for the official routes.
Sources: Microsoft passkey overview and manage your saved passkeys.