Reputation: 879
I have setup a Service Connections within Azure DevOps to my Azure Subscription. It uses a certificate to connect. When I create a new pipeline and select the task Azure App Service Deploy
.
In the drop down box for Azure Subscription I see nothing under Available Azure Service Connections, but I see my various Azure Subs under Available Azure Subscriptions.
Anyone Know what this could be? Is there some permission I am missing?
I have been looking about online and cannot really see anything.
Upvotes: 5
Views: 16758
Reputation: 71
If Azure Devops does not list your Azure suscription this is the way to get the verify working for the service connection and get a deployment ok:
Do the steps described in this link:
After that you can deploy sucessfully using that service connection.
Upvotes: 0
Reputation: 24374
We had this same issue, and it turns out you can't use service connections that are scoped to the Management Group
level in the classic release pipeline. It seems to work fine in a YAML pipeline though ¯\_(ツ)_/¯
Upvotes: 0
Reputation: 53
We had the same issue with the Service connection not showing up.
We had 2 projects configured in Azure Devops and each project had a service connection defined with the same name. It turned out that Azure Devops couldn't handle the duplicate name. We renamed one and everything was fine again
Upvotes: 0
Reputation: 374
You probably need to run your agent on a different type of virtual machine, please see Picture 1 below.
Try selecting a different OS and add a new task based on your selected vm. Also note that your service connection may not be available for the selected task as you can see in Picture 2 and Picture 3.
*Assuming you have already enabled pipeline permissions from the project settings in your repo.
Hope it helps.
Upvotes: 3
Reputation: 51073
If you are talking about below in the UI, select the connection name you assigned in the Azure subscription (or the equivalent connection name) setting of your pipeline.
Next you must authorize the service connection. To do this, use one of the following techniques:
If you want to authorize any pipeline to use the service connection, go to Azure Pipelines, open the Settings page, select Service connections, and enable the setting Allow all pipelines to use this connection option for the connection.
If you want to authorize a service connection for a specific pipeline, open the pipeline by selecting Edit and queue a build manually. You will see a resource authorization error and a "Authorize resources" action on the error. Choose this action to explicitly add the pipeline as an authorized user of the service connection.
Upvotes: 0