AZURE AD B2C TO ENTRA EXTERNAL ID

A quiet migration from Azure AD B2C to Entra External ID, without losing your users.

Start with a clear plan for accounts, passwords, social sign-in and the applications behind them. Account links are kept, and eligible users carry on with the password they already know.

B2C TO ENTRA MIGRATIONFIRST SIGN-IN
BEFOREAzure AD B2CExisting account & password
AFTEREntra External IDAccount ready for sign-in
Accounts with a local password are verified at first sign-in and connected to the new platform. Which accounts qualify is confirmed in the assessment.

What a migration has to carry

The directory is one part of it. Four more things cross only when someone plans them.

Passwords

Passwords cannot be exported from B2C.

THE APPROACH

Just-in-time migration: local password accounts move at first sign-in, using the password the customer already knows.

Account links

Business systems depend on existing identity keys.

THE APPROACH

Map old and new identifiers so the right account stays connected to the right services.

Sign-in routes

Passwords, social providers and company sign-in differ.

THE APPROACH

Design and test each route, including how to handle accounts with multiple providers.

Custom policies

Custom policies (Identity Experience Framework) do not carry over automatically.

THE APPROACH

Review the business rules they encode and design supported equivalents or alternatives.

HOW IT WORKS

Eight stages, from discovery to cutover.

Each migration is different. These stages give us a shared structure for the decisions, evidence and work ahead.

01Discover

Discover what identity touches.

I map your B2C sign-in journeys, custom policies, applications and identity dependencies. Your team explains the systems and customer journeys; I investigate the technical constraints.

We identify unknowns, duplicate identities and application links before choosing a migration route.

Outputs Identity map · sign-in inventory · risk register

Duration A couple of days, free of charge, ending in a proposed plan

02Design

Design the route before moving users.

I develop a target architecture for Entra External ID, covering sign-in routes, account matching, application tokens and business identifiers.

We review the choices together and agree how both systems coexist, how progress is monitored and when to roll back.

Outputs Target architecture · matching rules · rollback plan

03Accounts

Move accounts and keep their links.

We identify the account details and business links that need to carry across. I build the mapping between source and target identities.

We agree how to handle duplicate or multi-provider accounts and test representative journeys before wider migration.

Outputs Identifier map · account migration · exception review

04Passwords

A familiar password at first sign-in.

B2C passwords cannot be exported. I design a just-in-time migration for local password accounts: the existing password is verified at first sign-in, so users continue with the password they know.

We review the security, user experience and recovery paths together, and test before production traffic moves.

Outputs Sign-in flow · verification checks · recovery plan

05Social & company sign-in

Preserve the sign-in routes people use.

I inventory the social and company sign-in routes in use, then map and test provider identifiers, redirects, claims and consent behaviour.

We agree how to handle accounts linked to multiple providers, with a review path for ambiguous cases.

Outputs Provider map · federation setup · linking rules

06Applications

Prepare the whole application journey.

Working with your application teams, I prepare desktop, web and backend systems for the new platform, including app registrations, MSAL configuration and token validation.

We test the journeys users depend on, from sign-in through to account resolution and API authorization.

Outputs Application setup · journey tests · rollout matrix

07Sync during coexistence

Keep the target current.

New accounts and profile changes can continue during migration. We agree which changes matter and who owns each piece of data; I design a controlled way to keep the target current.

Reconciliation and alerts make failed or missing updates visible for review.

Outputs Change pipeline · reconciliation · operational alerts

08Cutover

Switch with evidence and a way back.

We agree readiness checks, support responsibilities and a rollback path. A pilot or limited group can validate the journey before a wider release.

We monitor the transition and track exceptions; the old route remains until the agreed exit criteria are met.

Outputs Readiness gates · rollout plan · retirement criteria

ABOUT

One specialist.
Working with your team.

You work with one person from the first call to cutover. I lead the technical work, explain the decisions and work alongside the people who know your users and systems best.

My experience includes an end-to-end production identity migration. Each engagement starts with your environment, not an assumption that every journey is the same.

Lucian Munteanu · Identity and authentication specialist · LinkedIn

More about how I work →

What I bring

  • Technical investigation and migration design
  • Implementation and testing
  • Each decision explained as we go

What your team brings

  • Knowledge of your systems
  • Knowledge of your customers and their journeys
  • Your operational requirements

LESSONS LEARNED

What a production migration teaches you.

Identity migrations are shaped by the edge cases as much as the main flow.

Identity is not just email.

A provider may not return an email claim. Account matching needs a reliable fallback and explicit rules.

Reset paths need review.

A password reset in the new system does not necessarily retire the old credential. Plan how both paths are handled.

Test the real journey.

Session behaviour, provider redirects and sign-in page styling need to be checked in the actual applications.

Keep exceptions visible.

Accounts with several sign-in methods may need to remain on the existing route until the right target is clear.

EXAMPLE SCENARIO

An example: a SaaS platform leaves B2C.

A fictional scenario, not a client case study.

ILLUSTRATIVE SCENARIOSAAS / CUSTOMER IDENTITY
THE CONTEXT

Customers sign in every day.

They use their accounts to reach their workspaces. The sign-in platform has to move without losing the connection between each person and the services they use.

THE APPROACH

Move the identity.

The team prepares identities for the new platform and plans a password transition for local password accounts, with tests and clear exception handling.

THE OUTCOME

Keep the relationship.

In this scenario, those users sign in with their familiar passwords and remain connected to the workspaces and account information they already use.

Identity services on Microsoft Entra

Migration is the main work. Sign-in, MFA and single sign-on are also taken on as projects of their own.

  • B2C migration

    The move to Entra External ID, with account links and password continuity for local accounts.

  • Entra authentication

    Microsoft Entra sign-in for your applications and the people who use them.

  • Multi-factor authentication

    A second verification step, with methods that suit your users, tenant and licensing.

  • Application sign-in and SSO

    Web, desktop and backend applications connected, with token validation.

QUESTIONS

Questions worth asking early.

Is Azure AD B2C being retired?

Microsoft stopped selling Azure AD B2C to new customers on 1 May 2025 and has said it will support existing tenants until at least May 2030. Entra External ID is the successor it directs customers to. Source: Microsoft's Azure AD B2C FAQ, checked November 2026.

Can you help with authentication if we are not migrating?

Yes. I implement Microsoft Entra sign-in, multi-factor authentication and application integration for new or existing setups. We agree the scope for your environment first.

Will customers need to reset their passwords?

Accounts that sign in with a local password can be designed to move at first sign-in using that password. Which accounts qualify, the exceptions and the recovery paths are assessed for your environment.

Will user IDs change?

The new directory can assign different identifiers. I plan a mapping so applications and business systems keep the relationship to the right customer.

What about social and company sign-in?

Each provider needs its own configuration and matching rules. I inventory the routes in use and review accounts connected to more than one provider.

How long does a migration take?

Discovery is free and takes a couple of days. From it I propose a plan with a timeline for your environment. The migration itself depends on identity routes, custom policies, applications, data quality and the testing needed.

What happens to B2C afterwards?

The existing route may need to stay available during coexistence and for unresolved accounts. Retirement follows agreed evidence and exit criteria.

NEXT STEP

Start with a free
30-minute assessment.

Bring the questions and constraints, whether it is a migration, a new sign-in or MFA. You leave with a sensible next step.

Online booking is not configured yet. Contact details will be added before launch.

  1. 01Call

    Thirty minutes on your current setup and what you need.

  2. 02Discovery

    A couple of days, free of charge, ending in a proposed plan.

  3. 03Decision

    You choose whether and how to continue.