Azure App Configuration
What it is
Azure App Configuration is a managed central store for application settings and feature flags. It keeps configuration outside an application’s deployed code, so multiple application instances can use the same named settings.
Think of a restaurant’s shared operations board: today’s delivery cutoff, the “new checkout” switch, and each branch’s opening settings belong on the board—not copied into every cashier’s instruction booklet.
Why it exists
When settings are scattered across code files, servers, and deployment pipelines, a small change can become hard to trace. App Configuration gives Northwind one place to manage ordinary settings by environment, geography, or application version.
Key ideas
- A key-value setting stores a named configuration value, such as
Checkout:MaxItems=100. - A label lets the same key have variants, for example
Production,Test, or a regional label. A label is an organizational selector, not access control. - A feature flag lets an application turn a feature on for a chosen audience or environment without changing the deployed code. The application must still implement safe behavior for both on and off states.
- Client libraries and providers load settings into supported applications. A configuration update can be refreshed without redeploying or restarting when the application is built to refresh it.
- App Configuration encrypts stored values and supports managed identities, but it complements—not replaces—Key Vault for secrets.
Northwind example
Luis keeps Checkout:DeliveryWindowMinutes and the NewRecommendations feature flag in App Configuration. The production label gives customers a 30-minute delivery window, while test uses five minutes. Priya can approve a gradual feature rollout without embedding a secret or production-only value in the release package. The database password remains in Key Vault, not beside the feature flag.
App Configuration versus Key Vault
| Store | Best for |
|---|---|
| App Configuration | Non-secret settings and feature flags that applications need to read and organize. |
| [[key-vault | Key Vault]] |
A setting may contain a reference to a secret, but access to the configuration store does not automatically grant access to the secret itself. Design and test both permission paths.
Common confusion
- A feature flag changes application behavior only if the application checks it. It is not a deployment rollback mechanism by itself.
- Labels organize configuration; they do not stop an authorized reader from seeing another label unless access design does so.
- Central configuration reduces drift but does not make an unsafe value safe. Review, test, and audit changes.
Related
key-vault · key-vault-secrets · app-service · azure-functions · deployment · northwind-traders-case-study
Sources and re-audit
- Microsoft Learn — What is Azure App Configuration?, checked 2026-09-16.