Azure AD B2C migration tools are now available

Introduction

Organizations using Azure AD B2C now have new Microsoft-supported tools to plan and execute a move to Microsoft Entra External ID. This matters because Azure AD B2C is no longer receiving new features, while Microsoft continues investing in External ID as its next-generation customer identity platform.

For IT teams, this is an important signal to start migration planning early rather than waiting for timelines or technical debt to create pressure later.

What’s new

Microsoft announced that the following migration resources are now generally available:

• Just-in-Time (JIT) migration for progressive user migration during sign-in
• High-Scale Compatibility (HSC) mode for large-scale or complex environments
• Migration guidance and architecture blueprint for planning application sequencing, credential migration, and cutover strategy

Microsoft also highlighted recent Entra External ID platform enhancements, including:

• Email and SMS OTP MFA
• Social identity providers through browser-delegated flows
• Native app to web view SSO
• Sign-in and sign-up with alias
• Microsoft Entra ID federation with External ID in public preview
• Self-service password reset with SMS OTP

Choosing between JIT and HSC

The two migration paths support different priorities:

• JIT migration is best for most organizations that want a cleaner cutover with minimal user disruption
• HSC mode is designed for high-scale environments, especially those with more than 5 million users or more complex architectural constraints

In short, JIT focuses on simplicity and user experience, while HSC focuses on scale and operational continuity.

Why this matters for administrators

Azure AD B2C remains supported for existing tenants, but Microsoft has made it clear that new innovation is happening only in Entra External ID. For identity and application teams, that means migration is now a strategic planning exercise rather than a future consideration.

External ID also brings benefits beyond feature parity, including:

• A modern extensibility model that reduces dependence on complex custom policy XML
• Better integration with the broader Microsoft Entra ecosystem
• Improved monitoring, diagnostics, and audit capabilities
• Continued investment in passwordless and fraud protection capabilities

Recommended next steps

Admins should take a structured approach:

1. Assess current applications, user populations, integrations, and custom policies
2. Decide whether JIT or HSC best fits business and technical requirements
3. Execute a proof of concept in a non-production environment
4. Validate identity flows, user journeys, and application dependencies
5. Engage partners if the environment includes complex customizations or large-scale migration needs

Microsoft has also published a qualified migration partner directory for organizations that need implementation support.

Bottom line

The new Azure AD B2C migration tooling gives organizations a clearer path to Microsoft Entra External ID. Starting early will help IT teams reduce risk, preserve user experience, and modernize customer identity on Microsoft’s actively developed platform.