Microsoft Entra ID
Authentication

Native Authentication Configure App

In brief

Browser-based apps, including SPAs, require a tenant-verified custom domain for Native Authentication API V2. Android and iOS apps using native HTTP transports can use their configured service authority without a custom domain.

What Entra admins need to know

Ensure a verified custom domain is configured for browser-based integrations; native mobile clients do not require one.

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.

  • An external tenant.
  • An account authorized to create or manage the application registration.
  • Access to create or select the user flow and associate the application with it. Coordinate policy changes and consent with the appropriate tenant administrator.
  • AFor browser-based apps, such as SPAs, a tenant-verified custom URL domain configured for the authentication service.

An application owner can manage the registration's authentication settings. For delegated access, use application-scoped permissions rather than assigning a tenant-wide administrator role solely for this task.

  1. Enter an application Name and select the single-tenant supported account type for your external tenant.
  2. Select Register.
  3. On Overview, record the Application (client) ID and Directory (tenant) ID.
  4. Record the tenant subdomain if your selected SDK requires it. Configure service API URLs with your tenant-verified custom domain as described in Configure the API authority.

For registration details, see Register an application. The client ID identifies this public client; it isn't a secret. Don't create or embed a client secret for these direct API requests.

Configure the API authority

Use yourThe Native Authentication API V2 requires a tenant-verified custom domain for all service API calls inbrowser-based apps, such as SPAs, to help protect against cross-site request forgery (CSRF). Non-browser clients, such as Android and iOS apps using native HTTP transports, don't require a custom domain. An embedded browser or webview isn't a native HTTP transport.

For a custom-domain integration, the current native authentication integration. The authority has the form https://{custom_domain}/{tenant}, where custom_domain is the verified authentication domain, such as login.contoso.com, and tenant is the Directory (tenant) ID, a GUID. Configure it as follows:

  1. Verify and configure the custom URL domain in the external tenant.
  2. Configure the application or SDK to use that domain for authorization challenges, native interaction operations, authorization continuation, and token exchange.

For SPAs with Embedded native authentication and BYO UX websites, configure a cross-origin resource sharing (CORS) proxy or edge policy for cross-origin browser API calls. A proxy address is a transport setting, not a replacement service authority. Its upstream calls still use the tenant-verified custom domain and tenant GUID. See the provider-neutral proxy requirements.

Android and iOS apps using native HTTP transports call thetheir configured service authority directly. TheyA custom domain is optional for these clients, and they don't need CORS configuration or a CORS proxy. Use your selected SDK's documented authority configuration. Validate returned links against that authority and preserve their paths, versions, and query parameters.

Enable public client and native authentication flows

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…