Are you having trouble with conencting Gearset to Azure DevOps?
When trying to load the repositories with Azure DevOps Git, do you receive the following error message:
"Gearset can't find any repositories. Either create one or update your security settings in Azure DevOps to grant access."
Is Gearset is only able to show some, but not other, Azure organizations, and therefore you cannot access the repo you want? This document troubleshoots the common problems we see.
Cause 1 - Does your repo have a default branch?
We have seen repositories without a Default branch, that causes a problem with retrieval. In this screenshot the master branch is the default - please check your repo has one too.
If your repo does have a default branch, the API response (see cause 4 below) to
https://<accountName>.visualstudio.com/_apis/git/repositories?api-version=1.0
should have a the parameter "defaultBranch":"refs/heads/<branch name>". If it does not, we need to set a default branch.
Resolution
Set a branch (usually master or main) as default.
Cause 2 - Are you connected to the right tenant?
If you have multiple tenants in Azure DevOps, it is likely that that Gearset has been connected to the wrong one, and therefore can't load the repositories you expect. Gearset will give you the error:
"Gearset can't find any repositories. Either create one or update your security settings in Azure DevOps to grant access"
Alternatively, if you are using Pipelines, Gearset could be showing you a banner that says:
"Pull requests can't be loaded and some of the pipeline functionality won't be available to you, please ask the owner for access."
To verify if you have multiple tenants, you can review it in the drop-down of your account's settings. To access this, go to User settings and click on Profile :
Then click on the link to the Azure DevOps Profile Page :
Here you can review your tenants in the drop-down. Make sure you have the right tenant selected.
Note: If you do not have multiple tenants, it is possible that your repo type is not git-based. Gearset only supports Git repo types, and not other types such as TFVC. If your repo is not a Git repo type, you will need to create a new Git-based repo.
Resolution
To resolve this, you need to:
In Azure DevOps, revoke the Gearset application authorisation on all tenant profiles.
Switch your Azure DevOps to the correct tenant profile.
In Gearset, delete the connection to Azure DevOps.
Log out of Gearset to clear the cached credentials.
Log into Gearset again and connect to Azure DevOps again. When you get the integration pop up, you can make sure that the part of the account / tenant in the parenthesis is correct.
You may need to log into an incognito window of your web browser to get the option to enter your desired Azure DevOps login details.
Sometimes Azure fails to properly assign the user to the correct tenant even know it appears to be on the correct tenant from the UI. We can verify this by going to Cause 4 - Can the API access the expected repos?
Cause 3: Can Gearset authenticate with OAuth?
If your Azure organization has not given permission for third-party access with OAuth, Gearset will not be able to retrieve repository data.
This will result in the error upon connection, and you may see below error message:
"Azure DevOps authorization error
A problem occurred while authorizing with AzureDev Ops.
An unknown error occurred. Please contact support if you need assistance with this issue."
Resolution
In Azure DevOps navigate to your
Organization settingsand in the left-hand menu clickPolicies.Make sure that
Third-party application access via OAuthis toggled toOn.
This should allow you to see the right repositories that you are looking for.
Cause 4 - Can the API access the expected Account/repos?
Check if you can access the list of repos via the API call in the URL to see what Gearset is able to see.
Start with this HTTP query in your browser to find the <publicAlias> value
https://app.vssps.visualstudio.com/_apis/profile/profiles/me?api-version=1.0
This should give an output similar to
{"displayName":"First Surname","publicAlias":"a1234567-8b9d-0def1-a234-5b6c78de90f1","emailAddress":"[email protected]","coreRevision":123456789,"timeStamp":"2024-11-25T14:50:56.66+00:00","id":"a1234567-8b9d-0def1-a234-5b6c78de90f1","revision":123456789}
Then use the publicAlias value from this output to request for the <accountName>
https://app.vssps.visualstudio.com/_apis/Accounts?memberId=<publicAlias>&api-version=1.0
If you get the response
{"count":0,"value":[]}Then Azure has not been able to successfully assign your account to the correct tenant. To resolve switch tenants then switch back. You should now be able to successfully retry adding an Azure connection.
If instead you receive an output similar to
{"count":1,"value":[{"accountId":"9876a543-bc21-09d8-7efa-654321b9c87d","accountUri":"https://myaccountname.vssps.visualstudio.com:443/","accountName":"myaccountname","accountType":"personal","accountStatus":"enabled","properties":{"Microsoft.VisualStudio.Services.Account.ServiceUrl.00012345-6789-12AB-34C5-6D7890123EF4":{"$type":"System.String","$value":"https://myaccountname.visualstudio.com/"}}}]}
Then use the <accountName> to request for the list of repos available:
https://<accountName>.visualstudio.com/_apis/git/repositories?api-version=1.0
This can verify which repos are expected to show up in Gearset.
"Problem getting user account information from Azure DevOps"? Ensure that the ADO account currently logged in on your web browser
Sometimes, you may come across this error message when you're trying to add an Azure account:
"Problem getting user account information from Azure DevOps. Ensure that ADO account currently logged in on your web browser is a member of an ADO organisation"
Users have reported this error message happening after they've successfully connected their ADO account (for the first time), then removed the connection in their Gearset app, and tried to re-connect.
Resolution
1. Make sure that in the browser where you have your Gearset app open, you're not logged into a different Azure account than the account you're trying to connect to in our app.
Particularly, if you have more than one tenant for the Azure account you're trying to connect.
2. If you've already tried to connect your Azure account on a different browser, or while using Incognito mode, or after clearing cache and re-logging into Gearset on your current browser - please, move to step 3.
3. Is the third-party application via OAuth enabled in your Azure Organization Settings under Security > Policies?
If not, make sure this setting is enabled and try to re-connect your Azure account in Gearset.
If the setting is enabled, try to revoke it on your Azure account, re-enable it, and then try to re-connect the ADO account in our app. We believe this may help resolve your issue.
If none of the above steps helps you resolve your Azure connection issue, please contact us in the in-app chat for further guidance.