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.
- Enter an application Name and select the single-tenant supported account type for your external tenant.
- Select Register.
- On Overview, record the Application (client) ID and Directory (tenant) ID.
- Record the tenant subdomain if your selected SDK requires it. Configure service API URLs
with your tenant-verified custom domainas 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:
- Verify and configure the custom URL domain in the external tenant.
- 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
@@ -3,7 +3,7 @@ title: Configure an app for Embedded native authentication description: Register an application, enable native authentication, associate a user flow, and prepare permissions and policies for direct API calls. ms.topic: how-to ms.custom: msecd-doc-authoring-1030-ms.date: 11/13/2026+ms.date: 11/17/2026 ai-usage: ai-generated #customer intent: As an application developer, I want to configure a direct API application so that I can run native authentication journeys in my external tenant. ---@@ -23,7 +23,7 @@ Configure your application registration and user flow before calling the Native - An [external tenant](../external-id/customers/how-to-create-external-tenant-portal.md). - 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.-- A [tenant-verified custom URL domain](../external-id/customers/how-to-custom-url-domain.md) configured for the authentication service.+- For browser-based apps, such as SPAs, a [tenant-verified custom URL domain](../external-id/customers/how-to-custom-url-domain.md) configured for the authentication service. An application owner can manage the registration's authentication settings. For delegated access, use [application-scoped permissions](~/identity/role-based-access-control/delegate-app-roles.md) rather than assigning a tenant-wide administrator role solely for this task. @@ -36,13 +36,15 @@ Create the registration in the external tenant that owns the customer accounts. 1. Enter an application **Name** and select the single-tenant supported account type for your external tenant. 1. Select **Register**. 1. On **Overview**, record the **Application (client) ID** and **Directory (tenant) ID**.-1. 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](#configure-the-api-authority).+1. Record the tenant subdomain if your selected SDK requires it. Configure service API URLs as described in [Configure the API authority](#configure-the-api-authority). For registration details, see [Register an application](quickstart-register-app.md). 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 your tenant-verified custom domain for all service API calls in 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.+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 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 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](../external-id/customers/how-to-custom-url-domain.md) in the external tenant. 1. Configure the application or SDK to use that domain for authorization challenges, native interaction operations, authorization continuation, and token exchange.@@ -50,7 +52,7 @@ Use your tenant-verified custom domain for all service API calls in the current 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](concept-native-authentication-cors.md#proxy-contract). -Android and iOS apps using native HTTP transports call the service authority directly. They don't need CORS configuration or a CORS proxy.+Android and iOS apps using native HTTP transports call their configured service authority directly. A 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 