Azure DevOps Services · REST API, Azure CLI and pipelines · Checked October 24, 2026

Azure DevOps: "VS800075: The project with id '…' does not exist, or you do not have permission to access it."

Azure DevOps answers VS800075 when the identity that called cannot see the project, and it does not say whether the project is missing or only hidden from that identity. In public reports it is most often a pipeline reaching a feed or a repository in another project, whose build service has no access there, and next a user or service principal behind az devops, Terraform or a script that is not a member of the project.

The whole answer

As public reports from 2021 to October 2026 quote it, from the REST API, the Azure CLI (az devops, az repos), the Terraform provider and pipeline tasks that download or publish packages:

VS800075: The project with id 'vstfs:///Classification/TeamProject/<GUID>' does not exist, or you do not have permission to access it.

• In the JSON answer its typeKey is ProjectDoesNotExistException. The reports show it with HTTP 400, 403 or 404, depending on the call.
• Azure Artifacts tasks in a pipeline wrap it: An error occurred on the service. VS800075: …
• A call that needed a project and got none says The project with id 'No project was specified.'

Only a signed-in identity gets it. On October 24, with no token, dev.azure.com answered a missing project in a public organization, by name and by GUID, with HTTP 401 and TF400813 instead: what that one means.

Whose access

• A pipeline acts as its build service account: <project> Build Service (<organization>) when Limit job authorization scope to current project for non-release pipelines is on, otherwise Project Collection Build Service (<organization>) (Microsoft's job access tokens). The project-level account sees only its own project until another project lets it in.
• A user or service principal (a personal access token, az login, Terraform, a script) sees the projects it is a member of, through a group such as Readers or Contributors.

Give access

1. A pipeline reaching another project. In the other project, open Project settings → Permissions, find the build service account under Users (select Expand search if it does not show up), and allow View project-level information. Microsoft's example puts the account in a new group for this. Then give it what it uses there, for example Read on a repository.
2. An Azure Artifacts feed in another project. In the feed, open the gear (Feed settings) → Permissions → Add users/groups, add the build service account as Feed and Upstream Reader (Collaborator), or Feed Publisher (Contributor) to publish. Microsoft's feed permissions page adds that, for the project-level account and a feed in a different project, that project must grant it at least Edit project-level information.
3. A user or service principal. A project administrator adds it to a group of the project (Readers to read, Contributors to change things).
4. A service connection with workload identity federation. Microsoft's workload identity page lists VS800075 for a service connection whose identity is not in the project: on the service connection's page, open View access in the current organization → Member of and add it to a group such as Readers, or in Organization settings → Users, open the identity → Manage access and select the projects. An identity that is not in the organization at all gets TF401444 first.

Also check

• Which organization and project the call used. The GUID in the message is a project ID. With the Azure CLI, az devops configure --list shows the default organization and project that commands use when you do not pass --org and --project.
• A project that was just created. In a 2023 report, az devops project create sometimes ended with VS800075 although the project was created: Azure DevOps accepts the request and sets the project up afterwards, and reading it before that is done gives this answer. Wait, then read it again.

Azure DevOps pull requests in IntelliJ IDEA and Rider

Azure DevOps Pull Requests, a plugin by Lesstep for JetBrains IDEs 2024.1 or later and Android Studio, reads the organization, project and repository from your git remote and lists the pull requests that wait for your review in an IDE tool window, on Azure DevOps Services and on Azure DevOps Server. From version 1.0.35, when Azure DevOps answers VS800075, it names the project and says to check the project name in the git remote and the account's membership, instead of asking for another token. Public projects are read without a token. The review inbox is free; voting, commenting and completing are Pro, with a 30-day trial.

Get it on JetBrains Marketplace

Azure DevOps is a trademark of Microsoft Corporation; IntelliJ IDEA and Rider are trademarks of JetBrains s.r.o. This page is not affiliated with or endorsed by Microsoft or JetBrains.

More: TF200016: no project by that name · TF401019: the repository does not exist or you do not have permissions · TF401027: a missing Git permission · TF401444: the organization does not know the account yet · 日本語