Microsoft Entra External ID
Authentication

Choose an Authentication Approach

In brief

The documentation now compares Microsoft-hosted authentication, embedded native authentication, and Bring Your Own UX. It explains interface hosting, team ownership, common policy foundations, and how to evaluate application requirements and supported journeys.

What Entra admins need to know

Administrators and architects can use the updated comparison to choose an authentication experience and ownership model for each customer-facing application. No required action is stated.

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.

Microsoft Entra External ID authentication approaches overview

Choose an authentication approachhow 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.

[!INCLUDE applies-to-external-only]

Browser-delegated authentication and native authentication are two sign-in approaches in Microsoft Entra External ID that define how your customer-facing app handles the authentication experience. Both approaches are fully supported, but they differ in user experience, development effort, and security model. Understanding these differences helps you choose the

Authentication approach that best fits your app.

With browser-delegated authentication, your app redirects users to a Microsoft-hosted sign-in page in a system browser or embedded web view. Microsoft Entra handles the entire authentication flow, and your app receives tokens after sign-in completes. This approach requires minimal code and offers built-in branding customization.

With native authentication, you build the sign-in UI experience directly into your app by using the Microsoft Authentication Library (MSAL) SDK or the native authentication API. Users never leave your app. You control every aspect of the UI, but your team is responsible for building and maintaining the authentication experience.

When to use browser-delegated authenticationoptions

Browser-delegated authentication is the better fit when:

  • Your app can accommodate a browser redirect during sign-in without disrupting the user experience.
  • You prefer lower implementation and maintenance effort. Microsoft manages security updates and new features automatically.
  • You want to support the broadest range of platforms and languages with less code.

For specific feature availability, see the feature comparison.

When to use native authentication

Native authentication is the better fit when:

  • You need full control over the sign-in UI so it blends seamlessly into your app.
  • A browser redirect would disrupt the user experience for your target platform.
  • Your organization operates both the app and the authorization server, and your users perceive them as a single entity.
  • Your development team can take on the additional implementation effort and ongoing maintenance.

For specific feature availability, see the feature comparison.

Feature comparison

The following table shows which features are available in each approach.

FeatureBrowser-delegated authenticationNative authentication
Sign up and sign in with email one-time passcode (OTP):heavy_check_mark::heavy_check_mark:
Sign up and sign in with email and password:heavy_check_mark::heavy_check_mark:
Sign in with email and password can use username (alias) and password:heavy_check_mark::heavy_check_mark:
Self-service password reset (SSPR):heavy_check_mark::heavy_check_mark:
Custom claims provider:heavy_check_mark::heavy_check_mark:
Multifactor authentication with email one-time passcode (OTP):heavy_check_mark::heavy_check_mark:
Multifactor authentication with SMS one-time passcode (OTP):heavy_check_mark::heavy_check_mark:
Social identity provider sign-in (Apple, Facebook, and Google)1:heavy_check_mark::heavy_check_mark:
Single sign-on (SSO)2:heavy_check_mark::heavy_check_mark:

1 Even with native authentication, social sign-in still uses a browser window for the identity provider step.

2 Native authentication supports SSO for embedded web views only. Cross-app SSO through system browsers isn't available with native authentication.

Supported languages and frameworks

The following languages and frameworks are supported for each approach.

Approach Supported languages and frameworksHow required authentication steps are presentedWhat your team controls
Browser-delegatedMicrosoft-hosted authentication
  • ASP.NET Core
  • Android (Kotlin, Java)
  • iOS/macOS (Swift, Objective-C)
  • JavaScript
  • React
  • Angular
  • Node.js
  • Python
  • Java
On Microsoft-hosted pages reached through a browser redirect.
Company branding: Tenant-wide logos, text, and styling. Branding themes: Customization for selected applications.
NativeEmbedded native authentication
  • Android (Kotlin, Java)
  • iOS/macOS (Swift, Objective-C)
  • Web (JavaScript, React, Angular)
For other languagesIn authentication screens your app implements.
Screens and platforms, you can use the native authentication API.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.

Security considerationsApplication and audience requirements

Browser-delegatedMatch each requirement to a candidate, then verify its journeys and integration requirements.

RequirementApproach to evaluateVerification or next step
Microsoft-managed authentication ispagesMicrosoft-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 appEmbedded 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 cycleBring Your Own UX.Review the website and domain requirements for one or more secure option. Microsoftapplications. Plan the website's API and browser integration.
Different interaction requirements across applicationsCombine approaches.Evaluate each application's interface, integration, session, and journey requirements.

[!INCLUDE authentication-approaches-preview]

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 surface, which reduceswith 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 app's exposure to phishingteam configures authentication policies, integrates the application, and credential-harvesting attacks.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 development team shares security responsibility with Microsoft Entra. Yourmaintains app screens and state handling. With BYO UX, your team must follow security best practiceshosts 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 handling user credentials. Before you choosedeploying fixes to the components your organization operates.

Feature comparison

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

RequirementCoverage to review
Sign-up, sign-in, and password resetConfirm method and journey availability for your approach. For tenant configuration, see identity providers and authentication methods.
Additional verificationConfirm method availability and factor registration requirements in the multifactor authentication (MFA) guidance.
Session behaviorReview Conditional Access, sign-in frequency, and single sign-on. Plan sign-out for each app's session.
Custom business logicConfirm 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, discussconfirm platform and SDK requirements in the security implicationsnative authentication overview. For BYO UX, plan a self-hosted browser authorization flow with your app's business owner and development team.a web-type redirect URI.

Next stepsRelated content

After you decide on an approach, register your app to continue your integration, or return to the planning guide for the full sequence of steps:

Browser-delegated authentication:

Native authentication:

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…