File share naming convention

The CAF abbreviation for File share is share. Names can be 3 to 63 characters long and allow lowercase alphanumerics and hyphens. The name must be unique within the parent resource.

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 Storage resources

Storage account naming, 3 to 24 characters, lowercase, no hyphens, globally unique, has its own dedicated guide. Backup Vaults and Resource Guards are usually centralized, one per environment protecting many resources, the same shared boundary logic as Log Analytics workspaces elsewhere in this list. File shares are scoped to their storage account, so they can be named simply and descriptively without worrying about a collision with a share in a different account.

The common mistake is creating a new backup vault per protected resource instead of consolidating an environment behind one vault, which fragments backup policies that are meant to apply consistently across everything they protect.

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 {
  file_share_name = lower("share-${var.workload}-${var.environment}-${var.region}-001")
}

var fileShareName = toLower('share-${workload}-${environment}-${region}-001')

Related Storage resources

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