Set up


Before you dive in, please note that the user that you choose to authenticate with Azure DevOps must be have the Project Administrators role. Read about permissions required.

For this reason, you might choose to create a specific integration user that can be controlled by a trusted member of your business. This mitigates against the situation where you have to delete a user that Avion is authenticated with if a person leaves your business. More info.

You might need to allow pop-ups if you browser blocks them, as Avion uses a pop-up window to authenticate with Azure DevOps.

Instance selection

If you are a user in multiple Azure DevOps instances, you will be asked to select an instance.

Project selection

Select the project you wish to integrate with. Avion supports a direct mapping of one or many story maps to one Azure DevOps project, although we recommend keeping it simple with a one to one mapping.

If you are struggling to find your instance or project, check that you are signed into the correct Microsoft account and that the right directory is selected.

Backbone sync selection

Choose whether you would like Avion to sync your journeys and steps to Azure DevOps Epics and Features or not. Unsure what to select? Advice and info.

State mapping

Map your Avion workflow to your Azure DevOps states. Advice and info.

Import from Azure DevOps

Import your backlog from Azure DevOps and even specify a WIQL query to restrict which work items are imported, although this is not a requirement. Advice and info.

Last updated