Azure is not a list of products to memorize. A cloud engineer should see it as a programmable operating environment built from identity, subscriptions, resource groups, networks, compute platforms, managed data services, observability and governance.
REQUIREMENT
↓
TENANT + SUBSCRIPTION + IDENTITY
↓
REGION + NETWORK + COMPUTE + DATA
↓
AUTOMATE / DEPLOY
↓
OBSERVE
↓
SECURE + SCALE + OPTIMIZE
↓
RECOVER + IMPROVE
For every workload, answer:
Where does it live? Tenant, management group, subscription, resource group, region and VNet.
Who or what can access it? Microsoft Entra principal, managed identity, Azure RBAC role, network path and policy.
Where is state stored? Managed disks, Blob Storage, Azure SQL, Cosmos DB, Azure Managed Redis, etc.
How is it operated? Azure Monitor, Log Analytics, Application Insights, Activity Log, alerts, backup, IaC and incident response.
Service model Azure manages more of You still own Virtual Machines facilities, hardware, hypervisor guest OS, patches, application, data, network/security choices AKS managed Kubernetes control plane and platform integration workloads, images, RBAC, policies, node/workload configuration, reliability Azure SQL Database database infrastructure, patching, built-in HA platform schema, access, queries, capacity/performance choices, application behavior Azure Container Apps servers, orchestration platform, ingress/scaling platform container, identity, config, revisions, dependencies, workload behavior Blob Storage storage infrastructure and durability mechanisms IAM/RBAC, networking, lifecycle, retention, data exposure
Need Common Azure service virtual machines Azure Virtual Machines autoscaled VM fleet Virtual Machine Scale Sets managed Kubernetes AKS serverless containers Azure Container Apps web/API PaaS App Service functions/event code Azure Functions object/file storage Blob Storage / Azure Files relational database Azure SQL / PostgreSQL / MySQL globally distributed NoSQL Cosmos DB in-memory data Azure Managed Redis container registry Azure Container Registry messaging Service Bus / Event Grid / Event Hubs metrics/logs/traces Azure Monitor / Log Analytics / Application Insights secrets/keys Key Vault IaC Bicep / ARM / Terraform
💡 bongoDev Tip
Learn service boundaries, failure modes and trade-offs , not only names. Cloud engineering is selecting, connecting, securing, automating and operating services as one system.
🎤 Interview Question
A product team says, “Deploy this application to Azure.” What questions do you ask before recommending any Azure services?
🧪 Hands-on Lab
Take a three-tier application and draw its Azure tenant/subscription, resource group, identity, network, compute, data, observability and recovery boundaries before selecting exact services.