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
Navigate to Azure DevOps Connections
- Open the Engineering Metrics Dashboard.
- Navigate to the Integrations section.
- Select Source Code Management Integrations.
- Choose Azure DevOps from the available integrations.
Create a New Azure DevOps Connection
- Click New Connection.
- The Manage Connections: Azure DevOps window will appear.
- 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 URL
Provide the URL of the Azure DevOps organization. Example: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.
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
- Click Test Connection.
- 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
- After a successful connection test, click Save Connection.
- The Azure DevOps connection will appear in the available connections list.
Configure Data Scopes
After creating the connection:- Select the Azure DevOps connection.
- Click Add Data Scope.
Repository Selection
- Select the Azure DevOps project.
- Search for the desired repository.
- Select one or more repositories using the available checkboxes.
- Click Save.
Managing Data Scopes
Users can:- Add Data Scope
- Associate Scope Entity
- Delete Data Scope
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
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
- 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
- Verify repository access permissions
- Confirm the correct project is selected
- Retry synchronization
Synchronization Issues
Possible causes:- API rate limits
- Authentication issues
- Repository access restrictions
- 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

