How steph409/tf-azure-monitor-baseline-alerts works
Project type and purpose
• This is an Infrastructure-as-Code (IaC) Terraform module targeting Azure.
• Its purpose is to deploy Azure Monitor baseline alerts across an Enterprise-Scale Landing Zone hierarchy using Azure Policy definitions and assignments.
File structure
A. Top-level
• terraform.tf, variables.tf, policy_definitions.tf, policy_assignment_*.tf – root Terraform configuration that orchestrates modules
• .github/scripts – automation scripts (PowerShell) for updating library definitions
• examples/ – opinionated usage scenarios illustrating default and parameterized deployments
B. lib/
• archetype_definitions/ – JSON templates for high-level “initiative” (policy set) definitions per management group archetype (root, platform, identity, etc.)
• policy_definitions/ – low-level JSON policy definitions for individual alerts
• policy_set_definitions/ – JSON combining multiple policy definitions into initiatives
• policy_assignments/ – JSON wrappers for assigning initiatives to management groups
C. module/
• policy_definition/ – Terraform module that reads JSON in lib/policy_definitions and policy_set_definitions to create Azure PolicyDefinition and PolicySetDefinition resources
• policy_assignment/ – Terraform module that reads JSON in lib/archetype_definitions and policy_assignments to assign initiatives to specific Management Groups
D. examples/
• default, default_with_all_parameters, default_with_dashboards, only_platform_subscription – sample root module invocations showing how to configure variables and parameters for different scopes
README for architectural insights
• Describes a hierarchy of Azure Management Groups: root → landing-zones; root-platform → {identity, connectivity, management}
• Indicates which initiatives (policy sets) get assigned to which management group
• Points to cleanup patterns, versioning, and parameter overrides
Main components
A. Developer / CI Environment
• Local Dev Machine or Azure DevOps / GitHub Actions runner
• Terraform CLI and PowerShell script (.github/scripts)
B. Code Repository (GitHub)
• Terraform root configuration, modules, lib JSON artifacts, examples
C. Terraform Modules
1. policy_definition module
2. policy_assignment module
D. Library of JSON definitions (lib/)
• policy_definitions, policy_set_definitions, archetype_definitions, policy_assignments
E. Azure Control Plane
• Azure Resource Manager (ARM) API
• Azure Policy Service
• Azure Management Groups hierarchy
F. Optional: Example Workflows
• example/ directories illustrating terraform init/plan/apply usage
• Parameter overrides via variables.tf or .tfvars
Relationships and interactions
1. Developer/CI pushes code → triggers GitHub Actions / CI pipeline
2. CI runner clones repo and executes Terraform init, plan, apply
3. Terraform root config invokes the policy_definition and policy_assignment modules
4. Modules load JSON artifacts from lib/ and call ARM API to:
a. Create PolicyDefinition and PolicySetDefinition resources
b. Assign those policy sets to specific Management Groups
5. Azure Policy Service stores definitions and enforces alerts on monitored resources
Architectural patterns & design principles
• Layered modularization: root config delegates to small purpose-built modules
• Separation of concerns: JSON artifacts decoupled from Terraform logic
• Reusability: examples show how to parameterize and reuse modules across subscriptions
• Declarative infrastructure: Terraform HCL drives all Azure changes
Technologies, frameworks & libraries
• Terraform (HCL)
• Azure Policy & Management Groups
• JSON for policy definitions
• PowerShell for library updates
• GitHub Actions / Azure DevOps for CI
Diagramming recommendations
• Code push → CI runner → Terraform execution
• Terraform modules → ARM API calls → Policy Service → Management Groups
• Green for code artifacts (repo, modules, JSON)
• Orange for CI pipeline
• Blue for Azure cloud services
Detail while avoiding over-complexity
• Major Terraform modules and JSON libraries as separate nodes