Passkeys in Microsoft Authenticator
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 6e28605 · +1 −1 lines · also on GitHub
⋯ 87 unchanged lines
8888
> [!NOTE]
8989
> For both iOS and Android, Authenticator attestation relies upon Apple and Google services to verify the authenticity of the Authenticator app. Heavy service usage can make passkey registration fail, and users might need to try again. If Apple and Google services are down, Authenticator attestation blocks registration that requires attestation until services are restored. To monitor the status of Google Play Integrity service, see [Google Play Status Dashboard](https://status.play.google.com/). To monitor the status of the iOS App Attest service, see [System Status](https://developer.apple.com/system-status/).
9090
91
−On iOS, users can only register attested passkeys directly in the Authenticator app. On Android, users can also register attested passkeys by using a cross-device registration flow.
91
+On iOS, users can only register attested passkeys directly in the Authenticator app. Separately, on Android, users can register attested passkeys by using a cross-device registration flow.
9292
9393
## Authenticator AAGUIDs
9494
⋯ 151 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 12 Oct 19:19 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.