How to create VSTS Service Endpoint using Azure Keyvault secrets

0
votes

Am working on VSTS CI&CD. For that, am trying to create “Azure Resource Manager” Service Endpoint as a VSTS Connection. But, here I don’t want give SPN credentials i.e. “Client Id and Client Secret” directly for making connection, in spite of that I need to pass SPN Credentials which are in Keyvault secrets saved in Azure keyvault. Is this possible, that the VSTS Service Endpoint creation using Azure Keyvault Secrets. If possible, please suggest me to “How to done it”

1
azureazure-devopsazure-keyvault

1 Answers

0
votes

Currently, VSTS can support the below list of service endpoints

  1. Azure Classic service connection
  2. Azure Resource Manager service connection
  3. Azure Service Bus service connection
  4. Bitbucket Cloud service enconnectiondpoint
  5. Chef service connection
  6. Docker Host service connection
  7. Docker Registry service connection
  8. External Git service connection
  9. Generic service connection
  10. GitHub service connection
  11. GitHub Enterprise service connection
  12. Jenkins service connection
  13. Kubernetes service connection
  14. npm service connection
  15. NuGet service connection
  16. Service Fabric service connection
  17. SSH service connection
  18. Subversion service connection
  19. Team Foundation Server / VSTS service connection
  20. Visual Studio App Center service connection

You need the ARM Service connection for at least connecting to the AzureKeyVault. I think you are bit worry to store the SPN (Client Id and client Secrets) in VSTS credentials. Actually, you don't need to worry about it. This credentials will be stored securely and can't be visible to other after it created.