Skip to main content

Azure Key Vault

Enterprise Feature

This feature is available exclusively in the Enterprise edition of the Radicalbit AI Gateway. Contact sales for licensing information.

This plugin enables the gateway to resolve !secret references from Azure Key Vault instead of a static secrets.yaml file.

Each time the gateway loads the backend, the plugin reads every secret in scope from the configured vault and resolves every !secret KEY reference from what it read. The gateway loads the backend when it registers a project's routes, when it validates a configuration, and on every request from the Secrets section. Nothing is cached between loads.

Enabling the Plugin​

export ENABLED_PLUGINS="azure_keyvault"

No secrets.yaml is needed when this plugin is active.

Environment Variables​

VariableRequiredDefaultDescription
AZURE_KEYVAULT_URLYes—Vault URL, e.g. https://myvault.vault.azure.net/
AZURE_TENANT_IDNo—Service Principal tenant ID
AZURE_CLIENT_IDNo—Service Principal client ID
AZURE_CLIENT_SECRETNo—Service Principal client secret
AZURE_KEYVAULT_SECRET_PREFIXNo—Only load secrets whose name starts with this prefix

Authentication Methods​

Service Principal (recommended for CI/CD and non-Azure environments):

export AZURE_KEYVAULT_URL=https://myvault.vault.azure.net/
export AZURE_TENANT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
export AZURE_CLIENT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
export AZURE_CLIENT_SECRET=your-client-secret

Managed Identity / Default credential chain (preferred for Azure-hosted workloads):

export AZURE_KEYVAULT_URL=https://myvault.vault.azure.net/
# No credentials needed; azure-identity uses DefaultAzureCredential chain
# (Managed Identity, Azure CLI, Workload Identity, etc.)

Secret Naming​

Azure Key Vault secret names may only contain alphanumeric characters and hyphens. Config references must use the exact name as it appears in the vault:

credentials:
api_key: !secret OPENAI-API-KEY
warning

Underscores (_) are not allowed in Azure Key Vault secret names. Use hyphens (-) instead. For example, name your secret OPENAI-API-KEY, not OPENAI_API_KEY.

Prefix Filtering​

When AZURE_KEYVAULT_SECRET_PREFIX is set, only secrets whose name starts with the given prefix are loaded. Useful in shared vaults:

export AZURE_KEYVAULT_SECRET_PREFIX=gateway-

The prefix limits which secret values are read. The vault's secret list is still read in full. Every load reads the secret value of each secret in scope, including every request from the Secrets section. In a vault that holds many secrets unrelated to the gateway, set a prefix to keep that cost down. A secret outside the prefix is not loaded at all, so a !secret reference to it does not resolve.

Dependencies​

  • azure-keyvault-secrets==4.9.0 — installed automatically from requirements.txt when the plugin is enabled
  • azure-identity==1.21.0 — installed automatically from requirements.txt when the plugin is enabled