AZD: Install and connect to Azure DevOps

Install AZD from JetBrains Marketplace, then connect it to your Azure DevOps organization. AZD stores one account per organization or collection, and every AZD tool window uses those accounts.

Before you start

The current version requires a JetBrains IDE 2026.3, build 263.5153 or a later 2026.3 build. IDEs 2026.2 get AZD 2026.2.23, the final release for that IDE version.
An account on Azure DevOps Services (https://dev.azure.com/<organization>) or on Azure DevOps Server 2020 or later.
A Git repository with an Azure DevOps remote. The AZD Pull Requests, AZD Pipelines and AZD Boards tool windows appear only in projects that have such a remote.
Optional: the Azure CLI (az) for Azure CLI sign-in, and Node.js 14 or later for the Azure Pipelines language server.

Install the plugin

Install AZD from the IDE

In the Settings dialog (Ctrl+Alt+S, macOS: ⌘ ,), select Plugins.
On the Marketplace tab, search for AZD.
Click Install, and restart the IDE if it asks you to.

Install AZD from the Marketplace website

Open the AZD page on JetBrains Marketplace.
Click the install button and select the running IDE.

Start the trial or activate a license

AZD is a paid plugin with a 10-day free trial. Start the trial or activate a license in Help | Register.

Buy or manage licenses on the AZD pricing page.

Connect to Azure DevOps

Sign in once per organization (Azure DevOps Services) or collection (Azure DevOps Server). You can sign in from any AZD tool window, from the Clone Repository dialog, or from Settings | Version Control | AZD.

Choose a sign-in method

Method	Works with	Use it when
Sign in with Microsoft	Azure DevOps Services	You sign in with a Microsoft Entra ID account. No token to create or renew.
Sign in with Azure CLI	Azure DevOps Services	Your organization blocks OAuth apps or is phasing out personal access tokens, and you use `az login`.
Personal access token	Azure DevOps Services and Azure DevOps Server	You connect to Azure DevOps Server, or you prefer a token with an expiry date.

Microsoft and Azure CLI sign-in sessions refresh on their own. If a sign-in error appears in a tool window, click Log in again…; see Renew a token.

The AZD tool windows appear only in a project with an Azure DevOps remote. Without one, sign in from Settings | Version Control | AZD (see below) or from the Clone Repository dialog.

Open the AZD Pull Requests, AZD Pipelines or AZD Boards tool window, for example from View | Tool Windows.
Check that the selector shows the right repository, and click Sign in with Microsoft.
In the Sign in with Microsoft dialog, choose the permissions to request, and click Continue:
- Full access (recommended): all features, including marking files as viewed in pull requests.
- Standard access: code, builds, pull requests and work items, but files cannot be marked as viewed.
Sign in to Microsoft Entra ID in the browser that opens.
When the browser shows Authentication Successful, return to the IDE.

When AZD knows the organization, for example when you sign in from a tool window of a project with an Azure DevOps remote, it adds an account for that organization. Otherwise, for example from the Clone Repository dialog, it discovers every organization your account can reach and adds one account per organization. To sign in from Settings instead, click + on the accounts page and select Sign in with Microsoft.

AZD gets its token from az account get-access-token, so the Azure CLI must be installed and signed in.

In a terminal, run az login.
In an AZD tool window, click Sign in with Azure CLI, or in Settings | Version Control | AZD click + and select Sign in with Azure CLI.

As with Microsoft sign-in, AZD adds an account for the organization of the repository. When it does not know the organization, for example in the Clone Repository dialog, it adds one account for each organization that your Azure CLI identity can reach.

AZD looks for az on the PATH and in the usual install locations. If it cannot find it, set the path in Settings | Version Control | AZD | Preferences, in the Azure CLI group, or click Detect.

Azure CLI group on the AZD Preferences page with the detected az path

If the Azure CLI session expires, AZD shows a notification. Run az login again, then retry.

Create a personal access token

A personal access token (PAT) works with both Azure DevOps Services and Azure DevOps Server. Create it in the Azure DevOps web portal.

Create a PAT

In Azure DevOps, open User settings | Personal access tokens and click New Token.
Azure DevOps Services only: in Organization, select All accessible organizations.
Select Custom defined scopes and grant these scopes:
- vso.build_execute
- vso.code_status
- vso.code_write
- vso.graph
- vso.identity
- vso.profile
- vso.project
- vso.test
- vso.threads_full
- vso.work_write
Click Create and copy the token. Azure DevOps shows it only once.
Treat the token like a password. Do not share it or commit it to source control.

What each scope is for

Scope	Name in the Azure DevOps portal	Used for
`vso.code_write`	Code (Read & write)	Cloning, pull requests and pushing changes
`vso.code_status`	Code (Status)	Pull request and build statuses
`vso.graph`	Graph (Read)	Finding users and groups
`vso.build_execute`	Build (Read & execute)	Running and watching pipelines
`vso.identity`	Identity (Read)	Reading user identities
`vso.project`	Project and Team (Read)	Reading projects and teams
`vso.threads_full`	Pull Request Threads (Read & write)	Pull request comments
`vso.profile`	User Profile (Read)	Your profile and avatar
`vso.work_write`	Work Items (Read & write)	Creating, editing and linking work items
`vso.test`	Test Management (Read)	Test results and test cases

In an AZD tool window, click Use token….
In Server, enter https://dev.azure.com.
Paste the token in Token. Generate… opens Microsoft's instructions for creating a token.
In Organization/Collection, enter the organization name, for example demo-org.
Click Log In.

Open Settings | Version Control | AZD.
Click + and select Sign in with Personal Access Token.
In the Add AZD Account dialog, fill in Server, Token and Organization/Collection, and click Log In.

If AZD reports missing scopes, create a new token with the scopes listed above for All accessible organizations.

Connect to Azure DevOps Server

Azure DevOps Server supports only personal access tokens. Microsoft and Azure CLI sign-in work only with Azure DevOps Services.

On your server, open User settings | Personal access tokens and create a token with the scopes listed above.
In an AZD tool window, click Use token…, or add an account in Settings | Version Control | AZD.
In Server, enter the server URL without the collection, for example https://ado.example.com. If the server runs under a tfs, azd, devops or azure virtual directory, include it, for example https://ado.example.com/tfs.
Paste the token in Token.
In Organization/Collection, enter the collection name, for example DefaultCollection.
Click Log In.

Manage accounts

All accounts are listed in Settings | Version Control | AZD.

AZD accounts page with an account and Clone git repositories using ssh selected

To add an account, click + and choose a sign-in method.
To remove an account, select it and click −.
To choose the account that AZD uses by default, select it and click Set as Default.
To renew an expired or revoked token, see Renew a token.
To switch the repository or account that the AZD tool windows use, see Choose the repository and account.

Each account shows its sign-in method after its name: [OAuth] for Microsoft sign-in, [Azure CLI] or [PAT].

AZD stores credentials in the IDE password storage. Accounts are not synchronized by Backup and Sync, so sign in again on each computer. If the IDE stores passwords in memory only, the accounts page shows a warning; see Credentials are not saved.

Renew a token

When a token expires or is revoked, the AZD tool windows show a sign-in error, and the account in Settings | Version Control | AZD shows Invalid access token.

Renew the token of an account

If the account uses a personal access token, create a new token; see Create a personal access token. If it uses the Azure CLI, run az login in a terminal.
In the AZD tool window, click Log in again… in the error message, or click Log in next to the account in Settings | Version Control | AZD.
For a personal access token, paste the new token in the Update AZD Account dialog and click Log In. For Microsoft sign-in, the Sign in with Microsoft dialog opens; see Sign in with Microsoft. For the Azure CLI, AZD gets a new token from az.

Open the AZD tool windows

AZD adds three tool windows to projects that have an Azure DevOps Git remote: AZD Pull Requests, AZD Pipelines and AZD Boards. Open them from View | Tool Windows or from the tool window bar.

You can also select Git | AZD | Show AZD Pull Requests.

Choose the repository and account

The AZD Pull Requests, AZD Pipelines and AZD Boards tool windows share one connection: one repository and one account. AZD connects on its own when the project has one Azure DevOps repository and you have a matching account, or when you connected before. Otherwise, the tool window shows a repository selector and an account selector.

Connect the AZD tool windows to a repository

Open an AZD tool window, for example View | Tool Windows | AZD Pipelines.
Select the repository in the repository selector.
Click the account selector and select an account. The same list offers the sign-in methods, and Renew Token for the selected account.
If you have no account for the organization or server of the repository, sign in with the buttons in the tool window; see Choose a sign-in method.
Click View Pull Requests, View Pipelines or View Work Items, depending on the tool window.

All three tool windows then show the selected repository. AZD remembers the choice and reconnects the next time you open the project.

To switch later, click ⋮ in the AZD Pull Requests tool window header and select Change Repository or Account…. This action is available only when the project has more than one Azure DevOps remote.

Open the welcome guide

Select Help | Show Welcome Guide to open the AZD Welcome tool window. It walks you through six steps: an overview, connecting to Azure DevOps, pull requests, pipelines, AI features, and resources.

02 October 2026