Edit

Share via

Set up an OpenID Connect provider with Azure AD B2C

  • Article

Azure Active Directory (Azure AD) B2C is one of the OpenID Connect identity providers you can use to authenticate visitors to your Power Pages site. You can use any identity provider that conforms to the Open ID Connect specification.

This article describes the following steps:

Note

Changes to your site's authentication settings might take a few minutes to be reflected on the site. To see the changes immediately, restart the site in the admin center.

Set up Azure AD B2C in Power Pages

Set Azure AD B2C as an identity provider for your site.

  1. In your Power Pages site, select Security > Identity providers.

    If no identity providers appear, make sure External login is set to On in your site's general authentication settings.

  2. To the right of Azure Active Directory B2C, select More Commands (…) > Configure or select the provider name.

  3. Leave the provider name as it is or change it if you like.

    The provider name is the text on the button that users see when they select their identity provider on the sign-in page.

  4. Select Next.

  5. Under Reply URL, select Copy.

  6. Select Open Azure.

    Don't close your Power Pages browser tab. You'll return to it soon.

Create an app registration

Create a tenant for Azure AD B2C and register an application with your site's reply URL as the redirect URI.

  1. Create an Azure AD B2C tenant.

  2. Search for and select Azure AD B2C.

  3. Under Manage, select App registrations.

  4. Select New registration.

  5. Enter a name.

  6. Select one of the Supported account types that best reflects your organization requirements.

  7. Under Redirect URI, select Web as the platform, and then enter the reply URL of your site.

    • If you're using your site's default URL, paste the reply URL you copied.
    • If you're using a custom domain name, enter the custom URL. Be sure to use the same custom URL for the redirect URL in the settings for the identity provider on your site.

  8. Select Register.

  9. Copy the Application (client) ID.

  10. In the left side panel, under Manage, select Authentication.

  11. Under Implicit grant, select Access tokens (used for implicit flows).

  12. Select Save.

  13. Configure token compatibility using an Issuer (iss) claim URL that includes tfp. Learn more about token compatibility.

Create user flows

  1. Create a sign-up and sign-in user flow.

  2. (Optional) Create a password reset user flow.

Get the issuer URL from the user flows

  1. Open the sign-up and sign-in user flow you created.

  2. Go to the Azure AD B2C tenant in the Azure portal.

  3. Select Run user flow.

  4. Open the OpenID Connect configuration URL in a new browser tab.

    The URL refers to the OpenID Connect identity provider configuration document, also known as the OpenID well-known configuration endpoint.

  5. Copy the Issuer URL in the address bar. Don't include the quotation marks. Do make sure that the Issuer (iss) claim URL includes tfp.

  6. Open the password reset user flow, if you created one, and repeat steps 2–5.

Enter site settings and password reset settings in Power Pages

  1. Return to the Power Pages Configure identity provider page you left earlier.

  2. Under Configure site settings, enter the following values:

    • Authority: Paste the issuer URL you copied.​

    • Client ID​: Paste the Application (client) ID of the Azure AD B2C application you created.

    • Redirect URI: If your site uses a custom domain name, enter the custom URL; otherwise, leave the default value, which should be your site's reply URL.

  3. Under Password reset settings, enter the following values:

    • Default policy ID: Enter the name of the sign-up and sign-in user flow you created. The name is prefixed with B2C_1.

    • Password reset policy ID: If you created a password reset user flow, enter its name. The name is prefixed with B2C_1.

    • Valid issuers: Enter a comma-delimited list of the issuer URLs for the sign-up, sign-in, and password reset user flows you created.

  4. (Optional) Expand Additional settings and change the settings as needed.

  5. Select Confirm.

Additional settings in Power Pages

The additional settings give you finer control over how users authenticate with the Azure AD B2C identity provider. You don't need to set any of these values. They're entirely optional.

  • Registration claims mapping​ and Login claims mapping: In user authentication, a claim is information that describes a user's identity, like an email address or date of birth. When you sign in to an application or a website, it creates a token. A token contains information about your identity, including any claims that are associated with it. Tokens are used to authenticate your identity when you access other parts of the application or site or other applications and sites that are connected to the same identity provider. Claims mapping is a way to change the information that's included in a token. It can be used to customize the information that's available to the application or site and to control access to features or data. Registration claims mapping modifies the claims that are emitted when you register for an application or a site. Login claims mapping modifies the claims that are emitted when you sign in to an application or a site. Learn more about claims mapping policies.

    • You don't need to enter values for these settings if you use the email, first name, or last name attributes. For other attributes, enter a list of logical name/value pairs. Enter them in the format field_logical_name=jwt_attribute_name, where field_logical_name is the logical name of the field in Power Pages and jwt_attribute_name is the attribute with the value returned from the identity provider. These pairs are used to map claim values (created during sign-up or sign-in and returned from Azure AD B2C) to attributes in the contact record.

      For example, you use Job Title (jobTitle) and Postal Code (postalCode) as User Attributes in your user flow. You want to update the corresponding Contact table fields Job Title (jobtitle) and Address 1: ZIP / Postal Code (address1_postalcode). In this case, enter the claims mapping as jobtitle=jobTitle,address1_postalcode=postalCode.

  • External logout: This setting controls whether your site uses federated sign-out. With federated sign-out, when users sign out of an application or site, they're also signed out of all applications and sites that use the same identity provider. For example, if you sign in to a site using your Microsoft account, and then sign out of your Microsoft account, federated sign-out makes sure that you're signed out of the site, too.

    • On: Redirects users to the federated sign-out experience when they sign out of your website.
    • Off: Signs users out of your website only.

  • Contact mapping with email: This setting determines whether contacts are mapped to a corresponding email address when they sign in.

    • On: Associates a unique contact record with a matching email address and automatically assigns the external identity provider to the contact after the user successfully signs in.
    • Off: Contact record is not matched with an identity provider. This is the default option for this setting.

  • Registration enabled: This setting controls whether users can register on your site.

    • On: Displays a sign-up page where users can create an account on your site.
    • Off: Disables and hides the external account registration page.

See also

Set up site authentication
Migrate identity providers to Azure AD B2C