Microsoft Entra ID
Authentication

Native Authentication Challenge Types

In brief

The documentation article covering native authentication flows, challenge types, capabilities, and fallback behavior was deleted.

What Entra admins need to know

No administrator action is specified.

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.

deleted file mode 100644

title: Native authentication challenge types description: Learn how apps that use native authentication notify native authentication API about the authentication flows that they support. manager: dougeby ms.service: identity-platform ms.subservice: external ms.topic: concept-article ms.date: 02/27/2026

#Customer intent: As a dev, devops, I want to learn about native authentication challenge types and capabilities, so that I can use them to notify native authentication API about the authentication flows that my app supports.

Native authentication challenge types and capabilities

[!INCLUDE applies-to-external-only]

Native authentication supports two authentication flows:

  • Email with one-time passcode (OTP)
  • Email and password with support for self-service password reset (SSPR)

A client app that uses native authentication to sign in users can use either authentication flow. To make successful calls to the native authentication API, the app must declare which authentication flows and capabilities it supports. The native authentication API enables client apps to advertise their supported challenge types and capabilities using predefined values.

Challenge types

Challenge types are predefined values that client apps include in their requests to declare which authentication flows they support to the native authentication API.

The following table contains the supported challenge type values:

[!INCLUDE native-auth-challenge-type]

New values are added when native authentication supports new authentication methods.

Challenge type values for native authentication flows

The following table summarizes the challenge type values an app should use for various authentication flows:

Sign-up flowSign-in flowSSPR
Email with passwordoob, password, and redirectoob, password, and redirectoob and redirect
Email OTPoob and redirectoob and redirectNot applicable

Important notes:

  • Apps that use the native authentication API directly must include the redirect challenge type when declaring their supported challenge types.
  • Apps that use native authentication SDKs (Android, iOS, or JavaScript) don't need to include the redirect challenge type as the SDK automatically includes it.

Capabilities

In addition to challenge types, client apps can specify a list of capabilities. While challenge_type defines which authentication methods the app supports, capabilities indicate which additional flows the client app can handle and what UI experiences it can provide to users.

Native authentication API supports the following capabilities:

  • mfa_required: Indicates that the client app can handle multifactor authentication (MFA) flows inline, including calling the /introspect, /challenge, and /token endpoints in sequence and displaying the appropriate UI for users to complete MFA challenges when required. Advertise this capability if your app integrates inline MFA scenarios such as risk-based MFA driven by Conditional Access authentication context (for example, third-party account takeover protection integrations that use a Web Application Firewall in front of native authentication endpoints). If the app doesn't advertise mfa_required and MFA is required, the native authentication API initiates a web fallback.
  • registration_required: The client can handle strong authentication registration: it can call the registration APIs and show UI to guide users through registering strong authentication methods.

Behavior for unsupported challenge types and capabilities

The following table summarizes the behavior when either the native authentication API or the client app doesn't support a given challenge type or capability:

ScenarioBehavior
Client app includes unsupported challenge typeNative authentication API returns an error and treats the request as invalid.
Client app includes unsupported capabilityNative authentication API returns an error and treats the request as invalid.
Client app fails to include a required challenge typeThe app doesn't support a challenge type configured by the administrator. Native authentication API initiates a web fallback.
Client app fails to include a required capabilityThe app functions normally if MFA or strong authentication registration is not required. If these capabilities are required but not supported, native authentication API initiates a web fallback to complete the authentication flow.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…