Integration Guide - Azure DevOps Repos

• LinearB user with Admin permissions.
• Azure DevOps account with sufficient rights to:
  • Create Personal Access Tokens.
  • Access the organization, projects, and repositories you want LinearB to monitor.
  • Create and manage Service Hook subscriptions for the relevant projects.

• Organization Owner or Project Collection Administrator permissions are required in Azure DevOps to ensure access to the required projects and repositories.
• The Azure DevOps account must also have permission to view and edit Service Hook subscriptions for the relevant projects.

LinearB uses read-level permissions to analyze Git history, repository activity, and metadata.

LinearB does not modify your source code or branches.

Service Hooks permissions allow LinearB to create and manage webhook subscriptions that notify LinearB about repository activity.

If your organization uses firewall rules, IP allowlists, or geolocation-based conditional access policies, ensure that communication with LinearB is allowed.

LinearB uses the following NAT Gateway IP addresses for Azure DevOps and Azure Repos connections:

If your organization restricts access based on IP address or geographic location, ensure these addresses are allowlisted before attempting to connect or reauthorize Azure DevOps.

• Approximately 5–10 minutes to create the PAT and connect Azure Repos to LinearB.

1. Navigate to Azure DevOps and sign in.
2. Click your User Settings in the upper-right corner and select Personal Access Tokens.
3. Click + New Token.
4. Provide a descriptive name for the token, such as LinearB Azure Repos.
5. Set an appropriate expiration date for the token based on your organization's security policies.
6. Assign the following permissions:
   • User Profile: Read (vso.profile)
   • Project and Team: Read (vso.project)
   • Code: Read (vso.code)
   • Build: Read (vso.build)
   • Graph: Read (vso.graph)
7. Click Create and copy the token securely. The token will not be viewable again after you leave the creation page.

For additional information about creating PATs and configuring permissions, see Microsoft's Azure DevOps PAT documentation .

1. In LinearB, navigate to Settings → Company Settings → Git.
2. Click Add Integration.
3. Select Azure DevOps as your source control provider.
4. Enter the name of your Azure DevOps organization.
5. Paste your Personal Access Token (PAT) into the required field.
6. Click Connect. LinearB begins processing your Azure Repos data.

• In LinearB, go to Settings → Company Settings → Git.
• Confirm that an Azure DevOps integration appears with a connected status.
• Click the integration entry to view available repositories and verify that your expected projects and repositories are listed.
• After initial processing, branches, commits, and pull requests from Azure Repos should begin appearing in your LinearB delivery and metrics views.

Possible cause

The Personal Access Token (PAT) is missing one or more required scopes, or the Azure DevOps organization name is incorrect.

Resolution

Verify that the organization name is correct and that the PAT includes all required permissions. Then retry the connection.

Possible cause

The Azure DevOps account used to create the PAT does not have access to all projects or repositories.

Resolution

Ensure the account has the required Azure DevOps permissions and can access the relevant projects and repositories.

Verify that the PAT was created for the correct Azure DevOps organization.

Possible cause

The Azure DevOps account does not have permission to manage Service Hook subscriptions for the relevant project.

Resolution

1. In Azure DevOps, go to Project Settings → Service hooks.
2. Open the Service Hooks security settings.
3. Verify that the account has permission to View subscriptions and Edit subscriptions.
4. Reauthorize the Azure DevOps integration in LinearB.

Possible cause

The Personal Access Token has expired or was revoked.

Resolution

Generate a new PAT with the required permissions and reconnect or reauthorize the integration.

Possible cause

Your organization uses firewall rules, IP allowlists, or geolocation-based conditional access policies that block communication with LinearB.

Resolution

Ensure the IP addresses listed in Firewall Requirements are allowlisted in your network and security policies.