Microsoft Entra External ID
Authentication

Choose Authentication Approach

In brief

The documentation now states that V2 requires a tenant-verified custom domain for browser-based apps and recommends planning a CORS proxy or edge policy. BYO UX guidance now emphasizes independently hosted, reusable authentication websites.

What Entra admins need to know

Administrators supporting browser-based apps must provide the verified domain and plan the required CORS approach.

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.

Evaluate Embedded native authentication when you want authentication interactions integrated into your application's interface. Your team builds the screens and handles credentials, state, and integration. Confirm platform and SDK support in the native authentication overview. For method and journey support, use the methods and journeys comparison and browser fallback requirements.

The current Native Authentication API V2 requires a tenant-verified custom domain for all service API calls. For a browser-based apps, such as single-page application (SPA)applications (SPAs), alsoto help protect against cross-site request forgery (CSRF). Also plan a cross-origin resource sharing (CORS) proxy or edge policy.policy for cross-origin browser calls. Non-browser clients, such as Android and iOS apps using native HTTP transportstransports, don't needrequire a custom domain or CORS or a CORS proxy.configuration. Enable the required methods in your tenant and test the journeys your app needs.

Bring Your Own UX

EvaluateWith Bring Your Own UX (BYO UX), you control and operate the authentication website instead of using Microsoft-hosted pages. Unlike embedded native authentication, the authentication website runs separately from your applications and can serve multiple apps.

Choose BYO UX when you want more control over the presentation and user experience than Microsoft-hosted custom branding provides, or if you want a separate authenticationsign-in website with its own designyou can share across applications and release cycle, whether for one application or several.update independently of their releases. Your team hoststakes responsibility for hosting and managesmaintaining the page while Microsoft Entra External ID verifies credentials and applies policy. The site uses HTTPS on a tenant-verified domain; all service API calls also use a tenant-verified custom domain.

Applications that use BYO UX start sign-in with Microsoft Entra External ID through standard browser-based integration patterns. BYO UX guidance focuses on implementing the authentication website, including its API calls and CORS proxy. An existing browser session can satisfy authentication without presenting the website.

For architecture, requirements, and implementation guidance,details, see the Bring Your Own UX overview.

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…