App Configuration vs Key Vault (what to store)

App Configuration y Key Vault sirven roles complementarios en administrar settings para apps.

Azure App Configuration

Está diseñado para app settings, en pares clave-valor, y que sean no sensibles.

Características

  • labels para diferenciar entornos
  • feature flag management
  • rollbacks
  • dynamic refresh

Esto incluye

  • endpoints
  • feature flags
  • batch sizes
  • rerty counts
  • timeout values
  • display strings

Azure Key Vault

Está diseñado para datos sensibles.

Características

  • Encripta los datos at rest con HSM-backed protection
  • loggea cada op y se puede auditar
  • fuerza expiration policies
  • automated rotation
  • provee soft-delete con purge protection

Esto incluye

  • API keys
  • connection strings
  • passwords
  • keys criptograficas
  • certificados

Ejemplos

Setting type Service Example
Configuracion nonsensitive App Configuration (direct value) OpenAI:Endpoint
Feature toggles App Configuration (feature flag) EnableBatchProcessing
API keys and tokens Key Vault (via App Configuration reference) OpenAI:ApiKey
Connection strings Key Vault (via App Configuration reference) CosmosDB:ConnectionString
Certificates Key Vault (direct access) TLS certificates for HTTPS

Anti-patterns

  • Storing secrets directly in App Configuration: always use Key Vault references for values that grant access to resources
  • Using Key Vault for non-sensitive settings
  • Duplicating settings across both services without references
  • Embedding all configuration in application code