Skip to main content
Version: Next

Naming Conventions

Canonical reference: Naming Conventions (full)
Applies to: All AzureLocal repositories
Last Updated: 2026-03-17


File & Directory Naming

TypeConventionPatternExample
Directorieslowercase-with-hyphens^[a-z][a-z0-9-]*$getting-started/
Markdown (docs/)lowercase with hyphens*.mddeployment-guide.md
Root filesUPPERCASEREADME.md, CHANGELOG.md
PowerShell scriptsPascalCaseVerb-Noun.ps1Deploy-Solution.ps1
Config fileslowercase-with-hyphensvariables.example.yml

Azure Resource Naming

All resources follow the IIC naming patterns:

Resource TypePatternExample
Resource Grouprg-iic-<purpose>-<##>rg-iic-platform-01
Virtual Networkvnet-iic-<purpose>-<##>vnet-iic-compute-01
Network Security Groupnsg-iic-<purpose>nsg-iic-compute
Key Vaultkv-iic-<purpose>kv-iic-platform
Storage Accountstiic<purpose><##>stiicdata01
Log Analyticslaw-iic-<purpose>-<##>law-iic-monitor-01

Variable Naming

RuleStandardExample
YAML sectionssnake_caseazure_local, networking
YAML keyssnake_casesubscription_id, resource_name
Pattern^[a-z][a-z0-9_]*$
Max length50 characters

Git Branch Naming

PatternUsageExample
mainDefault branch
feature/<description>New featuresfeature/add-validation
fix/<description>Bug fixesfix/config-parsing
docs/<description>Documentationdocs/deployment-guide
infra/<description>CI/CDinfra/add-pester-tests