Passwords
Passwords cannot be exported from B2C.
Just-in-time migration: local password accounts move at first sign-in, using the password the customer already knows.
AZURE AD B2C / ENTRA EXTERNAL ID / IDENTITY MIGRATION / APP AUTHENTICATION / MFA / SSO
Start with a clear plan: Microsoft Entra sign-in, MFA and single sign-on across your web, desktop and backend applications—or a B2C migration to Entra External ID, with account links and password continuity for eligible users.
The directory is one part of it. Four more things cross only when someone plans them.
Passwords cannot be exported from B2C.
Just-in-time migration: local password accounts move at first sign-in, using the password the customer already knows.
Business systems depend on existing identity keys.
Map old and new identifiers so the right account stays connected to the right services.
Passwords, social providers and company sign-in differ.
Design and test each route, including how to handle accounts with multiple providers.
Custom policies (Identity Experience Framework) do not carry over automatically.
Review the business rules they encode and design supported equivalents or alternatives.
HOW IT WORKS
Each migration is different. These stages give us a shared structure for the decisions, evidence and work ahead.
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
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
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
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
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
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
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
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
LESSONS LEARNED
Identity migrations are shaped by the edge cases as much as the main flow.
A provider may not return an email claim. Account matching needs a reliable fallback and explicit rules.
A password reset in the new system does not necessarily retire the old credential. Plan how both paths are handled.
Session behaviour, provider redirects and sign-in page styling need to be checked in the actual applications.
Accounts with several sign-in methods may need to remain on the existing route until the right target is clear.
EXAMPLE SCENARIO
A fictional scenario, not a client case study.
They use their accounts to reach their workspaces. The challenge is to move the sign-in platform without losing the connection between each person and the services they use.
The team prepares identities for the new platform and plans a password transition for local password accounts. The plan is tailored to the environment, with tests and clear exception handling.
In this scenario, those users sign in with their familiar passwords and remain connected to the workspaces and account information they already use.
Migration is the main work. Sign-in, MFA and single sign-on are also taken on as projects of their own.
The move to Entra External ID, with account links and password continuity for local accounts.
Microsoft Entra sign-in for your applications and the people who use them.
A second verification step, with methods that suit your users, tenant and licensing.
Web, desktop and backend applications connected, with token validation.
QUESTIONS
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.
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.
The new directory can assign different identifiers. I plan a mapping so applications and business systems keep the relationship to the right customer.
Each provider needs its own configuration and matching rules. I inventory the routes in use and review accounts connected to more than one provider.
There is no useful universal duration. It depends on identity routes, custom policies, applications, data quality and the testing needed. The assessment establishes the next steps.
The existing route may need to stay available during coexistence and for unresolved accounts. Retirement follows agreed evidence and exit criteria.
ABOUT
I’m an independent identity and authentication specialist. 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.
More about how I work →NEXT STEP
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.
Thirty minutes on your current setup and what you need.
A short written note of the risks and open questions.
You choose whether and how to continue.