Passkeys in Microsoft Authenticator
Observed content change
May need admin actionCheck whether new requirements apply to your setup.
Changed article references · 5 added · 0 removed
- Added link: Passkey registration during Identity-verified onboarding and recovery (preview)
#identity-verified-onboarding-and-recovery-during-preview - Added link: enrollment-method and app-deployment requirements
../conditional-access/policy-require-identity-verification#android-work-profile-compatibility-during-preview - Added link: work-profile compatibility and deployment prerequisites
../conditional-access/policy-require-identity-verification#android-work-profile-compatibility-during-preview - Added link: Link to Windows compatibility
../conditional-access/policy-require-identity-verification#link-to-windows-compatibility - Added link: Register passkeys in Authenticator
how-to-register-passkey-authenticator
[added: 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).]
Before: No saved wording on this side.
After: 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).
[added: The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.]
Before: No saved wording on this side.
After: The minimum Authenticator app versions listed below apply to identity verification step-up, onboarding, and recovery.
[added: Before deploying identity-verified onboarding or recovery with passkey setup:]
Before: No saved wording on this side.
After: Before deploying identity-verified onboarding or recovery with passkey setup:
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: 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.]
Before: No saved wording on this side.
After: 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.
[added: For step-up or recovery initiated from a mobile app, also review Link to Windows compatibility.]
Before: No saved wording on this side.
After: For step-up or recovery initiated from a mobile app, also review Link to Windows compatibility.
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- today 08:42 UTC
- Source update metadata
- today 08:34 UTC
- First observed on this installation
- 5 Oct 17:50 UTC
- Last successful check
- today 08:42 UTC
- Next check due
- today 14:42 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.