Naming Conventions
Most organizations have some kind of naming convention for their operating system instances. These typically include some kind of location identifier, perhaps a company identifier (to protect against future organizational mergers), a service type identifier, and then some kind of instance number. For example, I might use the following for the first (01) domain controller (DC) in Dallas (DAL) for my SavillTech (SAV) organization:
- SAVDALDC01
Naming is even more important when leveraging Azure resources, which can be in many regions and of many different types. Also remember that some resources have different requirements about what is supported as part of the name. In the cloud, the resources may include the type of resource in addition to the environment plus the types of information previously covered. The organization should pick a standard set of codes for the various Azure regions. Microsoft has detailed guidance on possible naming approaches to be used at:
