Azure Key Vault Enterprise
Open Project → Vaults & Secrets, create a vault, and select Azure Key Vault.
Enter your vault's HTTPS URL, for example https://my-vault.vault.azure.net.
Authentication
| Method | Configuration |
|---|---|
| Default Azure credential | Uses the Azure SDK credential chain, including environment credentials, managed identity, or an existing Azure CLI login (az login). It does not open a browser to log in. |
| Interactive User Login | Signs in to Microsoft Entra ID in your system browser. Tenant ID and client ID are optional. No client secret or Azure CLI login is required. |
| Client secret | Enter the Microsoft Entra tenant ID, application (client) ID, and client secret. |
| Access token | Supply a token for Azure Key Vault without the Bearer prefix. Kreya does not refresh an explicitly supplied token. |
The URL, authentication fields, secret names, and versions support templates. For example,
{{ env.azure_client_secret }} can use a value from your user-specific environment data.
Keep credentials out of shared project files. An authentication configuration supplying a token must not depend on secrets from the same vault.
For your own Microsoft Entra app registration, add a Mobile and desktop applications redirect URI
matching the Callback URL and the delegated Azure Key Vault → user_impersonation permission. Enter that
application's client ID and, for a specific directory, its tenant ID. Leave the callback URL empty to use
http://localhost with an available port, or enter a loopback URL such as http://localhost:8400
to use a specific port. Leaving the client ID empty uses the Azure SDK development application; use your own registration
for production. The signed-in user must have access to the vault and your tenant may require admin consent.
Test connection first checks reachability without authenticating, then checks access to secret metadata. Secret reads need get permission. Discovery and the authenticated connection test also need list permission (for example, the Azure RBAC Key Vault Secrets User role). If listing is forbidden, Kreya shows a warning: manually mapped secrets can still work with get permission. Vault firewalls and private endpoints must also allow the connection.
Secret mappings
| Column | Description |
|---|---|
| Name | The name used in Kreya templates. |
| Secret name | The name of the secret in Azure Key Vault. |
| Version | Optional version ID. Leave empty to read the latest version. |
Enable Automatically discover secrets to list available secrets and create mappings automatically.
Discovery reads metadata only, skips disabled secrets, and follows pagination. Names such as api-key
become api_key in Kreya. Discovered mappings always read the latest version.
The shared 100-secret limit applies; use manual mappings for larger vaults or to pin versions.
Values are fetched when used and are not stored in the project file. Azure SDK credentials are cached in memory; Settings → Clear caches → Azure Key Vault sessions clears them.
Referencing secrets
See Referencing secrets for how to use configured secrets in templates and scripts.