Integrate Aha! with Azure DevOps Server (integrations 1.0)

This support article refers to the historical 1.0 version of the Aha! integration with Azure DevOps Server. If you are looking for details about how to setup the Azure DevOps Server 2.0 integration, reference this article.

How it Works

This two-way integration allows you to push features and requirements from Aha! into the on-premise Microsoft Azure DevOps Server and receive updates back in Aha! from Azure DevOps Server (formerly Team Foundation Server). The integration requires Azure DevOps Server 2015 or later as prior versions of Azure DevOps Server did not include API support.

If your team is using the cloud version through Azure DevOps Services, please refer to our Azure DevOps Server integration article.

Note that you will need to create a firewall exception in order for Aha! to communicate with your on-premise Azure DevOps Server. See the whitelisting IP addresses for on-premise development systems article for help.

As with any Aha! and development tool integration, it is important to understand that Aha! comes first in the process. You plan, strategize, and complete work in Aha! and then send features and releases from Aha! to your development tool.


  • Authentication with Azure DevOps Server is done using NTLM.
  • One Aha! product is associated with one Azure DevOps Server project*.
  • A feature can be sent to the Azure DevOps Server using the Actions > Send to Azure DevOps Server menu on the features page.
  • Requirements are sent to Azure DevOps Server together with the feature.
  • Only the name, description and attachments of features and requirements are sent.
  • If you set up a subscription in Azure DevOps Server, the integration can receive updates about name changes, description changes or status changes.
  • The mapping of Azure DevOps Server states to Aha! workflow statuses is configurable.


You need to be product owner in Aha! to set up this integration.

To configure this integration, first add the integration in Aha! under Settings > Product > Integrations.

  1. Enter the URL of your Azure DevOps Server server, including the collection name, but without a trailing slash.
  2. Enter your Azure DevOps Server username and password.
  3. Click the Test connection button.
  4. On success, you should be able to choose which project to integrate with. You also must select an area of this project where features and requirements should be created.
  5. Select the workitemtype to which features should be mapped. Then select for each Azure DevOps Server state to which Aha! workflow status it should be mapped.
  6. Repeat step 5 for requirements.
  7. Enable the integration and test it by going to one of your features in Aha! and using the Send to Azure DevOps Server item in the Action menu.
  8. The feature should now appear in your Azure DevOps Server project together with its requirements.

If you want to be able to receive updates from Azure DevOps Server you must setup a subscription.

  1. Copy the Webhook URL from the Aha! configuration page.
  2. In your Azure DevOps Server account, go to the project you want to integrate with.
  3. Click the Project settings button in the bottom left and select the Service hooks page.
  4. Add a new service hook by clicking the + Create subscription button.
  5. Choose the Web Hooks service and click Next.
  6. Choose the Work item updated trigger from the dropdown menu. You can leave the filters unchanged and click Next.
  7. In the Action settings, paste the Webhook URL from Aha! into the URL field.
  8. Press Finish to create the subscription.

*Note: You can add the integration multiple times if you want to integrate multiple projects with a single Aha! product. Once you have added an integration, you may change the title to specify the project this integration belongs to by clicking on the title at the top of the integration set-up page. You can also create a separate integration for each of your Aha! products, and have each integration point to just one Azure DevOps Server project.

Was this article helpful?
2 out of 2 found this helpful