Article guideContents, topics, tags, and RSS
Identity platforms are easy to compare badly. A polished sign-in component can make very different products look interchangeable. One supplies application components, another provides a complete identity service, and another leaves your team to operate the software.
The differences usually appear later. An enterprise customer asks for SAML and SCIM. One person belongs to three customer organizations. Account linking creates a security problem. Finance discovers that each vendor counts active users differently.
Customer identity and access management (CIAM) manages identities for people who use your customer applications.
This guide compares 16 platforms. It gives a direct recommendation for each common requirement, then explains the features and costs that can change that recommendation.
Reviewed: 20 November 2026. Recommendations are editorial assessments of official documentation, published plans, and architecture fit. Prices use USD unless a different currency is shown. Annual prices show the required commitment. Messaging, infrastructure, support, and optional services can add costs.
What is the best CIAM solution in 2026?
Auth0 is the best overall managed CIAM choice in this comparison. It is the strongest general starting point when you need consumer accounts, business customers, enterprise federation, and several application frameworks.
Its main advantage is breadth. Universal Login, Organizations, Actions, enterprise connections, and management APIs cover many common identity requirements. Its main drawback is commercial complexity. Features and allowances depend on the selected plan and customer model. Check the current Auth0 plans before you estimate production costs.
A more specific requirement can produce a better choice. Clerk suits React and Next.js teams that want ready-made account screens. Keycloak suits teams that need deployment control. Microsoft Entra External ID suits organizations that want Microsoft-operated customer identity.
These recommendations apply to the platforms reviewed here. They do not rank every identity product on the market.
Best CIAM by requirement
| Your main requirement | First choice | Why it fits | Main condition |
|---|---|---|---|
| Best overall | Auth0 | Broad managed identity for consumer and business applications | Price the required production features |
| Best for developers | Clerk for React and Next.js | Ready-made sign-in, account, and organization components | Use a paid plan for production MFA and passkeys |
| Best for a small organization | Clerk for a small web product team | Reduces the account interface work that a small team must maintain | Choose WorkOS instead when free hosted core authentication is the main priority |
| Best for a medium-sized organization | WorkOS for a growing B2B product | Customer SSO, directory integration, and enterprise setup tools | Choose Auth0 for a broader mix of consumer and business applications |
| Best for a large organization | Auth0, with the required enterprise agreement | Broad federation, application integration, extensibility, and support options | Validate regions, quotas, availability, and contractual controls |
| Best-of-breed | Auth0 for general CIAM | A specialist identity service that does not require a specific application backend | WorkOS is more focused when enterprise customer setup dominates |
| Best SaaS solution | Auth0 for broad requirements | Managed operation with a wide identity feature set | WorkOS or Clerk can be simpler for narrower product needs |
| Best for self-hosting | Keycloak | A broad identity server with a permissive open-source license | Your team owns upgrades, recovery, and security operations |
| Most complete managed product | Auth0, with the necessary plans and add-ons | Broad coverage across login, federation, organizations, extensions, and management | The free plan does not include the complete commercial offering |
| Complete commercial product for your own infrastructure | FusionAuth | One deployable product with an admin interface, APIs, themes, and tenant management | Advanced features require the relevant license |
| Closest Microsoft Entra fit | Microsoft Entra External ID | Microsoft customer identity with Microsoft administration and integration tools | External customer tenants have a different feature set from workforce tenants |
| Best independent B2B product with Entra integration | WorkOS | Entra SSO and directory synchronization with customer setup tools | SSO and Directory Sync are separate paid connections |
| Best free software for self-hosting | Keycloak | No software license fee or licensed user allowance | Infrastructure and operation still cost money |
| Best free hosted core authentication | WorkOS AuthKit | Up to one million monthly active users for core authentication | Enterprise connections and custom domains cost extra |
| Best starting point for AI agents | Auth0 for broad managed requirements | MCP authorization and access to users’ external accounts | Compare Descope; verify feature status, allowances, and permission enforcement |
Organization size is a guide to likely requirements, not a technical requirement itself. A small company can serve millions of customers. A large company can operate a simple customer portal.
For developers, the main distinction is the integration model. Clerk's SDKs and components suit teams that want account interfaces inside their application. A mixed framework environment may benefit more from Auth0 and standard protocols. A Microsoft-focused .NET team should also evaluate Entra External ID.
Auth0 appears in several rows because those requirements overlap. Here, best-of-breed means a specialist CIAM service that you can select independently of your database and application platform. Most complete means broad documented coverage across the functions below. It does not mean that one low-cost plan includes every function.
A short decision tree
Follow the questions in order. Use the first matching row to select candidates. Check them against your mandatory requirements.
| Step | Question | If yes, compare | If no |
|---|---|---|---|
| 1 | Must you deploy the identity service yourself? | Keycloak and FusionAuth | Go to step 2 |
| 2 | Is Microsoft Entra your main priority? | Entra External ID for Microsoft-operated CIAM; WorkOS and Auth0 for customer Entra SSO and SCIM | Go to step 3 |
| 3 | Is B2B SSO and SCIM setup your main priority? | WorkOS and Stytch | Go to step 4 |
| 4 | Do you want ready-made React or Next.js account components? | Clerk and Auth0 | Go to step 5 |
| 5 | Do you want to build login flows visually? | Descope and Auth0 | Compare Auth0 and cidaas |
For self-hosting, compare Keycloak and ZITADEL instead if open source is mandatory. Check the license terms.
Choose Entra External ID if Microsoft must operate the identity service. For customers’ existing Entra directories, compare WorkOS and Auth0.
Reject a candidate that fails a mandatory requirement. You do not need a second candidate that cannot meet your needs.
Do I need CIAM, or is ASP.NET Core Identity enough?
ASP.NET Core Identity can be enough for an application that manages its own accounts. Microsoft's selection guidance distinguishes that requirement from shared sign-in and access to your API from third-party applications.
I’d shortlist a dedicated identity service when several applications share sign-in, or customers need enterprise federation, provisioning, and delegated administration. Compare the integration and operating work alongside the license.
.NET does not require Microsoft-operated CIAM. ASP.NET Core's OpenID Connect client connects to compatible identity providers. An application account library and an external identity service can also work together.
What is the best free CIAM solution in 2026?
Keycloak is the best free CIAM software in this comparison if you can operate it yourself. It combines standard protocols, identity federation, MFA, passkeys, administration, and organizations. Its Apache-2.0 license does not impose a software MAU charge.
WorkOS AuthKit is the best free hosted option here for core authentication at high user volumes. Its allowance covers up to one million monthly active users. SSO and Directory Sync each start at $125 per connection per month. A custom domain costs $99 per month. See the WorkOS pricing and production environment requirements.
Stytch is a strong free alternative when a B2B pilot needs enterprise SSO and SCIM. Its allowance includes 10,000 monthly active users and five combined SSO or SCIM connections. A customer that uses both normally consumes two connections. Usage above the allowance creates charges. See the Stytch pricing.
“Free” needs a precise definition:
- Free software: You can run the software without a license charge. You provide the infrastructure and operations.
- A free hosted allowance: The vendor operates the service. Usage limits and paid features still apply.
- A trial or development plan: You can evaluate the product. This does not establish a free production option.
Free plans and the costs that matter
MAU means monthly active users. DAU means daily active users. Clerk uses monthly retained users, or MRU. These units are not interchangeable.
| Platform | Free route | Important paid boundary |
|---|---|---|
| Auth0 | 25,000 MAU, five organizations, one enterprise connection, and inbound SCIM | Pro MFA is paid. Paid B2C plans do not automatically retain the free B2B entitlements |
| Clerk | 50,000 MRU per app; 100 retained organizations with up to 20 members each | Pro starts at $25 monthly, or $20 per month annually. Production MFA and passkeys require a paid plan |
| WorkOS AuthKit | One million MAU for core authentication | Production requires billing details. Enterprise connections, custom domains, and audit services have separate charges |
| Stytch | 10,000 MAU; unlimited organizations; five combined SSO or SCIM connections | Metered charges above allowances. Some live operations require billing verification |
| Descope | 7,500 MAU, ten active tenants, three SSO connections, MFA, and passkeys | Pro starts at $249 per month annually. SCIM starts at Growth, from $799 per month annually |
| cidaas | A 30-day trial for 500 registered users | No permanent free production tier. Essentials starts at €699 per month for 1,000 registered users |
| Amazon Cognito | Lite and Essentials include 10,000 direct or social MAU; enterprise federation has a separate 50-MAU allowance | Plus has no direct or social free allowance. Messaging and machine access can add charges |
| Entra External ID | The first 50,000 MAU of the core service | Add-ons have separate charges. The core allowance does not include every paid capability |
| Google Identity Platform | 50,000 Tier 1 MAU; SAML and OIDC providers have a separate 50-MAU allowance | Enterprise federation above its allowance costs $0.015 per MAU. SMS costs extra |
| Keycloak | Free Apache-2.0 software for self-hosting | Infrastructure, upgrades, monitoring, recovery, and support are your responsibility |
| ZITADEL | Self-hosted AGPL core; Cloud Free includes 100 DAU, three identity providers, and unlimited stored users and organizations | Cloud Pro starts at $100 per month. Review commercial licensing if the AGPL terms do not fit |
| Ory | Free open-source components for self-hosting | The free managed Developer plan has zero production environments. Production starts at $770 per year, plus usage |
| SuperTokens | Free self-hosted core; managed core is free below 5,000 MAU | Production MFA, SAML, and multitenancy are paid features, including when self-hosted |
| FusionAuth | Free proprietary Community edition for self-hosting | Hosted service and advanced editions are paid. SCIM requires Enterprise |
| Curity | Free self-hosted Community edition with unlimited users | Community excludes MFA. Standard and Enterprise use quoted annual subscriptions |
| Supabase Auth | Managed Free includes 50,000 MAU; self-hosted Supabase is also available | Pro starts at $25 per month with 100,000 MAU. End-user SAML requires a paid plan |
Clerk counts a user as retained when that user returns at least 24 hours after registration. Its organization allowance also uses retained organizations. Ory measures managed usage with average daily active users. Read each definition before you compare a cost estimate.
Several practical limits can matter before the user allowance does. Clerk's production MFA and passkeys require payment. Supabase Free projects can pause after a week of inactivity. WorkOS requires billing information for production, even when core usage stays within its free allowance.
For a cost estimate, count users, customer organizations, SSO connections, and provisioning connections separately. Include messages, environments, log retention, support, migration, and your own operating work.
A cost example: 10,000 users and ten business customers
Consider one production application with 10,000 monthly active users. It serves ten business customers, each with 1,000 users.
Each customer needs one enterprise SSO connection and one SCIM directory connection. The application therefore needs ten SSO connections and ten directory connections. Assume all users qualify as retained users under Clerk's definition.
The application requires MFA. This example assumes no metered SMS, additional machine-token usage, or optional audit services.
The following calculations use public monthly prices on 20 November 2026, without an annual commitment or negotiated discount.
| Platform | Base and organization cost | SSO and directory calculation | Monthly subtotal |
|---|---|---|---|
| WorkOS AuthKit | $0 within the core user allowance | 10 × $125 SSO + 10 × $125 Directory Sync | $2,500 |
| Stytch B2B | $0 within the user and organization allowances | (20 connections − 5 included) × $125 | $1,875 |
| Clerk Pro + Enhanced B2B | $25 Pro + $100 Enhanced B2B | (10 SSO − 1 included) × $75; Directory Sync currently has no charge | $800 |
These are platform and connection subtotals. They exclude taxes, messages, implementation, migration, application infrastructure, and additional support or availability agreements. This comparison requires no optional branding package or custom authentication domain. WorkOS adds $99 per month if you need a custom domain.
Clerk needs Enhanced B2B here because each customer exceeds the standard 20-member organization limit. Its monthly Pro price differs from its advertised annual-plan equivalent.
Clerk's subtotal changes from January 2027. Its Directory Sync documentation confirms that billing starts on 1 January. Nine additional directory connections then add 9 × $75 = $675 per month. With the other listed rates unchanged, the same example becomes $1,475 per month. Do not multiply today's temporary $800 subtotal by twelve for a 2027 budget.
The connection counts explain much of the difference. WorkOS prices SSO and Directory Sync separately. Stytch shares one free allowance across both connection types. Clerk includes one connection of each type, with Directory Sync billing starting later.
For comparison, a simpler application with the same user count can have much lower platform charges. Remove the customer organizations, enterprise SSO, and SCIM requirements. WorkOS and Stytch Consumer then remain within their free core allowances. Clerk Pro costs $25 per month when production MFA is required.
These examples do not establish equivalent features or support commitments. Obtain a plan-specific price for Auth0. Do not treat Entra's free core allowance as a complete quote for this B2B workflow.
What would self-hosting cost?
A free license is only one part of the calculation. The following Keycloak example uses illustrative assumptions, not vendor prices or measured operating costs.
| Cost item | Assumption | Monthly cost |
|---|---|---|
| Keycloak software license | No license charge | $0 |
| Infrastructure, backups, and monitoring | Assumed combined monthly cost | $200 |
| Routine operating work | 8 hours × $100 per hour | $800 |
| Recurring total | $0 + $200 + $800 | $1,000 |
If initial setup takes 40 hours at the same rate, it adds $4,000. The first-year model becomes 12 × $1,000 + $4,000 = $16,000.
Replace these assumptions with your own rates, a tested deployment design, and your required availability. SaaS also needs integration and support work. Use the same cost categories when you compare the two models.
What tools and features do the platforms offer?
Customer identity is different from workforce identity for employees and internal applications.
Five distinctions make the comparison easier:
| Function | What it does | What it does not establish |
|---|---|---|
| Authentication | Confirms the identity of a user or service | Permission to access every application resource |
| Federation and SSO | Lets a customer use an external identity provider, such as Entra | Automatic creation, removal, or synchronization of every user |
| SCIM provisioning | Exchanges user and group lifecycle changes between systems | Immediate termination of every active application session |
| Organizations | Represents customer membership, invitations, and organization roles | Every resource permission in your application |
| Authorization | Determines which actions an identity can perform | The identity's authentication method |
OIDC means OpenID Connect. It provides a standard sign-in protocol. OAuth 2.0 governs delegated access. SAML is another common federation protocol. MFA means multifactor authentication. SCIM is the System for Cross-domain Identity Management.
A product can support a protocol without supplying a complete customer setup process. It can also support a feature only in a paid edition or a specific integration.
Authentication and customer administration
The table describes documented product capabilities. Paid identifies a commercial boundary. Preview and experimental identify incomplete release status. “Custom integration” means that the application team must supply additional work.
| Platform | Login security | Enterprise federation and provisioning | Customer organization model |
|---|---|---|---|
| Auth0 | Passkeys, MFA, and attack controls; advanced capabilities depend on plan | Enterprise SAML/OIDC; inbound SCIM with the required connection entitlement | Organizations, membership, roles, and delegated customer setup |
| Clerk | Passwords, social login, and email methods; production MFA/passkeys are paid | Enterprise SSO and Directory Sync have plan and connection limits | Organizations, invitations, and account components; advanced organization controls cost extra |
| WorkOS | Passwords, social login, email codes, MFA, and hosted passkeys | SAML/OIDC SSO and SCIM Directory Sync are separate products | Native organizations, memberships, roles, and customer Admin Portal |
| Stytch | Consumer and B2B authentication differ; B2B includes MFA | SAML/OIDC SSO and SCIM; combined connection allowance | Native B2B Organizations and Members, discovery, invitations, and policies |
| Descope | Passkeys, MFA, step-up checks, and configurable login flows | SSO; SCIM requires Growth or higher | Tenants, tenant policies, and roles; advanced authorization is paid |
| cidaas | MFA, passkeys, account linking, and consent tools | OAuth/OIDC, SAML, and SCIM; confirm plan entitlement | Groups and B2B identity tools; scope depends on the package |
| Cognito | MFA; Essentials adds passkeys; Plus adds adaptive threat protection | SAML/OIDC providers; native customer SCIM was not confirmed | User pools, groups, clients, and application-defined customer membership |
| Entra External ID | Hosted MFA, TOTP, and passkeys; integration-specific limits apply | External federation; outbound SCIM to apps in standard mode | Customer tenant objects and application design; not workforce feature parity |
| Google Identity Platform | Password, social, phone, and MFA methods | SAML/OIDC providers; native customer SCIM was not confirmed | Separate tenants isolate users and identity providers |
| Keycloak | MFA, passkeys, configurable flows, and identity brokering | OIDC/OAuth, SAML, LDAP/AD; supported native SCIM from version 26.8 | Realms, Organizations, groups, roles, and admin APIs |
| ZITADEL | MFA, passkeys, and passwordless login | OIDC/OAuth and SAML; SCIM API is Preview | Organizations, delegated administration, projects, roles, and service users |
| Ory | Kratos supplies identities, MFA, and passkeys | Hydra supplies OAuth/OIDC; Polis supplies enterprise federation and directory sync | Compose the required services; managed plan limits differ |
| SuperTokens | Authentication recipes and sessions; production MFA is paid | Production SAML is paid; SCIM needs custom endpoints | Production multitenancy and organization features have paid boundaries |
| FusionAuth | Basic TOTP; passkeys require a free license key; advanced MFA is paid | Standard federation; SCIM requires Enterprise | Tenants, applications, registrations, groups, and management APIs |
| Curity | Community has basic login; Standard adds MFA and more methods | OAuth/OIDC, edition-dependent SAML, and documented SCIM support | Identity profiles and data-source configuration; customer UI needs additional work |
| Supabase Auth | TOTP MFA; native passkeys are experimental | Social/custom OAuth/OIDC; paid SAML; native customer SCIM was not confirmed | Organization membership belongs in your application database |
SCIM requires particular care. Keycloak promoted its native API to supported status in version 26.8. Its realm-level SCIM API handles users and groups. The Organization API manages organization-group membership. ZITADEL still labels its SCIM API as Preview.
Supabase labels its passkey feature as experimental. Stytch documents different capabilities across Consumer and B2B products. Its official SDK comparison lists Consumer passkeys. Confirm the B2B API and SDK capabilities before you require the same flow.
Do I need a separate identity tenant for each customer?
For a B2B SaaS product, start by evaluating customer organizations within one identity service. An organization represents membership in a customer account. A separate identity tenant can also separate users, applications, configuration, and administration.
Auth0 Organizations supports a user who belongs to several customers. Separate Auth0 tenants do not automatically share those users.
Imagine a consultant who administers Company A but can only read Company B's projects. Switching company must also change the active organization and applicable permissions. Auth0's token guidance requires APIs to validate organization context and restrict resource access accordingly.
Compare separate tenants or deployments when required administration, region, or infrastructure boundaries demand them. An organization feature alone does not isolate your application's data.
Does SCIM remove access immediately?
Do not assume that a directory update ends every application session. Your integration must enforce the change in memberships, sessions, and API access.
For example, WorkOS Directory Sync alone does not create AuthKit users or revoke sessions on deprovisioning. Directory Provisioning adds membership handling and session revocation, and requires support enablement. Existing directories are not automatically covered.
Entra cannot directly revoke an application's own session cookie. Already-issued token claims can also remain stale. Test user removal with an existing session, a refresh attempt, and an API request. Measure when access actually ends.
Developer tools and operating responsibilities
| Platform | Tools you work with | Main architectural trade-off |
|---|---|---|
| Auth0 | Universal Login, Actions, Forms, SDKs, APIs, and deployment tools | Broad customization creates dependencies on Auth0's configuration and runtime |
| Clerk | Sign-in, profile, and organization components; SDKs, backend APIs, and webhooks | Strong application integration can increase the work needed to change provider |
| WorkOS | AuthKit, Admin Portal, SDKs, events, and directory APIs | Core identity, enterprise connections, and audit services have separate commercial units |
| Stytch | APIs, SDKs, login components, and embedded customer administration | Choose the Consumer or B2B identity model early |
| Descope | Visual Flows, connectors, hosted or embedded screens, and backend SDKs | Flow changes need testing and release controls |
| cidaas | Management APIs, workflows, webhooks, consent tools, and integration modules | Confirm which modules and controls the quoted package includes |
| Cognito | AWS APIs, CLI, Lambda triggers, managed login, and infrastructure configuration | AWS integration is strong; customer administration often needs application work |
| Entra External ID | Microsoft Graph, MSAL, hosted authentication, and custom authentication extensions | Customer tenants and preview integrations need specific capability checks |
| Google Identity Platform | Firebase-compatible SDKs, Admin SDKs, blocking functions, and Google Cloud administration | Identity follows the Firebase and Google Cloud application model |
| Keycloak | Admin and account consoles, REST API, CLI, themes, and extensions | Your team operates the server, database, availability, and upgrade process |
| ZITADEL | Console, management APIs, Actions, service accounts, and audit history | Strong organization model; review AGPL terms and preview capabilities |
| Ory | Kratos, Hydra, Polis, Keto, Oathkeeper, APIs, and UI tools | You assemble the identity architecture from separate components |
| SuperTokens | Frontend SDK, backend SDK, Core service, recipes, and overrides | Authentication stays close to application code; enterprise features add cost |
| FusionAuth | Admin UI, management APIs, themes, webhooks, and one deployable runtime | Deployment control comes with license choices and operating work |
| Curity | RESTCONF administration, CLI, SDKs, configuration, and data-source integration | Strong identity and API infrastructure; less ready-made customer administration |
| Supabase Auth | Client SDKs, Auth APIs, hooks, JWT claims, and Postgres row-level security | Identity and database policy become part of the same backend choice |
Authentication logs are also different from a customer-facing audit product. Compare event export, retention, administrative events, and support access. WorkOS audit storage and streaming, Clerk log retention, and Descope audit connectors have different commercial boundaries.
Keep application authorization explicit. A CIAM role can identify a project administrator. Your application must still decide which projects that person can administer. Enforce that decision on the server.
Which CIAM is best for AI applications and agents?
For managed CIAM with broad AI agent requirements, I’d start with Auth0 and compare Descope. That recommendation reflects their documented options for MCP authorization and access to users’ external accounts.
The first question is whose permissions the agent uses. A chatbot behind a login can use normal CIAM. An agent acting for a customer needs delegated access. An autonomous agent needs its own identity and permissions.
MCP, the Model Context Protocol, connects agents to application tools and data. Here, MCP support means authorization for your application’s MCP server. A vendor’s administration MCP server serves a different purpose.
Where the platforms fit
| Platform | Where I’d evaluate it | What to verify |
|---|---|---|
| Auth0 | Token Vault manages credentials for users’ external accounts. Auth for MCP is generally available. | Required plans and usage allowances. The separate Agent as Principal feature remains in early access. |
| Descope | MCP authorization for your tools, and an Agent Auth SDK for credentials used by outbound calls. | Envoy, also called Agent Login, is a separate early-access feature that requires Enterprise. |
| WorkOS | MCP authorization and Pipes for external account connections. A useful candidate for teams already using WorkOS. | The separate Agent Auth product is in early access. Confirm the required commercial terms. |
| Stytch | Connected Apps lets external agents access your product through OAuth and MCP. It can work with an existing authentication provider. | This addresses access into your product. Check consent, scopes, and permission enforcement in your APIs. |
| Clerk | Its MCP guide provides a path for exposing tools from an existing Clerk application. | The application still checks permissions. Clerk announced Agent Auth in private beta on 30 October 2026. |
| Curity | Access Intelligence provides runtime authorization for agents. Consider it when you control the identity service and API architecture. | Test policy enforcement through your APIs or gateway, including approval for sensitive actions. |
| Keycloak | A self-hosted foundation for teams prepared to implement agent access. | Agent delegation is Preview. Its current MCP guide labels support for newer MCP versions Experimental. |
| Ory | Modular OAuth services with documented MCP integration paths. | The OSS Hydra v26.2.0 example lacks full resource-audience validation. The commercial OEL example supports resource indicators. |
| Microsoft Entra Agent ID | Agent identities and governance within the Microsoft ecosystem. Evaluate External ID separately for customer sign-in. | Agent ID is generally available, while some features remain in preview. Check agent governance licensing separately. |
Test a real permission boundary
Imagine a support agent that reads an assigned customer’s invoices and drafts a refund request. Reading an invoice and issuing a refund require different permissions. In this example, a person must approve the refund before the payment API executes it.
I’d use these checks in the proof of concept:
- Allow access to the assigned customer’s invoice.
- Deny access to another customer’s invoice.
- Require separate approval before issuing a refund.
- Revoke access, then repeat the request through the complete tool chain.
- Record the user, acting agent or service, requested action, and result.
Keep credentials out of model prompts. Enforce permissions in the tool or API that performs the action. A prompt asking an agent to behave is a poor substitute for an authorization check.
Revocation also needs testing at the external provider. For example, deleting an Auth0 connected account does not revoke provider tokens that were already issued.
The earlier cost examples exclude AI-specific add-ons and usage. For example, Descope meters machine exchanges, active consents, and active tokens separately from monthly active users. Price the complete agent flow.
Which CIAM works best with Microsoft Entra?
Choose Entra External ID when you want Microsoft-operated customer identity. Choose an independent CIAM when you want to connect customers' Entra directories to a separate product.
| What “close to Entra” means | Recommended route | What to verify |
|---|---|---|
| Microsoft should operate customer identity | Entra External ID, using an external customer tenant | Customer-tenant features, supported authentication approach, and preview limits |
| Customers should sign in with their existing Entra accounts | WorkOS for focused B2B setup; Auth0 for broader CIAM | Federation, organization mapping, customer administration, and connection cost |
| Customer directory changes should update application users and groups | WorkOS Directory Sync or Auth0 inbound SCIM | Provisioning direction, group mapping, synchronization delay, and session termination |
| Employees or invited partners need internal applications | Entra workforce applications and B2B collaboration | Whether customer CIAM is needed at all |
An external customer tenant is separate from a workforce tenant. Microsoft documents different tenant configurations for these audiences. Workforce capabilities do not automatically become available in customer tenants.
Microsoft supports configuring an existing Entra workforce tenant as an OIDC provider for an external customer tenant. This gives you a Microsoft-native route for customer accounts and federated business users.
Auth0 documents a Microsoft Entra enterprise connection. It also documents inbound SCIM from Entra, including user and group provisioning. Connection types and plan entitlements still matter.
WorkOS documents Entra SAML and Entra SCIM as separate integrations. This suits a B2B product that needs customer setup, federation, and directory events. Budget for both connections when a customer needs both services.
Do not confuse this with Entra External ID's outbound provisioning. Microsoft documents SCIM from external tenants to applications. Its service limits restrict this to standard mode. That does not establish equivalent inbound customer-directory functionality.
A Microsoft sign-in button is only one part of the integration. Test tenant identification, guest accounts, group changes, account linking, and user removal. Directory synchronization can be delayed. The application must also handle active sessions when access is removed.
Should I replace Azure AD B2C with Entra External ID?
Existing B2C customers do not face a general shutdown in 2026. Microsoft ended sales to new customers on 1 May 2025 and commits to support until at least May 2030. The B2C P2 tier retired separately on 15 March 2026.
External ID requires a migration. Microsoft's standard approach moves users and applications to an external tenant. Applications need updated configuration and token validation. Custom policy logic must be recreated, and equivalent behaviour is not guaranteed.
Inventory your identity providers, claims, recovery flows, and credential migration needs. Test the hardest custom sign-in journey before choosing a replacement.
Microsoft also documents High Scale Compatibility mode for very large existing tenants, with separate eligibility and feature limits. I’d compare the migration work for External ID with the work required for another CIAM.
SaaS or self-hosted: who operates the service?
With SaaS, the vendor operates the identity service. Your team still owns application integration, authorization, configuration, customer support, and the contract.
With self-hosting, your team also owns deployment, databases, upgrades, availability, keys, backups, and recovery. Free software removes a license charge. It does not remove those responsibilities.
Keycloak is the default self-hosted recommendation here. Its broad server functionality reduces the need to assemble several identity components. ZITADEL is particularly relevant when organizations and delegated administration drive the design. Ory suits teams that want separate identity, protocol, and authorization services.
FusionAuth fits a team that wants a commercially supported, deployable product. Curity deserves attention when OAuth/OIDC, API security, and customer-controlled infrastructure dominate the requirements.
The licenses differ. Keycloak and the relevant Ory and SuperTokens core components use permissive open-source licenses. ZITADEL uses AGPL-3.0-only with a commercial alternative. FusionAuth is proprietary. Curity is commercial software with a free Community edition.
A deployable product is not automatically open source. Check both the license and the feature entitlement for the version you plan to run.
What happens if the identity provider has an outage?
Existing sessions and new sign-ins can fail differently. An API that validates JWTs locally may continue accepting unexpired tokens with cached signing keys, subject to its authorization controls. New login, token refresh, and uncached key discovery can still fail.
Microsoft's signing-key guidance explains the cache and key-refresh dependency. Its resilience guidance covers token reuse and acquisition.
Test an existing session, a fresh login, token refresh, and a server with an empty key cache. Never bypass signature, issuer, audience, or expiry checks to keep requests flowing. Apply the same tests to self-hosted deployments.
How should vendor origin affect the choice?
Vendor origin can matter to procurement and operating policy. It does not establish where every identity record, backup, or support session goes.
cidaas identifies Widas ID GmbH in Germany and offers Germany/EU hosting. Curity is based in Sweden and provides software for customer-controlled deployment. Those are different ways to meet European sourcing requirements.
Check the contracting company, ownership, processing regions, subprocessors, support access, backup locations, and exit terms separately. A regional hosting option answers only part of that list.
Confirm the identity tenant's location before creating production accounts. For example, Entra External ID's Country/Region selection cannot be changed later.
The same applies to GDPR. Obtain the processing agreement and verify the actual data flows. Product features cannot determine your purposes, retention rules, or access decisions. The GDPR text remains the primary legal source.
Can I change CIAM provider without resetting every account?
Sometimes, if the source exports the required credentials and the destination accepts their formats. A user-list export does not establish either condition.
| Export route | Documented boundary |
|---|---|
| Auth0-hosted database | Password hashes require a support request. API and extension exports exclude them. |
| Clerk Dashboard | Includes password digests and TOTP secrets. Metadata requires another export route. |
| Clerk CLI or Backend API | Includes metadata, but excludes password digests and TOTP secrets. No Clerk export includes backup codes. |
Check each sign-in method separately. Clerk's documented instance migration also omits passkeys, social accounts, sessions, and Organizations. Those need a separate transfer or re-enrolment plan.
Passkeys depend on their relying-party ID. Preserving the login domain is only part of the work. Confirm that the destination can use the existing server-side credential records.
I’d test the exit before signing the contract. Export representative accounts, import them into the alternative, and test sign-in and recovery. Keep an application-owned user ID and map it to each provider's issuer and subject identifiers.
Include organization memberships, permissions, consent records, enterprise connections, and custom login logic in the migration plan. Budget for overlap and test rollback.
What should you test before choosing?
Build a small, realistic integration with your final two candidates. Use the planned production edition and actual identity providers.
- Connect your web or mobile application through the intended authentication flow.
- Add the real enterprise identity provider.
- Give one user different roles in two customer organizations.
- Enforce access to a real application resource on the server.
- Test account linking when two providers return the same email address.
- Test MFA recovery after a user loses an enrolled factor.
- If you need passkeys, test registration, device replacement, and recovery.
- Synchronize a user and a group through the intended provisioning connection.
- Remove that user upstream and measure the delay before application access ends.
- Export authentication and administrator events to your monitoring system.
- Test data export, deletion, and the proposed migration route.
- Calculate costs for expected usage and a higher-growth case.
For self-hosting, also test backup restoration, key rotation, and a failed upgrade. Assign an owner to each operation.
Choose the platform that your team can operate safely under those conditions. The sign-in screen is the easy part.
