Skip to main content

Azure Naming Convention Guide

Introduction

Consistent naming conventions are essential for managing cloud resources effectively. They improve discoverability, foster collaboration, and simplify the management of resources across teams and projects.

This guide outlines the naming conventions to be followed for all Azure resources within our organization.

note

The content in this guide is based on this authoritative KB article created by the Data Center Technical Architecture team. If you have access permissions, always refer to the KB article as the primary source of truth. While we strive to keep this guide up to date, the KB article may contain the latest standards and recommendations.

Azure Naming convention

The following considerations to be taken into account:

  • The resources from the same subscription can belong to different Azure regions;
  • There could be resources in the same Azure region belonging to different subscriptions;
  • A subscription contains either internet-facing resources or resources connected with ExpressRoute, not both;
  • The resource name should identify what subscription the resource belongs to;
  • The members of the same resource group should have the same naming pattern;
  • It should be easy to identify related resources;
  • One should easily distinguish production environment from qa, qa from test and so on;
  • The description in a resource group name helps differentiate between the groups.

The following schema should be used to build the resource name:

<objecttype>-<rgrpid>-<description>

This way the resources from multiple subscriptions will be, first, arranged by their types; second, by their resource groups; third, by the resource description.

Name forNamingLengthExamplesComment
<objecttype>varbckp, vnetShort name taken from the name of Azure service. For example, backup vault is shortened as BCKP. Virtual network as VNET. The list of already defined <objecttype> codes is given in the respective table below.
<vendor>3msf, aws3 letters short code, taken from the vendor name. e.g. MSF - for Microsoft, AWS - for Amazon.
<region>2we jw az2 letters code, shortened from the region name, where the vendor's datacenter is located. e.g. WE - West Europe; JW - Japan West; AZ - for global resources.
Azure subscriptionmsfaz<p|x><subscription#>8msfazp01, msfazx02<vendor> - msf in case of Azure. <P|X|V|M> - connectivity indicator: P - privately connected (datacenter extension), X - externally connected (internet-facing), V - Visual Studio subscription (comes with VS license), M - Personal Azure plans, usually 1 month evaluation. <subscription#> - sequential number of the subscription starting from 01, increasing by 1 for every new subscription.
<sitecode><vendor><region><p|x><subscription#>8msfwep01, msfnax01Standard JTI naming schema for cloud-based site codes. <subscription#> identifies the subscription a resource belongs to. For example, MSFWEP01 indicates Microsoft cloud in West Europe privately connected to JTI.
Resource group identifier, <rgrpid><sitecode>-<##>11msfwep01-01, msfeux02-02<##> is a sequential number, the same for all resources in the respective resource group. <rgrpid> is assigned to all objects and preferred to be the same within the same resource group. It is allowed to reuse <rgrpid> across different groups if they are part of the same project or activity.
Resource group identifier_short, <rgrpid_s><sitecode><##>10-11msfwep0101, msfeux0202Same as <rgrpid> but without the - symbol. Required for resources that do not support such characters in names (e.g., storage accounts).
Virtual machine<sitecode>-<function>-<##>15msfwep01-srv-01Exception to <object>-<location>-<##> schema due to standard JTI naming conventions for servers.
Storage accountstor<rgrpid><shortdescription>20, 22stormsfwep0101test<shortdescription> helps distinguish Storage Accounts within a Resource group. Note: storage accounts' names may contain only lowercase letters and numbers.

Regions to short code conversion table

RegionAcronym
West Europewe
North Europene
East USeu
West USwu
West US 2wu
Japan Eastje
Japan Westjw
East Asiaea
Southeast Asiasa

Object type codes table

Object typePrefixExampleMax charComment
Analysis Servicesanalysisservicesanalysisservicesmsfnex2010radrsglbdev63lowercase alphanumeric only
API Appapiappapiapp-msfwex14-lite-uk60 
API Managementapimapim-msfwex01-127-planit-api-prd50 
Application Gatewayagwagw-msfeax26-01-infra-hub-apac-prd80 
Application Gateway Policywafwaf-msfeax26-01-infra-hub-apac-prd80 
App Service Planappsvcplnappsvcpln-msfeux01-02-devqa40 
Application Insightsappiappi-msfwex01-131-agro-prd255 
Arc Kubernetesarckarck-msfwex01-131-agro-prd30 
Automation Accountaaaa-msfwep08-02-azure-automation-prd50 
└ Automation Runbookrbrb-msfwep08-02-ADTeam-PKI-CertRequest-prd50 
Azure Database for MySQLmysqldbmysqldb-msfwex01-145-ldhereandnow-dev63lowercase alphanumeric or hyphens
Azure Kubernetes Serviceaksaks-msfwex91-01-infra-dev30 
Backup Vaultbckvltbckvlt-msfwex01-01-blob-prod250 
Batchbatchbatch-msfwex01-13-tme24 
Bastionbastionbastion-msfeax26-01-infra-hub-apac-prd80 
Container Appscaca-msfsax05-22-be-letscml-prd32 
Container Apps Environmentcaecae-msfsax05-22-be-letscml-prd32 
Cognitive Searchsearchsearch-msfwex01-132-masterbotv2-prd63 
Cosmos DBcosmoscosmos-msfwex28-04-rombuc01-mongo44 
Data Brickbrickbrick-msfnex22-10-pr-prod30 
Data Factoryadfadf-msfwex01-31-regint-qa63 
Dedicated SQL poolsqldwsqldw-msfnex2410-gscsmarts-serving-sbx128was "Azure Datawarehouse"
Event Grid Namespaceevgsevgs-msfwex01-166-compmon-datasets-prd50 
Event Grid topicevgtevgt-msfwex01-166-compmon-datasets-prd50 
Event Grid Domainevgdevgd-msfwex01-166-compmon-datasets-prd50 
Event Hub Namespaceevhnsevhns-msfnex23-09-tmeapi-dev63 
└ Event Hubevhevh-msfnex23-09-tmeapi-<Short_Description>-dev63Naming should follow respective evhns-*
Firewallafwafw-msfeax26-01-infra-hub-apac-prd80 
Firewall Policyafwpafwp-msfeax26-01-infra-hub-apac-prd80 
Function Appfuncfunc-msfnex23-09-tmeapi-sbx60 
Key Vaultkvkv-msfwex18-23-prd, keyvault-msfwex18-23-prd24 
Load balancerlblb-msfwex02-12-staging-db80 
└ Load Balancer Front Endlbfelbfe-msfwex02-12-01-front80 
└ Load balancer Backend poollbbelbbe-msfwex02-12-01-sql80 
└ Load balancer Probelbprobelbprobe-msfwex02-12-01-1433-tcp80 
└ Load Balancer Rulelbrulelbrule-msfwex02-12-01-sql80 
Log Analyticslawlaw-msfwex11-14-gltdb-dev63 
Log Analytics Query Packlogpacklogpack-msfwex11-14-gltdb-prd63 
Logic Applogiclogic-msfwex15-cargoclaims-broker-dev80 
Machine Learningmlml-msfsax01-16-phdwh-prd260 
NAT Gatewayngng-msfwex01-317-DataCollectionBaltic-prd80 
Network security groupsnsgnsg-msfeux02-14-prod-db80 
Private Endpointpepe-msfsax01-394-drishti-mapbased-qa64 
Private Linkplpl-msfsax01-394-drishti-mapbased-qa64 
Public IP addresspippip-MSFWEX01-SRV-1280 
PostgreSQLpsqlpsql-msfwex01-54-fme-prd63lowercase alphanumeric or hyphens
Recovery Services vaultbckpasrbckp-msfwep01-01asr-msfwep01-0150 
Redis cacheredisredis-msfwex02-13-prod63 
Relayrelayrelay-msfwex01-54-fme-prd50 
Resource grouprgrprgrp-msfwex01-01-projecty-prd90 
Resource group managedrgrp-Databricks ( suffix -brick-managed)rgrp-msfwex01-01-infra-prd-brick-managedAKS ( suffix -aks-managed)rgrp-msfwex01-01-infra-prd-aks-managedSynapse ( suffix -syn-managed)rgrp-msfwex01-01-infra-prd-syn-managed90 
Route Tablertrt-msfeax26-04-cluster-qa80 
SQL Elastic Poolsqlepsqlep-msfwex01-01-projecty-prd128 
SQL Databasesqldbsqldb-msfwex01-127-planit-machines-qa128 
SQL Serversqlsql-msfwex01-0163 
Static Web Appstappstapp-msfwex01-345-so-external-qa40 
Storage accountstorstormsfwex0156pics24lowercase alphanumeric only
Synapse Analytics/Workspacesynsyn-msfeux01-87-tmesales-dwh-bolivia50lowercase alphanumeric or hyphens
Virtual networkvnetvnet-msfwep01-08-internal-vm80 
└ Virtual Network Subnetsnetsnet-msfwep01-08-0180 
VM Availability setavsavs-msfwex02-12-prod80 
VMmsfmsfwex01-srv-0364 
VirtualMachineScaleSetvmssvmss-msfwex02-12-prod64 
vWANvwanvwan-msfwex42-01-qa80 
Web Appwebappwebapp-msfwex01-103-concurbot-prd60 

If something is not on the list yet please use Microsoft Naming examples - we will use it as a reference in future: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations

Deployment Example with good name convention:

alt text