Microsoft Entra External ID
Authentication

Plan a Deployment

In brief

The guide now presents a six-step Microsoft Entra External ID deployment plan, with updated wording, authentication-approach guidance, diagram, links, and metadata.

What Entra admins need to know

Administrators can use the refreshed guide to plan external tenants, authentication, application registration, sign-in integration, and security.

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.

Planning for customer identity and access managementPlan a Microsoft Entra External ID deployment

[!INCLUDE applies-to-external-only]

Microsoft Entra External ID adds customer identity and access management (CIAM) to your app on the Microsoft Entra platform, so you get consistent app integration, tenant management, and operations across workforce and customer scenarios.

This article is a decision-making[!INCLUDE authentication-approaches]

Use this guide for theto plan your deployment in six planning steps. Each section summarizes the key choices and links to the canonical how-tossetup instructions and reference docs.documentation.

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal.png" alt-text="Diagram showing theof six setup steps assteps: create a horizontal flow: create an external tenant, choose authentication, register an authentication approach, register your application,app, integrate a sign-inuser flow, secure your sign-in, and customize your sign-in.":::

Jump to a step for details, or go straight to the How-to guides.

Step How-to guides
Step 1: Create an external tenant • Create an external tenant
• Or start a free trial
Step 2: Choose an authentication approach • Choose an authentication approach
Step 3: Register your application • Register your application
Step 4: Integrate a sign-in flow with your app • Create a user flow
• Add your app to the user flow
Step 5: Secure your sign-in • Add multifactor authentication (MFA)
• Review security and governance
• Integrate third-party bot protection (native authentication)
• Integrate third-party ATO protection (native authentication)
Step 6: Customize your sign-in • Customize branding (browser-delegated)Microsoft-hosted pages)
• Use a custom URL domain
• Add custom authentication extensions

Step 1: Create an external tenant

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal-step-1.png" alt-text="Diagram showing the setup flow with step 1, create an external tenant, highlighted.":::

Your external tenant is the resource where you register apps and manage customer identities, separate from your workforce tenant. When you create it, you choose its geographic location and domain name. If you currently use're migrating from Azure AD B2C, your existing B2C tenants aren't affected; seereview the Azure AD B2C migration planning guidance.

[!INCLUDE active-directory-b2c-end-of-sale-notice.md] For other identity deployments, review user migration guidance.

The directory contains both admin accounts and customer accounts. Customers usually self-register; you can also create local accounts. Customer accounts have a restricted default permission set and can't see other users, groups, or devices.

Step 2: Choose an authentication approach

Decide how to build the sign-in experience before you register your app. This choice drives the rest of your integration.

  • Browser-delegatedMicrosoft-hosted authentication — Microsoft hosts the sign-in page;page, and your app redirects users to it. Broad platform support, system-browser SSO, lower maintenance.You can apply company branding or application-specific branding themes.
  • NativeEmbedded native authentication — yourYour app hostspresents the sign-in UIinterface and calls MSALan SDK or the nativeNative Authentication API. Your team manages the interface and integration.
  • Bring Your Own UX (BYO UX) — Your team hosts a separate authentication API directly. Full UI control, more developmentwebsite within a browser-based authorization flow. Microsoft Entra External ID applies authentication policies and security responsibility.verifies credentials.

How to choose an authentication approach

Step 3: Register your application

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal-step-3.png" alt-text="Diagram showing the setup flow with step 3, register your application, highlighted.":::

Register your app in your external tenant to establish a trust relationship with Microsoft Entra ID. The settings you configure depend onits application identity. Follow the registration guide for your platform and authentication approach you chose in Step 2:approach.

Setting Browser-delegatedMicrosoft-hosted NativeEmbedded native authenticationBYO UX
Redirect URI Required (matchesRegister a callback URI for your app.Configure the redirect required by your platform or browser integration, separately from direct native code redemption.Register a web-type redirect URI, including for public clients.
Client typeChoose the registration for your app's sign-in callback)platform. Required only as a web fallbackPublic client; enable public client flows.Public or confidential client.
Public client flowsService API authority Not requiredDefault tenant domain or a custom URL domain. EnabledTenant-verified custom domain for the current API.Tenant-verified custom domain for API calls.
Native authenticationIntegration setup Not requiredConfigure hosted sign-in. EnabledEnable native authentication for the app.Use Microsoft Graph beta to configure your self-hosted authentication page.

After you registerregistration, configure your application and tenant identifiers. Keep confidential-client credentials on the app, update your code with the application (client) ID, tenant subdomain, and (if applicable)server; don't place client secret.secrets in mobile apps or browser code.

How to register your application

Step 4: Integrate a sign-in flow with your app

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal-step-4.png" alt-text="Diagram showing the setup flow with step 4, integrate a sign-in flow with your app, highlighted.":::

Create a sign-up and sign-in user flow that defines the sign-in methods, attributes to collect, and identity providers for your app. You createUse the user flowauthentication support matrix to check which configured features are available through your integration.

For the same way for both authentication approaches;Native Authentication API integrations, follow the difference is how your app drives it at runtime:attribute collection contract.

Browser-delegatedNative authentication
Runtime behaviorApp redirects to the Microsoft-hosted sign-in pageApp calls MSAL native authentication APIs from your own UI
Supported app typesWeb, SPA, mobile, daemonMobile, SPA
Federated identity providers (social, external IdPs)SupportedNot supported — use browser-delegated if needed
Company brandingApplies to Microsoft-hosted pagesManaged in your app's UI/localization
Attribute collectionConfigured in the user flowConfigured in the user flow; submitted via the MSAL user attribute builder

Plan your user flow

  • Attributes to collect. Decide which built-in attributes you need and whether you need custom attributes.
  • Terms and conditions consent. Use custom attributes to capture consent with links to your terms and privacy policies.
  • Token claims. Add required attributes to the token if your app depends on them.
  • Sign-in methods. Local accounts (email OTP, email + password) work with both approaches. FederatedConfigure local account methods and identity providers (for each user flow. With Microsoft-hosted authentication, configured federated providers can include Google, Facebook, Apple, another Microsoft Entra tenant, or custom OpenID Connect (OIDC)) require browser-delegated authentication.. Federation isn't supported through the Native Authentication API. Confirm method and journey availability in the methods and journeys comparison.

How to integrate a user flow with your app

Step 5: Secure your sign-in

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal-step-5.png" alt-text="Diagram showing the setup flow with step 5, secure your sign-in, highlighted.":::

EveryPlan MFA and review security for your customer-facing app needs MFAapps. Configure tenant policies and a baseline security review. Native authentication apps have extra work: becauseprotect application sessions, tokens, and any credentials or state your app isintegration handles. Assign ownership for the exposed sign-in surface, you front it with a web application firewall (WAF)interface, integration, and hosting components your team operates. For responsibility boundaries, see authentication integration responsibilities. Browser-delegated apps inherit Microsoft's platform-level protections on the hosted sign-in pages.

Step 6: Customize your sign-in

:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal-step-6.png" alt-text="Diagram showing the setup flow with step 6, customize your sign-in, highlighted.":::

Customize the sign-in look and feel and extend it with your own business logic. With native authentication, your app ownsYou can configure Microsoft-hosted pages, manage the UI, so the Microsoft Entra company-branding feature doesn't apply — manage visuals and localizationinterface in your app code.with Embedded native authentication, or host your own page with BYO UX.

  • Customize branding (browser-delegated only)Microsoft-hosted pages). Apply your logo, colors, and language strings to the Microsoft-hosted sign-in pages. See Customize the sign-in look and feel.
  • Use a custom URL domain. ReplaceAll service API calls for the default ciamlogin.com host with your owncurrent Native Authentication API and BYO UX use a tenant-verified custom domain. Also a prerequisite for native authentication bot/ATO protection in Step 5. See Custom URL domain.
  • Add custom authentication extensions. Extend the flow with server-side logic. Token-issuance extensions work with both approaches; attribute-collection extensions are browser-delegated only.Event availability can differ by approach and API or SDK version. See Custom authentication extensions.

Next steps

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…