2
votes

I'm following Microsoft's guidance to enable Dynamics Portal access via Azure AD B2C. Basics are up and running and working well. I'm using a "Sign-In" Policy. However, I'm having trouble with the claims mapping functionality.

I've configured the following site settings per the instructions in the document linked below.

Authentication/OpenIdConnect/B2C/RegistrationClaimsMapping Authentication/OpenIdConnect/B2C/LoginClaimsMapping

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/portals/azure-ad-b2c#claims-mapping

However, the mapped Dynamics attribute values are never (initial registration/contact creation, or subsequent logins) updated with values from Azure AD B2C, as expected based on this configuration.

An example of the Site Setting Value that I've tried: address1_city=http://schemas.xmlsoap.org/ws/2005/05/identity/claims/city

If I look at the JWT form data id_token after authentication, I see the values from B2C in the payload.

Is there an additional step not covered in the document to enable this functionality? Is this currently broken/not yet supported? Are my expectations of how this should be working (Dynamics attributes values updated based on B2C values) incorrect?

Thanks!

1

1 Answers

0
votes

Ensure you have the claim name the same as what is being returned within your ID Token. For example address1_city=city. Unless the Partner ClaimType within your B2C Policy is explicitly set to "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/city".