Skip to main content

Azure Concepts

Before you learn individual Azure services, it is essential to understand the platform's own organizing principles: how Azure structures its global infrastructure, models identity and resource hierarchy, builds virtual networks, and enforces governance. These core concepts recur in every architecture and service, and mastering them will make your later learning far more efficient.

This section of CloudComputingDevPro collects the foundational concepts of Microsoft Azure. Each page explains a single idea in depth, connecting it to related concepts and to the broader Cloud Foundations you already know. Use this hub to build a mental model of the platform before you dive into the service catalog.

Learning Path​

Azure concepts form the bridge between universal cloud fundamentals and the specific services you will later use. The recommended learning sequence is:

Cloud Foundations

↓

Azure Concepts (this section)

↓

Azure Services

↓

Azure Architecture

↓

Azure Best Practices

A solid grasp of concepts prevents the common trap of memorizing service names without understanding why they exist or how they fit together. An engineer who understands the Azure resource hierarchy, for example, can immediately reason about management group design and subscription strategy.

Global Infrastructure​

Azure's physical infrastructure directly affects latency, resilience, data residency, and service availability. These pages explain the building blocks.

  • Azure Global Infrastructure – An overview of how Azure organizes its worldwide presence into regions, zones, and edge sites.
  • Regions – Large geographic areas containing one or more Availability Zones; the primary boundary for data residency and service selection.
  • Availability Zones – Physically separate locations within a region, each with independent power, cooling, and networking, used for fault isolation.
  • Region Pairs – Two regions within the same geography that are paired for prioritized recovery and coordinated updates.
  • Edge Zones – Smaller infrastructure footprints placed closer to users for low‑latency workloads and content delivery.
  • Azure Edge Network – Global points of presence that accelerate traffic and provide DNS, CDN, and security services.

Identity & Resource Organization​

Azure uses a hierarchical structure to organize resources, manage access, and govern at scale.

  • Microsoft Entra ID – Azure's cloud‑native identity and access management service, formerly Azure Active Directory.
  • Tenant – A dedicated instance of Entra ID that represents your organization and contains users, groups, and applications.
  • Subscription – A logical container for Azure resources that also serves as a billing boundary and a trust boundary.
  • Management Group – A container for organizing subscriptions, applying policies, and managing access hierarchically.
  • Resource Group – A logical grouping of related Azure resources (like VMs, VNets, databases) that share a common lifecycle.
  • Resource Provider – A service that supplies a specific type of Azure resource (e.g., Microsoft.Compute, Microsoft.Network).

Networking Concepts​

Azure networking is built on the Virtual Network (VNet) and a set of connectivity primitives that control traffic flow, isolation, and hybrid connectivity.

  • Virtual Network (VNet) – A logically isolated network that you define within an Azure region, where you control IP addressing, subnets, and routing.
  • Subnet – A segment of a VNet’s IP address range, used to group and isolate resources, often for security or tier separation.
  • Network Security Group (NSG) – A set of allow/deny rules that filters inbound and outbound traffic at the subnet or NIC level.
  • User Defined Route (UDR) – Custom routing rules that override Azure’s default system routes to direct traffic through firewalls or gateways.
  • Azure Load Balancer – A Layer‑4 load balancer that distributes inbound traffic across backend VMs for high availability and scale.
  • Azure DNS – A hosting service for DNS domains, providing name resolution for Azure services and public domains.
  • Azure Firewall – A managed, cloud‑native network security service that provides stateful firewall capabilities for VNet traffic.
  • ExpressRoute – A dedicated, private connection between your on‑premises network and Azure, providing higher reliability and lower latency.

Governance & Operations​

Governance concepts help you manage security, compliance, cost, and operational consistency across your Azure estate.

  • Azure RBAC – Role‑Based Access Control that grants fine‑grained permissions to users, groups, and services at the appropriate scope.
  • Azure Policy – A service for creating, assigning, and managing policies that enforce rules and effects on your resources.
  • Resource Locks – Prevent accidental deletion or modification of critical resources through read‑only or delete locks.
  • Tags – Name‑value pairs of metadata that you apply to resources for cost allocation, organization, and automation.
  • Azure Landing Zone – A multi‑subscription foundation that provides a scalable environment for governance, networking, identity, and security.
  • Management Hierarchy – The structure of management groups, subscriptions, and resource groups that defines the governance and access control scope.
  • Management Groups – Containers above subscriptions that enable you to apply policies and access controls consistently across an organization.
  • Governance Strategy – The combination of policy, RBAC, locks, and tags that enforces compliance and operational discipline at scale.
  1. Learn Cloud Foundations – the universal concepts shared by all cloud platforms.
  2. Understand Azure Global Infrastructure – regions, zones, and edge.
  3. Learn Azure Identity and Resource Organization – tenants, subscriptions, and resource groups.
  4. Learn Azure Networking Concepts – VNets, subnets, and connectivity.
  5. Continue to Azure Services – explore compute, storage, databases, and more.
  6. Study Azure Architecture – apply concepts to design resilient, scalable systems.
  7. Apply Azure Best Practices – embed security, cost, and operational excellence into your work.

Continue Learning​

  • Azure Services – Detailed coverage of the service families that run on top of these concepts.
  • Azure Architecture – Patterns and frameworks for designing production‑ready systems.
  • Azure Best Practices – Operational and security guidance for everyday engineering.
  • Cloud Foundations – Revisit the vendor‑neutral fundamentals that underpin the entire platform.