Microsoft Azure is the second-largest cloud provider, with particularly strong adoption in enterprises that have existing Microsoft technology investments (Active Directory, Office 365, SQL Server, Windows Server). A cloud engineer who understands Azure's organisational hierarchy — tenants, management groups, subscriptions and resource groups — can navigate, provision and govern Azure resources with confidence. Increasingly, organisations use both Azure and AWS, making cross-cloud fluency valuable. Azure's architectural concepts map clearly to AWS equivalents with some important differences: Azure Active Directory (Entra ID) is the identity foundation; subscriptions are the billing and resource boundary; resource groups are the management and lifecycle grouping; and regions are pairs of datacenters that provide redundancy.
35 minbeginner
Azure Architecture — Tenants, Subscriptions, Resource Groups and Regions
Analogy🏏Cricket
🏏 Think of it like cricket: The match itself is the kernel — real computation at the hardware level. The commentators translating that action into words for the audience are the shell: they take raw events and present them in a form humans can understand and interact with. The television set in your living room is the terminal emulator: it displays the commentary but does not participate in the match.Just as switching from one broadcaster to another changes commentary style but not the underlying match, switching between Linux distributions changes shell defaults and package manager but not the kernel. Just as Star Sports and Sony Six both cover the same IPL match with different graphics packages, Ubuntu and Alpine both run the same kernel with different userspace tools.The insight is that these layers are genuinely separate, which is why you can swap any one of them independently.
Lesson 29 of 40
0% complete