Azure DevOps for Snyk Essentials

The Integrations page shows all active integrations, including data from your existing Snyk Organizations that is automatically synced and provides access to the Integration Hub.

Azure DevOps setup guide

Pulled entities

• Repository - the pulled entity retrieved by Snyk Essentials.

Integrate using Snyk Essentials

1. Profile name (mandatory): Input your integration profile name.

2. Organizations (mandatory): Input the names of all the relevant Azure DevOps organizations.

3. Access Token (mandatory): Create your Azure DevOps PAT from your Azure DevOps settings.

   • Access Token (mandatory): Create and add your Access token by following the instructions from the Generate a Personal access token from your Azure DevOps settings section.

   • API URL (mandatory): The API URL, for example, https://dev.azure.com/. You can use a custom URL that is publicly accessible.

4. Broker Token (mandatory): Create and add your Broker token if you use Snyk Broker.

   • Generate your Broker token by following the instructions from the Obtain your Broker token for Snyk Broker page.

   • Copy and paste the Broker token on the integration setup menu from the Integration Hub.

5. Add Backstage Catalog (optional): If you want to add your Backstage catalog, follow the instructions from the Backstage file for SCM Integrations page.

The following PAT token permissions requirements are for Snyk Essentials integrations. For SCM integration, see the Azure Respositories (TFS) permissions requirements on the Snyk SCM integrations pages.

Generate a Personal access token from your Azure DevOps settings

The user account that owns the PAT needs Basic access level on the Azure organisation.

1. Open Azure DevOps and click the Settings menu for your profile.

2. Click Personal access tokens and then New token.

3. Select the following scopes:

   • Permissions

     • Code - read

     • Project and Team - read

     • Analytics - read

     • Member Entitlement Management - read

   • Organization - Select All accessible organizations or a specific organization.

4. Set the expiration to 12 months.

5. Copy the generated personal access token and share it through a secured vault.

API version

You can use the Azure DevOps REST API v6 repository to access information about the API.