Step 1: Clone and Open

Quickstart

Current Version | Get running in 10 minutes

Prerequisites

Step 1: Clone and Open

git clone https://github.com/jonathan-vella/azure-agentic-infraops.git
code azure-agentic-infraops

Step 2: Open in Dev Container

1. Press F1 (or Ctrl+Shift+P)
2. Type: Dev Containers: Reopen in Container
3. Wait 3-5 minutes for setup

The Dev Container installs all tools automatically:

• Azure CLI + Bicep CLI
• PowerShell 7
• Python 3 + diagrams library
• 25+ VS Code extensions

Step 3: Verify Setup

az --version && bicep --version && pwsh --version

Step 4: Enable Subagent Orchestration

⚠️ REQUIRED: The Conductor pattern requires this setting.

Add this to your VS Code User Settings (Ctrl+, → Settings JSON):

{
  "chat.customAgentInSubagent.enabled": true
}

Why User Settings? Workspace settings exist in .vscode/settings.json, but user settings take precedence for experimental features like subagent invocation.

Verify it's enabled:

1. Open Command Palette (Ctrl+Shift+P)
2. Type: Preferences: Open User Settings (JSON)
3. Confirm the setting is present

Step 5: Start the Conductor

Option A: InfraOps Conductor (Recommended)

The Conductor (🎼 Maestro) orchestrates the complete 7-step workflow:

1. Press Ctrl+Shift+I to open Copilot Chat
2. Select InfraOps Conductor from the agent dropdown
3. Describe your project:

Create a simple web app in Azure with:
- App Service for web frontend
- Azure SQL Database for data
- Key Vault for secrets
- Region: swedencentral
- Environment: dev
- Project name: my-webapp

The Conductor guides you through all 7 steps with approval gates.

Option B: Direct Agent Invocation

Invoke agents directly for specific tasks:

1. Press Ctrl+Shift+A to open the agent picker
2. Select the specific agent (e.g., requirements)
3. Enter your prompt

Step 6: Follow the Workflow

The agents work in sequence with handoffs:

Approval Gates: The Conductor pauses at key points:

• ⛔ Gate 1: After planning (Step 4) — approve implementation plan
• ⛔ Gate 2: After validation (Step 5) — approve preflight results
• ⛔ Gate 3: After deployment (Step 6) — verify resources

What You've Created

After completing the workflow:

agent-output/my-webapp/
├── 01-requirements.md          # Captured requirements
├── 02-architecture-assessment.md  # WAF analysis
├── 04-implementation-plan.md   # Phased plan
├── 04-dependency-diagram.py     # Step 4 dependency diagram source
├── 04-dependency-diagram.png    # Step 4 dependency diagram image
├── 04-runtime-diagram.py        # Step 4 runtime diagram source
├── 04-runtime-diagram.png       # Step 4 runtime diagram image
├── 04-governance-constraints.md   # Policy discovery
├── 05-implementation-reference.md # Module inventory
├── 06-deployment-summary.md    # Deployed resources
└── 07-*.md                     # Documentation suite

infra/bicep/my-webapp/
├── main.bicep                  # Entry point
├── main.parameters.json        # Parameters
└── modules/
    ├── app-service.bicep
    ├── sql-database.bicep
    └── key-vault.bicep

Next Steps

Quick Reference

Conductor (Orchestrated Workflow)

Ctrl+Shift+I → InfraOps Conductor → Describe project → Follow gates

Direct Agent Invocation

Ctrl+Shift+A → Select agent → Type prompt → Approve

Skill Invocation

Skills activate automatically based on your prompt:

• "Create an architecture diagram" → azure-diagrams
• "Generate an ADR" → azure-adr
• "Create workload documentation" → azure-artifacts

Or invoke explicitly:

Use the azure-diagrams skill to create a diagram for my-webapp

Agent Personas