Microsoft Entra ID
AuthenticationEnable Authenticator Passkey
In brief
The documentation now separately states that Android users can register attested passkeys through a cross-device registration flow, while iOS users register them directly in the Authenticator app.
What Entra admins need to know
No administrator action is required.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
On iOS, users can only register attested passkeys directly in the Authenticator app. OnSeparately, on Android, users can also register attested passkeys by using a cross-device registration flow.
Authenticator AAGUIDs
@@ -88,7 +88,7 @@ When attestation is enabled, Microsoft Entra ID verifies the legitimacy of the p > [!NOTE] > 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/). -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.+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. ## Authenticator AAGUIDs