Skip to main content

​
Overview

The Azure DevOps integration connects your Azure DevOps repositories to G360. After you configure it, G360 synchronizes repository activity and uses it to generate engineering analytics, repository insights, and performance metrics. With this integration, you can:
  • Connect Azure DevOps repositories
  • Synchronize repository activity
  • Configure repository scopes
  • Monitor engineering performance metrics
  • Track development activity across projects

​
Prerequisites

Before you configure the integration, make sure you have:
  • Access to the Engineering Metrics dashboard
  • Access to an Azure DevOps organization
  • A valid Azure DevOps Personal Access Token (PAT), created as described in Create a personal access token
  • Permission to access the repositories you want to synchronize
  • Permission to configure integrations

​
Create an Azure DevOps connection

1

Open Azure DevOps connections

Open the Engineering Metrics dashboard and go to Integrations → Source Code Management Integrations → Azure DevOps.
2

Start a new connection

Click New Connection. The Manage Connections: Azure DevOps window opens.
3

Enter connection details

G360 builds the full Azure DevOps URL from the organization name you provide. Do not enter the complete web address.
4

Test the connection

Click Test Connection and wait for validation to finish. If it fails, verify the organization name, the PAT, and network connectivity, then retry.
5

Save the connection

After a successful test, click Save Connection. The connection appears in the connections list.

​
Create a personal access token

Before you start, make sure that:
  • You have access to the Azure DevOps organization you want to connect.
  • Your Azure DevOps administrator allows PAT creation.
  • Your account can access the projects and repositories that G360 will analyze.
1

Open Personal access tokens

Sign in to your Azure DevOps organization, click your Profile icon in the upper-right corner, and select Personal access tokens.
2

Start a new token

Click + New Token.
3

Configure the token

4

Select the minimum required scopes

G360 needs the following scopes to collect engineering metrics from Azure DevOps.
5

Create and copy the token

Create the token and copy it. Then paste it into the Personal Access Token field of the G360 connection.
Azure DevOps shows the PAT only once. If you lose it, you can’t retrieve it and must generate a new token.

​
Configure data scopes

A data scope is an Azure DevOps repository that you authorize for synchronization. Only repositories in configured data scopes are available for analytics and reporting.
1

Open Add Data Scope

Select the Azure DevOps connection and click Add Data Scope.
2

Select repositories

Select the Azure DevOps project, search for the repository, and select one or more repositories with the checkboxes. Then click Save. G360 adds the selected repositories as data scopes for the connection.
From the connection, you can also use these options to manage which repositories are included in synchronization and reporting:
  • Add Data Scope
  • Associate Scope Entity
  • Delete Data Scope

​
Synchronization and metrics

After you add repositories as data scopes, G360 collects their activity from Azure DevOps automatically, based on the platform’s configured schedules. Collected data may include:
  • Repository activity
  • Commit information
  • Pull request activity
  • Contributor activity
  • Development trends
The integration dashboard shows synchronization progress, successful and failed synchronizations, repository availability, and data collection status.

​
Troubleshooting

Possible causes
  • Invalid Azure DevOps organization name
  • Invalid or expired Personal Access Token
  • Missing repository permissions
  • Network connectivity issues
Actions
  • Verify the organization name.
  • Confirm the Personal Access Token is valid.
  • Ensure the token has the required permissions.
  • Retry the connection test.
If the connection fails because of insufficient permissions, verify that the Personal Access Token has Read access for each of the following scopes:
  • Work Items
  • Code
  • Build
  • Release
  • Test Management
  • Packaging
  • Organization
Actions
  • Generate a new PAT.
  • Update the PAT in the Azure DevOps integration settings in G360.
  • Save the connection.
Possible causes
  • Insufficient repository permissions
  • Organization access: the account that created the PAT must have access to the Azure DevOps organization, projects, repositories, work items, builds, releases, test plans, and package feeds that G360 analyzes
  • Incorrect project selection
  • Synchronization delay
Actions
  • Verify repository access permissions.
  • Confirm the correct project is selected.
  • Retry synchronization.
Possible causes
  • API rate limits
  • Authentication issues
  • Repository access restrictions
Actions
  • Verify the connection settings.
  • Confirm the token permissions.
  • Retry synchronization after resolving configuration issues.

​
Best practices

  • Use descriptive connection names.
  • Validate your PATs regularly.
  • Synchronize only the repositories you need.
  • Monitor synchronization activity and review repository analytics periodically.

​
Summary

The Azure DevOps integration connects your Azure DevOps repositories to G360. By configuring a connection, selecting repository scopes, and synchronizing repository activity, your teams gain visibility into development trends, repository activity, contributor engagement, and engineering performance metrics.