Cyberpediaby Brain

Switching to passkeys on your accounts

A passkey replaces the password and resists phishing. How to turn it on, which type to choose, and what to do if you lose your device.

On this page
  1. 1In 30 seconds
  2. 2What it is
  3. 3Straight answers
  4. 4How it works
  5. 5What you do
  6. 6Pitfalls
  7. 7Sources
  8. 8Cite this article

In 30 seconds

Where it happens
In an account's security or privacy settings, when creating an account, or in a window that offers to create a passkey at sign-in[1][2].
What the attacker wants
To steal a password, a code received by SMS or a code received by email, remotely and without touching the victim's device[3].
The reflex
When a service offers a passkey, accept it. When it does not, keep a strong password generated by a password manager, together with two-step verification[1].
If it is already done
Also create passkeys on your other devices, or save them in a synchronised manager, to have a backup key[2].

What it is

A passkey replaces the password. To sign in to an app or a website, you confirm with your face, your fingerprint or your device's lock code[1]. The NCSC (UK) recommends choosing passkeys over passwords wherever they are available[1].

This page explains why a passkey resists phishing, how to create one on your accounts, which type to choose and what to do when the device is lost.

Straight answers

What is a passkey?

It is a passwordless sign-in method, built on the FIDO2 standard[1]. The device creates a pair of keys: the private key stays safe on the device, and the public key is registered with the website or app[2]. The pair is specific to each service: a passkey only works on the website or app it was created for[3].

Why does a passkey resist phishing?

A passkey is tied to the service's domain. Microsoft gives the example of a passkey created for netflix.com, which can only be used on netflix.com: even if you land on a fake site that looks identical, the device does not offer it the passkey[2]. According to the NCSC, a passkey cannot be intercepted, reused or stolen the way a password can[1]. In addition, every sign-in requires the user to be present to unlock the passkey, so nobody can push the user into signing in from a device other than their own[3].

Does a passkey count as two-step verification?

Yes, according to Microsoft: the device that stores the passkey is what you have, and unlocking it with biometrics or a PIN is what you are or what you know[2]. The NCSC reaches the same equivalence when the user is verified during sign-in[4].

Is my biometric data sent to Microsoft?

No. Microsoft states that biometric data stays on the device and is never sent to it[2].

What if I lose my device?

It depends on the type of passkey. With a credential manager that synchronises, a backup is made: you should not lose access to your passkeys completely[1]. With a passkey tied to a single device, Microsoft warns that you lose the passkey along with the device, unless another recovery method exists or a backup passkey is registered[2]. The NCSC asks users to manage their own backups when they choose a FIDO2 credential on a single device, and to protect the synchronisation account against phishing by giving it a safe recovery option[4].

How it works

At each sign-in, the service sends a challenge to the device. The user unlocks it with biometrics or a PIN, the device signs the challenge with the private key, and the service checks the signature with the public key[3]. No password travels[2].

Microsoft describes two types of passkeys[3]. The device-bound passkey is created and stored on a single device, which it never leaves. Microsoft Authenticator and FIDO2 security keys are examples. The synchronised passkey is encrypted on the device, then stored with a cloud provider, which lets other devices connected to that provider use it. Apple iCloud Keychain and Google Password Manager are examples.

To sign in from a device that does not hold the passkey, Microsoft describes a QR code displayed on the device you want to sign in on. A proximity check verifies that the passkey is only used on a nearby device, which stops a distant attacker from using it[2].

Microsoft publishes figures from its consumer accounts where synchronised passkeys are used: 99% of users register one successfully, and sign-in takes 3 seconds instead of 69 with a password and traditional two-step verification[3]. The NCSC, for its part, reports sign-ins up to 8 times faster than with username, password and a two-step verification code[1].

SMS codes, email codes and notifications to approve are becoming less effective against today's attackers: phishing campaigns have shown that these second factors can be intercepted or spoofed[5]. Microsoft reports that 92% of its employees' productivity accounts are protected by phishing-resistant methods[5].

What you do

  • Look for the option in the account's security or privacy settings, and watch for invitations from services to switch to passkeys[1].
  • For a Microsoft account, add a passkey to your personal or work account, or accept the "Create a passkey?" window shown when you sign in on another site that offers one[2]. If the "Sign in faster with your face, fingerprint or PIN" screen appears, choosing "Next" guides you through creating and saving the passkey[2].
  • For a work or school account, check that the organisation allows it, because a passkey can only be created if the organisation supports passkeys. In that case, contact the IT administrator[2]. Microsoft also states that, for a work account, registering a passkey requires having completed multifactor authentication within the previous five minutes[6].
  • Save the passkey in a synchronised credential manager, such as Microsoft Password Manager, when possible. If you keep it on the device alone, also create passkeys on your other devices (phone, tablet, laptop) to serve as a backup key[2].
  • The manager is most likely the one built into the device, such as Apple Passwords, Google Password Manager or Samsung Pass, unless you have chosen to install a third-party one[1].
  • Check your hardware: Microsoft lists Windows 10 and later, macOS Ventura and later, iOS 16 and later, Android 9 and later, as well as compatible FIDO2 security keys[2].
  • When no passkey is offered, do not give up on passwords: use strong passwords generated by a manager, and turn on two-step verification[1].

Pitfalls

  • A synchronised passkey is not attested: Microsoft recommends treating it as a phishing-resistant credential, but with the same level of security as other non-attested authenticators[6].
  • Attackers try to get around strong protections: Microsoft cites social engineering, credential harvesting and downgrade techniques[3].
  • The NCSC asks users to keep the device updated and secure, to choose their authenticator carefully and to protect the account that synchronises passkeys[4]. Theft of a device protected by a weak code remains a possible risk for a passkey[4].
  • For highly privileged accounts or heavily regulated sectors, Microsoft recommends FIDO2 security keys instead, which can cost more in hardware, training and support, especially when a physical key is lost and the account must be recovered[3].
  • On a device managed by the organisation, some passkey options are not available[2].
  • Microsoft Password Manager is being rolled out: it requires Edge version 142 or later, with a personal profile[2].

Sources

  1. NCSC (UK), “Passkeys: what you need to know”. https://www.ncsc.gov.uk/passkeys (accessed 14 November 2026)
  2. Microsoft, “What are passkeys and why they matter”. https://support.microsoft.com/en-us/accounts-billing/security/what-are-passkeys-why-they-matter (accessed 14 November 2026)
  3. Microsoft, “Authentication methods in Microsoft Entra ID - passkeys (FIDO2)”. https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-passkeys-fido2 (accessed 14 November 2026)
  4. NCSC (UK), “Comparing the security properties of traditional user credentials and FIDO2 credentials for personal use”, 23 April 2026. https://www.ncsc.gov.uk/paper/traditional-user-and-fido2-credentials-personal-use (accessed 14 November 2026)
  5. Microsoft, “Phishing-resistant MFA (Secure Future Initiative)”. https://learn.microsoft.com/en-us/security/zero-trust/sfi/phishing-resistant-mfa (accessed 14 November 2026)
  6. Microsoft, “How to enable passkeys (FIDO2) in Microsoft Entra ID”. https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-authentication-passkeys-fido2 (accessed 14 November 2026)