AZD: FAQ and troubleshooting

The AZD tool windows are missing

The AZD Pull Requests, AZD Pipelines and AZD Boards tool windows appear only when the project has a Git remote that points to Azure DevOps, such as https://dev.azure.com/demo-org/demo-project/_git/demo-project. Check the remotes in Git | Manage Remotes. If the remote is there and the tool windows are still missing, see AZD does not recognize the Git remote.

AZD does not recognize the Git remote

AZD shows its tool windows only for a remote URL in one of these formats:

• Azure DevOps Services over HTTPS: https://dev.azure.com/<organization>/<project>/_git/<repository> or https://<organization>.visualstudio.com/<project>/_git/<repository>.

• Azure DevOps Services over SSH: git@ssh.dev.azure.com:v3/<organization>/<project>/<repository> or <organization>@vs-ssh.visualstudio.com:v3/<organization>/<project>/<repository>.

• Azure DevOps Server: https://<server>/<collection>/<project>/_git/<repository>, also with a virtual directory such as /tfs before the collection, or the matching ssh:// URL.

To recognize a remote that none of your accounts matches, AZD contacts the server once per IDE session. If the server was not reachable then, for example because the VPN was off, the tool windows stay hidden. To fix this, add an account for the organization or server in Settings | Version Control | AZD, or restart the IDE.

Sign-in fails

• Expired token: check the expiry date of the personal access token in Azure DevOps, and create a new one if needed. Then click Log in again… in the error message of the tool window, or click Log in next to the account in Settings | Version Control | AZD. See Renew a token.

  If AZD reports that the account already exists when you add the new token, renew the token of that account instead, or remove the account and add it again.

• Missing scopes or organizations: the token must have the required scopes and be created for All accessible organizations.

• Organization in the URL: enter the server URL in Server and the organization or collection in Organization/Collection. If the URL contains the organization or collection, AZD moves it to Organization/Collection; it rejects the URL only when it names a different organization or collection than that field.

• Azure DevOps Server: Microsoft and Azure CLI sign-in work only with Azure DevOps Services. Use a personal access token.

• Azure CLI: if AZD reports that az was not found, install the Azure CLI or set its path in Settings | Version Control | AZD | Preferences. If it reports that you are not signed in, run az login in a terminal and try again.

  If az login reports that no subscriptions were found, run az login --allow-no-subscriptions. If your Azure DevOps organization uses a different Microsoft Entra tenant than your default Azure CLI account, run az login --tenant <tenant-id>.

• Sign-in error in a tool window: click Log in again… in the error message.

• Account missing on another computer: AZD accounts are not synchronized by Backup and Sync. Sign in on each computer.

• Git asks for credentials: if the Git credential helper is enabled, Git operations do not use your AZD accounts. Sign in through the credential helper, or turn it off in your Git configuration. See Choose SSH or HTTPS.

Create a personal access token

Follow Create a personal access token. Create the token for All accessible organizations with the scopes listed there.

Marking a file as viewed fails

When AZD cannot mark a pull request file as viewed, it shows File viewed sync requires full access. Azure DevOps allows this only with full access.

• Sign in with Microsoft: remove the account, then sign in again and select Full access.

• Personal access token: create a token with Full access and renew the token in AZD.

Credentials are not saved

AZD keeps credentials in the IDE password storage. If your system blocks the native keychain, the IDE may keep passwords in memory only, and you must sign in after every restart. The AZD accounts page shows a warning in that case.

Requests fail behind a corporate proxy

• To send AZD requests through the IDE proxy, select Respect proxy configuration in Settings | Version Control | AZD | Preferences.

• If the proxy inspects TLS traffic and AZD reports certificate errors, select Accept untrusted SSL certificates on the same page. It affects only AZD connections.

• When a proxy interrupts a request, AZD retries it and keeps you signed in. It does not ask you for a new token in that case.

A view shows a message instead of content

The pipeline diagram, the metrics dashboards and the Kanban board use the IDE built-in browser (JCEF). If JCEF is not available, these views show a message instead of staying blank. Make sure the IDE runs on the bundled JetBrains Runtime, which includes JCEF. To check or switch it, press Ctrl+Shift+A (macOS: ⌘ ⇧ A) and run Choose Boot Java Runtime for the IDE….

Pipeline YAML has no completion

Completion and validation in pipeline files come from the Azure Pipelines language server, which needs Node.js 14 or later.

• Install Node.js, or set its path in Settings | Version Control | AZD | Pipeline Settings and click Validate Node.js.

• Check that Inject Azure DevOps YAML pipeline schema is selected on the same page.

• Check that the file counts as a pipeline file; see Which files are pipeline files.

The AzureDevOps task server type is missing

The task server integration needs the Issue Trackers plugin (formerly Task Management). Install it from JetBrains Marketplace; AZD works without it. See Use work items as IDE tasks.

Report a bug or request a feature

See AZD: Support. For an IDE error that comes from AZD, see Report an IDE error.

Licensing and trial

AZD is a paid plugin with a 10-day free trial. See Start the trial or activate a license.