Managing Secrets in Azure Container Apps

Azure Container Apps allows you to define sensitive configuration values as secrets! You can define them directly in you container app, or refer to secrets stored in Azure Key Vault. In this video, I explain how secrets work, and how you can manage them using Bicep.

0:00 How secrets work in Azure Container Apps
1:30 Bicep template walkthrough
2:05 Defining secrets in your Container Apps Bicep code
3:16 Enabling your Container App to read secrets from Key Vault
5:04 Referring to Key Vault Secrets in Azure Container Apps
6:02 Using secrets as Container App environment variables
6:51 Portal walkthrough
7:44 Note on using mount volumes for secrets
8:28 Wrap up

Connect with me!

[grif.n]

What would be the recommendation between using container app secrets to reference key vault versus accessing key vault in code? Is it more secure to use container app secrets and use them as environment variables in code?

[SnickersPlayaS]

I've got a setup with secret retrieval from KV using href, works when KV ingress is public however without having KV open to public it fails to setup complaining its unable to fetch the secret. I've whitelisted the container apps environment IP and allowed it access to KV using user-assigned managed identity. Do you know what the problem could be/what im missing?
Thank you.

[juliasingsmythsofficial]

I didn't hear a word you said because you're so handsome

[markkizhnerman]

Any examples of mounting secrets as volumes? None of the documentation actually works.