Azure Key Vault

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.

Available now One-click sync Encrypted transport

Sync to Azure Key Vault

Connected
DATABASE_URL
API_SECRET
STRIPE_KEY
Last syncedJust now
3 variables synced

Connect Azure Key Vault once, then stop copying values by hand

Sync targets live on the project. Pick the environment, pick where it deploys, and EnvManager pushes the same values every time they change.

EnvManager project integrations page showing enabled deployment sync targets

How to connect Azure Key Vault

Follow this flow and your variables are synced in minutes.

Create an app registration

With a client secret, and the Key Vault Secrets Officer role on the vault you want to sync into.

1

Validate the credentials

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.

2

Choose a prefix per environment

Optional. Two environments syncing into one vault need different prefixes, otherwise the second overwrites the first.

3

Sync

With one click from the project, per environment.

4

Azure Key Vault integration features

Everything needed to operate Azure Key Vault secrets from EnvManager.

One secret per variable

DATABASE_URL becomes a secret called DATABASE-URL. No JSON blob to unpack on the other side.

Built for secure automation

Names Key Vault accepts

Key Vault does not allow underscores in secret names, so we turn them into hyphens and say so in the dialog before you save.

Built for secure automation

Prefix per environment

Add a prefix like prod- or staging- and several environments can share one vault without getting in each other's way.

Built for secure automation

Removes what it added

Delete a variable here and the next sync deletes its secret from the vault. Secrets we never sent are left alone.

Built for secure automation

Secrets, variables or both

Choose per project whether secret variables, regular variables or both go to the vault.

Built for secure automation

Honest error messages

Wrong tenant or secret, missing role, wrong vault URL: the validate step tells you which one it is.

Built for secure automation

Ready to connect Azure Key Vault?

7-day free trial. Connect Azure Key Vault and sync your first variables in under 5 minutes.