Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

Personal access token failing Azure DevOps integration with Not Authorized error


The Personal Access Token created in Azure DevOps is not valid for authentication.


Jira admins will see a Not authorized error (with the following full error) when connecting to Azure DevOps with a Personal Access Token if the token was created for a specific Azure DevOps organization:


Technical info: Error:

2019-07-08 12:21:09,997 http-nio-8080-exec-436 ERROR sfj 741x4276982x1 a7oa8 /rest/gitplugin/1.0/trackedfolders/scan/4994-Bpv7dj9zmeyFAAf6 [] Rest API has thrown exception.
com.bigbrassband.jira.git.exceptions.external.WrappedMicrosoftAPIException: External service error
at java.util.concurrent.Executors$ Source)
at Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)
Caused by: com.bigbrassband.common.indexer.sources.clients.RequestException: Microsoft Unauthorized (401)
at com.bigbrassband.common.indexer.sources.clients.MicrosoftClient.runRequest(
at com.bigbrassband.common.indexer.sources.clients.MicrosoftClient.callSingleApi(
at com.bigbrassband.common.indexer.sources.clients.MicrosoftClient.getUserId(
... 10 more


Azure DevOps Personal Access Tokens must be created using the All accessible organizations in the Organization dropdown. Additionally – the token must either have Full access scope or Code: Read & Write (as shown below). Minimum requirement is Code: Read.

  1. Create new Personal Access Token:

  2. Copy token:

  3. Verify token uses All accessible organizations, has sufficient scopes, is not expired and is active:

  4. Paste newly created token:

  5. Click Connect.

Contact Us
If you still have a question – reach out to our Support Desk or email us at [email protected].


More articles about troubleshooting, workarounds and solutions

Why I am getting the error, “git-upload-pack not permitted”?

Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories

Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported

Connection Reset when Accessing the Database

“Dangerous use of multiple connections” error on local database

Duplicate entry 0 for key PRIMARY exceptions in log

Error while reindexing – Java heap space / Object too large, rejecting the pack

Error creating git branches and also using NFS

Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode

Fixing reindex issues using Indexing Queue Viewer

Gitolite integration: Why the Git integration app not see the master branch?

Health Check: Database Collation

Indexing error – Too many open files

Installation fails when installing manually

Jira index error: IndexNotFoundException: no segments* file found

Malformed input or input contains unmappable characters

Personal access token failing Azure DevOps integration with Not Authorized error (this page)

Problems with shared home on Azure Storage

Pull request index error: org.json.JSONException

Repositories missing from Azure DevOps integration

“Service proxy has been destroyed” exceptions in log

SQLException ‘Incorrect string value’ in merge requests

SSH key file format is invalid

TFS – Not authorized exception when Jira works thru proxy

Unexpected exception parsing XML document from URL error in log

Why don’t I see the Create Branch or Pull Request features?

Have feedback about this article? Did we miss something? Let us know!
On this page