 <p>A claim from website A will not be sent to website B.</p> <p>This could work this way: </p> <ol> <li>A users logs on to site A (using credentials from B2C)</li> <li>User saves info into B2C (using Graph API)</li> <li>Redirect to Site B</li> <li>User logs on to site B (this can occur without prompting the user, same B2C)</li> <li>Claim are created for site B, but they can contain values set during step 2</li> </ol> <p>graph API: <a href="https://azure.microsoft.com/en-us/documentation/articles/active-directory-b2c-devquickstarts-graph-dotnet/" rel="nofollow">https://azure.microsoft.com/en-us/documentation/articles/active-directory-b2c-devquickstarts-graph-dotnet/</a> <hr /> If the info is already in the B2C directory, the example is even more simple, create 2 sites: <a href="https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-b2c-devquickstarts-web-dotnet/" rel="nofollow">https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-b2c-devquickstarts-web-dotnet/</a></p> <p>Create a custom attribute to store the information: <a href="https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-b2c-reference-custom-attr/" rel="nofollow">https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-b2c-reference-custom-attr/</a></p> <ul> <li>Create a B2C custom attribute: </li> <li>Create 2(both) B2C Applications</li> <li>Create a single B2C sign-in policy using the custom attribute and add it to the claims</li> <li>Use the same policy in both applications, both should see the same claim</li> </ul>