How to Use This Guide

DOCUMENT CATEGORY: Runbook SCOPE: Automation guide usage and navigation PURPOSE: Help readers choose the right automation section and tool path MASTER REFERENCE: Microsoft Learn - Azure Local Deployment Introduction

Status: Active

This guide is organized so readers can move from platform setup to pipeline implementation and then into the tool-specific guidance required for delivery. It is not strictly linear for every reader, but the recommended reading order is deliberate.

Recommended Reading Order

1. Read Purpose and Scope
2. Complete Part 1: CI/CD Infrastructure
3. Choose one platform in Part 2: CI/CD Pipelines
4. Use Part 3: Automation Guides for the tools your team actually runs
5. Return to the Implementation Guide when executing phase-by-phase deployment steps

When to Use This Guide vs. the Implementation Guide

Use This Automation Guide When You Need To	Use the Implementation Guide When You Need To
Set up runners, repositories, and CI/CD variables	Follow the deployment sequence end to end
Decide between GitLab, GitHub Actions, or Azure DevOps	Understand prerequisites, assumptions, and phase objectives
Understand Terraform, Ansible, Bicep, and PowerShell assets	Execute operational and validation tasks in order
Generate automation inputs from variables.yml	Use the main runbook as the authoritative deployment narrative

Section Map

Section	Use It For
Part 1: CI/CD Infrastructure	Deploying CI/CD prerequisites such as projects, runners, environments, and variables
Part 2: CI/CD Pipelines	Choosing and configuring the delivery platform
Part 3: Automation Guides	Learning the tool-specific implementation model

Before You Start

Make sure the following are already in place:

• A working copy of the azurelocal-toolkit repository
• A populated config/variables/variables.yml file
• Authentication to Azure and any source control platform you plan to use
• Clarity on whether your deployment path is Terraform + PowerShell, Terraform + Ansible, or Ansible only

For broader prerequisite and authentication guidance, use:

• Implementation Guide
• How to Use This Runbook
• Authentication

Practical Usage Pattern

A typical reader workflow looks like this:

1. Build the CI/CD platform foundation
2. Pick the pipeline engine that matches organizational standards
3. Use the tool-specific guide for authoring, execution, and variable mapping
4. Execute the implementation phases using the chosen automation pattern

---

Navigation

Previous	Up	Next
Purpose and Scope	Automation Guide	Part 1: CI/CD Infrastructure