Azure Repos

Introduction

General Availability

This integration is generally available. To find more information about the release stages of our integrations, see Release Stages.

The LeanIX VSM Azure Repository integration offers an easy way to auto-discover all your services from Azure Repos workspace. Based on this VSM's mapping inbox allows you to easily sift through all the stale information from Azure Repos to decide, which services are really useful to your organization and hence should be part of your service catalog. This will help you to maintain a high standard of data quality when you subsequently map your services to their individual teams to create clear team ownership.

Integrate with Azure Repos to:

• Automatically discover your services to build your company-wide service catalog
• Map team ownership to have clear software governance in place

Setup

The Azure repository connector scans your "Azure Repos" organization(s) to fetch your repositories and adjacent information,
such as the programming languages used. The integration can be set up in full self-service via the Admin UI.

Configuration from Azure Repos

To integrate Azure Repos with LeanIX VSM you need two inputs:

1. A personal access token (PAT)
2. Your Azure Repos organization(s)

Creating Personal Access Token

1. Please refer to the official documentation
2. Ensure you enable the following scopes:
   • Code: Read
   • Analytics:Read

📘

Expiration

Choose a token expiration date that is far in the future to avoid breaking the integration

Fetching Azure Repos organization(s)

To see the names of your managed organizations, follow these instructions or directly fetch your organizations from your settings.

Configuration in VSM

In your LeanIX VSM workspace, go to Administration > Integrations and follow the instructions to set up the Azure Repos integration.

How to map your discovered repositories to VSM service catalog items?

After the integration successfully loaded all your repositories into the VSM mapping inbox you can now start to sift through and decide which of these repos are actually worthy to maintain in the service catalog. The repositories will arrive in the mapping inbox as {project}/{repo}. To continue the mapping:

1. Head over to Mapping Inbox and import the unmapped service entry to an existing service or create a new VSM service for the service catalog.

   

2. Congrats! you have now created your first VSM service - neat & tidy. Go ahead and explore what it has to offer and map it to
   your teams.

DORA Metrics

The Azure Repos repository integration automatically fetches information for two of the most important DORA metrics:

1. Deployment frequency: Number of deployments to production for a team.
2. Lead time for changes: Time from committing a change to code successfully running in production.

To have the two metrics show up for your teams, you need to add team members with their email addresses that they use within Azure Repos - most likely those are your corporate email addresses. Once set up, the system will start calculating the DORA metrics.

Imported data

The integration retrieves the following pieces of information from your Azure repo system:

1. Metadata, such as repository name, description, url etc.
2. Repository status e.g. archived, active
3. Repository code composition e.g. python
4. Repository tags e.g. frontend. Note we also inherit the tags from the parent project and add them to the repository tags.
5. Repository visibility e.g. private