Azure Tokens for SCM Bulk Integration and/or Monitoring

Overview

How to create a token for bulk onboarding and monitoring features via SCM Integrations. 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 SCM repositories, you will need a personal access token you create in Azure DevOps.

Authentication between Azure Repos and Polaris is managed with a personal token that you create in Azure DevOps. If you haven't done so already, create an access token. For additional information: 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. From Settings pulldown, select Personal Access Token.
  2. Click +New Token.
  3. Enter a Name for the token.
  4. Under Organization, select All accessible organizations.
  5. Set the token's expiration date.
  6. For scopes, select Custom defined.
    1. Under Code, select Read & Write.


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


    Important: Store your token in a secure location. Each time you modify a project's SCM integration, you'll need to reenter the token to save your changes.

Next Steps

Use this 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.