Well-Architected Framework: Operational Excellence
summary
Shows how an ARM Template moves from the portal or az deployments create to actual resources: syntax checking, preflight validation against resource providers, and a what-if diff run before any provisioning. The deployments runtime evaluates expressions, builds an execution graph from DependsOn edges, and issues parallel long‑running operations; each deployment becomes an Azure resource with per-resource operation details and a correlation ID for backend debugging. Introduces Bicep, a transpiled DSL that emits ARM JSON, and mentions a private preview of deployment Stacks (aka.ms/GETStacks) landing in a few weeks.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:36Welcome
- 1:29Review and Create
- 5:08Deployment
- 8:05Validation
- 11:51Deploying
- 12:41Execution Graph
- 13:23Deployment Sequence
- 14:55Operation Details
- 16:52Bicep
- 18:21Wrapup
- 18:58Questions
related talks
01h 01mARM FTW
01h 05mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
47mAutomated Infrastructure Deployment in Azure With Arm Templates and Azure Devops
27mEvaluating Your Toolbox
31mAzure DevOps for System Engineers
55mARM FTW – Azure Resource Manager For The Win
47mARM FTW – Azure Resource Manager For The Win
01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
