Azure Tokens for SCM Bulk Integration and/or Monitoring

Black Duck Polaris Platform

Overview

How to create a token for integration, bulk onboarding, and monitoring features via SCM Integrations for Azure DevOps instances. Monitoring includes Synchronizing Polaris with your SCM Provider and Event-Based Test Automation in Polaris for SCM Integrations.
Note: Available for Azure Repos.

Creating a personal access token

When integrating Azure repositories with Polaris (whether for on-prem ADO Server or cloud-based ADO Services), you will need a personal token created within the relevant Azure DevOps instance. If you haven't done so already, create this access token before starting the integration process. To assist you during this process, it might be useful to refer to the official Azure documentation: Use personal access tokens > Create a PAT

Important: Token must be created by an Azure DevOps Organization Owner or users with the "Manage organization webhooks" permission, who are authorized to manage organization webhooks. Although other Azure users may be able to select the scope requirements when creating a token, the token will not work due to permission requirements in Azure to manage organization webhooks.
  1. Log in to your ADO instance using your Azure credentials.
  2. Depending on whether you're integrating with a cloud-based or on-prem instance, do one of the following:
    • For ADO Services (cloud) integrations, select User settings > Personal access tokens.
    • For ADO Server (on-prem) integrations, select your user icon in the top-right corner of the page, then select Security.

    You'll now see the User settings page, with the Personal Access Tokens tab selected.

  3. Select +New Token.
  4. Enter a suitable Name for the token.
  5. Under Organization, select All accessible organizations.
  6. Set the token's Expiration date.
  7. For scopes, select Custom defined.
    1. Under Code, select Read & Write.


    2. Under Project and Team, select Read & Write.


  8. Select Create.
  9. From the confirmation dialog, copy and store your token in a secure location such as a password manager.
    Important: Each time you modify a project's SCM integration, you'll need to reenter the token to save your changes.

Next Steps

Use the token to connect to Polaris:

After the connection is established:

You can also scan on demand (see How to test from the web UI) or schedule automatic testing on a daily or weekly basis (see Test scheduling policies).

Note: From the Tests screen, before beginning a test manually, make sure to test the connection.