- Assuming we are doing ARM, everything in Azure is a typed reference, its impossible to create a conflict by naming two different typed items the same, e.g. a 'test' vritual machine and a 'test' storage account are different resources and are always referenced separately by their fully qualified type names
- Tags are where metadata about an object should be. THe objects name itself should be short or random, but the tags are where the real parsing/filtering/search need to occur by department, etc.
- A name in Azure is typically immutable, so it should not contain mutable properties, e.g. server environments can change, regions can change, etc.
- DNS conflicts in the customer DNS zone are a potential source however DNS is mutable and aliases can be created, and there are very few object types that share Azure dns namespaces. The original alias remains clean.
- While multiregion deployments are common, most
- An organization prefix is essential to minimize conflicts after organizational