![]() Complete the steps in Get started with custom policies in Active Directory B2C.For example, the customer can sign in to a banking application with a social or local account and check the account balance, but must verify the phone number before attempting a wire transfer. You don't require multifactor authentication to access an application in general, but you do require it to access the sensitive portions within it.For example, the customer can sign into an auto insurance application with a social or local account, but must verify the phone number before accessing the home insurance application registered in the same directory. You don't require multifactor authentication to access one application, but you do require it to access another.This feature helps applications handle scenarios such as: If you already created sign up and sign-in user flows, you can still enable multifactor authentication. You enable multifactor authentication without writing a single line of code. The steps required in this article are different for each method.Īzure Active Directory B2C (Azure AD B2C) integrates directly with Azure AD Multi-Factor Authentication so that you can add a second layer of security to sign-up and sign-in experiences in your applications. Azure Active Directory B2C offers two methods to define how users interact with your applications: through predefined user flows or through fully configurable custom policies. ![]() ![]() ![]() Before you begin, use the Choose a policy type selector to choose the type of policy you’re setting up. ![]()
0 Comments
Leave a Reply. |