GitKraken Client Documentation

Contact support  

Azure DevOps Integration

GitKraken allows you to connect to Azure DevOps (formerly VSTS), which will help you find repos on Azure DevOps when cloning.


  • Create repositories on Azure DevOps account including .gitignore and license
  • Automatically generate an SSH key pair and copy it to Azure DevOps
  • Clone from Azure DevOps repo list
  • Identify Azure DevOps repos with remote avatars on graph
  • Add remotes for Azure DevOps repos
  • Create and view Pull Requests

Azure DevOps Authentication

To authenticate with Azure DevOps, navigate to the upper right corner to access Preferences Integrations

Or alternatively if you are in the New Tab view, click on Preferences under Customize.

From the Authentication window, enter your Host Domain then click the

This opens a web browser where you next log in with your Azure DevOps credentials and generate an access token.

Copy your token to the clipboard as this is the only time you will see this token. Paste the token into GitKraken and click on .

Generating an SSH Key for Azure DevOps

GitKraken uses your local SSH Config from SSH Defaults to fetch and push unless you set up a Azure DevOps-specific SSH key, or enable your local SSH Agent.

Once your Azure DevOps account has been connected to GitKraken, you may easily generate an SSH key and add it to your Azure DevOps account from Preferences Integrations.

Click the magic button and add the key to your Azure DevOps account.

OAuth integration with Azure DevOps

GitKraken’s integration with Azure DevOps provides handy information about your repositories.

First, you may search through your existing repositories when cloning:

Next, GitKraken presents a list of forks of the current repository when adding remotes:

Of course, you still have the option of manually entering repo URLs.

Connecting to multiple Azure DevOps accounts

GitKraken connects to one Azure DevOps account at a time. However, with a paid GitKraken Pro/Teams/Enterprise plan, you can easily switch between multiple profiles that each have their own associated Azure DevOps accounts.

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