Azure Platform Engineering: Build an Enterprise Landing Zone From Scratch
Day-2 Operations: Maintaining and Evolving Your Azure Landing Zone
Nine months after go-live, internal audit asks a simple question: do the firewall rules running in production today match the ones that were approved? You run terraform plan to prove it. Fourteen changes come back. Three are rule edits someone made in the portal during an incident. One opened a port …
Cost Governance in the Landing Zone: Tagging Enforcement, Budgets, and FinOps Automation
The Azure invoice arrives on a Friday. $12,000 over budget. You spend the weekend clicking through the Cost Management portal, filter by resource group, filter by service, filter by tag — except half the resources have no tags at all. By Monday you have a spreadsheet, a list of suspects, and a …
CI/CD Pipeline for Your Landing Zone: Deploying Azure Verified Modules with GitHub Actions
Someone on your team runs terraform apply from their laptop. The change goes straight to production. There’s no PR, no review, no record of what changed or why. A week later, something breaks in the landing zone and nobody can explain what happened. You check the Azure activity log and find a …
Security Baseline: Defender for Cloud and Microsoft Sentinel in a Landing Zone
The compliance report lands in your inbox on a Tuesday morning. One finding: a production subscription had diagnostic logs disabled for 47 days. No one noticed because no one was watching. The subscription was vended six weeks ago, the app team started deploying workloads a week after that, and …
Centralized Monitoring: Log Analytics, Diagnostic Settings, and Azure Monitor Workbooks
The incident ticket lands on a Tuesday morning. Production degraded last Friday. You open the Azure portal, pull up the subscription’s Log Analytics Workspace, and realize the diagnostics on the App Gateway were never enabled. The VNet flow logs are going to a different workspace some …
Subscription Vending: Automating New Workload Onboarding with IaC
The ticket comes in on a Monday. A team needs a new production subscription — they have a sprint starting Thursday. You know what this means: Management Group placement, VNet config, hub peering, RBAC assignments, a budget, and a diagnostic settings policy to wire it up to the SIEM. Each step is …
Governance at Scale: Writing and Deploying Azure Policies with Terraform and Pulumi
The compliance report arrives on a Friday afternoon. You scan through it and stop on a finding: a Storage Account with public network access enabled, sitting in your production subscription, deployed three weeks ago. Someone bypassed the documented standard, the ARM deployment succeeded, and nobody …
Identity and Access Architecture for Azure Landing Zones: Entra ID, RBAC, and PIM
The security team’s Slack message arrives on a Tuesday afternoon: “We’re seeing resource deletions in prod. Investigating.” Your heart rate goes up. You pull the Azure Activity Log. The deletions are attributed to a service principal—one your team created eight months ago for …
Hub-and-Spoke Networking for Azure Landing Zones: Azure Firewall, Bastion, and Private DNS
Your new workload team files their first support ticket three weeks after go-live. A developer can’t reach the database. You pull the logs. The VM is making an outbound call to a public IP on port 1433—in plain text, no firewall inspection, straight out to the internet. You ask who approved …








