Skip to main content

​
Overview

The Azure DevOps integration allows organizations to connect Azure DevOps repositories to the Engineering Metrics Dashboard. Once configured, repository activity can be synchronized and used to generate engineering analytics, repository insights, and performance metrics. Using this integration, organizations can:
  • Connect Azure DevOps repositories
  • Synchronize repository activity
  • Configure repository scopes
  • Monitor engineering performance metrics
  • Track development activity across projects

​
Prerequisites

Before configuring the integration, ensure you have:
  • Access to the Engineering Metrics Dashboard
  • Access to an Azure DevOps organization
  • A valid Azure DevOps Personal Access Token (PAT)
  • Permissions to access the repositories that will be synchronized
  • Required permissions to configure integrations
  1. Open the Engineering Metrics Dashboard.
  2. Navigate to the Integrations section.
  3. Select Source Code Management Integrations.
  4. Choose Azure DevOps from the available integrations.

​
Create a New Azure DevOps Connection

  1. Click New Connection.
  2. The Manage Connections: Azure DevOps window will appear.
  3. Enter a unique Connection Name.

​
Example Connection Names

  • Azure DevOps Production
  • Engineering Repositories
  • Internal Development Team
  • Enterprise Azure DevOps

​
Configure Azure DevOps Authentication

Enter the required Azure DevOps connection details.

​
Azure DevOps Organization

In the Organization field, enter only the organization short name, not the full Azure DevOps URL. For example, if your Azure DevOps URL is:
Enter the following value in G360:
G360 automatically constructs the full Azure DevOps URL using the organization name you provide. Do not enter the complete web address.

​
Personal Access Token

Provide a valid Azure DevOps Personal Access Token (PAT).
The Personal Access Token must have sufficient permissions to access repositories and retrieve repository activity data.

​
Azure DevOps Personal Access Token (PAT)

Before creating a Personal Access Token, ensure that:
  • You have access to the Azure DevOps organization you want to connect.
  • Your Azure DevOps administrator allows Personal Access Token creation.
  • Your account has sufficient permissions to access the projects and repositories that G360 will analyze.

​
Create a Personal Access Token

  1. Sign in to your Azure DevOps organization.
  2. In the upper-right corner, click your Profile icon.
  3. Select Personal access tokens.
  4. Click + New Token.
  5. Configure the token with the following details:
  • Name – Enter a descriptive name such as G360 Integration.
  • Organization – Select the Azure DevOps organization you want to connect.
  • Expiration – Choose an expiration period that complies with your organization’s security policy.
  • Scopes – Select Custom defined.
  1. Configure the minimum required scopes shown below.
The following permissions are required for G360 to successfully collect engineering metrics from Azure DevOps.
Azure DevOps displays the Personal Access Token only once. If the token is lost, it cannot be retrieved and a new token must be generated.

​
Configure the Azure DevOps Integration in G360

After generating the PAT:
  1. Navigate to G360 → Integrations.
  2. Select Azure DevOps.
  3. Enter the following information:
    • Azure DevOps Organization URL
    • Personal Access Token (PAT)
  4. Click Test Connection.
  5. Once the connection is successful, click Save.

​
Troubleshooting

​
Insufficient Permissions

If the connection fails because of insufficient permissions, verify that the Personal Access Token includes Read access for each of the following scopes:
  • Work Items
  • Code
  • Build
  • Release
  • Test Management
  • Packaging
  • Organization

​
PAT Expired

If the Personal Access Token has expired:
  1. Generate a new PAT.
  2. Update the PAT in the Azure DevOps integration settings within G360.
  3. Save the connection.

​
Organization Access

Ensure that the account used to create the PAT has access to the Azure DevOps organization, projects, repositories, work items, builds, releases, test plans, and package feeds that G360 needs to analyze.

​
Optional Configuration

​
Proxy

If your organization uses a proxy server, enter the proxy details in the Proxy field.

​
Custom Rate Limit

Users can configure a custom API rate limit to control Azure DevOps API consumption and synchronization behavior.

​
Test the Connection

  1. Click Test Connection.
  2. Wait for the validation process to complete.

​
Expected Result

  • If the configuration is valid, the connection test will succeed.
  • If the test fails, verify the Azure DevOps URL, Personal Access Token, and network connectivity before retrying.

​
Save the Connection

  1. After a successful connection test, click Save Connection.
  2. The Azure DevOps connection will appear in the available connections list.

​
Configure Data Scopes

After creating the connection:
  1. Select the Azure DevOps connection.
  2. Click Add Data Scope.
The Add Data Scope window allows users to select repositories that should be synchronized with the platform.

​
Repository Selection

  1. Select the Azure DevOps project.
  2. Search for the desired repository.
  3. Select one or more repositories using the available checkboxes.
  4. Click Save.
The selected repositories will be added as data scopes for the Azure DevOps connection.

​
Managing Data Scopes

Users can:
  • Add Data Scope
  • Associate Scope Entity
  • Delete Data Scope
These options allow administrators to manage which repositories are included in synchronization and reporting.

​
Understanding Data Scopes

A data scope represents an Azure DevOps repository that has been authorized for synchronization. Only repositories included in configured data scopes will be available for analytics and reporting.

​
Synchronizing Repository Data

Once repositories have been added as data scopes, Engineering Metrics will begin collecting repository activity from Azure DevOps. Collected data may include:
  • Repository activity
  • Commit information
  • Pull request activity
  • Contributor activity
  • Development trends
Synchronization occurs automatically based on the platform’s configured schedules.

​
Monitoring Synchronization Status

The integration dashboard provides visibility into synchronization activity and repository processing status. Users can monitor:
  • Synchronization progress
  • Successful synchronizations
  • Failed synchronizations
  • Repository availability
  • Data collection status

​
Troubleshooting

​
Connection Test Failed

Possible causes:
  • Invalid Azure DevOps URL
  • Invalid Personal Access Token
  • Missing repository permissions
  • Network connectivity issues
Recommended actions:
  • Verify the Azure DevOps URL
  • Confirm the Personal Access Token is valid
  • Ensure the token has required permissions
  • Retry the connection test

​
Repositories Not Appearing

Possible causes:
  • Insufficient repository permissions
  • Incorrect project selection
  • Synchronization delay
Recommended actions:
  • Verify repository access permissions
  • Confirm the correct project is selected
  • Retry synchronization

​
Synchronization Issues

Possible causes:
  • API rate limits
  • Authentication issues
  • Repository access restrictions
Recommended actions:
  • Verify connection settings
  • Confirm token permissions
  • Retry synchronization after resolving configuration issues

​
Best Practices

  • Use descriptive connection names
  • Regularly validate Personal Access Tokens
  • Synchronize only required repositories
  • Monitor synchronization activity regularly
  • Review repository analytics periodically

​
Summary

The Azure DevOps integration enables organizations to connect Azure DevOps repositories directly to the Engineering Metrics Dashboard. By configuring a connection, selecting repository scopes, and synchronizing repository activity, teams can gain visibility into development trends, repository activity, contributor engagement, and engineering performance metrics.