Azure Naming Convention: Complete Reference for Every Resource Type and Region

CAF-aligned abbreviations, character limits, allowed characters and scope for every major Azure resource type and Azure region in one place.

Every Azure resource type has its own naming rules. Some allow up to 260 characters and accept hyphens freely. Others cap you at 24 characters, forbid hyphens entirely, and must be globally unique. Getting these rules wrong causes deployment failures, CI/CD pipeline breaks, and Azure Policy violations that are painful to untangle after the fact.

This reference build on top of the Microsoft Cloud Adoption Framework abbreviation recommendations and the Azure Resource Manager naming rules into a single, structured source you can bookmark and reference as you build.

If you'd rather not cross-reference this guide manually before every deployment, Clovernance generates and validates CAF-compliant names for any resource type automatically. Try it free

How to Read This Reference

Each table entry includes the following fields:

• Abbr: the CAF-recommended abbreviation prefix for that resource type.
• Length: the minimum and maximum character count enforced by Azure.
• Scope: where the name must be unique: globally across all Azure customers, within your subscription, within a resource group, or within a parent resource.

Recommended Naming Pattern

The CAF recommends a consistent naming pattern across all resource types. The standard structure is:

For example:

• rg-payments-prod-westeu-001Resource group
• kv-payments-prod-weu-001Key Vault (shortened region due to 24-char limit)
• stpaymentsprodweu001Storage Account (no hyphens allowed)

Not every resource can fit the full pattern within its character limit. For tightly constrained resources like Windows VMs (15 chars) and Key Vaults (24 chars), abbreviate the workload name and region aggressively while keeping the structure recognizable.

Check out our Azure naming conventions guide to learn more.

Naming Scope Explained

Scope determines where a name must be unique. It is one of the most commonly misunderstood aspects of Azure naming:

• Global: The name must be unique across all Azure customers worldwide. This applies to Storage Accounts, Key Vaults, App Services, Cosmos DB accounts, and others because the name becomes part of a public DNS hostname.
• Subscription: The name must be unique within your Azure subscription.
• Resource Group: The name must be unique within the resource group it belongs to.
• Parent Resource: The name must be unique within its parent, such as a subnet within a virtual network or a database within a SQL Server.

Complete Resource Reference

Complete Location Reference

Generate and Validate Names Automatically

Manually checking every resource name against this reference before every deployment is error-prone and slow. A better approach is to automate name generation and validation so that compliant names are produced by default and violations are caught before they reach your pipelines.

Clovernance applies all of these rules automatically. Configure your naming convention once, share it across your organization, and generate validated, CAF-compliant names for any resource type in seconds.

Stop cross-referencing naming rules manually. Let Clovernance handle it.