azure-agentic-infraops

azure-agentic-infraops

Agentic InfraOps transforms Azure deployments for IT Pros. Using GitHub Copilot and AI agents, it converts requirements into diagrams, validated designs, and deploy-ready Bicep templates—aligned with Azure best practices. Includes real-time pricing, compliance, and automation.

Stars: 60

Visit
 screenshot

Agentic InfraOps is a multi-agent orchestration system for Azure infrastructure development that transforms how you build Azure infrastructure with AI agents. It provides a structured 7-step workflow that coordinates specialized AI agents through a complete infrastructure development cycle: Requirements → Architecture → Design → Plan → Code → Deploy → Documentation. The system enforces Azure Well-Architected Framework (WAF) alignment and Azure Verified Modules (AVM) at every phase, combining the speed of AI coding with best practices in cloud engineering.

README:

Contributors Forks Stargazers Issues MIT License Azure


Logo

Agentic InfraOps

A multi-agent orchestration system for Azure infrastructure development
Requirements → Architecture → Plan → Code → Deploy → Documentation

Quick Start » · Sample Outputs · Scenarios · Report Bug


What is Agentic InfraOps?

What is Agentic InfraOps?

Agentic InfraOps transforms how you build Azure infrastructure with AI agents.

Instead of context-switching between requirements gathering, architecture decisions, Bicep authoring, and documentation, Agentic InfraOps provides a structured 7-step workflow that coordinates specialized AI agents through a complete infrastructure development cycle: Requirements → Architecture → Design → Plan → Code → Deploy → Documentation.

The system solves a critical challenge in AI-assisted infrastructure development: maintaining quality and compliance while moving quickly. By enforcing Azure Well-Architected Framework (WAF) alignment and Azure Verified Modules (AVM) at every phase, you get the speed of AI coding combined with best practices in cloud engineering.

Built upon patterns from copilot-orchestra and Copilot-Atlas, adapted for Azure infrastructure workflows.

(back to top)


Key Features

Key Features

🎭 Multi-Agent Workflow

The InfraOps Conductor orchestrates 7 specialized agents, each optimized for their specific role in the infrastructure development lifecycle.

🏛️ WAF-Aligned Decisions

Every architecture decision is evaluated against the 5 pillars of the Azure Well-Architected Framework: Security, Reliability, Performance, Cost Optimization, and Operational Excellence.

🔍 Preflight Validation

3 validation subagents (lint, what-if, review) provide quality gates before deployment—catching issues early when they're cheap to fix.

⏸️ Mandatory Approval Gates

Built-in pause points for plan approval, pre-deployment review, and post-deployment verification keep you in control of the infrastructure development process.

📋 Documentation Trail

Comprehensive artifacts at each phase (01-07) create an audit trail for reviewing all work completed and decisions made.

💎 Context Conservation

The majority of work is done in dedicated subagents, each with its own context window and dedicated prompt. This reduces hallucinations as the context fills up.

(back to top)


Agentic Workflow

Agentic InfraOps workflow diagram showing 7 pipeline steps from Requirements to Documentation with WAF guardrails and AVM enforcement
sequenceDiagram
    participant User
    participant Conductor
    participant Requirements
    participant Architect
    participant Bicep
    participant Deploy

    User->>Conductor: Describe infrastructure project
    Conductor->>Requirements: Gather requirements
    Requirements-->>Conductor: Return 01-requirements.md
    Conductor->>User: Present requirements
    User-->>Conductor: Approve requirements

    Conductor->>Architect: Assess architecture (WAF)
    Architect-->>Conductor: Return 02-assessment.md + cost estimate
    Conductor->>User: Present architecture
    User-->>Conductor: Approve architecture

    Note over Conductor: Step 3 (optional): Design diagrams & ADRs

    Conductor->>Architect: Create implementation plan
    Architect-->>Conductor: Return 04-plan.md + governance
    Conductor->>User: Present plan
    User-->>Conductor: Approve plan

    Conductor->>Bicep: Generate Bicep templates
    Bicep-->>Conductor: Return infra/bicep/{project}/

    alt Validation passes
        Conductor->>User: Present templates for deployment
        User-->>Conductor: Approve for deployment
    else Validation fails
        Conductor->>Bicep: Revise with feedback
    end

    Conductor->>Deploy: Execute deployment (what-if first)
    Deploy-->>Conductor: Return 06-deployment-summary.md

    alt Deployment succeeds
        Conductor->>User: Present deployment summary
        User-->>Conductor: Verify deployment
    else Deployment fails
        Conductor->>User: Request guidance
    end

    Conductor->>User: Workflow complete + 07-* documentation suite

(back to top)


Architecture Overview

Architecture Overview

The Agentic InfraOps system consists of specialized agents organized into three tiers:

Primary Agent: The Conductor

Agent Persona Role Model
InfraOps Conductor 🎼 Maestro Master orchestrator managing the complete 7-step workflow Claude Opus 4.6
  • Coordinates all specialized agents through handoffs
  • Manages 5 mandatory approval gates
  • Handles user interactions and pause points
  • Enforces the Requirements → Deploy → Docs cycle

Core Agents (7 Steps)

Step Agent Persona Role Model
1 requirements 📜 Scribe Captures infrastructure requirements Claude Opus 4.6
2 architect 🏛️ Oracle WAF assessment and design decisions Claude Opus 4.6
3 design 🎨 Artisan Diagrams and Architecture Decision Records Claude Sonnet 4.5
4 bicep-plan 📐 Strategist Implementation planning with governance Claude Opus 4.6
5 bicep-code ⚒️ Forge Generates AVM-first Bicep templates Claude Sonnet 4.5
6 deploy 🚀 Envoy Azure resource provisioning Claude Sonnet 4.5
7 📚 — As-built documentation (via skills)

Validation Subagents

Subagent Role When Invoked
bicep-lint-subagent Syntax validation (bicep lint, bicep build) Pre-deployment
bicep-whatif-subagent Deployment preview (az deployment what-if) Pre-deployment
bicep-review-subagent Code review (AVM standards, security, naming) Pre-deployment

Diagnostic Agent

Agent Persona Role
diagnose 🔍 Sentinel Resource health assessment and troubleshooting

(back to top)


How It Works

How It Works

The Conductor agent follows a strict 7-step cycle for every infrastructure project:

Step 1: Requirements (Scribe)

  • User Request — You describe the Azure infrastructure you want to build
  • Captures Requirementsrequirements agent gathers functional, non-functional, and compliance requirements
  • Outputagent-output/{project}/01-requirements.md

Step 2: Architecture (Oracle)

  • WAF Assessmentarchitect agent evaluates requirements against Well-Architected Framework
  • Cost Estimation — Azure Pricing MCP provides real-time SKU pricing
  • Outputagent-output/{project}/02-architecture-assessment.md

Step 3: Design Artifacts (Artisan | Optional)

  • Architecture Diagramsazure-diagrams skill generates Python-based diagrams
  • Decision Recordsazure-adr skill creates Architecture Decision Records
  • Outputagent-output/{project}/03-des-*.md/.py/.png

Step 4: Planning (Strategist)

  • Governance Discovery — Discovers Azure Policy constraints in target subscription
  • Implementation Planbicep-plan agent creates detailed, phased implementation plan
  • GATE: Plan Approval — User reviews and approves before implementation
  • Outputagent-output/{project}/04-implementation-plan.md

Step 5: Implementation (Forge)

  • Bicep Generationbicep-code agent creates AVM-first Bicep templates
  • Preflight Validation — Lint, what-if, and review subagents validate code
  • GATE: Pre-Deploy — User reviews validation results
  • Outputinfra/bicep/{project}/ with 05-implementation-reference.md

Step 6: Deployment (Envoy)

  • Azure Provisioningdeploy agent executes deployment with what-if preview
  • GATE: Post-Deploy — User verifies deployed resources
  • Outputagent-output/{project}/06-deployment-summary.md

Step 7: Documentation

  • As-Built Suiteazure-artifacts skill generates comprehensive documentation
  • Outputagent-output/{project}/07-*.md (design doc, runbook, DR plan, inventory)

(back to top)


⚡ Quick Start

⚡ Quick Start

Prerequisites

Requirement Details
🐳 Docker Desktop Or Podman, Colima, Rancher Desktop
💻 VS Code With Dev Containers extension
🤖 GitHub Copilot Active subscription with Chat extension
☁️ Azure subscription Optional for learning, required for deployment

1️⃣ Clone and Open

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

2️⃣ Start Dev Container

Press F1Dev Containers: Reopen in Container

⏱️ First build takes 2-3 minutes. All tools are pre-installed.

3️⃣ Enable Custom Agent Subagents

⚠️ Required Setting: In your VS Code User Settings (Ctrl+,), enable:

{ "chat.customAgentInSubagent.enabled": true }

Without this, the Conductor cannot delegate to specialized agents.

4️⃣ Start the Conductor

Press Ctrl+Shift+I → Select InfraOps Conductor from the agent dropdown

5️⃣ Try It

Create a web app with Azure App Service, Key Vault, and SQL Database

The Conductor will guide you through all 7 steps with approval gates. Say yes to continue, or provide feedback to refine.

📖 Full Quick Start Guide →

(back to top)


Usage Examples

Usage Examples

Example: E-Commerce Platform

User: Create an e-commerce platform with AKS, Cosmos DB, and Redis caching

Conductor:
  ├─ @requirements → 01-requirements.md (functional, NFRs, compliance)
  ├─ @architect → 02-architecture-assessment.md (WAF analysis, cost estimate)
  │   └─ Azure Pricing MCP (real-time SKU pricing)
  ├─ azure-diagrams skill → 03-des-diagram.py/.png
  ├─ @bicep-plan → 04-implementation-plan.md (governance constraints)
  │
  │   [GATE 1: User approves plan]
  │
  ├─ @bicep-code → infra/bicep/ecommerce/
  │   ├─ @bicep-lint-subagent → Syntax validation ✓
  │   ├─ @bicep-whatif-subagent → What-if preview ✓
  │   └─ @bicep-review-subagent → AVM compliance ✓
  │
  │   [GATE 2: User approves pre-deployment]
  │
  ├─ @deploy → 06-deployment-summary.md
  │
  │   [GATE 3: User verifies deployment]
  │
  └─ azure-artifacts skill → 07-*.md (design doc, runbook, DR plan)

Direct Agent Invocation

You can also invoke agents directly for specific tasks:

# Gather requirements only
Ctrl+Shift+A → requirements → "Capture requirements for a static web app"

# WAF assessment only
Ctrl+Shift+A → architect → "Assess the requirements in 01-requirements.md"

# Diagnose existing resources
Ctrl+Shift+A → diagnose → "Check health of my App Service apps"

(back to top)


Skills (Reusable Capabilities)

Skills (Reusable Capabilities)

8 skills provide reusable capabilities across agents:

Skill Purpose Output
azure-adr Architecture Decision Records 03-des-adr-*.md
azure-artifacts Template H2 structures, styling, generation rules 01-07 artifacts
azure-defaults Azure conventions, naming, AVM, WAF, pricing, tags
azure-diagrams Architecture diagrams (700+ Azure icons) .py + .png
docs-writer Repo-aware documentation maintenance
git-commit Conventional commit messages
github-operations GitHub issues, PRs, CLI, Actions, releases
make-skill-template Create new skills from template

(back to top)


Generated Artifacts

Generated Artifacts

Workflow Artifacts

Phase Artifact Description
1 01-requirements.md Functional, non-functional, compliance requirements
2 02-architecture-assessment.md WAF analysis, SKU recommendations, cost estimate
3 03-des-*.md/.py/.png Diagrams, ADRs, cost estimates
4 04-implementation-plan.md Phased implementation plan with governance
4 04-governance-constraints.md Azure Policy discovery results
5 05-implementation-reference.md Bicep module inventory and validation status
6 06-deployment-summary.md Deployed resources and verification
7 07-design-document.md Technical design documentation
7 07-operations-runbook.md Day-2 operations procedures
7 07-backup-dr-plan.md Backup and disaster recovery plan
7 07-resource-inventory.md Complete resource inventory

Sample Outputs

Explore complete workflow outputs in agent-output/:

Project Description Highlights
e2e-conductor-test End-to-end Conductor validation Full 7-step workflow
static-webapp Static Web App with Functions Production-ready pattern

(back to top)


🧩 MCP Integration

🧩 MCP Integration

Microsoft Azure MCP Server

The core enabler behind "agents with real Azure context":

Feature Description
RBAC-Aware Tools operate within your existing Azure permissions
Broad Coverage 40+ Azure service areas: platform, monitoring, governance
Day-0 to Day-2 Discovery, validation, and troubleshooting workflows

📖 Azure MCP Server →

💰 Pricing MCP Add-on

Real-time Azure retail pricing for cost-aware SKU decisions. Pre-configured in this repo.

📖 Pricing MCP Documentation →

(back to top)


📁 Project Structure

📁 Project Structure

├── 📁 .github/
│   ├── 📁 agents/             # 8 main agents + 3 validation subagents
│   │   ├── infraops-conductor.agent.md  # 🎼 Maestro - Master orchestrator
│   │   ├── requirements.agent.md        # 📜 Scribe - Requirements capture
│   │   ├── architect.agent.md           # 🏛️ Oracle - WAF assessment
│   │   ├── design.agent.md              # 🎨 Artisan - Diagrams/ADRs
│   │   ├── bicep-plan.agent.md          # 📐 Strategist - Planning
│   │   ├── bicep-code.agent.md          # ⚒️ Forge - Bicep generation
│   │   ├── deploy.agent.md              # 🚀 Envoy - Deployment
│   │   ├── diagnose.agent.md            # 🔍 Sentinel - Diagnostics
│   │   └── 📁 _subagents/               # Validation subagents
│   ├── 📁 instructions/       # Guardrails and coding standards
    └── 📁 skills/             # 8 reusable skills
├── 📁 agent-output/           # Generated artifacts per project
├── 📁 docs/                   # Documentation and guides
├── 📁 infra/bicep/            # Generated Bicep templates
├── 📁 mcp/azure-pricing-mcp/  # 💰 Pricing MCP add-on
└── 📁 scenarios/              # 9 hands-on learning scenarios

(back to top)


Configuration

Configuration

VS Code Settings

Required (in devcontainer.json or User Settings):

{
  "chat.customAgentInSubagent.enabled": true,
  "chat.agentFilesLocations": {
    ".github/agents": true,
    ".github/agents/_subagents": true
  },
  "chat.agentSkillsLocations": {
    ".github/skills": true
  }
}

Recommended (in .vscode/settings.json):

{
  "github.copilot.chat.responsesApiReasoningEffort": "high",
  "chat.thinking.style": "detailed"
}

Customizing Agents

Each agent is defined in a .agent.md file that you can modify:

  1. Adjust AI Model — Change the model field in frontmatter
  2. Modify Instructions — Edit the main section to change behavior
  3. Add Tools — Extend the tools array for additional capabilities

(back to top)


Best Practices

Best Practices

  1. Use the Conductor for complete workflows — Let it orchestrate the full 7-step cycle
  2. Review artifacts at each gate — The approval points are designed for human oversight
  3. Leverage preflight validation — Let the subagents catch issues before deployment
  4. Trust the WAF process — The architect agent enforces best practices
  5. Commit frequently — After each approved phase, commit the artifacts
  6. Delegate appropriately — Use direct agent invocation for focused tasks

(back to top)


🎯 Scenarios

🎯 Scenarios

9 hands-on scenarios from beginner to advanced (15-45 min each):

Level Scenarios
Beginner Bicep baseline, diagrams as code
Intermediate Documentation generation, service validation, troubleshooting, SBOM
Advanced Full agentic workflow, async coding agent, orchestration test

📖 Full Scenarios Guide →

(back to top)


📋 Requirements

📋 Requirements

Requirement Details
VS Code With GitHub Copilot
Dev Container Docker Desktop or Codespaces
Azure subscription For deployments (optional for learning)

Included in Dev Container:

  • ✅ Azure CLI with Bicep extension
  • ✅ PowerShell 7+ and Python 3.10+
  • ✅ All required VS Code extensions
  • ✅ Pricing MCP add-on (auto-configured)
  • ✅ Python diagrams library (auto-installed)

(back to top)


🤝 Contributing

🤝 Contributing

Contributions are welcome! See CONTRIBUTING.md for guidelines.

(back to top)


📄 License

📄 License

MIT License. See LICENSE for details.

(back to top)


Acknowledgments

Acknowledgments

This project builds upon the excellent work of:

  • copilot-orchestra by ShepAlderson — Foundation for multi-agent orchestration patterns
  • Github-Copilot-Atlas by bigguy345 — Inspiration for context conservation and parallel execution

(back to top)


Made with ❤️ by Jonathan Vella

GitHub Repo

🔗 Shortlink: aka.ms/agenticinfraops

For Tasks:

Click tags to check more tools for each tasks

For Jobs:

Alternative AI tools for azure-agentic-infraops

Similar Open Source Tools

For similar tasks

For similar jobs