Microsoft Entra ID
Authentication

Embedded native authentication CORS concepts

In brief

The documentation now scopes the custom-domain and CORS guidance to browser integrations using Embedded native authentication or BYO UX. It also states that non-browser clients using native HTTP transports don't require a custom domain.

What Entra admins need to know

Admins can distinguish browser integration requirements from non-browser client requirements when configuring Native Authentication API access.

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.

Embedded native authentication CORS concepts

Cross-Origin Resource Sharing (CORS) controls whether browser code can read a response from another origin. Single-page applications (SPAs) with Embedded native authentication and Bring Your Own UX (BYO UX) websites need a proxy or edge CORS policy for cross-origin calls to the Native Authentication API calls.API.

Android and iOS apps that call the API through native HTTP transports don't need CORS or a CORS proxy. They call the configured service authority directly. The requirements in this article apply to browser requests, not those native API calls.

Service authority and proxy transport

CurrentFor the browser integrations covered in this article, Embedded native authentication and BYO UX service API URLs use a tenant-verified custom authentication domain and the tenant GUID:

https://<tenant-verified-custom-domain>/<tenant-GUID>

With that local prefix, a service path of `/<tenant-GUID>/api/v2.0/signin/start` maps to `/api/api/v2.0/signin/start`. The first `/api` is the proxy prefix; the second belongs to the service path. OAuth requests similarly map to `/api/oauth2/v2.0/authorize-challenge` or `/api/oauth2/v2.0/token`.

DonFor these browser integrations, don't configure a `ciamlogin.com` address as the application's service API authority. Platform-managed origin routing behind a verified custom domain doesn't replace this requirement. Non-browser clients using native HTTP transports don't require a custom domain. See [Configure the API authority](how-to-native-authentication-configure-app.md#configure-the-api-authority).

## Proxy contract
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…