Registry /
azure / azure-mgmt-appconfiguration
Install & Compatibility
Where this runs
tested against v5.0.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 0.602s · 44.3MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 3.8s · import 0.556s · 45MB
43MB installed
● package 43MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
AppConfigurationManagementClient
✓ from azure.mgmt.appconfiguration import AppConfigurationManagementClient
DefaultAzureCredential
✓ from azure.identity import DefaultAzureCredential
Initializes the `AppConfigurationManagementClient` using `DefaultAzureCredential` for authentication and then lists all App Configuration stores within the specified Azure subscription. Ensure `AZURE_SUBSCRIPTION_ID` and authentication-related environment variables (`AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_SECRET`) are set.
import os
from azure.identity import DefaultAzureCredential
from azure.mgmt.appconfiguration import AppConfigurationManagementClient
# Set environment variables for authentication (Azure CLI, VS Code, environment variables)
# AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET or AZURE_FEDERATED_TOKEN_FILE
# AZURE_SUBSCRIPTION_ID
subscription_id = os.environ.get("AZURE_SUBSCRIPTION_ID", "")
if not subscription_id:
raise ValueError("AZURE_SUBSCRIPTION_ID is not set in environment variables.")
# Authenticate using DefaultAzureCredential
# This will try various methods like environment variables, managed identity, etc.
credential = DefaultAzureCredential()
# Create a client for App Configuration Management
client = AppConfigurationManagementClient(credential=credential, subscription_id=subscription_id)
# Example: List all App Configuration stores in the subscription
print("Listing App Configuration stores:")
for store in client.configuration_stores.list():
print(f" - {store.name} (Resource Group: {store.resource_group})")
print("Quickstart complete.")
Debug
Known issues
breakingStarting from version 4.0.0, the package primarily targets only the latest API version available on Azure and removes APIs of older versions. If your application relies on a specific, non-latest API version, you must pin the package to a previous released version (e.g., `<4.0.0`).fixReview your API usage. If you require an older API version, pin `azure-mgmt-appconfiguration` to a version prior to 4.0.0. Otherwise, update your code to use the latest API surface.
affects: 4.0.0 and later
breakingIn version 3.0.0, the operation `KeyValuesOperations.list_by_configuration_store` was removed, impacting users migrating from earlier versions who might have used this specific method.fixUpdate your code to use alternative methods for listing key values, such as `configuration_stores.list_key_values()` if available, or fetch key-values via the data plane SDK (`azure-appconfiguration`).
affects: 3.0.0 and later
breakingFor SDK versions 1.0.0b1 and newer, the credential system was completely revamped. Old authentication classes like `azure.common.credentials` or `msrestazure.azure_active_directory` are no longer supported. The `credential` parameter has also been renamed from `credentials`.fixMigrate your authentication code to use classes from the `azure-identity` library, such as `DefaultAzureCredential`, `ManagedIdentityCredential`, or `ClientSecretCredential`. Ensure the parameter name is `credential`.
affects: 1.0.0b1 and later
gotchaStoring sensitive information (secrets) directly in Azure App Configuration is not recommended. Instead, use Azure Key Vault to securely store secrets and then reference them from App Configuration. This provides hardware-level encryption and better secret management.fixIntegrate Azure Key Vault with App Configuration using Key Vault references. Configure your applications to resolve these references at runtime.
affects: All versions
gotchaWhen deploying applications to Azure services (like Azure Kubernetes Service, App Service, or Azure Functions), it's highly recommended to use Managed Identities for authenticating with App Configuration. This eliminates the need to explicitly manage connection strings or client secrets in your application or environment variables, enhancing security.fixEnable a Managed Identity for your Azure-hosted application and grant it the necessary roles (e.g., 'App Configuration Data Reader' or 'Contributor') on your App Configuration store. Use `ManagedIdentityCredential` or `DefaultAzureCredential` in your Python code.
affects: All versions
Upgrade
Version history
5.0.0latest on PyPI · released Jun 17, 2025
Audit
Dependencies
azure-identityrequiredRequired for Azure Active Directory token authentication.