Azure DevOps

Track and resolve bugs faster by using data from your Azure DevOps commits. (Azure DevOps was formerly known as Visual Studio Team Services, VSTS.)


  1. To install this integration, you need to have Sentry organization owner, manager, or admin permissions, as well as Azure organization owner permissions, or be a user in the Project Collections Administrators group.

  2. Go to your Azure Org's settings to make sure third-party access via OAuth is enabled.

  3. In, navigate to Settings > Integrations > Azure DevOps and click "Add Installation".

    Install Azure DevOps integration

  4. An Azure DevOps install window should pop up. Select the Azure DevOps account you'd like to link with Sentry, and press Submit.

    Configure Azure DevOps

Azure DevOps should now be enabled for all projects under your Sentry organization, but you'll need to configure the features below.


Use Azure DevOps to track commits and issue management.

Commit Tracking

Commit tracking allows you to hone in on problematic commits. Uncover which commits likely caused an issue, and allow your team to resolve issues by referencing the issue number in a commit message.

For more details, see the full documentation on commit tracking and releases.

You’ll also see that the author of the suspect commit will be listed as a suggested assignee for this issue. To assign the issue to the suggested assignee, click on their icon.

Issue Management

Issue tracking allows you to create Azure DevOps issues from within Sentry, and link Sentry issues to existing Azure DevOps Issues.

Issue management can be configured in two ways - automatically or manually.


To configure issue management automatically, create an Issue Alert. When selecting the action, choose Create a new Azure DevOps work item.

Create Azure DevOps work item as alert rule action

An Azure DevOps work item will be created automatically when the alert has been triggered.


Once you’ve navigated to a specific issue, you’ll find the Linked Issues section on the right hand panel. Here, you’ll be able to create or link Azure DevOps issues.

Link Azure DevOps work item to Sentry issue

Issue Sync

Sync comments, assignees, and status updates for issues in Sentry to Azure DevOps, to minimize duplication. When you delegate an issue to an assignee or update a status on Azure DevOps, the updates will also populate in Sentry. When you resolve an issue in Sentry, the issue status will automatically update in Azure DevOps.

To configure Issue sync, navigate to Organization Settings > Integrations, and click "Configure" next to your Azure DevOps instance. On the following page, you’ll see options of what information you’d like synced between Sentry and Azure DevOps.

Sync issue status

Resolve in Commit

Once you send commit data, you can start resolving issues by including fixes <SENTRY-SHORT-ID> in your commit messages. For example, a commit message might look like:

Prevent empty queries on users

Fixes MYAPP-317

When Sentry sees this, we’ll automatically annotate the matching issue with reference to the commit, and later, when that commit is part of a release, we’ll mark the issue as resolved. The commit must be associated with a release. Otherwise, if the commit is squashed, Sentry won’t know when the commit has been released, and the issue may never be marked as a regression.

Stack Trace Linking

Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).

  1. Navigate to Settings > Integrations > Azure DevOps > Configurations.

  2. Click "Configure" (the gear icon) next to your Azure DevOps Instance.

  3. Click the "Code Mappings" tab.

  4. Set up a code mapping for each

    projectRepresents your service in Sentry and allows you to scope events to a distinct application.
    you want to have stack trace linking. To create a new code mapping, click "Add Mapping".

  5. Fill out the form, then click "Save Changes". Each form field is described below:

    • Project (required): This is the Sentry project.
    • Repo (required): This is the Azure DevOps project associated with the Sentry project above. If you have more than one Azure DevOps project being used per Sentry project, you'll need multiple code mappings.
    • Branch (required): This is the default branch of your code we fall back to if you do not have commit tracking set up.
    • Stack Trace Root and Source Code Root (optional):
      • If the file path in your Sentry stack trace frame matches the path to your source code, you don't need to set these values.
        • For example, if everything after the branch (main) matches the file path of using a source code path of, you don't need to set either stack trace root or source code root
      • If the file path in your Sentry stack trace frame doesn't match the path to your source code, you will need to replace the stack_root part of the file path with your source_root to make the file path match the source code path.
        • For example, to get src/ to match when the source code path is, change the stack trace root to be set as src/, and leave source code root empty.


No accounts during installation

azure add account no accounts

If you reach the account selection page during the Azure Devops installation process (step 4 in the instructions above) and see that there are no accounts available to select, please check the following possibilities:

  • Ensure you are logged into the account connected to your Azure DevOps organization.
  • Double-check that your account is a Microsoft Account (MSA).
  • For single sign-on, see Azure Active Directory SSO.
  • If you have multiple accounts in Azure DevOps, open this link to Azure DevOps in another tab, select the correct account, then reinstall.
Help improve this content
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").