Demonstrates how to create an A/B testing policy to check a new user experience. For example, if you introduce new features into the user journey, such as the ability to sign-in with Google or MFA, you can test the policy for 50% of your users.
The first step of the SignUpOrSignIn_WithAbTesting invokes Get-RandomNumber technical profile that returns randomNumber claim with 0 or 1 values. Based on the value returned the user journey calls the corresponding sub user journey.
To test the policy, run the B2C_1A_signup_signin_WithAbTesting. Then, refresh the page several times. You should see that the sign-in with Google button appears and disappears (based on the random value).
Use Stack Overflow to get support from the community. Ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before. Make sure that your questions or comments are tagged with [azure-ad-b2c]. If you find a bug in the sample, please raise the issue on GitHub Issues. To provide product feedback, visit the Azure Active Directory B2C Feedback page.
This sample policy is based on SocialAndLocalAccountsWithMFA starter pack. All changes are marked with Sample: comment inside the policy XML files. Make the necessary changes in the Sample action required sections.