Naming Convention¶
Scope¶
This is the general Euvic naming convention. Azure resource names are generated from the schema in the Azure repo naming_schema folder. Hostnames, Active Directory objects, Intune/Jamf policies, and network devices follow the Naming Convention Template, instantiated per client.
Building blocks¶
Environment codes¶
| Code | Environment |
|---|---|
| P | Production |
| U | UAT |
| S | Stage |
| T | Test |
| D | Development |
| G | General purpose across all environments |
Location codes¶
Derived from the Azure region name: first letter of the first word plus the first two
letters of the second word (for example West Europe -> WEu, North Europe -> NEu).
GL is reserved for global resources and is assigned manually because the transformation
requires a two-word region name.
Organization codes¶
| Code | Scope |
|---|---|
| EIT | Resources dedicated to EIT only |
| ESA | Resources dedicated to ESA only |
| EORG | Resources for the whole group |
Azure resource names¶
Pattern: {environment}-{uniqueidentifier}-{regionName}-{abbreviation}-{number}
abbreviationcomes from the CAF resource abbreviation list resolved by the generator.- Separators are removed and the name is lowercased when the resource type requires it
(for example storage accounts:
peitcommonweust01). - Example with separators:
p-eit-common-weu-app-01. - Example group-wide resource:
G-{organization}-Security-WEu-LOG01.
Generate names with AzureResources-NameGenerator v1.0.4:
New-AzResourceNameGenerator -environment P `
-resourceTypeName @("Storage/storageAccounts", "Web/sites") `
-regionName "West Europe" -uniqueidentifier EIT-Common -number 1 `
-separator "-" -convertTolower $true `
-ResourceNameSchema "./naming-schema.json"
Related conventions¶
- Tagging
- Service Principals
- Naming Convention Template