How to fix “No access to Azure DevOps” error when creating a branch?

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.

To resolve

1. Check the personal access token’s scope of access; if the Code (Write) scope is missing, update the token on the Azure DevOps side.

2. Check your token's expiration date. Extend the expiration date on the Azure DevOps side if it has expired.

3. 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.

31 Jan 2025