Revision history [back]

There could be several reasons why Azure DevOps Service Connections are not visible during the new release pipeline setup:

1. Lack of permissions: The user creating the pipeline may not have the necessary permissions to view or access the Service Connections.

2. Inconsistent Organization: The Service Connections may exist in a different organization or project than the one where the pipeline is being set up.

3. Filter settings: The filter settings on the Service Connection tab may be preventing certain connections from being visible.

4. Incorrect Configuration: The Service Connection configuration may be incorrect or incomplete, causing it to not be visible in the new release pipeline setup.

5. Deprecated Connections: The Service Connection may be deprecated or no longer supported, leading it to be hidden during pipeline setup.