Maps account naming convention

The CAF abbreviation for Maps account is map. Names can be 1 to 98 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

Naming rules

Rules follow Microsoft's resource naming rules and CAF abbreviations. Some resource types have extra start/end character restrictions, so verify against the official docs before locking in a convention.

Naming Developer tools resources

App Configuration stores, Maps accounts, SignalR, and Web PubSub each become their own DNS endpoint and are typically shared across several apps or services rather than owned by one, similar in spirit to a shared API Management instance. Name them for the platform or shared boundary they serve, not for whichever app happened to need them first.

The common mistake is naming a shared App Configuration store after its first consumer, then having to work around that name once a second, unrelated app depends on the same store. Naming for the boundary from day one avoids that rename.

Example names

Generated by the same engine as the name generator, so length and character rules are already applied.

Naming in Terraform and Bicep

Build the name from variables so one module produces the right name in every environment.

locals {
  maps_account_name = "map-${var.workload}-${var.environment}-${var.region}-001"
}

var mapsAccountName = 'map-${workload}-${environment}-${region}-001'

Related Developer tools resources

See the full list of Azure resource naming rules or read the complete CAF naming guide.