Azure Infrastructure-as-Code Lab
An Azure infrastructure-as-code lab exploring reusable deployments with Terraform and Bicep across networking, RBAC, Key Vault, monitoring, Log Analytics, and CI/CD workflows.
Overview
The Azure Infrastructure-as-Code Lab explores how repeatable definitions can make cloud changes easier to review, reproduce, and reason about. It is a technical lab, not a claim of a particular client or production topology.
Infrastructure-as-code approach
The work examines reusable deployment patterns, explicit configuration, version-controlled change, and delivery checks. Terraform and Bicep are presented as two explored approaches; the evidence does not establish that both managed the same deployment.
Terraform
Terraform provides a declarative workflow for describing Azure resources, reviewing planned changes, and organizing reusable configuration.
Bicep
Bicep provides an Azure-native declarative language for expressing infrastructure through modules and Azure Resource Manager deployments.
Networking, access, secrets, and monitoring
Confirmed areas include networking, role-based access control, Key Vault, Azure Monitor, and Log Analytics. These are technology areas rather than a diagram of specific deployed resources.
CI/CD tools explored
GitHub Actions and Azure DevOps appear in the canonical lab evidence as delivery-workflow tools. They are not presented as stages in one combined pipeline because that relationship is not confirmed.
Reusability goal
The lab’s central goal is to reduce one-off configuration by treating infrastructure definitions, review, and repeat deployment as reusable engineering work.
Evidence boundaries
No VM, AKS, App Service, database, storage, firewall, load-balancer, NAT, private-endpoint, hub-and-spoke, or multi-region topology is claimed. No fabricated source sample or topology diagram is used.
Lessons
Infrastructure-as-code improves repeatability only when the scope, state, review path, and validation expectations are as explicit as the resource definitions.