As we briefly discussed in Chapter 1, Getting Started with Azure, your architecture begins with the subscriptions structure and an overall naming convention. The reason I bring this up is that these go hand in hand from a fundamental perspective. I have learned that there are two paths you can take with respect to your Azure configuration: the corporate path and the consultant path. The corporate path is for organizations that develop their own solutions, and all work is strictly for the organization alone. The consultant path is for those that do work for others and themselves. The reason this becomes important to point out is that this not only affects the structure of your subscriptions, but how the optional parts of the naming convention work.
Now, I like to take a simplistic approach to building things in Azure and when I am architecting solutions in Azure.
Let's take a look at what I mean. When you are building out a subscription model and a naming convention...