Skip to main content
Ex Libris Knowledge Center

Configuring Microsoft Azure (Graph) for the Roles Product Integration

campusM + cmLibrary Logo wh bkg sm1.png

This page describes the procedure for configuring the Roles product integration with Microsoft Azure (Graph). For more information, see Microsoft Graph API Permissions and campusM Product Integrations.

If you already have an application created on Azure for campusM, you can skip the first step.
  1. Create the Application in Microsoft Azure:
    1. Login to Azure.
    2. Navigate to the Azure Active Directory > App Registrations.
    3. Select New Registration.


      Register an Application
    4. Fill in the relevant details for your organizational requirements and click Register.
  2. Select Integration Assistant on the left pane, select Daemon, and select Evaluate my app Registration.


    Evaluate Registration
  3. Configure API permissions on Microsoft Graph for use by the roles service.
    1. Navigate to API permissions and select Add a Permission.


      Add A Permission
    2. Select Microsoft Graph and select Application permissions.


      Application Permissions
    3. Add the following permissions:
      • User.Read.All and Group.Read.All – if you are managing the roles in groups.
      • Directory.Read.All – if you are managing the roles in Directory Roles.
    4. Select Grant Admin Consent.
  4. Add a Client Secret to be used by campusM roles service.
    1. Navigate to Certificates & secrets in the navigation pane and click New client secret.


      New Client Secret
    2. Copy the client secret to be added to the Roles PI in Appmanager.
  5. Retrieve App Registration Metadata to complete the Roles PI in appmanager.
    1. Navigate to Overview on the Navigation pane and copy the values of the below fields:
      • Directory (tenant) ID
      • Application (client) ID
    2. In the Roles product integration, use these values to configure the Tenant ID and Client ID. The Grant Type field should have the value: client_credentials


    Roles Product Integration Configuration
  6. Common errors:
    • A 401 error typically indicates the secret value or another value is wrong.
      You should use the secret value, not the secret ID.
    • A 403 error typically indicates that you have not granted the correct API permissions.
  • Was this article helpful?