Azure naming · Microsoft.Storage/storageAccounts

st Storage account

Blob, file, queue, and table storage. The name forms a public DNS label (<name>.blob.core.windows.net).

Naming constraints

CAF abbreviationst
Resource typeMicrosoft.Storage/storageAccounts
Length3–24 characters
CaseLowercase only
Allowed charactersLowercase letters and numbers only. No hyphens, underscores, or uppercase.
Uniqueness Global
SeparatorNone (no separators allowed)
Watch out: Globally unique across all of Azure and no separators allowed, so the tokens run together. Easiest name to collide on. Portal-created function apps, Cloud Shell, and diagnostics create storage accounts with generated names.

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

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

« Recovery Services vault Azure Cache for Redis »

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

More in Storage

All resource types