Sleuth Documentation
HomeBlogSupportSign up
Search…
Getting started
DORA metrics
Deployment tracking
Slack & Email Notifications
Auto-verify deploys
Deploy workflows (beta)
Slack mission control
Sleuth API
Integrations
About Integrations...
Code integrations
Azure DevOps
Bitbucket
GitHub
GitLab
Custom Git
Terraform Cloud
Feature flag integrations
Impact integrations
Slack integration
CI/CD integrations
Issue tracker integrations
Incident tracker integrations
Settings
Organization settings
Project settings
Account settings
Role Based Access Control
Resources
FAQ
Sleuth TV
Purchasing
About Sleuth...
Powered By GitBook
Azure DevOps

About the integration
​

Integrating Azure DevOps with Sleuth is simple. If you're connecting to a personal Azure DevOps repo, you just need your credentials. If you're part of an organization and aren't the owner, you will need permission to allow Sleuth to connect to the repo—after you connect you'll be able to select individual private or public repositories.
The integration is best tested against Azure DevOps Services, however, it should work for Azure DevOps Server as well. Which is which?
  • Azure DevOps Services (formerly known as Visual Studio Team Services, or VSTS_)_ is a cloud-based solution
  • Azure DevOps Server (formerly known as Team Foundation Server, or TFS) is an on-premises offering

Setting up the integration

To set up the Azure DevOps integration:
  1. 1.
    Click Integrations in the left sidebar, then click Change Sources.
  2. 2.
    In the Azure DevOps tile, click enable.
  3. 3.
    You must grant Sleuth access to your Azure DevOps account. Don't worry, you'll select the Azure DevOps repo to connect to your Sleuth project later.
    ​
  4. 4.
    In a separate browser tab or window, visit your Azure DevOps account, and under User settings, click on Personal Access Tokens and generate a token with the required scopes. The Work Items and Build scopes are only necessary if you want to configure issue and build integration. Paste this token into the Sleuth form.
  5. 5.
    On successful integration, Azure DevOps enabled will be displayed in the Azure DevOps tile. You'll next configure the code deployment to connect your repo to a project.

Custom HTTP headers

If you using Azure DevOps on-premise behind Cloudflare access or similar, Sleuth might need to include some HTTP headers in order to reach your instance. In order to set Sleuth to send any custom HTTP headers when making requests:
  1. 1.
    In the Azure DevOps dialog, click on the Advanced setting
  2. 2.
    Enter comma separated list of custom headers you want Sleuth to include

Configuring the integration

You now need to add a code deployment for your Azure DevOps repo to a Sleuth project. Once configured and you start registering deploys Sleuth will be tracking deploys for your code changes.To configure the Azure DevOps integration:
  1. 1.
    After step #4 above, you will be taken back to the Azure DevOps integration tile. On the Azure DevOps tile, click the Add code deployment dropdown.
  2. 2.
    Select the Sleuth project you wish to add a chance source to from the dropdown list.
  3. 3.
    Follow the instructions for setting up a new code deployment​

Removing the integration

If you wish to remove the Azure DevOps integration for the organization:

  1. 1.
    Click on Integrations in the left sidebar, then on Change Sources.
  2. 2.
    In the Azure DevOps integration card, click disable.
The Azure DevOps integration is disconnected and no longer available to any projects within that organization.
Integrations - Previous
Code integrations
Next
Bitbucket
Last modified 2mo ago
Copy link
On this page
About the integration
Setting up the integration
Custom HTTP headers
Configuring the integration
Removing the integration