Agent RulesAgent Rules
AZ

Azure Naming & Tagging

Standardize naming and organization elements within Azure Resource Manager.

Microsoft Azure
Architecture
Use in BuilderAll Microsoft Azure Options

Details

Language / Topic
azure-cloudMicrosoft Azure
Category
Architecture

Rules

balanced
- Stick to the pattern: `<resource-type>-<app>-<environment>-<region>` (e.g., `vnet-myapp-prod-eastus`)
- Apply consistent tags (`CostCenter`, `Environment`, `Owner`) enforced via Azure Policies
- Understand resource type character limits (e.g., Storage Accounts must be 3-24 lowercase letters/numbers globally unique)
- Create Resource Groups spanning exactly one lifecycle boundary—deploy items that spin up and die together within the identical Resource Group
- Establish mandatory Azure Policies that reject resource creation outright if organizational tags (`Environment`, `Project`) are missing
- Abbreviate standard Azure resources accurately relying on Microsoft's suggested abbreviations (e.g., `st` for Storage Account, `kv` for Key Vault)