There could be several reasons why Azure DevOps Service Connections are not visible during the new release pipeline setup:
Lack of permissions: The user creating the pipeline may not have the necessary permissions to view or access the Service Connections.
Inconsistent Organization: The Service Connections may exist in a different organization or project than the one where the pipeline is being set up.
Filter settings: The filter settings on the Service Connection tab may be preventing certain connections from being visible.
Incorrect Configuration: The Service Connection configuration may be incorrect or incomplete, causing it to not be visible in the new release pipeline setup.
Deprecated Connections: The Service Connection may be deprecated or no longer supported, leading it to be hidden during pipeline setup.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2022-12-12 11:00:00 +0000
Seen: 7 times
Last updated: Apr 09 '22
What is the process for uploading files to Azure Storage using Terraform in Azure Pipeline?
Why isn't my CodePipeline pipeline triggered by my CloudWatch Event rule?
How to verify plan alterations while using Terraform in a pipeline?
What occurs precisely when a Skylake CPU makes an incorrect prediction regarding a branch?
How can a pipeline trigger from a different project be added in Azure?
What are the steps to establish CD CI for nodejs and deploy it to Azure?