Resources can follow a similar naming convention to resource groups. Let's verify the following samples:
<service>-<location>
<product>-<location>-<environment>-<service>
<company>-<location>-<environment>-<product>-<service>
Depending on your needs, you may require different data to be available. In general, you can implement the following two approaches:
- Each element has to be as verbose as possible.
- A child element only has to implement the extra information that is not available for the parent.
Here are examples of those two approaches:
TheCloudTheory-IT-Prod -> TheCloudTheory-SomeProduct-Use-Prod-Rg -> TheCloudTheory-SomeProduct-Use-Prod-AppServicePlan
TheCloudTheory-IT-Prod -> SomeProduct-Use-Prod-Rg -> AppServicePlan
The choice is yours – you have to select an approach that meets your requirements when it comes to administering resources in Azure.
Enforcing a naming convention...
