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 |
| Step 6: Customize your sign-in | • Customize branding ( |
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.
- Create an external tenant in the Microsoft Entra admin center.
- Don't have a tenant yet? Start a free trial.
- Using
VSVisual Studio Code? Use the Microsoft Entra External ID extension(and its quickstart guide).
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-inpage;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 apphostspresents the sign-inUIinterface and callsMSALan SDK or thenativeNative 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 andsecurity responsibility.verifies credentials.
How to choose an authentication approach
- Choose an authentication approach — feature comparison and trade-offs.
Native authentication overviewEmbedded native authentication overview —detail if you're considering native.integration guidance for an interface in your app.
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 | BYO UX | ||
|---|---|---|---|
| Redirect URI | 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 type | Choose the registration for your app's |
Public or confidential client. | |
| Tenant-verified custom domain for API calls. | |||
| 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
- Find platform-specific guidance on the Samples by app type and language page.
- If your platform isn't listed, follow the general
register an applicationregister an application quickstart. - For Embedded native authentication app settings, see
How to enable native authenticationConfigure an app for Embedded native authentication.
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.
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
- Define custom attributes (if needed).
- Create the sign-up and sign-in user flow.
- Add your application to the user flow.
Wire upIntegrate your app code:Browser-delegated:Microsoft-hosted:followFollow a sample or quickstart for your app type.NativeEmbedded native authentication:followStart with thenative authentication overview and tutorialsapplication configuration guide, SDK quickstart, or Native Authentication API reference. Confirm platform and SDK coverage in the native authentication overview. For an existing V1 integration, use the V1 API reference and migration guide.- Bring Your Own UX: Review the Bring Your Own UX overview for architecture, requirements, and implementation guidance.
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.
- Enable MFA. Review available MFA methods.
- Review security and governance. Plan for Conditional Access, risk-based policies, and auditing. See Security and governance
. Add bot protection(native authentication only). Requires a custom URL domain. See Integrate third-party bot protection.Add account takeover (ATO) protection(native authentication only). Requires a custom URL domain. See Integrate third-party ATO protection.
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 theMicrosoft-hostedsign-in pages. See Customize the sign-in look and feel. - Use a custom URL domain.
ReplaceAll service API calls for thedefaultciamlogin.comhost 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
- Start a free trial or create your external tenant.
- Find samples and guidance for integrating your app.
- Learn how to migrate users from your current identity provider.
- See also the Microsoft Entra External ID Developer Center for the latest developer content and resources.
- Microsoft Entra External ID deployment guide for security operations.
@@ -1,42 +1,40 @@ ----title: Plan a CIAM Deployment-description: Discover the steps for setting up a customer identity and access management (CIAM) solution in an external tenant, including creating a tenant, registering apps, and setting up user flows for sign-in.+title: Plan a Deployment+description: Plan a Microsoft Entra External ID deployment, from creating an external tenant and choosing an authentication approach to integrating and securing sign-in. ai-usage: ai-assisted ms.topic: concept-article-ms.date: 05/21/2026--ms.custom: it-pro, seo-july-2024+ms.date: 11/12/2026 +ms.custom: it-pro, seo-july-2024, msecd-doc-authoring-1030+#customer intent: As an application developer or IT administrator, I want to plan a customer identity deployment so that I can configure and secure sign-in for my applications. --- -# Planning for customer identity and access management--[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]+# Plan a Microsoft Entra External ID deployment 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 guide for the six planning steps. Each section summarizes the key choices and links to the canonical how-tos and reference docs.+[!INCLUDE [authentication-approaches](../includes/applies-to-authentication-approaches.md)] -:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal.png" alt-text="Diagram showing the six setup steps as a horizontal flow: create an external tenant, choose an authentication approach, register your application, integrate a sign-in flow, secure your sign-in, and customize your sign-in.":::+Use this guide to plan your deployment in six steps. Each section summarizes the key choices and links to setup instructions and reference documentation.++:::image type="content" source="media/concept-planning-your-solution/planning-flow-horizontal.png" alt-text="Diagram of six setup steps: create a tenant, choose authentication, register an app, integrate a user flow, secure sign-in, and customize 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](#step-1-create-an-external-tenant)** | • [Create an external tenant](how-to-create-external-tenant-portal.md)</br>• <a href="https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl" target="_blank">Or start a free trial</a> |-|**[Step 2: Choose an authentication approach](#step-2-choose-an-authentication-approach)** | • [Choose an authentication approach](concept-choose-authentication-approach.md) |-|**[Step 3: Register your application](#step-3-register-your-application)** | • [Register your application](/entra/identity-platform/quickstart-register-app) |-|**[Step 4: Integrate a sign-in flow with your app](#step-4-integrate-a-sign-in-flow-with-your-app)** | • [Create a user flow](how-to-user-flow-sign-up-sign-in-customers.md) </br>• [Add your app to the user flow](how-to-user-flow-add-application.md) |-|**[Step 5: Secure your sign-in](#step-5-secure-your-sign-in)** | • [Add multifactor authentication (MFA)](concept-multifactor-authentication-customers.md)</br>• [Review security and governance](concept-security-customers.md)</br>• [Integrate third-party bot protection](tutorial-third-party-bot-protection-native-api-sign-up.md) *(native authentication)*</br>• [Integrate third-party ATO protection](tutorial-third-party-account-take-over-protection-native-api.md) *(native authentication)* |-|**[Step 6: Customize your sign-in](#step-6-customize-your-sign-in)** | • [Customize branding](concept-branding-customers.md) *(browser-delegated)*</br>• [Use a custom URL domain](concept-custom-url-domain.md)</br>• [Add custom authentication extensions](concept-custom-extensions.md) |+| Step | How-to guides |+| --------- | --------- |+| **[Step 1: Create an external tenant](#step-1-create-an-external-tenant)** | • [Create an external tenant](how-to-create-external-tenant-portal.md)</br>• <a href="https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl" target="_blank">Or start a free trial</a> |+| **[Step 2: Choose an authentication approach](#step-2-choose-an-authentication-approach)** | • [Choose an authentication approach](concept-choose-authentication-approach.md) |+| **[Step 3: Register your application](#step-3-register-your-application)** | • [Register your application](/entra/identity-platform/quickstart-register-app) |+| **[Step 4: Integrate a sign-in flow with your app](#step-4-integrate-a-sign-in-flow-with-your-app)** | • [Create a user flow](how-to-user-flow-sign-up-sign-in-customers.md) </br>• [Add your app to the user flow](how-to-user-flow-add-application.md) |+| **[Step 5: Secure your sign-in](#step-5-secure-your-sign-in)** | • [Add multifactor authentication (MFA)](concept-multifactor-authentication-customers.md)</br>• [Review security and governance](concept-security-customers.md) |+| **[Step 6: Customize your sign-in](#step-6-customize-your-sign-in)** | • [Customize branding](concept-branding-customers.md) *(Microsoft-hosted pages)*</br>• [Use a custom URL domain](concept-custom-url-domain.md)</br>• [Add custom authentication extensions](concept-custom-extensions.md) | ## 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 Azure AD B2C, your existing B2C tenants aren't affected; see [Plan your migration from Azure AD B2C to External ID](plan-your-migration-from-b2c-to-external-id.md).--[!INCLUDE [active-directory-b2c-end-of-sale-notice.md](~/includes/active-directory-b2c-end-of-sale-notice.md)]+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're migrating from Azure AD B2C, review the [Azure AD B2C migration planning guidance](plan-your-migration-from-b2c-to-external-id.md). For other identity deployments, review [user migration guidance](how-to-migrate-users.md). The directory contains both [admin accounts](how-to-manage-admin-accounts.md) and customer accounts. Customers usually self-register; you can also [create local accounts](how-to-manage-customer-accounts.md). Customer accounts have a restricted [default permission set](reference-user-permissions.md) and can't see other users, groups, or devices. @@ -44,7 +42,7 @@ The directory contains both [admin accounts](how-to-manage-admin-accounts.md) an - [Create an external tenant](how-to-create-external-tenant-portal.md) in the Microsoft Entra admin center. - Don't have a tenant yet? [Start a free trial](https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl).-- Using VS Code? Use the [Microsoft Entra External ID extension](https://aka.ms/ciamvscode/quickstarts/marketplace) ([learn more](https://aka.ms/ciamvscode/quickstartguide)).+- Using Visual Studio Code? Use the [Microsoft Entra External ID extension](https://aka.ms/ciamvscode/quickstarts/marketplace) and its [quickstart guide](https://aka.ms/ciamvscode/quickstartguide). ## Step 2: Choose an authentication approach @@ -52,47 +50,43 @@ The directory contains both [admin accounts](how-to-manage-admin-accounts.md) an Decide how to build the sign-in experience before you register your app. This choice drives the rest of your integration. -- **Browser-delegated authentication** — Microsoft hosts the sign-in page; your app redirects users to it. Broad platform support, system-browser SSO, lower maintenance.-- **Native authentication** — your app hosts the sign-in UI and calls MSAL or the native authentication API directly. Full UI control, more development and security responsibility.+- **Microsoft-hosted authentication** — Microsoft hosts the sign-in page, and your app redirects users to it. You can apply company branding or application-specific branding themes.+- **Embedded native authentication** — Your app presents the sign-in interface and calls an SDK or the Native Authentication API. Your team manages the interface and integration.+- **Bring Your Own UX (BYO UX)** — Your team hosts a separate authentication website within a browser-based authorization flow. Microsoft Entra External ID applies authentication policies and verifies credentials. ### How to choose an authentication approach - [Choose an authentication approach](concept-choose-authentication-approach.md) — feature comparison and trade-offs.-- [Native authentication overview](/entra/identity-platform/concept-native-authentication) — detail if you're considering native.+- [Embedded native authentication overview](~/identity-platform/concept-native-authentication.md) — integration guidance for an interface in your app. ## 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 on the authentication approach you chose in Step 2:+Register your app in your external tenant to establish its application identity. Follow the registration guide for your platform and authentication approach. -| Setting | Browser-delegated | Native authentication |-|---|---|---|-| Redirect URI | Required (matches your app's sign-in callback) | Required only as a [web fallback](/entra/identity-platform/concept-native-authentication-web-fallback) |-| Public client flows | Not required | Enabled |-| Native authentication | Not required | Enabled |+| Setting | Microsoft-hosted | Embedded native authentication | BYO UX |+| --- | --- | --- | --- |+| Redirect URI | Register 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 type | Choose the registration for your app's platform. | Public client; enable public client flows. | Public or confidential client. |+| Service API authority | Default tenant domain or a custom URL domain. | Tenant-verified custom domain for the current API. | Tenant-verified custom domain for API calls. |+| Integration setup | Configure hosted sign-in. | Enable native authentication for the app. | Use Microsoft Graph beta to configure your self-hosted authentication page. | -After you register the app, update your code with the application (client) ID, tenant subdomain, and (if applicable) client secret.+After registration, configure your application and tenant identifiers. Keep confidential-client credentials on the server; don't place client secrets in mobile apps or browser code. ### How to register your application - Find platform-specific guidance on the [Samples by app type and language page](samples-ciam-all.md).-- If your platform isn't listed, follow the general [register an application](/entra/identity-platform/quickstart-register-app) quickstart.-- For native authentication app settings, see [How to enable native authentication](/entra/identity-platform/concept-native-authentication#how-to-enable-native-authentication).+- If your platform isn't listed, follow the general [register an application](~/identity-platform/quickstart-register-app.md) quickstart.+- For Embedded native authentication app settings, see [Configure an app for Embedded native authentication](~/identity-platform/how-to-native-authentication-configure-app.md). ## 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 create the user flow the same way for both authentication approaches; the difference is how your app drives it at runtime:+Create a sign-up and sign-in user flow that defines the sign-in methods, attributes to collect, and identity providers for your app. Use the [authentication support matrix](concept-supported-features-customers.md#authentication-approach-supportability) to check which configured features are available through your integration. -| | Browser-delegated | Native authentication |-|---|---|---|-| Runtime behavior | App redirects to the Microsoft-hosted sign-in page | App calls MSAL native authentication APIs from your own UI |-| Supported app types | Web, SPA, mobile, daemon | Mobile, SPA |-| Federated identity providers (social, external IdPs) | Supported | Not supported — use browser-delegated if needed |-| Company branding | Applies to Microsoft-hosted pages | Managed in your app's UI/localization |-| Attribute collection | Configured in the user flow | Configured in the user flow; submitted via the MSAL [user attribute builder](/entra/identity-platform/concept-native-authentication-user-attribute-builder) |+For the Native Authentication API integrations, follow the [attribute collection contract](~/identity-platform/concept-native-authentication-user-attributes.md). ### Plan your user flow @@ -100,41 +94,40 @@ Create a sign-up and sign-in user flow that defines the sign-in methods, attribu - **Attributes to collect.** Decide which built-in attributes you need and whether you need [custom attributes](how-to-define-custom-attributes.md). - **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](how-to-add-attributes-to-token.md) if your app depends on them.-- **Sign-in methods.** Local accounts (email OTP, email + password) work with both approaches. Federated providers ([Google](how-to-google-federation-customers.md), [Facebook](how-to-facebook-federation-customers.md), [Apple](how-to-apple-federation-customers.md), [another Microsoft Entra tenant](how-to-entra-id-federation-customers.md), [custom OIDC](how-to-custom-oidc-federation-customers.md)) require browser-delegated authentication.+- **Sign-in methods.** Configure local account methods and identity providers for each user flow. With Microsoft-hosted authentication, configured federated providers can include [Google](how-to-google-federation-customers.md), [Facebook](how-to-facebook-federation-customers.md), [Apple](how-to-apple-federation-customers.md), [another Microsoft Entra tenant](how-to-entra-id-federation-customers.md), or [custom OpenID Connect (OIDC)](how-to-custom-oidc-federation-customers.md). Federation isn't supported through the Native Authentication API. Confirm method and journey availability in the [methods and journeys comparison](concept-supported-features-customers.md#methods-and-journeys-by-approach). ### How to integrate a user flow with your app - [Define custom attributes](how-to-define-custom-attributes.md) (if needed). - [Create the sign-up and sign-in user flow](how-to-user-flow-sign-up-sign-in-customers.md). - [Add your application to the user flow](how-to-user-flow-add-application.md).-- Wire up your app code:- - **Browser-delegated:** follow a [sample or quickstart](samples-ciam-all.md) for your app type.- - **Native authentication:** follow the [native authentication overview and tutorials](/entra/identity-platform/concept-native-authentication).+- Integrate your app code:+ - **Microsoft-hosted:** Follow a [sample or quickstart](samples-ciam-all.md) for your app type.+ - **Embedded native authentication:** Start with the [application configuration guide](~/identity-platform/how-to-native-authentication-configure-app.md), [SDK quickstart](~/identity-platform/quickstart-native-authentication.md), or [Native Authentication API reference](~/identity-platform/reference-native-authentication.md). Confirm platform and SDK coverage in the [native authentication overview](~/identity-platform/concept-native-authentication.md#how-to-use-native-authentication). For an existing V1 integration, use the [V1 API reference](~/identity-platform/reference-native-authentication-api-v1.md) and [migration guide](~/identity-platform/how-to-migrate-native-authentication-v1-v2.md).+ - **Bring Your Own UX:** Review the [Bring Your Own UX overview](concept-bring-your-own-ux.md) for architecture, requirements, and implementation guidance. ## 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."::: -Every customer-facing app needs MFA and a baseline security review. Native authentication apps have extra work: because your app is the exposed sign-in surface, you front it with a web application firewall (WAF). Browser-delegated apps inherit Microsoft's platform-level protections on the hosted sign-in pages.+Plan MFA and review security for your customer-facing apps. Configure tenant policies and protect application sessions, tokens, and any credentials or state your integration handles. Assign ownership for the interface, integration, and hosting components your team operates. For responsibility boundaries, see [authentication integration responsibilities](concept-choose-authentication-approach.md#security-considerations). -- **Enable MFA.** [Available MFA methods](concept-multifactor-authentication-customers.md).-- **Review security and governance.** Conditional Access, risk-based policies, auditing. See [Security and governance](concept-security-customers.md).-- **Add bot protection** *(native authentication only)*. Requires a [custom URL domain](concept-custom-url-domain.md). See [Integrate third-party bot protection](tutorial-third-party-bot-protection-native-api-sign-up.md).-- **Add account takeover (ATO) protection** *(native authentication only)*. Requires a [custom URL domain](concept-custom-url-domain.md). See [Integrate third-party ATO protection](tutorial-third-party-account-take-over-protection-native-api.md).+- **Enable MFA.** Review [available MFA methods](concept-multifactor-authentication-customers.md).+- **Review security and governance.** Plan for Conditional Access, risk-based policies, and auditing. See [Security and governance](concept-security-customers.md). ## 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 owns the UI, so the Microsoft Entra company-branding feature doesn't apply — manage visuals and localization in your app code.+Customize the sign-in look and feel and extend it with your own business logic. You can configure Microsoft-hosted pages, manage the interface in your app with Embedded native authentication, or host your own page with BYO UX. -- **Customize branding** *(browser-delegated only)*. Apply your logo, colors, and language strings to the Microsoft-hosted sign-in pages. See [Customize the sign-in look and feel](concept-branding-customers.md).-- **Use a custom URL domain.** Replace the default `ciamlogin.com` host with your own domain. Also a prerequisite for native authentication bot/ATO protection in [Step 5](#step-5-secure-your-sign-in). See [Custom URL domain](concept-custom-url-domain.md).-- **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. See [Custom authentication extensions](concept-custom-extensions.md).+- **Customize branding** *(Microsoft-hosted pages)*. Apply your logo, colors, and language strings to the sign-in pages. See [Customize the sign-in look and feel](concept-branding-customers.md).+- **Use a custom URL domain.** All service API calls for the current Native Authentication API and BYO UX use a tenant-verified custom domain. See [Custom URL domain](concept-custom-url-domain.md).+- **Add custom authentication extensions.** Extend the flow with server-side logic. Event availability can differ by approach and API or SDK version. See [Custom authentication extensions](concept-custom-extensions.md). ## Next steps - [Start a free trial](https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl) or [create your external tenant](how-to-create-external-tenant-portal.md). - [Find samples and guidance for integrating your app](samples-ciam-all.md). - [Learn how to migrate users from your current identity provider](how-to-migrate-users.md). - See also the [Microsoft Entra External ID Developer Center](https://aka.ms/ciam/dev) for the latest developer content and resources.-- [Microsoft Entra External ID deployment guide for security operations](../../architecture/deployment-external-operations.md)+- [Microsoft Entra External ID deployment guide for security operations](../../architecture/deployment-external-operations.md). 