Switch back to the (classic) Azure portal or navigate to it at . Sign in as the Subscription Administrator if needed. This is the same work or school account or the same Microsoft Account that you used to create your B2C tenant above. Navigate to the B2C tenant on the ACTIVE DIRECTORY extension by clicking in our configuration Contoso 369 Corporation. Click USERS. End users that signed up with a social identity are listed as cpim_<user#>@<YourDirectory>.onmicrosoft.com, where <YourDirectory> is the B2C tenant you created, and <user#> an allocated user number, for example in our configuration: cpim_964916140232284@contoso369b2c.onmicrosoft.com. Likewise, end users that signed up locally with a verified address mail are listed as <VerifiedEmailAddress>1#EXT#@<YourDirectory>.onmicrosoft.com, <VerifiedEmailAddress> is the verified email address where @ is replaced by an underscore. Adding Multi-Factor Authentication As previously depicted, Azure AD B2C integrates directly with Azure MFA to allow you to smoothly add an additional factor of authentication to sign-up and sign-in experiences in your consumer-facing applications Note For more information, see article . Let’s modify both the previously configured sign-up and sign-in policies, and try the reconfigured policies. Modifying the sign-up policy to enable authentication To enable a multi-factor authentication in the sign-up policy, proceed with the following steps: Switch back to the B2C features blade or navigate to the related URL: Sign-up policies. Click the previously configured B2C_1_B2CSignUp sign-up policy to open it. Click Edit at the top of the blade, and then click Multifactor authentication. Toggle to State ON. Click OK. Click Save at the top of the blade. A consumer account gets created in your B2C tenant before the multifactor authentication step occurs. During the step, the consumer is asked to provide their phone number and verify it. If verification is
Switch back to the (classic) Azure portal or navigate to it at . Sign in as the Subscription Administrator if needed. This is the same work or school account or the same Microsoft Account that you used to create your B2C tenant above. Navigate to the B2C tenant on the ACTIVE DIRECTORY extension by clicking in our configuration Contoso 369 Corporation. Click USERS. End users that signed up with a social identity are listed as cpim_<user#>@<YourDirectory>.onmicrosoft.com, where <YourDirectory> is the B2C tenant you created, and <user#> an allocated user number, for example in our configuration: cpim_964916140232284@contoso369b2c.onmicrosoft.com. Likewise, end users that signed up locally with a verified address mail are listed as <VerifiedEmailAddress>1#EXT#@<YourDirectory>.onmicrosoft.com, <VerifiedEmailAddress> is the verified email address where @ is replaced by an underscore. Adding Multi-Factor Authentication As previously depicted, Azure AD B2C integrates directly with Azure MFA to allow you to smoothly add an additional factor of authentication to sign-up and sign-in experiences in your consumer-facing applications Note For more information, see article . Let’s modify both the previously configured sign-up and sign-in policies, and try the reconfigured policies. Modifying the sign-up policy to enable authentication To enable a multi-factor authentication in the sign-up policy, proceed with the following steps: Switch back to the B2C features blade or navigate to the related URL: Sign-up policies. Click the previously configured B2C_1_B2CSignUp sign-up policy to open it. Click Edit at the top of the blade, and then click Multifactor authentication. Toggle State to ON. Click OK. Click Save at the top of the blade. A consumer account gets created in your B2C tenant before the multifactor authentication step occurs. During the step, the consumer is asked to provide their phone number and verify it. If verification is
An-overview-of-AAD-B2C.docx