Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Passkeys in Microsoft Authenticator

This page's changes and edits · All guidance changes

Microsoft's edit ·

Publish Ignite 2026 High Assurance documentation release (#15002)

Microsoft's commit message in MicrosoftDocs/entra-docs · commit d55e854 · +37 −1 lines · also on GitHub

Source wording view
⋯ 4 unchanged lines
55 ms.date: 10/02/2026
66 ms.reviewer: mjsantani, guptashi, tilarso
77 ms.collection: M365-identity-device-management
8 −ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-1013
8 +ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-108
99 ai-usage: ai-assisted
1010 # 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.
1111 ---
⋯ 147 unchanged lines
159159
160160 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.
161161
162 +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).
163 +
162164 ### Workarounds for an authentication strength Conditional Access policy loop
163165
164166 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:
⋯ 77 unchanged lines
242244
243245 > [!NOTE]
244246 > 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.
247 +
248 +<a id="identity-verified-onboarding-and-recovery-during-preview"></a>
249 +
250 +## Passkey registration during Identity-verified onboarding and recovery (preview)
251 +
252 +The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.
253 +
254 +Before deploying identity-verified onboarding or recovery with passkey setup:
255 +
256 +- **Authenticator app:** Before registering device-bound passkeys in Microsoft Authenticator, meet the requirements for your platform and enable Authenticator as a passkey provider.
257 +
258 + - **Android:** Install Microsoft Authenticator version **6.2610.7075** or later. Earlier versions can't complete passkey setup during onboarding or recovery.
259 +
260 + Enable Authenticator as a passkey provider:
261 +
262 + 1. Open device **Settings** and search for **Passkey**, or open **Passwords & accounts**.
263 + 1. Under **Additional providers**, enable **Authenticator**.
264 +
265 + 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).
266 +
267 + - **iOS:** Install Microsoft Authenticator version **6.8.58** or later. Earlier versions can't complete passkey setup.
268 +
269 + Enable Authenticator as a passkey provider:
270 +
271 + 1. On **iOS 18**, open **Settings** > **General** > **AutoFill & Passwords**. On **iOS 17**, open **Settings** > **Passwords** > **Password Options**.
272 + 1. Turn on **AutoFill Passwords and Passkeys**.
273 + 1. Under **AutoFill From**, select **Authenticator**.
274 +
275 + For detailed instructions, see [Register passkeys in Authenticator](how-to-register-passkey-authenticator.md).
276 +- 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.
277 +
278 +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.
279 +
280 +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).
245281
246282 ## Register a passkey in Authenticator
247283
⋯ 18 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 today 17:49 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 17:57 UTC · 272 of 275 readable · 270 fully read · documentation 469/469 current