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.
Next Steps
Use the token to connect to Polaris:
- Connect a Polaris project to an ADO repository
- Onboard ADO repositories to an existing Polaris application
- Onboard ADO repositories to Polaris applications
After the connection is established:
- Synchronizing Polaris with your SCM Provider
- Event-Based Test Automation in Polaris for SCM Integrations
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.