video1.0<iframe src="https://www.loom.com/embed/08218a407ae648709c9c75f1b9db1708" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/08218a407ae648709c9c75f1b9db1708-ea92fb1f685d6624.gif584.522This Loom explains how Elijah built an Azure Update Manager patch management lab using Terraform, including the architecture, security choices, deployment, and compliance validation. He set up a small Windows domain with a domain controller and two workstations and used four Terraform modules for networking, key vault secret storage, compute (domain promotion and joining VMs), and update manager configuration with per-VM assignments, with remote state stored in an Azure storage account. He highlights real deployment blockers including a CPU quota limit (region allowed 4 vCPUs vs an original 6), a public IP limit (max 3 per region), capacity-restricted VM size requiring a different SKU, and two configuration bugs involving a required managed identity for the assessment policy and correct patch orchestration mode before linking to maintenance. The final result shows all three machines enrolled and passing validation with zero missing critical or security patches, and it generates a JACE JSON compliance report for auditing.