Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Prepare applications for Azure deployment by generating infrastructure code, Dockerfiles, and config files.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/services/container-apps/environment.md
1# Container Apps Environment Variables23## Standard Environment Variables45```bicep6env: [7{8name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'9value: applicationInsights.properties.ConnectionString10}11{12name: 'AZURE_CLIENT_ID'13value: managedIdentity.properties.clientId14}15]16```1718## Secret References (Key Vault)1920Use secrets for sensitive values:2122```bicep23configuration: {24secrets: [25{26name: 'database-url'27keyVaultUrl: 'https://myvault.vault.azure.net/secrets/database-url'28identity: managedIdentity.id29}30]31}3233template: {34containers: [35{36env: [37{38name: 'DATABASE_URL'39secretRef: 'database-url'40}41]42}43]44}45```4647## Common Variables4849| Variable | Source | Notes |50|----------|--------|-------|51| `APPLICATIONINSIGHTS_CONNECTION_STRING` | App Insights | Telemetry |52| `AZURE_CLIENT_ID` | Managed Identity | SDK auth |53| `DATABASE_URL` | Key Vault secret | Connection string |54| `REDIS_URL` | Key Vault secret | Cache connection |5556## Best Practices5758- Never hardcode secrets in Bicep59- Use Key Vault references for all sensitive values60- Use Managed Identity for authentication61- Set `AZURE_CLIENT_ID` for SDK-based auth62