Configure Sentry for automatic user provisioning

This article describes the steps you need to perform in both Sentry and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to Sentry 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.

Capabilities Supported

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

Prerequisites

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

• A Microsoft Entra tenant.
• One of the following roles: Application Administrator, Cloud Application Administrator, or Application Owner.
• This feature is only available if your Sentry organization is on a Business or Enterprise plan.It is not available on Trial plans.
• You'll need to have Azure SSO set up already configured for your organization.

Step 1: Plan your provisioning deployment

1. Learn about how the provisioning service works.
2. Determine who will be in scope for provisioning.
3. Determine what data to map between Microsoft Entra ID and Sentry.

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

1. Sign in to your Sentry Organization. Select Settings > Auth
2. Under General Settings select Enable SCIM, then Save Settings
3. Sentry will display SCIM Information that contains your Auth Token and SCIM Base URL.
4. SCIM Base URL will be your Tenant URL in Microsoft Entra ID, and Auth Token will be your Secret Token.

Step 3: Add Sentry from the Microsoft Entra application gallery

Add Sentry from the Microsoft Entra application gallery to start managing provisioning to Sentry. If you have previously setup Sentry for SSO you can use the same application. However it is 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 / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

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

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

Step 5: Configure automatic user provisioning to Sentry

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

To configure automatic user provisioning for Sentry 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

   

3. In the applications list, select Sentry.

   

4. Select the Provisioning tab.

   

5. Set the Provisioning Mode to Automatic.

   

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

   

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

   

8. Select Save.

9. In the Mappings section, select Synchronize Microsoft Entra users to Sentry.

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

    Attribute	Type	Supported for filtering
    userName	String	✓

11. Under the Mappings section, select Synchronize Microsoft Entra groups to Sentry.

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

    Attribute	Type	Supported for filtering
    displayName	String	✓
    members	Reference

13. To configure scoping filters, refer to the following instructions provided in the Scoping filter article.

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

    

15. Define the users and/or groups that you would like to provision to Sentry by choosing the desired values in Scope in the Settings section.

    

16. When you are ready to provision, click Save.

    

This operation starts the initial synchronization cycle of all users and groups 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 is to completion
• If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

More resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Related content

• Learn how to review logs and get reports on provisioning activity