What does the Azure AD B2C transition to Microsoft Entra External ID mean for existing tenants?
Asked by
MellowPine47
I'm still getting familiar with Azure and am trying to understand the Azure AD B2C transition to Microsoft Entra External ID. Is this mainly a product rename and portal change, or will existing applications need to be migrated? Will existing tenants still be managed through the Azure portal, or will administration move to a different Entra portal?
Our organization has a production tenant, two development tenants, and an older Microsoft 365 tenant that hosts several virtual machines. Could any of these tenants or workloads be affected? We also have applications using tenant-specific URLs such as tenantname.b2clogin.com, app registrations with client secrets, and API connectors for B2C custom enrichment.
All of these tenants currently show Microsoft Entra ID Free rather than P1 or P2. I'm mainly trying to understand whether we need to take action now and whether our existing sign-in URLs, user flows, app registrations, secrets, or API connectors will continue working.
Answers
The notices do not mean that every tenant, virtual machine, or workforce identity is being migrated automatically. Your older Microsoft 365 tenant and the VM workloads should not be affected simply because they exist alongside B2C. The main area to evaluate is each B2C external-identity tenant and the applications connected to it. Keep an inventory of user flows, app registrations, secrets, API connectors, redirect URIs, policies, and authentication settings before deciding whether migration is necessary.
Reply to this answer
For existing Azure AD B2C customers, this is not an immediate shutdown. Microsoft has indicated that existing customers are supported for several years, with guidance commonly referring to at least May 2030. However, B2C is effectively feature-complete, and new customers can no longer purchase it. Microsoft’s intended replacement is Microsoft Entra External ID, so it’s worth planning rather than treating the change as only a rebrand.
Reply to this answer
Existing application endpoints such as tenantname.b2clogin.com are generally expected to keep working during the supported lifetime of the B2C service. A future migration to External ID may require different tenant configuration, endpoints, policies, or feature implementations, so don’t assume every URL and custom feature will transfer unchanged. Test MFA, API connectors, enrichment, custom policies, and user journeys against the External ID feature set before making a plan.
CopperWren53: MFA support is one area I’d check carefully. The available methods and capabilities may not match B2C exactly, so a feature-by-feature comparison is more useful than assuming the products are interchangeable.
Reply to this answer
The P1/P2 notices are separate from the general B2C transition. Azure AD External Identities P2 has been retired in B2C tenants, while some identity-protection capabilities remain available in workforce tenants. Since your tenants show the Free edition, check the current licensing and migration documentation for the specific features you use rather than relying only on the portal banner. You probably do not need an emergency cutover, but you should monitor Microsoft’s deadlines and begin testing in a development tenant.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine47: That helps clarify the banners. I was worried that our tenants were about to stop working, but I’ll review the migration guidance and compare the available features with our current user flows.