AADB2C90011 - user flow / policy always returns error.

Question

AADB2C90011 - user flow / policy always returns error.

David Bowman 0

I've tried setting up a new external identity, removing and adding the user flow and application identifier.

Nothing changes, as soon as I try to connect to Entra ID, I get this error - AADB2C90011: The client id '<actual client ID>' provided in the request does not match client id '4829629c-4ae8-42a5-9def-bd28fbfd6992' registered in policy.

Whats interesting here, I know nothing about the client id it's claiming is registered with the policy. Similarly, other messages identifying this error are all seeing the same client ID associated with the policy.

This seems to suggest that this is an internal Microsoft ID - and clearly a bug with the User Flow mechanism.

This problem has been registered more than once in the last year, and no resolution that I can find.

Can anyone at Microsoft suggest a solution?

Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-03-23T17:45:25.2433333+00:00
Hello David Bowman,

This is not a product bug. It happens when the client ID in the request does not match the one associated with the user flow.

The client ID shown in the error is typically from a previously linked or default application that the policy is still using.

Please check the following:

Verify the Application (client) ID in App registrations

Open the user flow and ensure your application is added to it

Confirm your request is using the correct:

client_id

policy name in the URL

Also try clearing browser cache or testing in a new session to rule out stale values.

If the issue still persists, create a new user flow, add your application, and test again. This helps identify if the existing policy is still tied to an older configuration.
David Bowman 0 Reputation points

2026-03-23T18:26:32.13+00:00
Hi

Thanks for the response, but that's not the behaviour I'm seeing.

Thus far I've tried:

Delete the user flow entirely and recreate it

Remove and add the Application associated with the flow

Build a completely new test app that uses the settings to connect

Run the app in incognito mode to eliminate caching issues

Create a new Flow with a different name

Verify communication with Azure by calling the endpoint directly

The situation simply is that the ID that is being used by the policy is incorrect. The error is reporting an ID associated with the policy (4829629c-4ae8-42a5-9def-bd28fbfd6992) that does not exist anywhere in my tenant. This is the same ID that other users have reported, which must be beyond coincidence.

The application ID that is registered with the user flow is the ID that is being passed from the client, this has been verified over and over again.

The problem doesn't appear to be with the configuration - I'm happy to share screen shots if that would help - but there's nothing I seem to be able to do to have the user flow use the actual application ID that is registered.

Your answer

Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-03-23T17:45:25.2433333+00:00

Hello David Bowman,

This is not a product bug. It happens when the client ID in the request does not match the one associated with the user flow.

The client ID shown in the error is typically from a previously linked or default application that the policy is still using.

Please check the following:

Verify the Application (client) ID in App registrations

Open the user flow and ensure your application is added to it

Confirm your request is using the correct:

client_id

policy name in the URL

Also try clearing browser cache or testing in a new session to rule out stale values.

If the issue still persists, create a new user flow, add your application, and test again. This helps identify if the existing policy is still tied to an older configuration.
David Bowman 0 Reputation points

2026-03-23T18:26:32.13+00:00

Hi

Thanks for the response, but that's not the behaviour I'm seeing.

Thus far I've tried:

Delete the user flow entirely and recreate it

Remove and add the Application associated with the flow

Build a completely new test app that uses the settings to connect

Run the app in incognito mode to eliminate caching issues

Create a new Flow with a different name

Verify communication with Azure by calling the endpoint directly

The situation simply is that the ID that is being used by the policy is incorrect. The error is reporting an ID associated with the policy (4829629c-4ae8-42a5-9def-bd28fbfd6992) that does not exist anywhere in my tenant. This is the same ID that other users have reported, which must be beyond coincidence.

The application ID that is registered with the user flow is the ID that is being passed from the client, this has been verified over and over again.

The problem doesn't appear to be with the configuration - I'm happy to share screen shots if that would help - but there's nothing I seem to be able to do to have the user flow use the actual application ID that is registered.