Edit

Microsoft Entra External ID authentication approaches overview

Choose how your customer-facing application presents Microsoft Entra External ID authentication. Compare where the interface runs, what your team maintains, and which capabilities you need. Different applications can use different approaches.

Applies to: Green circle with a white check mark symbol that indicates the following content applies to external tenants. External tenants (learn more)

Authentication approach options

Approach How required authentication steps are presented What your team controls
Microsoft-hosted authentication On Microsoft-hosted pages reached through a browser redirect. Company branding: Tenant-wide logos, text, and styling. Branding themes: Customization for selected applications.
Embedded native authentication In authentication screens your app implements. Screens and their integration with your app.
Bring Your Own UX (BYO UX) On a separate authentication website your team hosts. The website, its presentation, and its integration.

Common policy foundation

All approaches use user flows and authentication policies configured in Microsoft Entra External ID. External ID provides the authentication service; the approaches differ in how the interface is hosted and integrated.

For each application, consider your sign-up, sign-in, account recovery, identity provider, and policy requirements. Confirm that your chosen integration supports those journeys by using the methods and journeys comparison. Feature availability can differ by approach and API or SDK version.

Application and audience requirements

Match each requirement to a candidate, then verify its journeys and integration requirements.

Requirement Approach to evaluate Verification or next step
Microsoft-managed authentication pages Microsoft-hosted authentication. Review company branding, application-specific themes, and sign-up and sign-in availability. Plan the app integration and presentation settings.
Authentication screens integrated into your app Embedded native authentication. Review platform support and method availability. Plan the app screens and authentication-state handling.
An authentication website with its own UI and release cycle Bring Your Own UX. Review the website and domain requirements for one or more applications. Plan the website's API and browser integration.
Different interaction requirements across applications Combine approaches. Evaluate each application's interface, integration, session, and journey requirements.

Important

The Native Authentication API V2 and Bring Your Own UX (BYO UX) are in preview. The Native Authentication API V1 remains generally available. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to preview features.

Plan how your team updates the authentication interface:

  • Configure company branding and themes for Microsoft-hosted pages.
  • Release Embedded native authentication screens with your application.
  • Deploy a BYO UX website on its own release schedule.

Microsoft-hosted authentication

Evaluate Microsoft-hosted authentication when you want authentication pages hosted and managed by Microsoft. Configure company branding across the tenant, or use branding themes for selected applications. Your team integrates the app and configures policy.

Embedded native authentication

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 requires a tenant-verified custom domain for all service API calls. For a browser-based single-page application (SPA), also plan a cross-origin resource sharing (CORS) proxy or edge policy. Android and iOS apps using native HTTP transports don't need CORS or a CORS proxy. Enable the required methods in your tenant and test the journeys your app needs.

Bring Your Own UX

Evaluate BYO UX when you want a separate authentication website with its own design and release cycle, whether for one application or several. Your team hosts and manages 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, see the Bring Your Own UX overview.

Ownership and security responsibilities

For every approach, your team configures authentication policies, integrates the application, and protects application sessions and tokens. Plan accessibility, testing, monitoring, security updates, incident response, and release coordination for the components your team operates.

Microsoft maintains Microsoft-hosted sign-in pages. With Embedded native authentication, your team maintains app screens and state handling. With BYO UX, your team hosts and manages the website, proxy, and browser integration.

Protect any credentials, continuation state, and tokens your integration handles. Avoid exposing them in URLs or logs. Test what happens when policy requires another verification step and when a session expires. Identify the team responsible for deploying fixes to the components your organization operates.

Feature comparison

Use the authentication approach support matrix to compare methods, policies, and journeys.

Requirement Coverage to review
Sign-up, sign-in, and password reset Confirm method and journey availability for your approach. For tenant configuration, see identity providers and authentication methods.
Additional verification Confirm method availability and factor registration requirements in the multifactor authentication (MFA) guidance.
Session behavior Review Conditional Access, sign-in frequency, and single sign-on. Plan sign-out for each app's session.
Custom business logic Confirm which custom authentication extension events your integration supports.

Supported languages and frameworks

For Microsoft-hosted integration, see Samples by app type and language and Register an app. For Embedded native authentication, confirm platform and SDK requirements in the native authentication overview. For BYO UX, plan a self-hosted browser authorization flow with a web-type redirect URI.