Why so many parts and pieces Azure?
When the Azure Resource Management (ARM) structure was implemented for Azure in 2014, a new management structure and platform was implemented to control & compartmentalized aspects of the Azure environment. These ensured that tasks were repeatable, control can be segregated based on roles & tasks, and consistent regardless of the tools utilized to manage the environment. Unfortunately, if you haven't had the opportunity to work with it consistently, remembering which part performs which tasks and how to best utilize them can be difficult to track.
What are the core Azure structures?
For many who are just getting into Azure, it is difficult to keep track of all the different types of pieces of Azure and how they interact. Azure is designed with very specific structures of management, controls, and commands that can help unify the control of the environment. As you learn and understand these pieces, it can help simplify your use and management of the environments:
|Azure Resource Manager (ARM)
|The unified & distributed interface for all control and monitoring of the Azure platform
|Azure AD Tenant
|Identity and access control mechanism for cloud platforms (not just Azure)
|Repository and boundary for resources running on the Azure platform
|Any computational or storage structure for services running on the Azure Platform
|Organizational structures for storing Resources in
|Structured files for telling Azure how to build and configure resources
|Jobs run in Azure to create Resources based on Templates
|Role Based Access Control (RBAC) that grant users in Azure AD access to Azure scopes
|Restrictions and standards assigned to Azure scopes to limit activity and ensure consistency
We will go over each of these in more detail in later articles as they all have deeper information available to them. However, here is some more summary about where and when you use them.