Skip to content
Guides & Articles

Azure Naming
Conventions Blog

Guides, CAF best practices, and IaC naming patterns for Terraform and Bicep.

api managementapimintegration

Azure API Management Naming Conventions: Service, APIs, and Products

CAF naming for Azure API Management. The service is a globally unique azure-api.net endpoint (1 to 50 chars); APIs, products, backends, and named values inside are function-named. Patterns and examples.

Read more →
service busmessagingintegration

Azure Service Bus Naming Conventions: Namespaces, Queues, and Topics

CAF naming for Azure Service Bus. The namespace is a globally unique servicebus.windows.net endpoint (6 to 50 chars); queues, topics, and subscriptions inside are relaxed. Patterns and examples.

Read more →
container registryacrcontainers

Azure Container Registry Naming: Rules, Limits, and CAF Patterns

Azure Container Registry name requirements: 5 to 50 characters, lowercase alphanumeric only, no hyphens, globally unique. The CAF pattern, examples, and Terraform and Bicep.

Read more →
cosmos dbdatabasesazure

Azure Cosmos DB Naming Conventions: Account, Database, and Container

Azure Cosmos DB account names are globally unique DNS endpoints: 3 to 44 characters, lowercase letters, numbers, and hyphens. CAF patterns per API, plus databases and containers.

Read more →
logic appsintegrationazure

Azure Logic App Naming Conventions: Consumption vs Standard

Naming Azure Logic Apps with CAF. Consumption workflows are resource-group scoped (1 to 43 characters); Standard logic apps are Microsoft.Web hostnames (globally unique, 2 to 60). Plus Terraform.

Read more →
subscriptionsmanagement groupsgovernance

Azure Subscription and Management Group Naming Conventions

Naming the top of the Azure hierarchy. Subscriptions have no enforced rules (descriptive display names); management groups have an immutable 1 to 90 character ID plus a display name. CAF patterns and examples.

Read more →
azurecafnaming conventions

Custom Azure Naming Conventions: Reordering CAF for Your Team

Microsoft CAF's naming order is a default, not a mandate. How to safely customize the component order and abbreviations, what you must never change, and how to stay consistent.

Read more →
app servicefunctionscompute

Azure App Service and Function App Naming Conventions

CAF naming for web apps, function apps, App Service plans, and slots: the azurewebsites.net hostname rules, the 32-character Functions host ID gotcha, and IaC examples.

Read more →
azureregionsnaming conventions

Azure Region Abbreviations: The Complete List for Resource Naming

Every Azure region with its ID and short abbreviation for resource naming, plus guidance on when to abbreviate, common variants, and how to wire the mapping into Terraform.

Read more →
sqldatabasesazure

Azure SQL Naming Conventions: Servers, Databases, and Managed Instances

CAF naming for Azure SQL: globally unique lowercase server names, database and elastic pool conventions, managed instances, failover groups, and Terraform examples.

Read more →
virtual machinescomputeazure

Azure VM Naming Conventions: Resource Name vs Computer Name

How to name Azure virtual machines with CAF: the 64-character resource name, the 15-character Windows computer name, VMSS prefixes, and Terraform/Bicep examples.

Read more →
key vaultsecurityazure

Azure Key Vault Naming Conventions: CAF Rules and Soft-Delete Gotchas

CAF compliant naming for Azure Key Vault, including the 24-character limit, globally unique names, soft-delete name reservation, and Terraform/Bicep examples.

Read more →
multi-regiondisaster recoveryazure

Azure Naming Conventions for Multi-Region Deployments

How to extend your Azure CAF naming scheme to handle multi-region, active-active, and primary/failover architectures without name collisions or ambiguity.

Read more →
azurenaming conventionsbest practices

7 Azure Naming Convention Mistakes (and How to Fix Them)

The most common Azure naming convention mistakes teams make, and practical fixes before they become permanent technical debt.

Read more →
tagginggovernanceazure

Azure Tagging Strategy: Best Practices for Cost, Governance, and Ops

A practical Azure tagging strategy that works alongside your naming conventions, covering required tags, enforcement, and Terraform/Bicep implementation.

Read more →
storageazurecaf

Azure Storage Account Naming Conventions: Rules, Limits, and CAF Patterns

Storage accounts have the strictest naming rules in Azure, 3 to 24 characters, lowercase alphanumeric only, globally unique. Here's how to get it right.

Read more →
networkingvnetnsg

Azure Virtual Network Naming Conventions: VNet, Subnet, and NSG

CAF compliant naming for Azure Virtual Networks, subnets, Network Security Groups, and related networking resources, with Terraform and Bicep examples.

Read more →
resource groupsazurecaf

Azure Resource Group Naming Conventions: CAF Best Practices

How to name Azure resource groups consistently using Microsoft's Cloud Adoption Framework, patterns, examples, and strategies for multi-environment and multi-region setups.

Read more →
bicepazurecaf

Azure Bicep Naming Conventions: CAF Compliant Resource Names

How to generate and enforce CAF compliant Azure resource names in Bicep templates, including the azure-naming module, string functions, and practical examples.

Read more →
akskubernetesazure

AKS Naming Conventions: Azure CAF Best Practices for Kubernetes

CAF compliant naming for Azure Kubernetes Service clusters, node pools, and the surrounding infrastructure, ACR, VNet, NSG, and managed identities.

Read more →
terraformazureiac

Naming Azure Resources in Terraform: A CAF Compliant Approach

How to implement Microsoft CAF naming conventions in Terraform using locals, including handling Storage Accounts, Key Vaults, and other resources with tight character limits.

Read more →
azurecafnaming conventions

Azure Naming Conventions: The Complete CAF Guide (2026)

A practical guide to Microsoft's Cloud Adoption Framework naming conventions for Azure resources, components, separators, length limits, and real examples.

Read more →