The Fork
Auth0 and Microsoft Entra External ID

Your customer login is changing. Choose where it lands.

Follow Tidewell Hotels & Resorts, a fictional brand with 4.2 million loyalty members, through the decision and the move. It takes about ten minutes. Start with where you are today.

Short on time? Read the two minute version for or .

The two minute version

Leaving B2C means migrating either way so make it Auth0

Where Auth0 and External ID differ, chapter by chapter

    01 · The clock

    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.

    1 · May 1, 2025

    End of sale

    B2C is no longer sold to new customers. Existing tenants keep running.

    2 · Mar 15, 2026

    P2 discontinued

    B2C Premium P2 retired for all customers. P2 tenants were moved to P1.

    3 · Nov 2026

    You are here

    Your tenant still works and is still supported. Microsoft calls External ID its next generation product.

    4 · May 2030

    Supported until at least

    Microsoft commits to support until at least this date and says migration plans are still to come.

    Doesn't move #1

    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.

    Doesn't move #2

    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.

    01 · The decision

    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.

    Next: Extensibility
    02 · Extensibility

    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.

    1Build and host an API, for example an Azure Function, and validate the bearer token Entra sends (azp, aud, iss).
    2Register a custom authentication extension and a custom claims provider on OnTokenIssuanceStart.
    3Return the tier in Microsoft's response format (below). The tier claim is done.
    4Tier based MFA: the documented events add claims, check sign up fields, or send OTP email. None of them decides MFA, so that rule moves into your app or a broader Conditional Access policy.
    
            
    B2C policy excerpt
    Auth0 Action
    Moment in the flowAuth0 ActionsExternal ID extensions

    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.

    Next: Attack protection
    03 · Attack protection

    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.

    Member Attack request CAPTCHA failed Breached password stopped
    0
    Attack requests
    0
    Stopped by Auth0
    0
    Wrong password
    0
    Accounts taken over

    Members are signing in normally. Launch the attack to see what gets through.

    Auth0

    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.
    Entra External ID

    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.
    Next: Passkeys
    04 · Passkeys

    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.

    Welcome back

    Sign in to Tidewell Rewards

    Sign in
    Skip the password next time?

    Create a passkey and sign in with your face or fingerprint.

    Create a passkey
    Remind me later

    Verifying…

    Welcome back, Maya

    maya.chen@example.com

    Continue with passkey

    Use password instead

    Hi Maya

    Gold member · 48,210 points

    Upcoming stay
    Lisbon Harbor
    May 3 to 6
    ✓ Signed in with a passkey, no password typed
      
    Auth0

    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.
    Entra External ID

    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.

    Next: Partners
    05 · Partners

    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.

    Auth0 Organizations

    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.
    Entra External ID

    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.
    Next: AI agents
    06 · AI agents

    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.

    Tidewell Concierge
    What Auth0 is doing
    Scroll here to start the conversation.
    Auth0 for AI Agents · generally available since Nov 2025 Auth for MCP · generally available since May 2026
    Auth0 for AI Agents

    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.
    Microsoft Entra Agent ID

    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.
    Next: Migration
    07 · The move

    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.

    Azure AD B2CLegacy user database Auth0
    Not moved yet Moved on sign inMoved with password Profile imported, sets a password on return
    0
    Day
    0%
    Members on Auth0
    0
    Forced resets for active members
    0
    Dormant members who set a password on return

    Activity rates in this model are illustrative. Real numbers depend on how often your members sign in.

    1. PrepareStand up Auth0 on your custom domain, rebuild journeys as Actions, and turn on a ROPC user flow in B2C for local accounts.
    2. 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.
    3. Import the long tailBulk import remaining profiles. B2C has no hashes to give, so these members set a new password when they return.
    4. Retire B2CPoint the last apps at Auth0 and switch the tenant off.
    1. PrepareStand up Auth0 on your custom domain and export users with their password hashes.
    2. Bulk import with hashesbcrypt imports as is. Argon2, PBKDF2, scrypt, the SHA and MD families, HMAC, and LDAP formats go in custom_password_hash.
    3. Move the rest on sign inMembers with an unsupported hash format move through a custom database connection the next time they sign in.
    4. Retire the old storeSwitch the legacy database off.
    The login script that checks passwords against B2C
    
        
    One member in a bulk import file
    
        
    Leaving Auth0

    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.

    Leaving Microsoft

    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.

    Plan your move

    Tick what you run today and get your move to Auth0 as a list you can forward

    Your move to Auth0

      Steps are in the order most teams run them. The real plan depends on your apps and how often members sign in.

      Next: Using both
      08 · Using both

      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.

      Microsoft Entra IDWorkforce identity
      EmployeesSupport staffAdmins
      Auth0Customer and partner identity
      MembersAgenciesAI agents
      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.

      1. What's the supported path off B2C and what happens to our custom policies?
      2. Which features we need are generally available today and which are still in preview?
      3. Can we run our own code at sign up and login without managing XML or extra infrastructure?
      4. Which sign up and login events can we run our own code on today?
      5. Can we export our users' password hashes if we ever leave, and how?
      6. What bot and credential stuffing protection is built in and what costs extra?
      7. How do AI agents get access on a customer's behalf that's scoped and that we can revoke?
      Next: Next step