azure-caf-naming

CAF resource-name pattern

<type>-<workload>-<env>-<region>-<instance>

Examples:

Resource	CAF abbreviation	Example name
Storage account	st	stmyappdeveus001 (no hyphens — storage limits to 24 chars, alphanumeric)
App Service	app	app-myapp-dev-eus-001
Container App	ca	ca-myapp-dev-eus-001
Container App Environment	cae	cae-myapp-dev-eus-001
Key Vault	kv	kv-myapp-dev-eus-001
SQL Server	sql	sql-myapp-dev-eus-001
SQL Database	sqldb	sqldb-myapp-dev-eus-001
Log Analytics Workspace	log	log-myapp-dev-eus-001
Application Insights	appi	appi-myapp-dev-eus-001
Container Registry	cr	crmyappdeveus001 (no hyphens — ACR has restrictions)

If microsoft-learn MCP is available, call microsoft_docs_search with "Azure Cloud Adoption Framework abbreviations" to retrieve the full current list before running checks.

---

Step 1 — Extract resource names

For each resource declaration in .bicep files, extract:

• type (e.g., Microsoft.Storage/storageAccounts)
• name value (may be a parameter reference — record as unknown if so)
• tags property

---

Step 2 — Validate naming pattern

For each resource with a literal string name:

1. Look up the CAF abbreviation for the resource type.
2. Check that the name starts with the abbreviation followed by - (or is concatenated correctly for no-hyphen types like storage accounts and container registries).
3. Check that the name contains environment segment (dev, test, staging, prod, uat).
4. Check that the name ends with a numeric instance segment (001, 01, etc.).

// BAD: no CAF structure
resource sa 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: 'mystoragedev'    // no type prefix, no region, no instance
}

// GOOD: storage uses concatenation (no hyphens allowed)
param workload string = 'myapp'
param env string = 'dev'
param region string = 'eus'
param instance string = '001'

resource sa 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: 'st${workload}${env}${region}${instance}'
}