Cloud and platforms
Cognito vs Entra External ID vs Google Identity Platform
In short
The three products differ in what you create and what you can tune. Cognito gives you regional user pools with token lifetimes set per app client. External ID uses a separate external tenant, with access-token lifetime set through Microsoft Graph. Identity Platform keeps users in a project, with tenants as an option. Triggers, MFA and migration paths differ too.
What do you actually create in each product?
In Amazon Cognito you create a user pool, a user directory that issues OIDC tokens. It needs no identity pool. Quotas are per Region: 1,000 user pools by default (adjustable to 10,000) and 40,000,000 users per pool.
In Microsoft Entra External ID you create a separate tenant with an external configuration. The docs say it is distinct from your workforce tenant and cannot be created in the Azure portal, only in the Microsoft Entra admin center. Defaults are 20 external tenants per subscription and 300,000 objects per tenant.
In Google Identity Platform the project is the container. Tenants are an optional multi-tenancy feature: separate silos of users and settings inside one project. The quotas page lists 2 tenants per project without a billing instrument.
The names are current on the pages I read. Microsoft says Azure AD B2C stopped being available to new customers on 1 May 2025. Google calls the product Identity Platform and keeps MFA, blocking functions, SAML, OIDC and multi-tenancy out of plain Firebase Authentication.
Checked against: source 1, source 2, source 8, source 9, source 10, source 15, source 16, source 20
Which sign-in methods and federation does each support?
Cognito user pools accept Amazon, Google, Apple and Facebook sign-in plus SAML and OIDC providers, up to 300 identity providers per pool by default. Its docs footnote that MFA and security monitoring are unavailable to federated users.
External ID names username and password, one-time passcode, and Google, Facebook, Apple, Microsoft Entra ID and custom OIDC identities. SAML appears on that page as a protocol your registered apps can use, not as a customer identity provider.
Identity Platform lists email and password, phone, Google, Facebook, Twitter, GitHub, SAML, OIDC, anonymous and custom auth. Inside a tenant the multi-tenancy page narrows this to email and password, Google, Microsoft, LinkedIn, SAML and OIDC. Google lists no limit on identity providers per project or tenant.
Checked against: source 1, source 2, source 8, source 16, source 22
Which token lifetimes can you change?
Cognito lets you set them per app client. ID and access tokens run from 5 minutes to 1 day, and refresh tokens from 1 hour to 3,650 days, with a 30-day refresh default. Optional refresh token rotation has a grace period of up to 60 seconds and does not extend the original window.
Entra has one setting, AccessTokenLifetime, covering access, ID and SAML tokens, from 10 minutes to 1 day. It is managed only through Microsoft Graph, with no portal screen. Refresh and session lifetimes stopped being configurable on 30 January 2021, and the page points to Conditional Access sign-in frequency instead. That page covers the Microsoft identity platform generally and does not mention external tenants.
For Identity Platform I found no lifetime setting in the pages I read. Google's IAP documentation says Identity Platform sessions are valid for one hour. I would treat that as fixed until Google documents otherwise.
How do the MFA options differ?
Cognito sets MFA to required, optional or off for the whole pool. Methods are SMS, email and TOTP. Email MFA needs your own Amazon SES setup and the Essentials or Plus feature plan. A passkey with user verification can satisfy MFA as a first factor, but it cannot be a second factor after a password.
External ID enforces MFA through Conditional Access after the first factor. Methods are email one-time passcode, SMS (an add-on), TOTP and passkeys, but your first factor limits the second: email one-time passcode cannot be reused as MFA. The page says TOTP in external tenants becomes generally available at the end of November 2026, and that TOTP and passkeys are not available through the Native Authentication API or Bring Your Own UX.
Identity Platform documents SMS MFA setup. TOTP appears only in sign-in code samples. MFA needs a verified email and works with every provider except phone, anonymous and Apple Game Center. A user can hold up to 5 second factors.
Where do custom claims and sign-in logic run?
Each product calls your code at different points, with different limits.
Cognito can customize access tokens only with trigger event version 2 or 3 on the Essentials or Plus plan, and version 3 is needed for machine-to-machine tokens. Entra offers events for token issuance, attribute collection and one-time passcode sending, and the REST API it calls must be publicly accessible. Google splits claims in two: custom claims persist on the user record, while session claims set in beforeSignIn apply to the current token only.
| Product | Hook | Time limit | Other documented limit |
|---|---|---|---|
| Cognito | Pre token generation Lambda | 5 seconds, fixed | 5,000 combined claim and scope changes |
| Entra External ID | Custom authentication extension | 2,000 ms, 1 retry | 50 requests per second per tenant, 100 extensions |
| Identity Platform | Blocking functions | 7 seconds | Custom claims cannot exceed 1000 bytes |
Checked against: source 5, source 6, source 10, source 13, source 17, source 21
What do the docs say about migrating users in?
Cognito has a CSV import of up to 500,000 rows and 100 MB, and a migrate-user Lambda trigger that moves users at first sign-in. A CSV job can carry password hashes in one algorithm per job: bcrypt, scrypt, Argon2id or PBKDF2-SHA256. Without hashes, users are set to reset their password.
The External ID migration page describes creating users through Microsoft Graph. You set plaintext passwords if you hold them. Otherwise you set random ones and validate the old password at sign-in with a custom extension, or let users reset. It does not describe importing hashes.
Identity Platform imports up to 1000 users per call with the Admin SDK. It lists HMAC, MD5, SHA, PBKDF2, scrypt and bcrypt hash types. It performs no duplicate checks, and a matching uid replaces the existing user.
I would start from how your current passwords are stored. That is the question the three docs answer most differently.
What else do people ask?
Is Azure AD B2C the same thing as Entra External ID?
Not exactly. Microsoft says External ID is its next-generation customer identity product and that Azure AD B2C is no longer available to new customers since 1 May 2025.
Does Firebase Authentication include MFA?
Google's comparison page lists MFA, blocking functions, SAML, OIDC and multi-tenancy under Identity Platform only. Upgrading is described as needing no app changes.
Sources
- AWS, What is Amazon Cognito, fetched 2026-11-19
- AWS, Quotas in Amazon Cognito, fetched 2026-11-19
- AWS, Cognito refresh tokens, fetched 2026-11-19
- AWS, Adding MFA to a Cognito user pool, fetched 2026-11-19
- AWS, Cognito pre token generation Lambda trigger, fetched 2026-11-19
- AWS, Customizing user pool workflows with Lambda triggers, fetched 2026-11-19
- AWS, Importing users into a Cognito user pool from a CSV file, fetched 2026-11-19
- Microsoft Learn, External tenant overview (Entra External ID), fetched 2026-11-19
- Microsoft Learn, Entra External ID tenant configurations, fetched 2026-11-19
- Microsoft Learn, External ID service limits and restrictions, fetched 2026-11-19
- Microsoft Learn, Configurable token lifetimes, fetched 2026-11-19
- Microsoft Learn, Multifactor authentication in external tenants, fetched 2026-11-19
- Microsoft Learn, Custom authentication extensions overview, fetched 2026-11-19
- Microsoft Learn, Migrate users and credentials to External ID, fetched 2026-11-19
- Google Cloud, Identity Platform and Firebase Authentication comparison, fetched 2026-11-19
- Google Cloud, Identity Platform multi-tenancy, fetched 2026-11-19
- Google Cloud, Identity Platform blocking functions, fetched 2026-11-19
- Google Cloud, Identity Platform multi-factor authentication (web), fetched 2026-11-19
- Google Cloud, Migrating users to Identity Platform, fetched 2026-11-19
- Google Cloud, Identity Platform quotas, fetched 2026-11-19
- Google Cloud, Configure custom claims on users, fetched 2026-11-19
- Google Cloud, Identity Platform authentication concepts, fetched 2026-11-19
- Google Cloud, Managing sessions with external identities (IAP), fetched 2026-11-19
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page compares vendor documents that I fetched on 19 Nov 2026. I did not run Cognito, Entra External ID or Identity Platform for it, so it reports documented limits, not observed behaviour. It does not cover prices, SDK details, or how each product behaves under load. Found a mistake? Tell me.