![\"\"](\"https:\/\/www.flip-design.de\/wp-content\/uploads\/2021\/12\/image-14.png\")
<\/a><\/figure>\n\n\n\nNext, you need to create a service connection to your Azure tenant:<\/p>\n\n\n\n Select Azure Resource Manager<\/p>\n\n\n\n Select service principal<\/p>\n\n\n\n Select your subscription and the Resource Group where the KeyVault is stored<\/p>\n\n\n\n After creating your Service Principal, you can get the name of it by clicking to the Manage link<\/p>\n\n\n\n After clicking at ServiePrincipal, you will get the name of it, and your can add the Access Policy:<\/p>\n\n\n\n Select Get and List to get the Secrets and the content<\/p>\n\n\n\n Add your Service Principal which was created by DevOps<\/p>\n\n\n\n Don\u2019t forget to click Save. Next, back to Azure DevOps and refer to Library. Here you can add a new variable group which uses your KeyVault.<\/p>\n\n\n\n You need click to Authorize to enable the connection. Next, you must go to your pipeline variables and add the newly created library<\/p>\n\n\n\n Inside your tasks you can use these variables. If your passwords contain some special characters, please put them into single quotes.<\/p>\n\n\n\n By viewing the results, you can see the using of the KeyVault<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" The most DevOps pipelines use variables to store credentials and other variables. With DevOps you have the possibility to hide\/encrypt data, but in an enterprise environment mostly KeyVaults are in use to store the sensitive data in a central store … Continue reading <\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n