This article provides information on possible reasons for the "No access to Azure DevOps" error on the Azure DevOps for Jira branch creation modal.
"No access to Azure DevOps" error
The "No access to Azure DevOps" message informs you that the connection created with a personal access token lost access to Azure DevOps.
There can be several reasons for this:
-
the personal access token you are using has expired;
-
the personal access token you are using doesn't have Code (Write) scope of access;
-
you provided the wrong Azure DevOps domain URL;
-
the Azure DevOps Server domain URL is not accessible from the Internet; there are firewall and network restrictions.
These are the most common causes, but this message can appear for any issue that prevents Jira from reaching your Azure DevOps organisation - for example a temporary Azure DevOps outage, a conditional access policy blocking the request, or rate limiting. If none of the steps below resolve it, the connection itself may be temporarily unavailable rather than misconfigured - try again shortly before assuming the token or URL is wrong.
To resolve
-
Check the personal access token's scope of access; if the Code (Write) scope is missing, update the token on the Azure DevOps side.
-
Check your token's expiration date. Extend the expiration date on the Azure DevOps side if it has expired.
-
Ensure you have provided the correct Azure DevOps domain URL. Additionally, check your network settings to ensure the firewall or proxy allows communication with the server. Navigate to Manage connection and click on Update token.
Updated: January, 2025