Plan your migration from Azure AD B2C to External ID
In brief
The page’s metadata and table formatting were updated, and the sentence describing third-party fraud protection for native authentication API flows through a WAF was removed. The statement that web-hosted flows don’t support this integration in HSC mode remains.
What Entra admins need to know
Administrators should use the revised page when reviewing migration guidance; no action is required by this update.
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.
Plan your migration from Azure AD B2C to External ID
Decision summary
| Standard migration | High Scale Compatibility (HSC) mode migration |
|---|---|
| Best for: Most tenants Typical trigger: Below high-scale thresholds Identity approach: Plan to migrate users (and, where required, credentials) as part of moving to External ID Coexistence: Not designed for long-running side-by-side operation at very large scale Feature coverage: Broadest compatibility |
Best for: Very large Azure AD B2C tenants Typical trigger: ~5 million+ directory objects and scale-driven constraints Identity approach: Keep existing users and credentials in place while migrating applications in phases Coexistence: Azure AD B2C and External ID run side by side in the same tenant and might require schema updates Feature coverage: Significant feature gaps today — no social identity providers, no passkeys, no age gating, no admin portal experience, and limited Conditional Access. See HSC mode limitations |
If your tenant meets the HSC mode eligibility criteria, review both approaches below before deciding. The standard approach might still be the better fit depending on your feature requirements.
Security and fraud prevention
- Third-party fraud protection integration for web-hosted (browser-based) sign-in and sign-up flows isn't supported in HSC mode.
Native authentication API flows can integrate with third-party fraud protection by using a web application firewall (WAF) in front of the native authentication endpoints. For implementation guidance, see Integrate third-party bot protection with native authentication and Integrate third-party account takeover protection with native authentication.
User experience and compliance
@@ -2,8 +2,9 @@ title: Plan your migration from Azure AD B2C to External ID description: Choose between the standard migration approach and High Scale Compatibility (HSC) mode when moving from Azure AD B2C to Microsoft Entra External ID. ms.topic: concept-article-ms.date: 03/13/2026+ms.date: 11/11/2026 ai-usage: ai-assisted+ms.custom: msecd-doc-authoring-1030 --- # Plan your migration from Azure AD B2C to External ID@@ -44,7 +45,7 @@ HSC mode migration might be a good choice if **all** the following are true: ### Decision summary | Standard migration | High Scale Compatibility (HSC) mode migration |-|---|---|+| --- | --- | | **Best for**: Most tenants<br>**Typical trigger**: Below high-scale thresholds<br>**Identity approach**: Plan to migrate users (and, where required, credentials) as part of moving to External ID<br>**Coexistence**: Not designed for long-running side-by-side operation at very large scale<br>**Feature coverage**: Broadest compatibility | **Best for**: Very large Azure AD B2C tenants<br>**Typical trigger**: ~5 million+ directory objects and scale-driven constraints<br>**Identity approach**: Keep existing users and credentials in place while migrating applications in phases<br>**Coexistence**: Azure AD B2C and External ID run side by side in the same tenant and might require schema updates<br>**Feature coverage**: Significant feature gaps today — no social identity providers, no passkeys, no age gating, no admin portal experience, and limited Conditional Access. See [HSC mode limitations](#hsc-mode-limitations) | If your tenant meets the HSC mode eligibility criteria, review both approaches below before deciding. The standard approach might still be the better fit depending on your feature requirements.@@ -175,7 +176,7 @@ Review these limitations carefully before enabling HSC mode. They apply in addit **Security and fraud prevention** -- Third-party fraud protection integration for web-hosted (browser-based) sign-in and sign-up flows isn't supported in HSC mode. Native authentication API flows can integrate with third-party fraud protection by using a web application firewall (WAF) in front of the native authentication endpoints. For implementation guidance, see [Integrate third-party bot protection with native authentication](tutorial-third-party-bot-protection-native-api-sign-up.md) and [Integrate third-party account takeover protection with native authentication](tutorial-third-party-account-take-over-protection-native-api.md).+- Third-party fraud protection integration for web-hosted (browser-based) sign-in and sign-up flows isn't supported in HSC mode. **User experience and compliance** 