Miscellaneous topics that do not fit into specific categories.
This behavior is a limitation of how the embedded browser in the older iOS app integrates with Microsoft Entra ID and modern WebAuthn/FIDO2 flows.
Passkey/FIDO2 and Microsoft Authenticator-based passwordless sign-in rely on full WebAuthn support and specific platform integrations that are guaranteed only in supported combinations of OS + browser + app framework. Microsoft explicitly documents that:
- Passkey (FIDO2) support depends on the browser/host surface; the recommended approach for apps is to use the system browser or supported web authentication sessions rather than a custom/legacy embedded browser.
- For iOS apps, FIDO2 is supported when using MSAL with ASWebAuthenticationSession or broker integration (Microsoft Authenticator / Intune Company Portal). If an app uses its own legacy embedded web view, FIDO2/passkey options may not be available even though other methods (password, Temporary Access Pass) still work.
In Safari on the same iPad, the full, supported WebAuthn surface is available, so all configured methods (FIDO2 security keys, Authenticator passkeys, etc.) appear. Inside the older embedded browser, only methods that do not require full WebAuthn/platform integration (password, TAP) are exposed.
To use passwordless methods such as FIDO2, Microsoft Authenticator passkeys, or device-bound passkeys on iOS:
- Use a supported browser (Safari, Edge, Chrome, etc.) or
- Use an app that authenticates via MSAL with ASWebAuthenticationSession or broker integration, rather than a custom embedded browser.
If the older iPad app cannot be updated to use a supported authentication surface, it will be limited to the methods that currently appear (password and TAP) even though the same account supports stronger methods elsewhere.
References: