Curriculum Overview: Core Architectural Components of Azure

This document provides a comprehensive roadmap for mastering the foundational physical and logical structures of Microsoft Azure. Understanding these components is essential for passing the AZ-900 exam and architecting reliable, compliant solutions in the cloud.

Prerequisites

Before diving into the architectural components, learners should have a foundational understanding of:

• Basic Cloud Concepts: Familiarity with the definitions of cloud computing and the shared responsibility model.
• Cloud Service Types: Understanding the differences between IaaS, PaaS, and SaaS.
• General IT Knowledge: Basic awareness of what servers, networking, and datacenters are in a traditional on-premises context.

[!NOTE] Completing Unit 1: "Describe Cloud Concepts" is highly recommended as it establishes the "Why" before this module explains the "How."

Module Breakdown

Learning Objectives per Module

1. Physical Infrastructure

• Describe Azure Datacenters: Understand the physical facilities that house the hardware.
• Describe Availability Zones: Explain how AZs provide protection against datacenter failures through physically separate locations within a region.
• Describe Azure Regions: Define the geographical boundaries used for resource deployment.

2. Logical Organization & Hierarchy

• Resource Management: Explain the purpose of Azure Resources and Resource Groups.
• Subscription Management: Describe how subscriptions serve as a unit of management, billing, and scale.
• The Governance Hierarchy: Illustrate how Management Groups provide a level of scope above subscriptions.

3. Resilience and Sovereignty

• Region Pairs: Explain why regions are paired (usually 300 miles apart) to ensure business continuity during large-scale disasters.
• Sovereign Regions: Identify specialized instances like Azure Government or Azure China for specific compliance and legal requirements.

Visualizing the Physical Structure

The following diagram illustrates how Azure organizes its physical presence from a single facility up to a global geography.

\begin{tikzpicture}[node distance=2cm] \draw[thick, fill=blue!10] (0,0) rectangle (8,5); \node at (4,4.5) {\textbf{Azure Region}};

\draw[thick, fill=green!10] (0.5,0.5) rectangle (2.5,3.5); \node[align=center] at (1.5,2) {AZ 1\\small(Datacenters)};

\draw[thick, fill=green!10] (3,0.5) rectangle (5,3.5); \node[align=center] at (4,2) {AZ 2\\small(Datacenters)};

\draw[thick, fill=green!10] (5.5,0.5) rectangle (7.5,3.5); \node[align=center] at (6.5,2) {AZ 3\\small(Datacenters)};

\draw[<->, thick] (2.5,2) -- (3,2); \draw[<->, thick] (5,2) -- (5.5,2); \node[below, font=\tiny] at (4,0.5) {High-speed, low-latency fiber connections}; \end{tikzpicture}

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

1. Diagram the Hierarchy: Accurately draw the relationship between Management Groups, Subscriptions, Resource Groups, and Resources.
2. Compare Availability Options: Choose between deploying in a single Region, across Availability Zones, or across Region Pairs based on a given Service Level Agreement (SLA) requirement.
3. Identify Boundary Use-Cases: Explain when a company would require a separate Subscription (e.g., for billing different departments) versus a separate Resource Group (e.g., for managing a specific project's lifecycle).
4. Define Sovereignty: Correctly identify which Azure offering to use when data must legally remain within a specific national border (e.g., US Government regions).

Real-World Application

Understanding Azure architecture is not just for the exam; it is critical for business operations:

• Cost Control: By organizing resources into subscriptions and using management groups, enterprises can track spending across global departments and enforce spending limits.
• Disaster Recovery: A developer who understands Region Pairs will ensure that their application's backup data is stored in a paired region to survive a localized natural disaster (like a hurricane or earthquake) that might take out an entire region.
• Compliance: In industries like healthcare and finance, knowing how Geographies and Sovereign Regions work allows architects to guarantee that sensitive patient or financial data never leaves its country of origin, meeting strict legal requirements.

[!IMPORTANT] Resources can only exist in one Resource Group, and Resource Groups cannot be nested. This flat structure at the bottom of the hierarchy ensures that lifecycle management (deleting a group to delete all contained resources) remains predictable.