Passkey (FIDO2) authentication method
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit e9c80ec · +1 −1 lines · also on GitHub
⋯ 40 unchanged lines
4141
- **Device-bound passkeys**: The private key is created and stored on a single physical device and never leaves it. Examples:
4242
- Microsoft Authenticator
4343
- FIDO2 Security keys
44
−- **Synced passkeys**: When created, the private key is created by a hardwear security module (HSM) and encrypted on the local device. This encrypted key is then synced to the cloud passkey provider with end to end encryption. Other devices registered with the passkey provider may then access the passkey. This may differ depending on the provider. Synced passkeys do not support attestation. Examples:
44
+- **Synced passkeys**: The private key is created by the hardware security module (HSM) and encrypted on the local device. This encrypted key is then synced and stored in the cloud passkey provider. Other devices authenticated with the passkey provider may then use the passkey. This may differ depending on the provider. Synced passkeys do not support attestation. Examples:
4545
- [Apple iCloud Keychain](https://support.apple.com/en-us/102195)
4646
- [Google Password Manager](https://security.googleblog.com/2022/10/SecurityofPasskeysintheGooglePasswordManager.html)
4747
⋯ 35 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 03:46 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.