Azure AD B2C end of life: Migration planning should start now
23.6.2026, 3 minutes read time
TL; DR: Microsoft Azure AD B2C is reaching end of life, and now is the time to plan your migration to Entra External ID, Microsoft’s new target for customer identity.
Microsoft Entra External ID is the new target for customer identity
Azure AD B2C is no longer Microsoft’s platform for new customer identity projects. Microsoft Entra External ID is taking its place, and since May 1, 2025, Azure AD B2C has not been available for purchase by new customers. Existing customers may continue using the service, but support will be terminated by 2030.
If you are using Azure AD B2C today, the first step towards migrating to Entra External ID is to get a structured assessment that shows what exists, what depends on it, and what needs to change before moving, including customer identity and access management. Customer identity platforms are usually connected to several applications, user flows, and downstream systems, and these dependencies take time to understand before they can be migrated safely.
The move from Azure AD B2C to Entra External ID should be treated as an architecture transition rather than a tenant copy. The goal should not be to recreate every old B2C pattern, but rather to build a customer identity platform that is easier to govern, secure, and operate. It is designed for users outside the workforce who need access to digital applications and services, such as:
Why does an Azure AD B2C environment need an assessment before migration?
Many B2C environments contain more complexity than the sign-in page suggests, and migration should start with an inventory.
You need to know which applications use B2C, which flows and policies are active, and how users are connected to application data.
Custom policies need particular attention, as some of the custom logic may move to External ID custom authentication extensions, some may move into applications, and some may require redesign.
Azure AD B2C migration options
The right migration approach depends on scale, active usage, application complexity, credential handling, and tolerance for user disruption.
Smaller, simpler B2C environments may be suitable for bulk migration and controlled cutover, while larger environments often need just-in-time migration, where users move when they next sign in.
Very large or multi-application environments may need a structured coexistence model, such as High Scale Compatibility mode.
The migration method should be chosen after an assessment has been done, not before. A tenant with built-in user flows and few active users is a different project from a tenant with custom policies, several applications, social identity providers, and claim dependencies.
What to do now
Start by mapping the current Azure AD B2C environment.
Then identify production risks.
After that, define your Microsoft Entra External ID target state.
Azure AD B2C is still supported, but it is no longer the platform to build on.
If you start assessing your current set-up now, you may migrate on your own terms, reduce technical debt, and avoid a deadline-driven project later.
Talk to us about Entra External ID Services
We help assess your current environment and assist in
migrating from Azure AD B2C to Entra External ID in a controlled way, without breaking production.