--- title: "Azure DevOps" description: "Learn more about Sentry's Azure DevOps integration and how it can track and resolve bugs faster by using data from your Azure DevOps commits." url: https://docs.sentry.io/integrations/source-code-mgmt/azure-devops/ --- # Azure DevOps | Sentry Docs Azure DevOps was formerly known as Visual Studio Team Services (VSTS). ## [Install](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#install) ##### Note We recommend creating a dedicated service account on Azure DevOps when installing this integration rather than using a personal user account. Since the integration authenticates via OAuth, activities such as comments and work item creation will be attributed to the Azure DevOps user who authorized the integration. Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization. After creating the Azure DevOps service account, you will need to sign into Sentry with an user account that has owner, manager, or admin permissions to install the integration. 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 - navigate to **Organization Settings > Security > Policies** and enable "Third-party application access via OAuth". 3. In Sentry.io, navigate to [**Settings > Integrations**](https://sentry.io/orgredirect/organizations/:orgslug/settings/integrations/) > **Azure DevOps** and click "Add Installation". 4. An Azure DevOps install window should pop up. Select the Azure DevOps account you'd like to link with Sentry, and press **Submit**. Azure DevOps should now be enabled for all projects under your Sentry organization, but you'll need to configure the features below. ## [Configure](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#configure) Use Azure DevOps to [track commits](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#commit-tracking) and [issue management](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#issue-management). ### [Commit Tracking](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#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](https://docs.sentry.io/product/releases/setup.md). 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](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#issue-management) Issue tracking allows you to create Azure DevOps issues from within Sentry, and link Sentry issues to existing Azure DevOps Issues. ##### Note Manual issue management is available to organizations on Team, Business, and Enterprise plans. Automatic issue management is available to organizations that include transactions in their Business and Enterprise plans. Issue management can be configured in two ways - automatically or manually. #### [Automatically](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#automatically) To configure issue management automatically, create an [**Alert**](https://docs.sentry.io/product/monitors-and-alerts/alerts.md). When selecting the **action**, choose **Create a new Azure DevOps work item**. An Azure DevOps work item will be created automatically when the alert has been triggered. #### [Manually](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#manually) Once you’ve navigated to a specific issue, you’ll find the **External Links** section on the right hand panel. Here, you’ll be able to create or link Azure DevOps issues. ### [Issue Sync](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#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. ##### Note Issue sync is available for organizations on the Team, Business, and Enterprise plans. To configure Issue sync, navigate to [**Organization Settings > Integrations**](https://sentry.io/orgredirect/organizations/:orgslug/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. ### [Resolve in Commit](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#resolve-in-commit) Once you send commit data, you can start resolving issues by including `fixes ` in your commit messages. For example, a commit message might look like: ```bash 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](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#stack-trace-linking) Stack trace linking takes you from a file in your Sentry stack trace to the same file in Azure DevOps. If you've set up commit tracking, Sentry links to the version of the file from the commit associated with the event. Otherwise, it links to the branch set in your code mapping. To set up stack trace linking, [add a code mapping](https://docs.sentry.io/integrations/source-code-mgmt/code-mappings.md) for each Sentry project and Azure DevOps repository you want to link. ### [Source Context](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#source-context) If your events don't carry inline source context (for example, native crashes or releases built without source maps), you can have Sentry fetch the surrounding lines from your repository on demand and render them in the issue stack trace. See [SCM Source Context](https://docs.sentry.io/integrations/source-code-mgmt/source-context.md) for setup and access details. ## [Troubleshooting](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#troubleshooting) ### [No accounts during installation](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md#no-accounts-during-installation) 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](https://docs.sentry.io/organization/authentication/sso/azure-sso.md). * If you have multiple accounts in Azure DevOps, open [this link to Azure DevOps](https://aex.dev.azure.com) in another tab, select the correct account, then reinstall. If reinstallation solves the problem, please upvote [that solution in GitHub](https://github.com/getsentry/sentry/issues/14357), which is where we're tracking this improvement.