How to fix errors that occur during the integration setup?

To set up integration between Azure DevOps and Jira, you need to generate a Personal Access Token. In this guide, we will help you solve the most common issues related to Personal Access Token accessibility.

Invalid Personal Access Token

This error occurs when you enter an incorrect or non-existent token.

To resolve this error:

1. Make sure that the Personal Access Token you are using is generated on the Azure DevOps platform. To create a new one, please, follow this guide.

2. Double-check that you copied all characters of the Personal Access Token to the input field.

Personal Access Token has not been created with the "All accessible organizations" option selected

This error message informs you that the Personal Access Token you use doesn’t have access to all organisations. This integration requires access to all Azure DevOps organizations making it possible to fetch organizations and projects from the entire Azure DevOps instance to set up associations.

To resolve this error:

1. Please ensure the token you use has access to all organisations:

   1. Go to User Settings on the Azure DevOps platform.

   2. From the drop-down select Personal Access Tokens.

   3. Select the token you use and click on Edit.

   4. Check the option chosen in the Organization field.

2. If there is access only to one organisation, you need to generate a new Personal Access Token. Please, follow this guide.

3. Once you generate a new Personal Access Token click on Disconnect. Then paste a new one.

Personal Access Token doesn't belong to a project administrator

This error appears when you try to create a new association. It means that the Personal Access Token was created by a person who is not an administrator and does not have Edit Subscriptions and View Subscriptions permissions for the selected project. Microsoft guide. Those permissions allow us to create subscriptions to changes in Azure DevOps entities.

To resolve this error:

1. Ask your Azure DevOps organization’s admin to grant the token’s creator administrator permissions for the project you want to create an association:

   1. Go to Organization Settings and click on the Users section.

   2. Find the user you want grand permissions and click on the three-dots menu.

   3. Click on Manage user and edit permissions.

   4. Once permissions are granted try to create an association again.

      

2. If you have administrator permissions for the project you want to create an association, generate a new Personal Access Token. Please, follow this guide.

3. Once you generate a new Personal Access Token click on Disconnect. Then paste a new one.

Personal Access Token does not have the required scope(s)

This error message informs you that the Personal Access Token you use doesn’t have the minimal scope of access we need.

To resolve this error:

1. Please check the token you use has the necessary scope of access:

   1. Go to User Settings on the Azure DevOps platform.

   2. From the drop-down select Personal Access Tokens.

   3. Select the token you use and click on Edit.

   4. Check the Scope section.

2. If there is no necessary access, edit the existing Personal Access Token and click on Save. Try again to create an association.

3. Here is the guide on token details → How to create Microsoft Azure DevOps personal access token

How to create Microsoft Azure DevOps personal access token

Updated: 16 Nov 2023