Azure DevOps Configuration
Create an Access Token in Azure DevOps
Required Token Permissions
|Automated Commit Feedback|
|Automated Pull Requests|
|Pull Request Commenting|
|Pull Request Line Commenting||Not Applicable for AzureDevOps|
|Bitbucket Code Insights||Not Applicable for AzureDevOps|
To create a personal access token:
- Log in to your organization in Azure DevOps
- Open your user settings
- Select Personal access tokens from the User Settings menu.
- Click the + New Token button
Name your token and select All accessible organizations. Choose an expiry date for your token.
Important! If you do not select All accessible organizations, the Easy SCM Onboarding feature will not work.
To enable automated pull requests and automated commit feedback:
- Select the scopes for this token to authorize for your specific tasks. For the full features of IQ SCM support enable Code: Read & Write and then select Create.
See this explanation for details of Azure DevOps scopes
- Save the personal access. You will not be able to view it again.
Protecting the Target Branch
You can prevent users from merging Pull Requests with failing IQ Policy Evaluations. IQ Policy Evaluations must be set to Fail at the Source Stage.
Create and configure a Branch Policy to protect your target branch:
1. Navigate to Repos → Branches in the left menu, and select a branch to protect (typically main or
develop ). Select Branch policies from the menu.
2. Find Status checks and click the + button
3. Fill out the form
Status to check * → Security/IQ Policy Evaluation
Policy requirement → Required
The rest of the values can use the default options