Azure DevOps + Terraform — Lesson 1: Azure Repos, Branching, Pull Requests, and Terraform Repository Design

Technical Scope

• Git repositories and Terraform folder structure
• Branch policies, pull requests, reviewers, and build validation
• Environment configuration and reusable modules
• Work items, commits, ownership, and change traceability

Instructor Demonstration

Create a pull-request workflow for an Azure Terraform repository.

Applied Workshop

Design branch policies that require validation and platform-team review for production modules.

1. Translate the scenario into configuration, access, state, pipeline, or module decisions.
2. Implement the change in a controlled workspace or repository.
3. Capture the plan, logs, outputs, policy results, and post-change checks.
4. Explain one safer or more maintainable alternative and its trade-off.

Validation Standard

Every infrastructure change is reviewed and linked to a work item and owner.

• The intended target, identity, environment, and state boundary are confirmed.
• The plan or execution evidence contains no unexplained destructive action.
• Security, reliability, maintainability, and operational ownership are reviewed.
• The final result can be reproduced from version-controlled inputs.

Failure Analysis

Resolve merge conflicts, bypassed policies, path filters, and untraceable commits.

Learners isolate the smallest verified cause, correct it, rerun the relevant validation step, and record the preventive action in the course improvement log.