az-appconfig
Manage Azure App Configuration resources
TLDR
Create an App Configuration
Delete a specific App Configuration
List all App Configurations under the current subscription
List all App Configurations under a specific resource group
Show properties of an App Configuration
Update a specific App Configuration
SYNOPSIS
az appconfig [@{path_to_file}] [create|delete|export|import|list|revision|show|update | kv delete|import|list|list-revisions|restore|set|set-key|show | featureflag delete|list|set|show] [options]
PARAMETERS
--debug
Increase logging verbosity to show all debug logs.
--help -h
Show this help message and exit.
--only-show-errors
Only show errors, suppressing warnings.
--output -o
Output format: json|jsonc|table|tsv|yaml.
--query
JMESPath query string to customize output.
--subscription
Name or ID of Azure subscription.
--verbose
Increase logging verbosity.
--name -n
Name of the app configuration store (required for most subcommands).
--resource-group -g
Name of the resource group.
create
Create an app configuration store.
delete
Delete an app configuration store.
list
List app configuration stores.
show
Get details of an app configuration store.
update
Update an app configuration store.
kv set
Set a key-value pair.
kv delete
Delete a key-value pair.
kv list
List key-value pairs.
featureflag set
Set a feature flag.
import
Import key-values from file or URI.
export
Export key-values to file or URI.
DESCRIPTION
The az appconfig command is part of the Azure CLI, a cross-platform toolset for managing Azure resources. Azure App Configuration is a fully managed service for storing hierarchical configuration data, feature flags, and settings centrally across applications, environments, and teams.
This command group enables creation, deletion, listing, updating, and querying of App Configuration stores. It supports key-value (KV) operations like set, delete, import, and export; feature flag management; and revision tracking. Common use cases include CI/CD integration for dynamic config updates, reducing app redeploys, and securing sensitive data with vaults integration.
Operations respect labels for environment-specific configs (e.g., dev/prod), locking to prevent overwrites, and expiration for temporary values. Authentication uses Azure CLI login, service principals, or managed identities. Ideal for microservices, .NET, Java, Node.js apps leveraging SDKs or REST APIs alongside CLI automation.
Requires Azure CLI 2.1.0+ with appconfig extension implicitly available in recent versions.
CAVEATS
Requires Azure CLI login and appropriate RBAC permissions (e.g., App Configuration Data Owner). Some operations like import/export support specific formats (JSON, YAML, .NET properties). Store names must be globally unique and 3-50 lowercase chars.
AUTHENTICATION
Uses az login; supports AAD, MSI, service principals. Endpoint: https://management.azure.com.
EXAMPLES
az appconfig create --name myconfig --resource-group myRG --location eastus --sku free
az appconfig kv set --name myconfig --key mykey --value 'hello' --label prod
HISTORY
Introduced in Azure CLI 2.4.0 (2020) alongside public preview of App Configuration service. Evolved with feature flags support in 2.20.0+ and enhanced KV ops. Actively maintained by Microsoft for Azure DevOps integration.


