Integration Guide - Azure DevOps Repos

• LinearB user with Admin permissions.
• Azure DevOps account with sufficient rights to:
  • Create Personal Access Tokens.
  • Access the organization and projects you want LinearB to connect to.

• Organization Owner or Project Collection Administrator permissions are required in Azure DevOps to ensure you can see all required projects and repos.

LinearB uses read-level access to analyze Git history and metadata. It does not modify your code or branches.

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:

• Inbound: 18.118.232.229, 52.15.80.85
• Outbound: 35.226.140.92

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 (top-right corner) and select Personal Access Tokens.
3. Click + New Token.
4. Provide a descriptive name for the token (for example, LinearB Azure Repos).
5. Set an appropriate expiration date for the token, based on your 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 (it will not be viewable again).

For more details on PAT creation and scope meanings, see Microsoft’s Azure DevOps PAT documentation.

1. In LinearB, navigate to Settings → Company Settings, and select the Git tab.
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 will begin 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 repos are listed.
• After initial processing, branches, commits, and pull requests from Azure Repos should begin to appear 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 read 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 Organization Owner or Project Collection Administrator permissions and that the PAT was created from the correct Azure DevOps organization.

Possible cause

The Personal Access Token has expired or was revoked.

Resolution

Generate a new PAT with the required permissions and reconnect 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.