Azure Active Directory SSO
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 Applicationsand navigate to it. Click "+ New application". Search for
Sentryto create the application for Sentry.
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):
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 Okta.
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.