Microsoft Entra ID
Authentication

Native Authentication API V2 reference

In brief

The reference now identifies the API as V2 and explains that tenant-verified custom domains are required for browser-based apps, such as SPAs, but not for native iOS or Android clients using native HTTP transports.

What Entra admins need to know

Admins can determine whether their applications need a tenant-verified custom domain for Native Authentication API V2.

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.

Native authenticationAuthentication API v2V2 reference

[!INCLUDE applies-to-external-only]

  • An external tenant and an application configured for public client and native authentication flows. See Configure an application.
  • A user flow associated with the application.
  • AFor browser-based apps, such as SPAs, a tenant-verified custom URL domain configured for all service API calls.
  • The delegated permissions and consent required by your target resource, if you request access to an API.
  • For SPAs with Embedded native authentication and BYO UX websites, a proxy or edge policy that implements the browser proxy requirements.

Operations and authority

The examples use https://{custom_domain}/{tenant}, where custom_domain is a tenant-verified authentication domain, such as login.contoso.com, and tenant is its Directory (tenant) ID, a GUID. client_id is the Application (client) ID. AllIn these examples, all service API call URLs use this custom domain, including authorization challenges and token exchange.

The Native Authentication API V2 requires a tenant-verified custom domain for browser-based apps, such as SPAs, to help protect against cross-site request forgery (CSRF). Non-browser clients, such as iOS and Android apps using native HTTP transports, don't require a custom domain. An embedded browser or webview isn't a native HTTP transport. BYO UX remains browser-based and requires a tenant-verified custom domain. See Configure the API authority.

Except for the initial authorization request and token exchange, use the URL advertised by the current response. Method IDs are opaque. Resolve relative links against the configured authority origin, validate the destination, and retain the returned path and query unchanged.

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…