Set up the Azure DevOps integration

Last updated: Feb 5, 2026

Follow these steps to set up Fluid Attacks’ integration with Azure DevOps:

1. Go to your Azure DevOps Organization Settings and ensure it allows third-party application access via OAuth.

   

   This configuration needs to be done by someone with permissions to modify organization settings on Azure DevOps.

   Azure allows you to configure certain issue templates with custom fields, some being mandatory. Since the integration is generic, you need to access your project, navigate to Project Settings > Permissions > Project Administrators, and ensure you have the option “Bypass rules on work item updates” set to “Allow” for the integration to function correctly. Also, if you would like to add tags when creating work items from our platform, please verify that the “Create tag definition” setting is also set to “Allow.”

   
   • The integration assumes that it is possible to create items using the ‘Issue’ work item type. If this work item type is not available in your project, or if you are unsure whether it is, please review the following documentation .
   • To avoid creating duplicate issues, the integration first checks if there is an existing issue with the same title as the type of vulnerability. If that is the case, it uses it as the parent issue and creates only the associated “Tasks” for individual vulnerabilities of the type in question.

2. On Fluid Attacks’ platform, access the Integrations section from the collapsible sidebar.

   

   To continue with this integration, make sure you have permissions to view and create issues in your project on Azure DevOps.

3. Click on Use integration in the Azure DevOps card. If your organization has set up this integration before, the card does not show that button, and you have to click the available gear icon () instead.

   

4. Click the Connect button corresponding to the group for which you desire the integration.

   

   If instead you wish to modify details (e.g., organization, project, creating issues automatically for reported vulnerabilities) of an existing connection, you can click on the Edit button available next to the group name, make the necessary changes and click Update to finish setting up the integration.

5. Click on Authorize to connect your group to the Azure DevOps account.

   

6. Read the permissions you give Fluid Attacks with this integration and click the Accept button to agree to them.

   

7. Once redirected to the platform, enter your Azure DevOps organization. This, as well as the project that you have to select next, must correspond to your organization and project configured on your Azure DevOps, respectively.

   

8. Select the specific Azure DevOps project to connect, select the person who will be assigned the vulnerabilities and write any tags to assign to every new issue. Bear in mind that the options available in the Assigned To field are the emails of all those who have access to the project on Azure and not necessarily to the group on Fluid Attacks’ platform.

   

   Issues are created for vulnerabilities reported after setting up the integration with this feature enabled and not for those reported before.

9. Click the Update button and you will be all set.

To see the automatically created issues on Azure DevOps, access your project and select Boards and then Work items from the left-side menu.

Inside the issue, you can see the Location and Specific details  of reported vulnerabilities related to the weakness in question, among other relevant information. Locations are created as child tasks under the issue, and their titles indicate where the vulnerability was found. As explained in the note under step 1 about avoiding duplicate issues, if an existing issue’s title matches the title of the reported finding, the locations are reported under the existing issue instead of creating a new one; the same validation is applied to child tasks.

On Fluid Attacks’ platform, to show you where you are using this integration across your groups, the Azure DevOps card displays how many of the groups you have access to have the integration configured.