Manage Azure App Configuration with Python

Wraps the Azure App Configuration SDK for Python (pip install azure-appconfiguration) for centralized configuration management, feature flags, and dynamic settings. It authenticates via a connection string (AzureAppConfigurationClient.from_connection_string) or Entra ID (AzureAppConfigurationClient(base_url=..., credential=DefaultAzureCredential())), reading the endpoint or connection string from AZURE_APPCONFIGURATION_CONNECTION_STRING/AZURE_APPCONFIGURATION_ENDPOINT.

from azure.appconfiguration import AzureAppConfigurationClient
from azure.identity import DefaultAzureCredential

client = AzureAppConfigurationClient(
    base_url=os.environ["AZURE_APPCONFIGURATION_ENDPOINT"],
    credential=DefaultAzureCredential()
)

It covers the full settings lifecycle: get_configuration_setting (optionally scoped by a label for environment-specific values), set_configuration_setting (with key, value, label, content type, and tags via a ConfigurationSetting object), delete_configuration_setting, and list_configuration_settings filtered by key prefix (key_filter="app:settings:*") or by label_filter. Feature flags are stored as configuration settings with a .appconfig.featureflag/<name> key and the application/vnd.microsoft.appconfig.ff+json content type, set/read/listed the same way as regular settings, with the flag's enabled state parsed from its JSON value. It supports locking a setting read-only (set_read_only) to prevent accidental changes, creating a point-in-time snapshot of settings matching a filter (begin_create_snapshot, an async long-running operation) and listing settings from a named snapshot, and a fully async client (azure.appconfiguration.aio) mirroring the sync API with await/close() calls.

It documents the client's core operations (get/set/delete/list a setting, list snapshots, lock/unlock read-only, create a snapshot) and stated best practices: use labels for environment separation, use key prefixes for logical grouping, make production settings read-only, create snapshots before deployments for rollback, prefer Entra ID over connection strings in production, refresh settings periodically in long-running apps, and use feature flags for gradual rollouts and A/B testing.

Use it for centralized configuration management, feature-flag control, or dynamic settings in a Python application backed by Azure App Configuration. As with any skill output, verify results against the current environment, and stop to ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Input is an Azure App Configuration connection string or Entra ID credential/endpoint, plus setting keys, values, labels, and filters. Output is a retrieved, created, updated, or deleted configuration setting or feature flag, a filtered list of settings, or a named point-in-time snapshot.

Uses the azure-appconfiguration Python SDK and azure-identity for Entra ID authentication, with a separate async client namespace for asyncio-based applications, and stores feature flags in the same App Configuration store using Microsoft's standard feature-flag content type.

Python developers centralizing application configuration and feature flags on Azure who need settings, environment labels, snapshots, and read-only locks managed from code.