Create an app registration
With a client secret, and the Key Vault Secrets Officer role on the vault you want to sync into.
Azure Key Vault Integration
Connect an app registration and we push each variable into your Key Vault as its own secret. Your services keep reading from Key Vault like they do today, we only take over the part where someone has to keep the values up to date.
Sync targets live on the project. Pick the environment, pick where it deploys, and EnvManager pushes the same values every time they change.


Follow this flow and your variables are synced in minutes.
With a client secret, and the Key Vault Secrets Officer role on the vault you want to sync into.
Paste the tenant ID, client ID, client secret and vault URL. We check that we can really reach the vault before we let you connect.
Optional. Two environments syncing into one vault need different prefixes, otherwise the second overwrites the first.
With one click from the project, per environment.
Everything needed to operate Azure Key Vault secrets from EnvManager.
DATABASE_URL becomes a secret called DATABASE-URL. No JSON blob to unpack on the other side.
Key Vault does not allow underscores in secret names, so we turn them into hyphens and say so in the dialog before you save.
Add a prefix like prod- or staging- and several environments can share one vault without getting in each other's way.
Delete a variable here and the next sync deletes its secret from the vault. Secrets we never sent are left alone.
Choose per project whether secret variables, regular variables or both go to the vault.
Wrong tenant or secret, missing role, wrong vault URL: the validate step tells you which one it is.
7-day free trial. Connect Azure Key Vault and sync your first variables in under 5 minutes.