Customer intent: As a Microsoft Entra administrator, I want to learn about Authenticator-specific requirements for passkeys so I can enable and suppo…
In brief
The documentation now requires specific Authenticator versions and passkey-provider settings for Android and iOS onboarding or recovery. Android Management API users should receive a Temporary Access Pass instead of completing passkey setup.
What Entra admins need to know
Before deployment, verify app versions and provider configuration; configure TAP issuance for applicable Android Management API journeys.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Passkeys on Android are used only from the profile where they're stored. If a passkey is stored in an Android Work profile, it's used from that profile. If a passkey is stored in an Android Personal profile, it's used from that profile. To make sure that users can access and use the passkey they need, users with both an Android Personal profile and an Android Work profile should create their passkeys in Authenticator for each profile.
For identity-verified onboarding and recovery during preview, users enrolled through Android Management API (AM API) should complete the journey with TAP issuance instead of being required to set up a passkey. See Passkey registration during Identity-verified onboarding and recovery (preview).
Workarounds for an authentication strength Conditional Access policy loop
Users can get in a loop when they try to add a passkey in Authenticator if a Conditional Access policy requires phishing-resistant authentication to access All resources (formerly 'All cloud apps'). For example:
Passkey registration during Identity-verified onboarding and recovery (preview)
The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.
Before deploying identity-verified onboarding or recovery with passkey setup:
Authenticator app: Before registering device-bound passkeys in Microsoft Authenticator, meet the requirements for your platform and enable Authenticator as a passkey provider.
Android: Install Microsoft Authenticator version 6.2610.7075 or later. Earlier versions can't complete passkey setup during onboarding or recovery.
Enable Authenticator as a passkey provider:
- Open device Settings and search for Passkey, or open Passwords & accounts.
- Under Additional providers, enable Authenticator.
Settings names vary by device manufacturer and Android version. For Android work profiles, also review the enrollment-method and app-deployment requirements.
iOS: Install Microsoft Authenticator version 6.8.58 or later. Earlier versions can't complete passkey setup.
Enable Authenticator as a passkey provider:
- On iOS 18, open Settings > General > AutoFill & Passwords. On iOS 17, open Settings > Passwords > Password Options.
- Turn on AutoFill Passwords and Passkeys.
- Under AutoFill From, select Authenticator.
For detailed instructions, see Register passkeys in Authenticator.
For Android users enrolled through Android Management API (AM API), configure onboarding and recovery to issue a Temporary Access Pass (TAP) at completion instead of requiring passkey setup. Those journeys remain supported, but a device-bound passkey created in the personal profile can't currently be used from the work profile.
For Android identity verification step-up with a device-compliance requirement, review work-profile compatibility and deployment prerequisites. The Android Management API (AM API) restriction and Enterprise Mobility Management API (EMM API) app-deployment requirements apply to that policy combination, not to all Authenticator use.
For step-up or recovery initiated from a mobile app, also review Link to Windows compatibility.
Register a passkey in Authenticator
After an admin enables passkeys in Authenticator, users can register a passkey in the app on their iOS or Android device.
@@ -5,7 +5,7 @@ ms.topic: how-to ms.date: 10/02/2026 ms.reviewer: mjsantani, guptashi, tilarso ms.collection: M365-identity-device-management-ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-1013+ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-108 ai-usage: ai-assisted # Customer intent: As a Microsoft Entra administrator, I want to learn about Authenticator-specific requirements for passkeys so I can enable and support them for my users. ---@@ -159,6 +159,8 @@ This section covers issues that users might see when they use passkeys in Authen Passkeys on Android are used only from the profile where they're stored. If a passkey is stored in an Android Work profile, it's used from that profile. If a passkey is stored in an Android Personal profile, it's used from that profile. To make sure that users can access and use the passkey they need, users with both an Android Personal profile and an Android Work profile should create their passkeys in Authenticator for each profile. +For identity-verified onboarding and recovery during preview, users enrolled through Android Management API (AM API) should complete the journey with TAP issuance instead of being required to set up a passkey. See [Passkey registration during Identity-verified onboarding and recovery (preview)](#identity-verified-onboarding-and-recovery-during-preview).+ ### Workarounds for an authentication strength Conditional Access policy loop Users can get in a loop when they try to add a passkey in Authenticator if a Conditional Access policy requires phishing-resistant authentication to access **All resources (formerly 'All cloud apps')**. For example:@@ -243,6 +245,40 @@ Here are some workarounds: > [!NOTE] > With any proposed workaround, users must also satisfy any Conditional Access policy that targets **Register security info** or they can't register the passkey. If you have other conditions set up with the **All resources** policies, they also must be met before users can register a passkey. +<a id="identity-verified-onboarding-and-recovery-during-preview"></a>++## Passkey registration during Identity-verified onboarding and recovery (preview)++The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.++Before deploying identity-verified onboarding or recovery with passkey setup:++- **Authenticator app:** Before registering device-bound passkeys in Microsoft Authenticator, meet the requirements for your platform and enable Authenticator as a passkey provider.++ - **Android:** Install Microsoft Authenticator version **6.2610.7075** or later. Earlier versions can't complete passkey setup during onboarding or recovery.++ Enable Authenticator as a passkey provider:++ 1. Open device **Settings** and search for **Passkey**, or open **Passwords & accounts**.+ 1. Under **Additional providers**, enable **Authenticator**.++ Settings names vary by device manufacturer and Android version. For Android work profiles, also review the [enrollment-method and app-deployment requirements](../conditional-access/policy-require-identity-verification.md#android-work-profile-compatibility-during-preview).++ - **iOS:** Install Microsoft Authenticator version **6.8.58** or later. Earlier versions can't complete passkey setup.++ Enable Authenticator as a passkey provider:++ 1. On **iOS 18**, open **Settings** > **General** > **AutoFill & Passwords**. On **iOS 17**, open **Settings** > **Passwords** > **Password Options**.+ 1. Turn on **AutoFill Passwords and Passkeys**.+ 1. Under **AutoFill From**, select **Authenticator**.++ For detailed instructions, see [Register passkeys in Authenticator](how-to-register-passkey-authenticator.md).+- For Android users enrolled through Android Management API (AM API), configure onboarding and recovery to issue a [Temporary Access Pass (TAP)](howto-authentication-temporary-access-pass.md) at completion instead of requiring passkey setup. Those journeys remain supported, but a device-bound passkey created in the personal profile can't currently be used from the work profile.++For Android identity verification step-up with a device-compliance requirement, review [work-profile compatibility and deployment prerequisites](../conditional-access/policy-require-identity-verification.md#android-work-profile-compatibility-during-preview). The Android Management API (AM API) restriction and Enterprise Mobility Management API (EMM API) app-deployment requirements apply to that policy combination, not to all Authenticator use.++For step-up or recovery initiated from a mobile app, also review [Link to Windows compatibility](../conditional-access/policy-require-identity-verification.md#link-to-windows-compatibility).+ ## Register a passkey in Authenticator After an admin enables passkeys in Authenticator, users can register a passkey in the app on their iOS or Android device. 