Connect Azure Repos to LinearB
Connect Azure Repos to LinearB using a Personal Access Token (PAT). Once connected, LinearB reads repository activity (commits, branches, and pull requests) to power delivery metrics and automation.…
Connect Azure Repos to LinearB using a Personal Access Token (PAT). Once connected, LinearB reads repository activity (commits, branches, and pull requests) to power delivery metrics and automation.
Overview
Azure Repos integrates with LinearB through an Azure DevOps Personal Access Token (PAT). The PAT provides read-level access so LinearB can retrieve repository and project data required to calculate engineering metrics.
After the integration is connected, LinearB begins ingesting Git activity and backfills historical data. The duration of the initial backfill depends on repository size and history.
Before you begin
- LinearB: Company Admin permissions
- Azure DevOps: Permission to create Personal Access Tokens and access the organization and projects you want to connect
- Recommended role: Organization Owner or Project Collection Administrator
LinearB uses read-level access to analyze Git history and metadata. It does not modify repositories, code, or branches.
Estimated time: ~5–10 minutes
Step 1 — Generate a Personal Access Token in Azure DevOps
- Sign in to Azure DevOps.
- Open User Settings (top-right corner).
- Select Personal Access Tokens.
- Click + New Token.
- Provide a descriptive name (for example, LinearB Azure Repos).
- Set an appropriate expiration date based on your organization's security policy.
- Assign the following scopes:
- User Profile: Read (
vso.profile) - Project and Team: Read (
vso.project) - Code: Read (
vso.code) - Build: Read (
vso.build) - Graph: Read (
vso.graph)
- Click Create.
- Copy the token and store it securely. You will not be able to view it again.
Step 2 — Connect Azure Repos in LinearB
- In LinearB, go to Settings → Company Settings → Git.
- Click Add Integration.
- Select Azure DevOps as the Git provider.
- Enter your Azure DevOps organization name.
- Paste the Personal Access Token you generated.
- Click Connect.
After the connection is established, LinearB will begin processing your Azure Repos data.
Verify
Use the following checks to confirm the integration is working.
- In LinearB, navigate to Settings → Company Settings → Git.
- Confirm the Azure DevOps integration shows a Connected status.
- Open the integration and confirm your expected repositories and projects are listed.
- After processing completes, commits and pull requests should begin appearing in LinearB dashboards.
Troubleshooting
| Problem | Likely Cause | Resolution |
|---|---|---|
| Connection fails during setup | Incorrect organization name or PAT missing required scopes | Verify the organization name and ensure the PAT includes all required read scopes. |
| Some repositories are missing | PAT or Azure DevOps user lacks access to certain projects | Confirm the Azure DevOps account has access to those projects and regenerate the PAT if needed. |
| Integration previously worked but now fails | PAT expired or was revoked | Create a new PAT with the same scopes and reconnect the integration in LinearB. |
If issues persist, please contact LinearB Support.
FAQs
What is the Azure DevOps organization name?
This is the organization identifier in your Azure DevOps URL. For example:
https://dev.azure.com/your-organization
Does LinearB require write access to repositories?
No. LinearB only requires read-level access to retrieve Git activity and metadata.
Done?
Once Azure Repos is connected and repositories are visible, return to the Enterprise Setup Guide and continue with the next step in Phase 1.
How did we do?