Azure Architecture Guide

Azure Overview

What This Chapter Is About

Build the mental model needed to understand Azure before choosing services or designing architectures.

This chapter is for readers who are new to Azure and for readers who already know another cloud but want Azure to feel less like a list of unfamiliar product names. The focus is not to memorize services. The focus is to understand how Azure organizes identity, governance, subscriptions, resource groups, networking, workload services, and operations.

Keep one durable idea in view:

Azure architecture starts with boundaries and responsibilities before service selection.

Sections

  1. High-Level Overview

  2. Mapping Azure from AWS and GCP Experience

  3. Azure Hierarchy and Why It Is Useful

How the Chapter Develops

The chapter develops in this order:

  1. Start with the basic Azure operating model: what Azure helps a team organize, secure, connect, run, and operate.

  2. Translate existing AWS or GCP instincts into Azure vocabulary without pretending that service mapping is enough.

  3. Explain the Azure hierarchy in more detail: tenant, management groups, subscriptions, resource groups, and resources.

Together, these sections show that Azure is familiar in purpose but specific in structure. Every major cloud handles identity, access, governance, billing, networking, deployment, monitoring, and operations. Azure's architecture model becomes clearer when the reader knows where Azure places those responsibilities.

What You Will Be Able to Do

By the end of this chapter, the reader should be able to:

  • Explain Azure at a high level without listing random services.

  • Compare Azure's operating model with AWS and GCP.

  • Describe the Azure hierarchy from tenant to resources.

  • Explain why management groups, subscriptions, and resource groups exist.

  • Understand why Azure architecture starts with identity, governance, organization, networking, workload placement, and operations.

  • Ask better architecture questions before choosing Azure services.

Key Ideas

  • Azure is a cloud platform, but it is also an operating model for ownership, access, cost, security, deployment, and operations.

  • Service names are useful vocabulary, not the whole architecture method.

  • Tenant, management groups, subscriptions, resource groups, and resources form the basic Azure hierarchy.

  • Subscriptions are major boundaries for billing, access, policy, quotas, and workload separation.

  • Resource groups are practical containers for resources that usually share ownership, lifecycle, deployment, or operational responsibility.

  • Readers coming from AWS or GCP should map responsibilities first and services second.