Azure naming · Microsoft.DocumentDB/databaseAccounts

cosno Cosmos DB account

Azure Cosmos DB for NoSQL account (<name>.documents.azure.com). CAF uses cosmon, coscas, costab, and cosgrm for the other APIs.

Naming constraints

CAF abbreviationcosno
Resource typeMicrosoft.DocumentDB/databaseAccounts
Length3–44 characters
CaseLowercase only
Allowed charactersLowercase letters, numbers, and hyphens. Start with a letter or number.
Uniqueness Global
SeparatorHyphen
Watch out: Only 44 characters and globally unique. The prefix depends on the API, so a single naming policy can't check it reliably.

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
cosno-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^[a-z0-9][a-z0-9-]{2,43}$
Bicep naming expression
var name = take(toLower('cosno-${workload}-${env}-${region}-${instance}'), 44)
Terraform local
locals {
  name = substr(lower(join("-", compact(["cosno", var.workload, var.env, var.region, var.instance]))), 0, 44)
}

Azure Policy can't evaluate regular expressions, so a policy can check the cosno 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