Hello Atul !
Thank you for posting on Microsoft Learn.
From the error you are getting, I think that you have an issue with the token exchange process failing and it can be due to scope misconfiguration or incorrect token request format.
Chatbots use OAuth 2.0 behind the scenes with an AAD B2C connection set in the Bot Channel Registration, so if you're using custom policies, the scope you use must match the scope configured in the Azure AD B2C app registration.
The scope shoul be set to:
<client_id>
or:
https://<tenant>.onmicrosoft.com/<custom-api>/user_impersonation
You need to avoid using the offline_access or openid scope unless required and supported.
Another thing to be aware of, is that the token endpoint must match the custom policy in the OAuth Connection Settings:
https://<tenant>.b2clogin.com/<tenant>.onmicrosoft.com/B2C_1A_signup_signin/oauth2/v2.0/token
Sometimes the custom policy XML does not pass client_id or misses required output claims for token issuance so the RelyingParty section in the policy returns the correct claims, like sub, email...
These steps will help you investigate the issue, but if the problem still persists I recommend that you open a support ticket for better assistance.