Pipeline Level Access Control for Service Connection in Azure DevOps - Classic Editor Pipelines
I have a SSH service connection created in Azure DevOps. My account has enabled 'New service connections experience' preview feature and able to see new security features for service connections. It appears that we can enable security so that certain YAML pipeline(s) are able to use service connection.However, I do not see similar feature for Classic Editor pipeline.Can I get some suggestions on how I can achieve something similar for Classic Editor?
Example : Below details are under same ADO organization and project with same level of user(user/admin/reader) level access
Service Connection name : test-ssh-connection Classic Editor Pipelines Created: 1) pipeline1 - this can use service connection 2) pipeline2 - we want to restrict service connection so that this pipeline is not able to use service connection.
It appears that we can enable security so that certain YAML pipeline(s) are able to use service connection.However, I do not see similar feature for Classic Editor pipeline.Can I get some suggestions on how I can achieve something similar for Classic Editor?
Sorry but a similar experience for Classic pipeline is not supported for now. Just as the document states, pipeline permissions are only for Yaml pipelines while user permissions are for Classic pipelines.
For Classic pipelines, if the account someone uses to sign in Web portal doesn't have the user permission, then the pipeline created by him can't access the service connection:
Though what you want is not supported, I agree with you that it would be better if the pipeline permissions feature can support Classic pipelines. So my suggestion is to add your request for this feature on our UserVoice site. Thank you for helping us build a better Azure DevOps!
- How to Migrate TFVS project to Azure Git Repos from different Organization
- How to branch from non-default branch in Azure DevOps GitHub.com integration?
- Can't provide NuGet package source credentials to Azure Function
- Azure Pipelines: How to make a task dependent on a previous task?
- How to use multiple environments from one Azure pipeline?
- Azure DevOps pipeline continues to run despite removing schedule
- How to prevent creating a new branch of a certain branch
- Azure Active Directory App service Principal create new client secret
- Azure Devops Pipeline - Use Microsoft Visual Studio Installer Projects
- Azure DevOps yaml - Get current date with MMM (month short name)
- Accessing azure custom field using OData query
- build validation and status check policy on branch for Python code
- How to connect to Azure VM Windows Admin Center from Azure DevOps without enabling PSRemoting in VM
- Bash Task in Azure DevOps not able to recognize variable in set in Classic Release pipeline
- Is it possible to have a link to raw content of file in Azure DevOps
- USING RUNTIME VARIABLES IN AZURE YAML CHECKOUT
- How to configure Dependabot on Azure DevOps to create only one PR for minor/patch updates
- Pass an array of string to a powershell script from a yaml template
- Repository permanency between stages in an Azure DevOps pipeline
- Deploying Container App with Arm Template via Azure Devops: UNAUTHORIZED: authentication required
- NU1301: Unable to load the service index for source, even after setting up Personal Access Token
- How to deploy files to a server
- Azure Pipelines: git lfs not known with explicit declaration but UI config
- Comparison of string parameters always return false in Azure DevOps 2022
- Create Azure Devops pipeline without code checkout
- Increment Azure Pipelines version number with commits
- Azure Devops odata query returns UserEmail:Unknown
- In Azure Dev Ops, given a branch name, how I do I get the corresponding Pull Request (if one exists)
- Terraform Initialize Error on Azure Devops release pipeline
- How to use an Azure Devops Release task to execute a Azure Pipeline