Glimpse - Key Vault Vs App Configuration for App service
In this post, we are jsut going to see glimpse of comparison between Keyvaukt and App Configuration for App services references.
Why we are comparing these two?
Recently App Configuration references on App Service become Generally Available and it can complements Keyvault.
Let us consider a scenario that we need to have client-id and secret which will be used in an API call for authentication from Azure function app/ App service / Logic App standard, in a secure place.
So, Here we come to know 2 azure native services are as follows
- Azure Keyvault
- Azure App Configuration
Azure people(we) typically use keyvault to handle secrets in secure way whereas App Configuration also complements Azure Keyvault then which is better or in which scenario we can pick either of the one.
According to me,
We can go for keyvault
- when we need to handle secrets environment specific. Here, environment refers to, Dev, QA and Prod.
- when need of hardware-level encryption
- when granular level access required
- when need to perform certificate rotation
- When a data or secret which is common across all the environments, we can go for App Configuration which is central place to have secrets/configuration details.
You can use below references in Environment Variables section of App Service as below.
@Microsoft.KeyVault - @Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret) - App service retrieves "mysecret" value from "myvault"
@Microsoft.AppConfiguration - @Microsoft.AppConfiguration(Endpoint=https://myAppConfigStore.azconfig.io; Key=myAppConfigKey) - App service retrieves the value of key called myAppConfigKey from App Configuration.
Your thoughts are Welcome!
Comments
Post a Comment