Azure DevOps for Jira
Azure DevOps for Jira
Breadcrumbs

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 resolve the most common issues with Personal Access Token access.

Invalid Personal Access Token

image-20240815-082003.png

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.

Please provide the organization name the token has access to

image-20240815-082215.png

This error message informs you that the Personal Access Token you use doesn’t have access to all organizations.

To resolve this error:

If you use the token with access to a specific Azure DevOps organisation (not all organisations), you need to provide the organisation name.

Organization not found

image-20240815-082431.png

This error message informs you that the organisation entered does not match the one the Personal Access Token has access to.

To resolve this, check the organisation name listed on the token and ensure they match exactly.

Personal Access Token doesn't belong to a project administrator

image-20230913-202141.png

This error appears when you try to create a new association. It means Personal Access Token was created by someone who is not an administrator and does not have the Edit Subscriptions and View Subscriptions permissions for the selected project (see the Microsoft guide). Those permissions allow us to subscribe to updates on Azure DevOps entities.

To resolve this error:

  1. Ask your Azure DevOps organisation’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 to grant permissions to, then click the three-dot menu.

    3. Click Manage user, then edit permissions.

    4. Once permissions are granted, try creating the association again.

      user_manage.png

  2. If you have administrator permissions for the project, generate a new Personal Access Token and create a project connection. Please follow this guide.

Personal Access Token doesn’t have the required scope of access

image-20250131-195232.png

This error message indicates that Personal Access Token you’re using doesn’t have the minimum scope of access we need.

To resolve this error:

  1. Please check that 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 the required scope of access is missing, edit the existing Personal Access Token and click Save. Then try to create the integration once more.

  3. You can find a guide to creating the Personal Access Token here →How to create Microsoft Azure DevOps personal access token.

"No suitable repositories found" - Code (Read) scope can't be fully validated

image-20260710-144933.png

This message informs you that the integration could not fully validate the Code (Read) scope of your Personal Access Token. Unlike the error above, this does not block the setup, and you can still save the integration and continue. It also does not mean a permission is missing; the Personal Access Token can be correct.

The message appears when one or more projects in your Azure DevOps organisation have no repository the app can validate the Code (Read) scope against. This is usually the case when:

  • project in the organisation has no repositories, or

  • repository exists but has no commits, or

  • repository has no active default branch.

To resolve this error:

  1. You can save the integration as it is. All your Azure DevOps projects are still connected, including the empty ones; the message only means the Code (Read) scope could not be fully validated for the projects that currently have no repository.

  2. Once you add a repository to such a project, its code will start syncing with the integration.

  3. To confirm which projects are affected, open them in Azure DevOps under Repos and verify that each has a repository with at least one commit and an active default branch.

How to create Microsoft Azure DevOps personal access token


Updated: