Skip Navigation

Migrate your Microsoft Azure IDP from Legacy Custom Authentication to the Modern Authenticator Framework

Two simple steps to add your Microsoft Azure IDP as an authenticator and use it in an authentication policy to secure console sign in.

You can also migrate the custom authentication settings for the following external IDPs. For instructions, click your IDP: 

You can configure the authenticator using one of the following two methods. BlackBerry recommends that you use the secure method to set up the authenticator for Cylance Endpoint Security. You can configure using the easy method first and switch to the secure method later. However, if you change the configuration method and you have configured your authenticator to require users to validate their email with a one-time code, users will need to validate again the next time that they sign in after the change.

Federated ID: The Federated ID is a unique value that is used to link the user in Azure and the management console.

Email address: The Email address ensures the correct user is signing in to the management console. It is obtained from the “email” claim in the SAML response.

Important: The Azure IDP configuration and the Cylance Endpoint Security authenticator configuration must match the claim names to allow the management console to retrieve the users’ credentials. If they do not match, users cannot sign in to the management console.

The following tasks walk you through the Easy configuration method.

1. Configure Azure to communicate with Cylance Endpoint Security.

In your Azure administration console, you must add a new single sign-on URL for Cylance. Add

By default, the Cylance management console requires all SAML responses to include the user’s email addresses. Important: The email addresses in Azure must match the addresses that are registered in the Cylance management console. 

In this example, we are adding the new single sign-on URL to the existing list of Reply URLs.

In the image, the numbers correspond to the step number in the procedure; not all steps are represented in the image.

1. In the Azure portal, open your existing CylancePROTECT SAML application.

2. Update the SAML Sign-in method. Complete the following steps:

                 a. In the Manage section, click Single sign-on.

                 b. Beside Basic SAML Configuration, click Edit.

3. In the Reply URL section, click Add reply URL and enter  (see the image to the left).

4. Click Save

2. In the Cylance console, create an authentication policy and assign it to users or groups.

Create a policy that includes the required authenticators for your environment. You can create a user policy or add the authenticator to the default authentication policies for the console, CylancePROTECT Mobile app or CylanceGATEWAY agent. Assign the policy to one administrator to verify the sign in policy is functioning as expected. You can then assign the authentication policy to your users.

In the image, the numbers correspond to the Step number in the procedure; not all steps are represented in the image.

  1. On the menu bar, click Settings > User Policy.
  2. Click the Authentication tab.
  3. Click Add Policy.  
  4. Enter a name and description for the policy (for example, Console Authentication Policy).
  5. In the Authenticator rules section, click Add Authenticator (see the image to the left). In the Add authenticator dialog box, select the “Migrated Custom Authentication Connector: Azure - Configuration Required” authenticator. Optionally, we recommend you rename this Authenticator to remove the “Configuration Required” from the name. This can be done after the steps below are completed.
  6. Click Save.
  7. To create the authentication policy, click Save.
  8. Assign the policy to one administrator and then verify the sign in is working as expected. Complete the following steps: 

a. In the Assign the authentication policy dialog box, click Yes.

b. Click Add User or Group.

c. Start typing a name to search for the user that you want to add.

d. Select the user from the search results.

e. Click Add.

f.  Log out of the console, or open an In Private window and access the Console log in page

g.  Enter the email address of the administrator that you assigned the authentication policy to above and click Sign In.

h.  When prompted, enter your credentials from Azure.

i.    Complete the sign in with your Azure credentials and verify that the administrator can successfully sign in to the Cylance console.

For more information on additional authentication policy settings, see Create an authentication policy.

Optionally, it is recommended that you create a user policy (User policy > Authentication) that requires only a Cylance console password and assign it to one or more designated administrators. You should use a strong password for the user policy. You can use this policy as a failsafe while you migrate Azure to an authenticator.   

That's it!

You have successfully configured an Azure SAML authenticator based on the existing custom authentication and assigned the authentication policy to users and groups. 

Users can now sign-in to the Cylance console using their Azure credentials from the sign-in page.

Next steps: Disable Custom Authentication.

After you have verified that you can sign in to the Cylance console from the primary login page using your Azure credentials, you can go to Settings > Application and clear the Custom Authentication check box.

Sign out and sign in to the Cylance console from the sign-in page using the administrator account with the new authentication policy that was applied in step 2 of this workflow and your Azure credentials.

Warning: Make sure that you sign in to the Cylance console from the primary sign-in page using you external IDP credentials. If you test the sign in from the “Or sign in with your External Identity Provider” page and then Disable Custom Authentication, you may become locked out of the console.

BlackBerry recommends you secure the Administrator account that you created with the password-only policy by assigning the Azure policy or changing the password-only policy to add an OTP code for better security.

BlackBerry recommends that you use the secure method to set up the authenticator for Cylance Endpoint Security. For more information about migration your custom authentication settings to an authenticator using the secure method, see the BlackBerry UES Setup Guide.