Using Azure Key Vault from Bicep
I have previously written a post on how to use Azure Key Vault with GitHub Actions, and this time I want to show you have to use Key Vault with Bicep deployments in Azure. The reason behind using Key Vault is to avoid having any passwords or secrets stored in templates. Using Key Vault, I can reference a secret that the deployment will look up at deployment time and not display in any log files. Another benefit of using Key Vaults is that the person who deploys the resources does not need to know the password for the resource but only the reference to the Key Vault. Deploying resources using Key Vaults dramatically increases the security and, at the same time, eases the deployments.