> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/sast-and-sca/prezero/integrations/azureboards.md).
# Azure Boards integration
The following instructions will walk you through enabling the Azure Boards integration for linking Qwiet findings with Azure DevOps work items.
## Prerequisites
You must have administrative privileges for Qwiet and Collection Admin privileges for Azure DevOps to set up the integration.
## Step 1: Authorize with Azure DevOps
1. Log into the Qwiet Dashboard and go to [Organization Settings](https://app.shiftleft.io/organization/settings). Initiate the authorization flow by clicking the **Connect Azure Boards** button.
2. Grant consent to manage Azure Boards for **Qwiet Azure App**.
## Step 2: Project Association
You need to configure Azure project mapping with your Qwiet organization’s application. These configurations are used to create work items in selected projects. This can be accomplished on the Qwiet **Applications** > **Settings** page.
To associate an Azure project, please follow these steps:
* Select the **Organization** from the dropdown. It will list all the organizations that you have access to.
* Selecting the organization will allow you to select the **Project** under that organization.
* After selecting the Project, you can also specify which **work item type** should be used for creating work items from the dropdown.
* Click **Save**.
These configurations can be updated later and will be applicable on further finding associations.
## Step 3: Assign a finding to Azure Boards
After successful project association, you will get an option on the Qwiet finding's page to assign the finding to Azure Boards. Select any Qwiet finding and click the **Assign To Azure** button.
## Step 4: Navigating between Azure Boards and Qwiet
Once you've successfully submitted a finding to Azure, you'll see the newly created finding in Azure Boards:
 
## Organization roles
There are different permission scopes assigned to organization roles. These scopes can also be used to create custom roles.
| Role | Scope |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Guest | azureboard\_workitem:read |
| Member | azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
| Team Developer | azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
| Collaborator | azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
| Power User | azureboard\_auth:write, azureboard\_association:write, azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
| Super Admin | azureboard\_auth:write, azureboard\_association:write, azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
| Team Manager | azureboard\_auth:write, azureboard\_association:write, azureboard\_association:read, azureboard\_workitem:read, azureboard\_workitem:write |
### Scope definition
| Scope | Usage |
| ----------------------- | ---------------------------------------- |
| azureboard\_workitem | Used for Azure work item access/creation |
| azureboard\_association | Used for Azure board project association |
| azureboard\_auth | Used for authorization with Azure Boards |