Azure Active Directory SSO
If you change your organization slug, you'll need to make the same update in the steps where you enter the SAML configuration values.
Log in to the Azure portal.
Under "Manage Azure Active Directory" (the picture of the shield), click "View". This takes you to the Organization Overview page.
If you don't require a permission group for Sentry, skip to Step 5.
In the search bar, search for "Groups" then navigate to it. From there, create a new group, add an owner and members to the group. Set "Group type" to Office 365. For more details about group creation, see the Azure docs.
Return to the Overview page. In the search bar, enter
Enterprise Applications, then navigate to it. Click "+ New application". Search for
Sentryto create the application.
Once the application is created, you'll be directed to Sentry - Overview.
Click on "1. Assign users and groups", then "+ Add user". Add yourself and the group you've created to the Sentry app. Click "Assign".
Navigate back to Overview, click on "2. Set up single sign-on" and then select SAML as your single sign-on method.
For Section (1), labeled "Basic SAML Configuration", enter the following data in each line and save your changes.
Identifier (Entity ID):
https://sentry.io/saml/metadata/YOUR_ORG_SLUG/Ensure that the URL includes a trailing slash to prevent Azure from throwing a misconfiguration error (AADSTS650056).
Reply URL (Assertion Consumer Service URL):
Sign on URL:
In Section (3), labeled "SAML Signing Certificate", copy the "App Federation Metadata URL".
Navigate to your Org Settings > Auth (or go to
https://sentry.io/settings/YOUR_ORG_SLUG/auth/) and click on "Configure" for Active Directory.
Paste the App Federation Metadata URL from above and click "Get Metadata".
In the next page, enter the following keys in their respective fields to map the attributes from AzureAD to Sentry, and then save them.
IdP User ID:
For more details about mappings for custom configs, see The Role of Claims.
Sentry will attempt to authenticate and link your account with Azure. After successful authentication, you'll be redirected to Sentry's SSO configuration page, where you can take the following actions:
You can share the "Login URL" value, which will be used for SP-initiated SSO, with the users in your organization.
Scroll down to the bottom and ensure that "Require SSO" is checked if you want to enforce logging in with Azure Active Directory.
Set a "Default Role" for new SSO users. Selecting "Member" should cover most use cases.
If you made changes, click "Save Settings" to complete your setup.
This feature is only available if your organization is on a Business or Enterprise plan; it is not available on Trial plans.
If you change your organization slug, you'll need to make the same update in the steps where you enter the SCIM configuration values.
Sentry users can manage provisioning using Azure with SCIM. You'll need to have Azure SSO set up and configured for your organization already. Sentry supports User and Group provisioning with Azure.
Sign in to sentry.io. Select Settings > Auth
Under General Settings select "Enable SCIM", then "Save Settings"
Log in to the Azure portal.
In your Azure portal, navigate to Enterprise applications in the sidebar.
Select the existing Sentry application.
Set "Provisioning Mode" to "Automatic".
Use the values from your Sentry SCIM configuration to enter your SCIM URL in the "Tenant URL" field and your SCIM AuthtokenIn search, a key-value pair or raw search term. Also, a value used for authorization.in the "Secret Token" field.
Select "Test Connection" and wait for the message that confirms that the credentials are authorized to enable provisioning.
We recommend that you select the option to "Send an email notification when a failure occurs".
As a result of these changes, users who are assigned will be sent an invitation email. When a user is un-assigned, their membership object in Sentry will be deleted.
You can use Use Group Provisioning to sync and assign groups in Azure; they will be reflected in Sentry teams.
Please see the Microsoft AD tutorial for further documentation on Azure provisioning setup. If you are using a custom enterprise application, you must follow the instructions for only enabling attribute mappings that Sentry supports (Step 5).
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").