The Azure DevOps integration bridges the gap between product discovery and product delivery by empowering product managers and developers to work together.
Product managers and developers focus on two different areas: product discovery and product development. Product managers find and prioritize the right problems, and developers build the right solutions to those problems. But, developers use different tools from product managers, so they often need to switch between them, resulting in siloed information.
This is where the Azure DevOps integration comes into play. The integration shows critical information in both systems so the product and development team work harmoniously. The product managers can push features as a new work item or link them to an existing work item in Azure DevOps. This way, developers know what to build next and why.
In this article:
In order to configure this integration, you must be an admin in Productboard and an administrator who is either in the Project Collection Service Accounts or Project Collection Administrators groups in Azure DevOps.
Not sure which Azure product your organization has? See Microsoft's documentation here.
If you are using Azure DevOps Server (on-premise), you'll need to:
- Run Azure DevOps Server, version 2018 (Team Foundation Server 2018) or higher. For more information, contact email@example.com.
- Whitelist the following static IP addresses on your firewall with port 443:
Note: If you run into an error, double check with your network administrator that Productboard has access to your Azure DevOps network.
Your Azure DevOps on-premise setup needs to be in a public network with a public IP address. The IP address can be inaccessible from the internet in general, but it must be available to Productboard.
Installing and configuring your Azure DevOps Integration
- In Productboard, click your account name in the top right to open your main menu. Then click on Integrations:
- Scroll down to Azure DevOps, click [+] to add a new integration:
Name the integration. You can change this anytime, and add your Azure DevOps Server URL (i.e. https://dev.azure.com/zlack). This is a great way to distinguish multiple integrations.
Then, click on the Create integration button.
Note: If you're using a legacy version of Azure DevOps, your URL may have a different format: http://youraccount.visualstudio.com instead.
- Click the Open Azure DevOps button to go to the Personal Tokens page of your Azure DevOps admin account. If you need to go back to the Personal Tokens page, in Azure DevOps click on User Settings > Personal access tokens.
Note: The user who is configuring the integration has to be a member of Project Collection Service Accounts in Azure DevOps.
- In Azure DevOps click on + New Token:
- Click Give your token a name (i.e. Zlack DevOps Account), and make sure you select the same Organization you used in Productboard. For instance, if you entered https:// zlack.azure.com/, the Organization value is Zlack.
- Under Expiration (UTC), select Custom defined from the drop-down menu. Using the calendar drop-down, select the furthest possible date from today.
- Then authorize the scope access of the token you created. You need to add permissions for the following scopes for the integration: Notifications and Work Items.
For both, select the Read and Write authorization. Then, click Create.
Copy your unique token. You won't be able to do this again in the future, so don't forget!
- Go back to the Productboard Integrations page. Paste your unique token and click Authorize integration.
- If the token authorization is successful, you'll see a Valid check () letting you know that you finished the integration setup.
Finally, you can associate this integration with the relevant products in your account (this is an Enterprise-only feature).