Azure naming · Microsoft.AppConfiguration/configurationStores

appcs App Configuration store

Central configuration store (<name>.azconfig.io).

Naming constraints

CAF abbreviationappcs
Resource typeMicrosoft.AppConfiguration/configurationStores
Length5–50 characters
CaseMixed case
Allowed charactersAlphanumerics and hyphens. Can't start or end with a hyphen or contain more than two hyphens in a row.
Uniqueness Global
SeparatorHyphen

Source: Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviation from the Cloud Adoption Framework.

Example & copy-ready

A worked name for workload app, env prod, region weu, instance 001.

Example name
appcs-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^(?=.{5,50}$)(?!.*---)[A-Za-z0-9][A-Za-z0-9-]*[A-Za-z0-9]$
Bicep naming expression
var name = take('appcs-${workload}-${env}-${region}-${instance}', 50)
Terraform local
locals {
  name = substr(join("-", compact(["appcs", var.workload, var.env, var.region, var.instance])), 0, 50)
}

Azure Policy can't evaluate regular expressions, so a policy can check the appcs prefix but not the full format. Run the regex in your pipeline, or audit existing names on a schedule.

Uniqueness scope

Globally unique across all of Azure — the name backs a public DNS label, so a clash with any other tenant's resource fails the deployment. Build in enough entropy (org/region/instance) to avoid collisions.

Open in the name generator