Tutorial: Configure Rootly for automatic user provisioning

This tutorial describes the steps you need to perform in both Rootly and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and deprovisions users to Rootly using the Microsoft Entra provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID.

Supported capabilities

  • Create users in Rootly.
  • Remove users in Rootly when they do not require access anymore.
  • Keep user attributes synchronized between Microsoft Entra ID and Rootly.
  • Single sign-on to Rootly (recommended).

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

  • A Microsoft Entra tenant
  • A user account in Microsoft Entra ID with permission to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
  • A user account in Rootly with Admin permissions.

Step 1: Plan your provisioning deployment

Step 2: Configure Rootly to support provisioning with Microsoft Entra ID

  1. Create a free Rootly account.
  2. Contact Rootly support to enabled SCIM if your plan doesn't allow it.

Add Rootly from the Microsoft Entra application gallery to start managing provisioning to Rootly. If you have previously setup Rootly for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4: Define who will be in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users to the application. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described here.

  • Start small. Test with a small set of users before rolling out to everyone. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. When scope is set to all users, you can specify an attribute based scoping filter.

  • If you need more roles, you can update the application manifest to add new roles.

Step 5: Configure automatic user provisioning to Rootly

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users in Rootly based on user assignments in Microsoft Entra ID.

To configure automatic user provisioning for Rootly in Microsoft Entra ID:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Identity > Applications > Enterprise applications

    Screenshot of Enterprise applications blade.

  3. In the applications list, select Rootly.

    Screenshot of the Rootly link in the Applications list.

  4. Select the Provisioning tab.

    Screenshot of Provisioning tab.

  5. Set the Provisioning Mode to Automatic.

    Screenshot of Provisioning tab automatic.

  6. Under the Admin Credentials section, input your Rootly Tenant URL and Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to Rootly. If the connection fails, ensure your Rootly account has Admin permissions and try again.

    Screenshot of Token.

  7. In the Notification Email field, enter the email address of a person who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

    Screenshot of Notification Email.

  8. Select Save.

  9. Under the Mappings section, select Synchronize Microsoft Entra users to Rootly.

  10. Review the user attributes that are synchronized from Microsoft Entra ID to Rootly in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Rootly for update operations. If you choose to change the matching target attribute, you need to ensure that the Rootly API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Rootly
    userName String
    active Boolean
    name.givenName String
    name.familyName String
    externalId String
  11. Under the Mappings section, select Synchronize Microsoft Entra groups to Rootly.

  12. Review the group attributes that are synchronized from Microsoft Entra ID to Rootly in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in Rootly for update operations. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Rootly
    displayName String
    members Reference
    externalId String
  13. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  14. To enable the Microsoft Entra provisioning service for Rootly, change the Provisioning Status to On in the Settings section.

    Screenshot of Provisioning Status Toggled On.

  15. Define the users that you would like to provision to Rootly by choosing the desired values in Scope in the Settings section.

    Screenshot of Provisioning Scope.

  16. When you're ready to provision, click Save.

    Screenshot of Saving Provisioning Configuration.

This operation starts the initial synchronization cycle of all users defined in Scope in the Settings section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running.

Step 6: Monitor your deployment

Once you've configured provisioning, use the following resources to monitor your deployment:

  • Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
  • Check the progress bar to see the status of the provisioning cycle and how close it's to completion
  • If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states here.

More resources

Next steps