We are currently evaluating the migration from Azure AD B2C to Microsoft Entra. To complete our analysis and plan accordingly, we require clarity on the following items:

Question

We are currently evaluating the migration from Azure AD B2C to Microsoft Entra. To complete our analysis and plan accordingly, we require clarity on the following items:

ZTS 40

Problem Statement

Availability and parity of B2C features within Entra

Planned or upcoming changes to supported capabilities

Migration timeline, including deprecation dates for B2C

Potential impact on existing customer workflows

This information is required to support internal migration planning and timeline alignment across impacted systems.

As part of our evaluation of the migration from Azure AD B2C to Microsoft Entra, we are requesting the following details to support internal planning and technical readiness:

A confirmed or tentative migration timeline, including key dates and any planned deprecation milestones for B2C. A detailed feature comparison between Azure AD B2C and Microsoft Entra, with a focus on functionality that may be deprecated, changed, or added. Any documentation on current limitations or known differences between the platforms that may impact enterprise workflows. A roadmap or release plan, if available, covering upcoming Entra capabilities relevant to this migration. Please share the available documentation

ZTS 40 Reputation points

2025-07-21T14:53:24.1+00:00

Do you have a detailed roadmap showing how Azure AD B2C's XML-based custom policy capabilities (which we currently rely on) will be supported in Entra External ID, given the B2C support end date of May 30, 2030.

While I appreciate the information you've provided, it appears to cover only the general migration overview we had already reviewed in our initial analysis before reaching out.

We're specifically looking for more detailed capability mapping and timeline information for the custom policy features we depend on.

Could provide us more detailed technical roadmap information? We want to ensure we're planning our migration strategy appropriately.
Raja Pothuraju 29,330 Reputation points Microsoft External Staff Moderator

2025-07-21T22:38:10.3466667+00:00

Hello ZTS,

We recognize that custom policy capabilities are critical for tailoring identity experiences to your unique business needs. While it is currently unavailable in Microsoft Entra External ID tenants and not part of our immediate roadmap, we are actively investing in supporting core scenarios as the product evolves.

In the meantime, we recommend migrating user flows to maintain continuity and leverage the latest platform enhancements.
Raja Pothuraju 29,330 Reputation points Microsoft External Staff Moderator

2025-07-24T00:07:56.73+00:00

Hello ZTS,

Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.

1 answer

Your answer

ZTS 40 Reputation points

2025-07-21T14:53:24.1+00:00

Do you have a detailed roadmap showing how Azure AD B2C's XML-based custom policy capabilities (which we currently rely on) will be supported in Entra External ID, given the B2C support end date of May 30, 2030.

While I appreciate the information you've provided, it appears to cover only the general migration overview we had already reviewed in our initial analysis before reaching out.

We're specifically looking for more detailed capability mapping and timeline information for the custom policy features we depend on.

Could provide us more detailed technical roadmap information? We want to ensure we're planning our migration strategy appropriately.
Raja Pothuraju 29,330 Reputation points Microsoft External Staff Moderator

2025-07-21T22:38:10.3466667+00:00

Hello ZTS,

We recognize that custom policy capabilities are critical for tailoring identity experiences to your unique business needs. While it is currently unavailable in Microsoft Entra External ID tenants and not part of our immediate roadmap, we are actively investing in supporting core scenarios as the product evolves.

In the meantime, we recommend migrating user flows to maintain continuity and leverage the latest platform enhancements.
Raja Pothuraju 29,330 Reputation points Microsoft External Staff Moderator

2025-07-24T00:07:56.73+00:00

Hello ZTS,

Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.

Answer 1

Hello ZTS,

Based on your description, I understand that you are planning to migrate from Azure AD B2C to Microsoft Entra External ID, and are seeking information regarding the deprecation timeline of B2C, key migration milestones, and current feature differences and limitations between the two services.

Migration Timeline & Deprecation Milestones Azure AD B2C end of sale:

Effective May 1, 2025 Azure AD B2C will no longer be available to purchase for new customers, but current Azure AD B2C customers can continue using the product. The product experience, including creating new tenants or user flows, will remain unchanged; however, new tenants can only be created with Azure AD B2C P1. Azure AD B2C P2 will be discontinued on March 15, 2026, for all customers. The operational commitments, including service level agreements (SLAs), security updates, and compliance, will also remain unchanged. We'll continue supporting Azure AD B2C until at least May 2030.

Feature comparison between Azure AD B2C and Microsoft Entra External ID.

Feature Area	Azure AD B2C	Microsoft Entra External ID	Notes
User Flows	Customizable via XML policies	Simplified with Pre/Post Attribute Collection Custom Extensions	Entra External ID simplifies extensibility
Identity Providers	Social + Local + Enterprise	Microsoft Entra accounts (via invite), Facebook, Google, Apple, custom OIDC, and SAML/WS-Fed identity provider federation	Entra adds broader protocol support
Security Features	Basic MFA, limited risk detection	Passkeys, phishing-resistant MFA, adaptive access	Entra offers modern security capabilities
Developer Experience	XML-based custom policies	Unified Graph API, VS Code extensions	Entra improves developer tooling
Licensing Model	Per-authentication P1/P2	Monthly Active Users (MAU)	First 100K MAUs free
Branding & UX Customization	Extensive via custom policies	Branded sign-up, extensible flows	Entra supports Pre/Post Attribute Collection Custom Extensions and branding

For Entra External ID service limitations you can refer: https://learn.microsoft.com/en-us/entra/external-id/customers/reference-service-limits

To know what the latest features are publicly released, you can check at below document:

https://learn.microsoft.com/en-us/entra/external-id/whats-new-docs?tabs=external-tenants

Microsoft recommends transitioning to Microsoft Entra External ID for all new external identity scenarios. To migrate users and credentials from Azure AD B2C or any existing IdP, refer to:

How to migrate users to Entra External ID

Azure AD B2C: Frequently asked questions (FAQ):
https://docs.azure.cn/en-us/active-directory-b2c/faq?tabs=app-reg-ga

Microsoft Entra External ID frequently asked questions

https://learn.microsoft.com/en-us/entra/external-id/customers/faq-customers

Share via

We are currently evaluating the migration from Azure AD B2C to Microsoft Entra. To complete our analysis and plan accordingly, we require clarity on the following items:

1 answer

Your answer