Skip to content
Microsoft CAF Compliant

Azure Resource
Name Generator

Generate consistent, CAF compliant names for all 204 Azure resource types, then export them as Terraform, Bicep or CSV in one click.

204 Resource Types
14 CAF Categories
Free No Login Required
Export Terraform · Bicep · CSV
1

Configure naming inputs

2

Select resource types

Starting points:

Fill in the inputs and select at least one resource type to generate names.

Fills a payments workload in production East US with eight common resources.

Frequently asked questions

Common questions about Azure naming conventions and AzureNamer.

What is the Azure CAF naming convention?

Microsoft's Cloud Adoption Framework recommends building names from a resource type abbreviation plus workload, environment, region, and instance, for example kv-payments-prod-eus-001. It gives every resource a consistent, predictable structure.

What is the maximum length of an Azure storage account name?

Storage account names must be 3 to 24 characters, lowercase letters and numbers only, with no hyphens, and they must be globally unique across all of Azure.

Can I rename an Azure resource after it is created?

Most Azure resources cannot be renamed. Changing a name usually means deleting and recreating the resource, so it is best to settle on names before your first deployment.

Is AzureNamer free?

Yes. AzureNamer is completely free, needs no login, and generates CAF compliant names for all 204 Azure resource types.

Can I export the generated names to Terraform or Bicep?

Yes. One click exports Terraform, Bicep, JSON, Markdown, or CSV. Terraform and Bicep can be exported as exact names or as a parameterized, variable-driven file that derives the right names for every environment.

Can I customize the naming pattern?

Yes. Open "Customize pattern" in the generator to reorder the name components (for example workload first with the type at the end) and to edit the environment abbreviations. The custom convention applies to every generated name and export, and it travels in shared links.

What separator should I use in Azure resource names?

Use a hyphen for most resources, such as rg-payments-prod-eus-001. A few types like storage accounts and container registries do not allow hyphens, so their components are concatenated, such as stpaymentsprodeus001.