Microsoft Entra ID
Authentication

Native Authentication Flow

In brief

The documentation now requires a tenant-verified custom domain for browser-based apps, such as SPAs, but not for non-browser clients such as iOS and Android apps.

What Entra admins need to know

Verify that browser-based apps use a configured tenant-verified custom domain; this requirement does not apply to the listed non-browser clients.

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.

The initial authorization challenge request contains the application ID, requested scopes, and optional claims. If authentication is required, its 401 InsufficientAuthorization response contains a continuation token and journey links. This response is an invitation to interact, not a failed password check.

Use the configured tenant-verified custom domain and tenant GUIDservice authority consistently for every service API call. This authority applies to authorization, native interactions, and token exchange. The Native Authentication API V2 requires a tenant-verified custom domain for browser-based apps, such as SPAs, but not for non-browser clients, such as iOS and Android apps using native HTTP transports. The examples use a custom domain and tenant GUID. See Operations and authority.

Sign-in, sign-up, and password reset all return to authorization when the service returns state: continue. Your application posts the latest continuation token to the returned continue link. It then exchanges the resulting authorization code at the token endpoint.

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…