Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Address VS800075 Error #1421

Open
kubilayverboom opened this issue Oct 21, 2024 · 0 comments
Open

[Feature Request] Address VS800075 Error #1421

kubilayverboom opened this issue Oct 21, 2024 · 0 comments
Labels
Feature Feature Work required.

Comments

@kubilayverboom
Copy link

Is your feature request related to a problem? Please describe.
I am using an Azure DevOps pipeline to standardize the deployment of new projects in Azure DevOps, utilizing the Azure DevOps CLI extension. While the project gets created and is visible in my organization, the pipeline throws the following error:

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

I have verified that the service connection has the correct privileges within the new project. Additionally, I unchecked the following settings based on suggestions from similar issues:

  • Limit job authorization scope to current project for non-release pipelines
  • Limit job authorization scope to current project for release pipelines

Despite these changes, the error persists.

Describe the solution you'd like
I would like a solution or guidance to prevent this error from occurring when creating new projects using the pipeline. If this requires a new feature or command in the Azure DevOps CLI extension, it should verify or synchronize permissions immediately after a project is created, ensuring the pipeline can access it without this error.

Additional context
I am using a service connection with the appropriate permissions, and the project is visible in the organization after creation. This issue appears to be related to either permission propagation delays or a missing configuration setting that isn't obvious from the current documentation. Any further troubleshooting steps or insights would be appreciated.

@kubilayverboom kubilayverboom added the Feature Feature Work required. label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature Work required.
Projects
None yet
Development

No branches or pull requests

1 participant