From ClickOps to IaC in Azure

This article explores the shift from manual 'ClickOps' to Infrastructure as Code (IaC) in Microsoft Azure. It highlights the limitations of portal-based resource management, such as configuration drift and lack of reproducibility, and advocates for IaC using tools like Bicep or Terraform. The piece covers best practices including establishing a central module library, enforcing version control, restricting portal access, implementing state management, securing secrets, and standardizing CI/CD pipelines. It emphasizes the strategic importance of IaC for achieving scalability, compliance, and operational resilience in Azure environments, especially during early landing zone design.