Using Managed (System) Identities to access Azure Key Vault
  • 17 May 2022
  • 2 Minutes to read
  • Contributors
  • Comments
  • Dark
    Light
  • PDF

Using Managed (System) Identities to access Azure Key Vault

  • Comments
  • Dark
    Light
  • PDF

#ServerlessTips - Azure Logic Apps
Author: Kent Weare Integration MVP

A common challenge that integrators run into is managing secrets and subsequently, managing access to secrets. Azure Key Vault is a service that developers can use to store their secrets, keys and other sensitive data. However, there is still a challenge with accessing these secrets. If you are storing the credentials to access Key Vault in a non-secure manner, you have just pushed the problem to another area.

The good news is that we can use a capability called Managed Identities to establish trust between some Azure services. For example, we can have a Logic App that can have a Managed Identity associated with it which can then be added to Azure Key Vault RBAC roles. This establishes trust between our Logic App and Azure Key Vault.

Let’s now explore how we can get this setup.

  1. Click on Identity as part of your Logic App settings, subsequently turn the Status to On. After this is completed, you will see an Object ID populated which is essentially creating an identity for your Logic App within Azure AD. Copy this value, it will allow us to assign permissions to our Logic App in a subsequent step.

Click on Azure role assignments to continue.
1-Identity

  1. Click on Add role assignment followed by selecting the appropriate Subscription. From there select the appropriate Scope, Subscription, Resource (your keyvault instance) and the appropriate Role. In this case we will select Key Vault Secrets User which will allow us to extract secrets contents but not modify.

2-role(1)

  1. Repeat this step to include Key Vault Reader
  2. After we click Save we should see the result.

3-result(4)

  1. Next up, we need to assign an Access Policy on our Key Vault instance and assign access to the Managed Identity that we just created. Find your Key Vault in Azure Portal. Click on Access policies and then Add Access Policy.

3b-AccessPolicy

  1. We can use the Secret Management template to help accelerate completing this task. When it comes to Secret permissions, we will reduce all access to just Get and List. Lastly, we will find our Managed Service principal that we created in step 1. Click Add and Save to continue.

3c-AddPolicy

  1. We can now edit our Logic App and add an Azure Key Vault action to our canvas. Instead of signing in with our credentials, we will click on Connect with managed identity.

4-connect

  1. Specify a Connection name of your choosing and type in the name of your Vault. Click Create to continue.

5-VaultName

  1. Select Name of the secret to match the secret that you want to extract.

5b-secretname

  1. We can now add a Compose action where we can write out the Azure Key Vault secret value to ensure our process works.

Note: Whenever using sensitive information in Logic Apps, ensure that you use the Secure Inputs/Outputs feature to avoid secrets leaking into your run history.
6-testing(1)

  1. Test your Logic App to ensure your secret is obtained successfully.

Conclusion

In this post, we discussed how we can use Managed System identities when accessing Azure services like Key Vault. This allows organizations to securely connect to Azure resources without there being a tie to an individual’s credentials/account.

Logic Apps-2


Was this article helpful?