Azure B2C

This guide will explain how to set up an external login provider connecting to Azure AD, so that it becomes possible for users to login to the backend and frontend using Azure B2C accounts.

Please note that the Dynamicweb solution must have a valid SSL certificate.

To set up external authentication using Azure AD you must first create a tenant. An Azure AD tenant is a sort of directory, in this case a collection of user accounts which you want to give access to a Dynamicweb backend using their Azure B2C credentials.

  1. Go to
  1. After the tenant is created, click Continue to go to the Active directory Overview page where you need to navigate into B2C service
  1. Create Azure Active Directory B2C according to guide
  2. By default three user flows are created – they handle profile editing, password reset, and sign up/sign in. Note down their names as they are needed to configure the external login provider on the Dynamicweb solution.
  1. Open and edit the B2C_1_susi flow and configure it – we recommend that you check all attributes in application claims section

Next, you must register an Application – this provides you with a secure way of allowing requests and also ensures that your users are sent to a trusted place after signing in.

  1. Go to the application list
  2. Click New registration
  1. Fill in the details
    1. Name
    2. Account type – make sure you select an appropriate account type, as you cannot change it later
    3. Redirect url
    4. Permissions
  1. Once the application is created, note down the Application ID and Directory ID – they will be used for Dynamicweb provider settings
  1. Add you solution URIs to the application Redirect URIs – see below where [dw9.local] should be your solution url
  1. Also you need to scroll down the screen and make sure you have selected “ID tokens” option.
  1. Finally, create and note down a client secret key to use in the Dynamicweb provider settings

Ok, so with all that done you’re finally ready to set up the external login provider in Dynamicweb:

  1. Go to Settings > Control Panel > External Authentication and click Add in the toolbar
  2. Provide a name and (optionally) check enable for backend
  3. Select the Azure B2C  login provider and configure it (Figure 6.1)

The following settings are available:





From azure portal


Active directory id

From azure portal



From azure portal

Default is b2c_1_susi


From azure portal

Default is b2c_1_edit_profile


From azure portal

Default is b2c_1_reset

Application Id

From azure portal


Application key

From azure portal


Phone claim name


See appendix A

Customer impersonation id claim name


See appendix A

Redirect page

Page to redirect the user to after login.

Any url used here will need to be added to the Azure application redirect urls.

If left blank the user will be redirected to the first URL set on the Azure application

Logout from Azure on extranet logout


If not checked a returning user may be logged in immediately without being redirected to azure

Group for new users

Select group(s) for new users to be added to

To check if a user exists the provider first checks the email used (if included in the azure application claims) against the user database, then it checks if the default user name from Azure matches the User.Username in Dynamicweb.

If both of these checks return negative a new user is created with the email and username sent by Azure.



Generates more verbose logs for testing and debugging purposes


After configuring the provider and saving it you must IIS Reset the solution in order for the login provider to be loaded.

Once everything is setup, customers can log in to the frontend using their Azure B2C credentials. To use the B2C credentials to login to the backend a user must go to https://[solution url]/Admin/Access/ExternalAuthentication.aspx – and of course be authorized to log in.

From the Azure Active Directory B2C overview page you can go to user attributes list where you might add 2 custom user attributes works with Dynamicweb provider.

The attributes are:

  1. Phone custom attribute. If you create phone attribute and set its name as Dynamicweb “Phone claim name” the Dynamicweb user phone will be filled with value set to the Azure phone user custom attribute.
  2. CustomerId custom attribute. If you create phone attribute and set its name as Dynamicweb “Customer impersonation id claim name”. On Azure user login Dynamicweb will try to find other users having user customer number equal to “CustomerId” from Azure and if there is found user, it will be set as “User I can set as secondary” for the one who logged in.