Creating and Using Local Terraform Modules for Azure Networking

Terraform modules are the primary mechanism for organizing and reusing infrastructure code. A local module is simply a directory containing .tf files that accepts input variables, creates resources, and exposes output values: the same building blocks as a root configuration, but packaged so the same logic can be called multiple times with different parameters. Without modules, Terraform projects grow into monolithic configurations where a Virtual Network definition is copy-pasted every time a new environment or tier needs one, creating drift and maintenance overhead. Modules eliminate that duplication while enforcing a clear contract between the caller and the implementation through explicit variable and output declarations.

Variable scope in Terraform is strictly module-level: a variable defined in a child module is invisible to the root module unless explicitly passed through an output, and root-level variables do not automatically flow into child modules unless explicitly set as input arguments. This boundary is what makes modules genuinely reusable rather than just cosmetic grouping.

In this lab, you will scaffold a local networking module for Azure Virtual Networks and subnets, define module inputs and outputs, call the module from a root configuration, deploy and verify the infrastructure, and reuse the same module a second time to observe how variable scope and outputs work across multiple module instances.

Objectives

By completing this Intermediate level lab, you will be able to:

• Create a local Terraform module directory structure with variables, resources, and outputs
• Define input variables with types, descriptions, and default values for a networking module
• Call a local module from a root configuration using the module block with a relative source path
• Pass values into a module and consume its outputs in the root configuration
• Deploy Azure Virtual Networks and subnets through a reusable module
• Reuse the same module with different parameters and observe Terraform's module-level variable scoping

Who is this lab for?

• Cloud Engineers learning to structure Terraform projects with reusable, composable modules
• DevOps Practitioners looking to reduce duplication and enforce consistency across Azure deployments
• Infrastructure Engineers who want to understand variable scope boundaries between root and child modules

Basic familiarity with Terraform syntax (HCL), Azure Virtual Networks, and the Azure CLI is recommended.