Last updated: November 2026
Use this page to connect GitKraken Desktop to Azure DevOps for repository access, pull request work, and SSH setup by using OAuth or a personal access token. The integration requires a Pro subscription or higher, and PAT authentication is the fallback when an Azure DevOps organization blocks third-party OAuth access.
Requirements and limits
- Integration covered here: Azure DevOps
- Plan: Pro subscription tier or higher
- Authentication options: OAuth or Personal Access Token (PAT)
- OAuth constraint: If the Azure DevOps organization disables third-party OAuth access, use a PAT instead
- Account limit: 1 Azure DevOps account per profile; multiple profiles require a paid Pro, Teams, or Enterprise plan
- SSH behavior: GitKraken Desktop uses the key in Preferences > SSH unless you configure a service-specific key or system SSH Agent
| Method | When to use | Requires | Limitation |
|---|---|---|---|
| OAuth | Standard Azure DevOps browser-based connection | Pro subscription and third-party OAuth access | Not available if the organization blocks third-party OAuth |
| Personal Access Token | OAuth is blocked or policy requires token-based access | Pro subscription, host domain, PAT | Manual token generation and paste flow |
| SSH key setup | You want SSH-based Git operations after connecting | Existing integration connection and SSH key upload | Uses GitKraken SSH settings unless overridden |
Quick Start
- Go to Preferences > Integrations in GitKraken Desktop.
- Select Azure DevOps and click Connect to Azure DevOps.
- Finish connecting in your browser at gitkraken.dev. If asked, log in with your Azure DevOps credentials.
- If your Azure DevOps account has more than 1 organization, choose one from the Azure Organization list on the Azure DevOps card.
You must be signed in to your GitKraken account to connect with OAuth. The connection belongs to your GitKraken account, so you can also use it on your other computers and profiles. See How integrations connect through your GitKraken account.
If OAuth is not available, for example because your organization has disabled third-party access, use a Personal Access Token (PAT) instead:
- In Preferences > Integrations, enter your host domain.
- Click Generate a token on Azure DevOps to open the token creation page.
- Copy the token and paste it into GitKraken Desktop, then click Connect.
After connecting, GitKraken Desktop can browse your Azure DevOps repositories when cloning, display fork options when adding remotes, and show pull request details. To use SSH, go to Preferences > Integrations, click Generate SSH key and copy to clipboard, and add it to your Azure DevOps SSH settings.
What the Azure DevOps integration lets you do
- Create new repositories on your Azure DevOps account with optional .gitignore and license files.
- Generate an SSH key and copy it to your clipboard for Azure DevOps.
- Clone directly from your Azure DevOps repository list.
- Identify Azure DevOps repositories by remote avatars on the Commit Graph.
- Add remotes for Azure DevOps repositories.
- Create and view pull requests, and add reviewers.
Note: The Azure DevOps integration requires a Pro subscription tier or higher.
How to authenticate with Azure DevOps
Use OAuth when: your Azure DevOps organization allows third-party application access and you want the simplest browser-based setup. Use a PAT when: OAuth is blocked by policy or you need token-based access that matches your organization’s security controls.
To authenticate with Azure DevOps:
- Open Preferences > Integrations in the top-right corner.
- Choose Azure DevOps and click .
- Finish connecting in your browser at gitkraken.dev. If asked, log in with your Azure DevOps credentials.
- If your Azure DevOps account has more than 1 organization, the card reads Select an organization to finish connecting Azure DevOps. Choose your organization from the Azure Organization list.
How to choose an organization after you sign in
If Azure DevOps is linked to your GitKraken account, GitKraken Desktop can connect it when you sign in. When your Azure DevOps account has more than 1 organization, GitKraken Desktop shows Choose an Azure DevOps organization, either as a step during setup or in a window after you sign in again. With 1 organization, GitKraken Desktop selects it for you.
- Select an organization from the list.
- Click Continue.
To decide later, click Skip this step. Azure DevOps stays partly connected until you choose an organization in Preferences > Integrations > Azure DevOps. You can change the organization there at any time.
You can also connect using a Personal Access Token (PAT):
- Enter your host domain and click .
- Log in to Azure DevOps and generate a token.
- Copy the token and paste it into GitKraken Desktop, then click . Azure DevOps shows the token only once.
How to generate an SSH key for Azure DevOps
GitKraken Desktop uses your default SSH configuration from Preferences > SSH unless you configure a specific key for Azure DevOps or enable your system SSH agent.
After you connect, generate a new SSH key:
- Click .
- Paste the key into your Azure DevOps SSH settings.
What Azure DevOps OAuth enables in GitKraken Desktop
Use the Azure DevOps integration when: you want repository discovery, remotes, and pull request workflows directly in GitKraken Desktop. Do not rely on it alone when: your Azure DevOps setup requires organization-specific workflows outside the features surfaced here.
When you are authenticated, GitKraken Desktop lets you:
- Browse your Azure DevOps repositories while cloning:
- View fork options when adding remotes:
You can still enter a remote URL manually.
How to connect multiple Azure DevOps accounts
GitKraken Desktop supports 1 Azure DevOps account per profile. With a paid Pro, Teams, or Enterprise plan, use multiple profiles to switch between accounts.
Use multiple profiles when: you need to switch cleanly between separate Azure DevOps identities or organizations. Do not use multiple profiles when: one account already covers the repos you need and profile switching would only add overhead.
How to enable Azure DevOps OAuth for GitKraken Desktop
To connect via OAuth, Azure DevOps must allow third-party applications:
- In Azure DevOps, go to Organization Settings > Policies.
- Enable Third-party application access via OAuth.
For details, see the Microsoft documentation: Change application connection & security policies for your organization.
If you cannot enable this setting, connect using a Personal Access Token (PAT) instead.
Azure DevOps troubleshooting
Use these fixes when an Azure DevOps feature does not appear as expected.
How to fix a missing Azure DevOps pull request form
If your Azure DevOps pull request does not appear in GitKraken Desktop:
- In the Left Panel, right-click the remote (typically
origin) and select Edit. - Make sure the URL uses the format
dev.azure.com/[organization]and matches the domain of your integration:- If you use a PAT, the URL must match the Host Domain URL in Preferences > Integrations.
- If you use OAuth, the URL must match the connected domain.
- Do not use the deprecated VSTS format,
[organization].visualstudio.com. - Click Edit Remote to save changes.
