One Command. Entire Azure Monitoring Stack Deployed. 7 Bicep Modules. Done.

Seven Bicep modules. The entire monitoring stack. Deployed with one command. Click-ops monitoring dies the moment someone asks: can we reproduce this in another environment? Building a complete Azure monitoring stack in Bicep - from Log Analytics to 31 KQL-based alert rules, 8 action groups, and two-stage deployment. The inheritance situation was familiar: someone had clicked through Azure Portal, created alert rules one by one, documented the process as "I know how it works," then left the team. Monitoring became a black box nobody dared touch. Why Bicep over Terraform for this? Bicep speaks Azure's language natively with no translation layer, gets new features on day one, and handles DCR quirks without edge cases. The 7 composable modules are: Resource Group with environment-aware naming, Log Analytics Workspace, DCR for VM Insights, DCR for Logs split by server type, Custom Tables for SQL and app-specific data, 31 KQL-based Alert Rules, and 8 Action Groups mapped to team channels. Deployment is two-stage because dependencies matter: Stage 1 handles the infrastructure layer - resource group, workspace, DCRs, custom tables. Stage 2 deploys the alerting layer - the 31 rules and…