Microsoft Azure Azure App Configuration Management Client
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdoauth217 EndpointsREST
For Agents
Provision and manage Azure App Configuration stores, rotate their access keys, and read individual key-values via the management plane.
Use for: List all App Configuration stores in subscription 1111-2222-3333-4444, Get the details of App Configuration store 'contoso-config' in resource group 'rg-prod', Regenerate the primary access key on store 'contoso-config', Check whether the App Configuration store name 'contoso-config' is available
Not supported: Does not perform high-volume data-plane reads or writes against key-values, manage feature flag rollouts, or integrate with Azure Key Vault directly — use only for App Configuration store lifecycle and access key management.
Jentic publishes the only available OpenAPI specification for Azure App Configuration Management Client, keeping it validated and agent-ready. This API manages Azure App Configuration store resources at the control plane: create, list, retrieve, and delete configuration stores, list and regenerate access keys, and read or list specific key-values held in a store. It is the surface used to provision the centralised configuration service that applications then read from at runtime.
Install Jentic One Beta
Connect the Azure App Configuration Management Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure App Configuration Management Client, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Azure App Configuration Management Client API.
Create, list, get, and delete App Configuration stores in a subscription
List access keys for a configuration store
Regenerate a primary or secondary access key on demand
Read a specific key-value held in a store via the management plane
Check whether a proposed configuration store name is available
List operations exposed by Microsoft.AppConfiguration
Use Cases
Patterns agents use Azure App Configuration Management Client API for, with concrete tasks.
★ Configuration Store Provisioning
Platform teams provision an App Configuration store per environment via PUT on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}. Once provisioned, apps connect using the access keys returned by the ListKeys endpoint. The lifecycle (create, list, delete) is fully scriptable so environment teardown leaves no orphan stores.
Provision App Configuration store 'contoso-config' in resource group 'rg-prod' in westeurope and return the connection string from ListKeys
Quarterly Access Key Rotation
Compliance schedules dictate access key rotation on App Configuration stores every 90 days. POST /service/{configStoreName}/RegenerateKey rotates the primary or secondary key in place, and ListKeys returns the new value so deployment pipelines can update consumers without downtime if they are configured for dual-key roll.
Regenerate the secondary key on store 'contoso-config', update the consuming app's secret reference, then regenerate the primary
Centralised Feature Flag Inspection
On-call engineers triaging an incident often need to read the current value of a single feature flag without waiting for the runtime. POST /service/{configStoreName}/listKeyValue retrieves a single key-value via the management plane, bypassing the data plane endpoint when the issue is configuration-driven.
Read the key-value 'feature-flag-checkout' from store 'contoso-config' and return its value and label
Agent-Driven Configuration Store Audits
An AI agent running quarterly platform audits can list every App Configuration store in a subscription, check its SKU and location, and flag stores that should be rotated or decommissioned. Through Jentic, intent search returns the right list, get, and ListKeys operations; the Azure OAuth token never leaves the credential vault.
Search Jentic for 'list Azure App Configuration stores', execute against the production subscription, and emit a CSV of name, SKU, and location
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for azure app configuration management client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AppConfiguration/configurationStores
List configuration stores in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores
List stores in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}
Get a configuration store
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/ListKeys
List access keys
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/RegenerateKey
Regenerate an access key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/listKeyValue
List a specific key-value
POST
/subscriptions/{subscriptionId}/providers/Microsoft.AppConfiguration/checkNameAvailability
Check store name availability
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AppConfiguration/configurationStores
List configuration stores in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores
List stores in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}
Get a configuration store
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/ListKeys
List access keys
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/RegenerateKey
Regenerate an access key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/listKeyValue
List a specific key-value
POST
/subscriptions/{subscriptionId}/providers/Microsoft.AppConfiguration/checkNameAvailability
Check store name availability
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure Active Directory OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; the agent calls Microsoft.AppConfiguration with a short-lived scoped token. Returned access keys can also be stored back into the vault rather than the agent context.
Intent-based discovery
Agents search by intent (e.g., 'rotate Azure App Configuration keys') and Jentic returns the matching App Configuration operation with its input schema, so the agent does not need to know the long Microsoft.AppConfiguration path layout.
Time to first call
Direct ARM integration: 1-3 days for AAD app registration, token acquisition, retry/throttling, and async lifecycle handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure App Configuration Management Client API through Jentic.
Why is there no official OpenAPI spec for Azure App Configuration Management Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure App Configuration Management Client via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Azure App Configuration Management Client use?
The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD app secret is held in the MAXsystem vault and exchanged for a short-lived bearer token at execution time, so agents never see the raw secret.
Can I rotate App Configuration access keys with this API?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/RegenerateKey rotates the primary or secondary key in place. Pair it with ListKeys to retrieve the new value for downstream consumers.
How do I read a specific feature flag value through the management plane?
Call POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/listKeyValue with the key and label. This is useful for ad-hoc inspection during incidents without standing up the data plane SDK.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling. Key regeneration and listKeyValue calls are subject to tighter limits because they touch secret material. Honour HTTP 429 Retry-After values and avoid scripting tight loops over RegenerateKey.
How do I provision an App Configuration store and retrieve its connection string through Jentic?
Run pip install jentic, then search Jentic with 'create Azure App Configuration store'. Jentic returns the PUT configurationStores endpoint and the ListKeys endpoint with their schemas. Execute create, then ListKeys to obtain the connection string; the OAuth token is resolved from the vault automatically.
GET STARTED