Table of contents

Five phases. Each one ends in something you built.

In this trade the build is the examination. A phase is not complete until the artifact exists in a repository with your name on it. Every phase closes the same way: a one-page recap that draws the classes together, then a build that proves them.

Phase OneFoundations

Nine classes · AZ-900

Resource hierarchy, identity, RBAC, policy — the governance instincts that separate an engineer from someone clicking through a portal.

00Start Here · Meet the client, Campux Retail ↳See the shop — the live Campux Retail storefrontdemo 01What is Cloud? 02Why Cloud? 03Pros, Cons & When Not To 04IaaS / PaaS / SaaS 05Deployment Models 06AWS vs Azure vs GCP 07Entra ID, Subscriptions, Groups 08RBAC & Azure Policy 09Service Principals & Managed Identity §Phase One Recap — the nine, on one pagerecap

Build I

A governed subscription: management group, environment separation, role assignments, and two policies — expressed as code, not clicks.

Open the build →

Phase TwoCore Infrastructure

Seven classes · AZ-104

Networks, compute, storage, private endpoints, DNS — the depth most self-taught engineers are missing.

10Virtual Networks & Subnets 11Compute: VMs, Scale Sets, App Service 12Storage Accounts 13Load Balancing & Traffic 14Private Connectivity 15Hybrid & DNS 16REST APIs & ARM §Phase Two Recap — the seven, on one pagerecap

Build II

A two-tier application with storage the public internet cannot reach, fronted by an application gateway, resolving through private DNS.

Open the build →

Phase ThreeThe DevOps Core

Nine classes · AZ-400 (partial)

Bicep and Terraform, GitHub Actions federated to Azure without a single stored credential. This phase is the difference between two salary bands.

17Git Fundamentals 18Repositories & Collaboration 19Branching Strategies 20Infrastructure as Code: Bicep 21Infrastructure as Code: Terraform 22GitHub Actions Fundamentals 23Actions → Azure with OIDC 24Runners & Advanced Pipelines 25Scripting for Cloud Engineers §Phase Three Recap — the nine, on one pagerecap

Build III

A complete GitOps loop: a pull request that plans, a merge that deploys, a gate that waits for a human, and no secret anywhere in the repository.

Open the build →

Phase FourOperate, Secure, and the AI Question

Sixteen classes

Containers, monitoring, KQL, DevSecOps, FinOps — and three classes on AI as infrastructure, not theory.

26Containers & Docker 27Containers on Azure 28Azure Monitor & Log Analytics 29KQL Essentials 30App Insights & Alerting 31Security & DevSecOps 32Cost Management & FinOps 33AI Foundations: Context, Tools & MCP 34AI Infrastructure I: Deployment 35AI Infrastructure II: Network & Cost 36Incident Response 37Azure Databases 38API Management 39Azure DevOps Pipelines 40Message Queues & Service Bus 41Azure Functions §Phase Four Recap — the sixteen, on one pagerecap

Build IV

Observability and cost guardrails across everything you have built to this point. Diagnostic settings, a KQL alert that matters, and a budget that shouts before the invoice does.

Open the build →

Phase FiveProof & Payoff

Capstones + Class 42

Build the receipts, then go get hired: three portfolio capstones you can hand an interviewer, and the class on turning them into an offer.

+The three capstonesprojects 42Landing the Job §Phase Five Recap — the whole bootcamprecap