Skip to main content

3 posts tagged with "azure"

View All Tags

Migrating Azure AD B2C users without password hashes

· 16 min read
GR Patil
Phase Two

Azure AD B2C will not give you password hashes. Microsoft Graph's passwordProfile is a write path — you set a password on an account you are creating — and there is no property, endpoint or support process that reads one back. So moving users to Keycloak means moving profiles, which is easy, and then dealing with credentials, which is the whole project.

There are three patterns, and most migrations use two of them. Broker B2C as an OIDC identity provider and let users keep signing in through it while applications move. Validate the password at first login against B2C and store it locally. Send a reset to whoever is left at the cutover date.

The received wisdom — the pattern that works for Auth0 and Cognito — is that the second one is the default. For B2C it is not, and the reason is in Microsoft's own documentation: the only endpoint that can validate a B2C password from your code is the ROPC endpoint, which is documented as local-accounts-only and explicitly unsupported server-to-server. Start from brokering instead.

Everything below was run against Keycloak 26.8.1 in start-dev; the Java compiles against 26.8.1. Every HTTP status and response body is copied from an actual run.

Porting Azure AD B2C custom policies to Keycloak

· 15 min read
Jeff Patzer
Phase Two

Most of an Azure AD B2C custom policy maps onto Keycloak configuration rather than code. A user journey becomes an authentication flow, orchestration steps become executions, preconditions become conditional subflows, the claims schema becomes the declarative user profile, and page layouts become themes. None of that is Java.

Three things are not configuration. RESTful technical profiles called mid-journey become a custom Authenticator. Long claims-transformation chains become either several protocol mappers or one script mapper — and the script mapper is a JAR you build, not JavaScript you paste into the console, which surprises people. And orchestration that branches on a computed value rather than on the presence of a claim has no declarative equivalent at all.

Everything below was run against Keycloak 26.8.1 in start-dev. The Java compiles against 26.8.1; every HTTP status and response body is copied from an actual run.

What Azure AD B2C's end of sale actually means

· 10 min read
GR Patil
Phase Two

Azure AD B2C's end of sale means Microsoft stopped selling it to new customers on 1 May 2025 and committed to supporting it until at least May 2030. It is not being shut down. Existing customers keep their tenants, can still create new ones, and keep the SLA, the security updates and the compliance posture. What ended is the roadmap.

One other date is doing a lot of damage. Premium P2 was discontinued on 15 March 2026 for all customers, and tenants moved to P1. That is a pricing-tier retirement, not a tenant retirement — but it has been reported often enough as "B2C shuts down in March 2026" that it is worth saying plainly: your tenant is fine, and you have roughly four years to make a decision rather than four months to execute one.

Four years is enough time to make a good decision and short enough that the one you make now is the one you live with. Here is what the three realistic destinations actually cost.