You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: