4

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.

Shayki Abramczyk
  • 36,824
  • 16
  • 89
  • 114
markblue777
  • 829
  • 3
  • 13
  • 28

4 Answers4

3

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.

Picture 1 Picture 2 Picture 3

LoLo
  • 374
  • 2
  • 7
0

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.

enter image description here

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.

PatrickLu-MSFT
  • 49,478
  • 5
  • 35
  • 62
  • 3
    The Service Connection I created is not showing in that location. That is what I was saying in my question. Cheers – markblue777 Apr 11 '19 at 08:26
  • @markblue777 Did this only occurs on your specific release pipeline or all pipelines such as build pipeline. Have you try to enable the setting **Allow all pipelines to use this connection** option for the connection and try again. – PatrickLu-MSFT Apr 11 '19 at 08:34
  • 1
    On all pipelines I am getting this error. It is enabled for all pipelines. The service connection type i made was Azure Classic. I am thinking this might be the wrong type for the deploy type being used. Just confirming this theory – markblue777 Apr 11 '19 at 08:37
0

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

Ajay Sewradj
  • 43
  • 7
0

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 ¯\_(ツ)_/¯

enter image description here enter image description here

deadlydog
  • 22,611
  • 14
  • 112
  • 118