Leaving B2C means migrating either way so make it Auth0
Where Auth0 and External ID differ, chapter by chapter
Moving to External ID is a migration too
Microsoft stopped selling B2C in May 2025 and its answer is External ID. Getting there means rebuilding your journeys and moving every member's password, which is the same work it takes to move to any other identity provider. If you're migrating anyway move to Auth0.
End of sale
B2C is no longer sold to new customers. Existing tenants keep running.
P2 discontinued
B2C Premium P2 retired for all customers. P2 tenants were moved to P1.
You are here
Your tenant still works and is still supported. Microsoft calls External ID its next generation product.
Supported until at least
Microsoft commits to support until at least this date and says migration plans are still to come.
Your custom policies
External ID doesn't run B2C custom policies. In July 2026 Microsoft shipped a Migration Policy Analyzer that scopes which parts of each policy need rebuilding or custom development.
Your members' passwords
B2C doesn't export password hashes. Every destination, External ID included, needs a just in time migration that checks each password against B2C at the member's next sign in. Microsoft's own migration guide uses the same approach.
Judge customer identity on its own, not as part of a bundle
External ID usually comes up as part of a bigger Microsoft conversation, next to Entra ID, Azure, and Microsoft 365. One vendor is simpler to buy. But customer identity does a different job than workforce identity: it's the front door for sign ups and revenue, it takes the brunt of credential attacks, and it has to handle partners and AI agents. It's also hard to replace once members are on it. Work through these questions before the bundle makes the call for you.
Can we run our own logic at every step of login?
03 · AttacksWhat stops credential stuffing on day one?
04 · PasskeysWill members adopt passkeys?
05 · PartnersCan each partner bring its own SSO?
06 · AI agentsHow do agents act for our customers safely?
07 · MigrationIf we ever leave, do passwords come with us?
Run your own logic at any step of login
Tidewell wants two things: the member's loyalty tier in every token, and an MFA prompt when a Platinum member redeems points. Below is that requirement on each platform.
azp, aud, iss).OnTokenIssuanceStart.External ID column: Microsoft's list of custom authentication extension events (updated May 2026) plus the password event its migration guide uses. Each extension calls a REST API you host and secure. Auth0 Actions run inside the login pipeline as Node.js, with secrets, npm packages, and version history.
What happens when leaked passwords hit your login
Attackers replay leaked email and password pairs against your login. Turn Auth0's protections on and off, then launch the attack.
This is a simulation with made up rates. It shows how the layers stack, not real block rates.
Interactive simulation of a credential stuffing attack against the login. Open the link to run it.
Members are signing in normally. Launch the attack to see what gets through.
Built into the login
- Bot Detection, Suspicious IP Throttling, Brute Force Protection, and Breached Password Detection are Attack Protection features in the same tenant.
- They apply at sign in as well as sign up, so a replayed password list runs into every layer above.
- Which features you get depends on your plan.
Partly built in, partly partners
- Smart lockout and custom banned password lists are built in. SMS uses CAPTCHA and telephony throttling.
- Sign up bot and fake account protection comes from Arkose Labs or HUMAN Security, set up through the Microsoft Security Store.
- Entra ID Protection, Microsoft's risk detection service, isn't supported in external tenants.
Getting members onto passkeys
The best moment to offer a passkey is right after a successful sign in, when the member is already verified. Auth0 calls this progressive enrollment. Follow Maya, a Tidewell Gold member.
Animated passkey enrollment on a phone. Open the link to watch it.
Welcome back
Sign in to Tidewell Rewards
Skip the password next time?
Create a passkey and sign in with your face or fingerprint.
Verifying…
Welcome back, Maya
maya.chen@example.com
Use password instead
Hi Maya
Gold member · 48,210 points
Ask right after sign in
- Progressive enrollment offers a passkey right after a password sign in. Members can put it off and keep using their password.
- Works on a custom database connection with Import Users to Auth0 turned on, so members arriving through a migration can enroll on their first sign in.
- Native passkey APIs for iOS and Android apps, alongside Universal Login on the web.
Passkeys with conditions
- Only email or username plus password accounts can register one. Social sign in and email code users can't.
- Members must complete MFA before they can register a passkey.
- Registration requires a custom URL domain.
Both platforms bind passkeys to your domain, so set up a custom domain before launch either way.
Give each partner its own login, SSO, and roles
Tidewell sells through agencies and corporate travel accounts. Each partner wants its own SSO, its own branding, and control over who's in. In Auth0, each partner is an Organization. Choose a partner to see its login.
Members
Invitations go out by email. Your partner portal sends them through the Auth0 Management API.
Each partner managed on its own
- Each Organization gets its own enterprise connection: Okta, Microsoft Entra ID, Google Workspace, any SAML or OIDC provider.
- Logo and colors per Organization on the same Universal Login page.
- Roles assigned per Organization, so one person can be an admin at one agency and a booker at another.
- Email invitations into a specific Organization.
Business sign up today, partner management still filling in
- Self service sign up supports business customers, and federation with Entra ID, OIDC, and SAML providers is available.
- Invitations in external tenants are for administrative roles only. Microsoft states they can't be used to bring customers into your apps.
- Groups and application roles are still being phased in.
Letting an AI agent book for a member
Tidewell's concierge books rooms for members. It has to know who it's acting for, call Tidewell's tools with only the access it needs, ask before spending money, and reach the member's calendar without holding their password.
Interactive conversation: the Tidewell concierge books a room for a member while Auth0 handles each step. Open the link to watch it.
Lisbon Harbor Suite · May 3 to 6 · $1,840 on your card ending 4417
Agents your customers use
- User authentication, Token Vault, Async Authorization, and fine grained authorization for RAG, in the same tenant as your members.
- Auth for MCP secures your MCP server for clients like ChatGPT, Claude, and Cursor.
- The member stays in control: consent up front, approval for sensitive steps.
Agents your company runs
- Gives agents inside your organization an identity, governed with Conditional Access and audit logs.
- Available to Entra customers. Extending Entra security features to agents requires Microsoft Agent 365, included in Microsoft 365 E7 or sold as an add-on.
- A strong fit for workforce agents. Customer facing agents are a different problem.
Moving 4.2 million members without a mass password reset
Moving in, and keeping a way out
Each dot is about 3,600 Tidewell members. Start the migration and watch members move to Auth0 as they sign in, keeping the password they already have.
Coming from your own user database? Auth0 imports common password hash formats directly, so most members move on day one with their existing password. Each dot is about 3,600 members.
Interactive migration: members move to Auth0 as they sign in. Open the link to run it.
Activity rates in this model are illustrative. Real numbers depend on how often your members sign in.
- PrepareStand up Auth0 on your custom domain, rebuild journeys as Actions, and turn on a ROPC user flow in B2C for local accounts.
- Move members on sign inA custom database connection with Import Users to Auth0 checks each password against B2C once, then stores the member in Auth0. Social sign in users keep using Google or Apple, and an Action can copy their B2C profile through Microsoft Graph.
- Import the long tailBulk import remaining profiles. B2C has no hashes to give, so these members set a new password when they return.
- Retire B2CPoint the last apps at Auth0 and switch the tenant off.
- PrepareStand up Auth0 on your custom domain and export users with their password hashes.
- Bulk import with hashesbcrypt imports as is. Argon2, PBKDF2, scrypt, the SHA and MD families, HMAC, and LDAP formats go in
custom_password_hash. - Move the rest on sign inMembers with an unsupported hash format move through a custom database connection the next time they sign in.
- Retire the old storeSwitch the legacy database off.
The login script that checks passwords against B2C
One member in a bulk import file
The door opens both ways
Auth0's standard export tools leave out password hashes, but you can request them through a support ticket. If you ever move on, your members' passwords can move with them.
Worth asking now
B2C doesn't export password hashes, so moves off it rely on checking passwords against B2C with the ROPC flow. External ID lists ROPC as unsupported. Ask Microsoft how a future move off External ID would carry passwords.
Tick what you run today and get your move to Auth0 as a list you can forward
Steps are in the order most teams run them. The real plan depends on your apps and how often members sign in.
Entra ID for employees, Auth0 for customers
Microsoft's pitch is one vendor for every kind of identity. That's simpler on paper, but your workforce and your customers need different things, and the right platform for one isn't automatically right for the other. You don't have to choose between Microsoft and Auth0. Each one does the job it's built for.
Your workforce stays put
Employees, admins, and support staff keep signing in with Entra ID. Nothing changes for IT, and Auth0 doesn't try to replace workforce identity.
Customer login earns its own decision
Customer login drives sign ups, revenue, and how your brand feels. Judge it on what the chapters above test (extensibility, attack protection, partners, and agents), not on what came with the bundle.
Keep your options open
With one vendor across workforce, cloud, and customer login, one contract and one roadmap decide all three. Auth0 connects over standard OIDC and SAML to apps on Azure, AWS, or anywhere else.
Five questions to ask any customer identity vendor, including us
Put the same questions to every vendor on your shortlist and compare the answers side by side.
- What's the supported path off B2C and what happens to our custom policies?
- Which features we need are generally available today and which are still in preview?
- Can we run our own code at sign up and login without managing XML or extra infrastructure?
- Which sign up and login events can we run our own code on today?
- Can we export our users' password hashes if we ever leave, and how?
- What bot and credential stuffing protection is built in and what costs extra?
- How do AI agents get access on a customer's behalf that's scoped and that we can revoke?
Bring us your B2C tenant
Bring us your requirements
- Send your custom policy files or a list of your user flows. We'll map every journey to Auth0 and flag what changes.
- Tell us your rough sign in patterns. We'll size the just in time window and the long tail.
- You get a written migration plan with the cutover steps and a rollback path.
- Share your apps, sign in methods, and partner scenarios. We'll walk each one through Auth0 live.
- Bring the hard cases: custom logic in login, partner SSO, agents acting for customers.
- You get a side by side write up you can take to your architecture review.
Sources
Accessed November 15 to 19, 2026.