Before you start / Requirements

Run workshop commands in Linux Bash, not PowerShell, CMD, or Git Bash. We recommend the supplied Dev Container in GitHub Codespaces on your own fork. WSL2 with Ubuntu, a local Linux Dev Container, or native Ubuntu are alternatives. Confirm Azure access, regional quota, and separate Azure/Codespaces costs before deploying.

Read requirements and environment setup →

Then run pre-flight checks in your Linux terminal and resolve failures with your coach: Azure Operations prerequisites or SQL Server DBA prerequisites. Container setup installs tools; it does not log in to Azure or deploy the lab.

Azure Operations Track

Configure the agent in Challenges 00–06, explore telemetry in 07–09, and investigate PaaS, IaaS, and network incidents in 10–15. Challenges 16–18 cover scheduled reporting and cost review. In Challenge 19, build and test your own use case and explain what it needs before production use. Coaches: press Shift+C to unlock solution guides.

00
Setup CH — 00

Prerequisites &
Lab Setup

Deploy the workloads with Terraform, create your Azure SRE Agent, and generate baseline traffic. Add the agent's capabilities in Challenges 01–06.

01
Config CH — 01

Connect Your
Codebase

Connect GitHub and link your repository. Verify that the agent can read source code and use GitHub actions within the configured scope.

02
Config CH — 02

Explore the
Knowledge Base

Add lab knowledge documents, then compare the agent's answers before and after upload. Check resource details and citations.

03
Config CH — 03

Discover Operational
Skills

Add the supplied skills so the agent can run KQL queries, inspect Container App health, and follow operational runbooks. Test its tool and approval boundaries.

04
Config CH — 04

Discover Connected
Systems

Connect Microsoft Learn through MCP so the agent can retrieve current Azure documentation. Verify its citations.

05
Config CH — 05

Discover Specialist
Agents

Add domain-specific subagents with their own instructions, tools, and runbooks. Compare their investigation plans with the main agent's.

06
Config CH — 06

Understand
Response Plans

Connect Azure Monitor and configure response plans. Compare an unmatched alert with one that starts an investigation, then inspect Review and Autonomous modes.

07
Autonomous CH — 07

Hybrid Ecosystem
Telemetry

The Parking Manager spans Container Apps, VMs, and a third-party OpenTelemetry API. Use the agent to query all three platforms and produce a unified cross-system view.

08
Autonomous CH — 08

Application Dependency
Mapping

Map Grubify dependencies from Application Insights, including call counts and response times. Add Berlin Parking API metrics as a separate telemetry source.

09
Autonomous CH — 09

Daily Application
Health Report

Ask the agent to generate a structured health report for all four Parking Manager APIs — CPU, memory, error rate, response time — with a health score and recommended remediation for any service falling below threshold.

10
Autonomous CH — 10

Incident to
GitHub Issue

Trigger a Parking Manager incident and have the agent create or update a GitHub issue with evidence, a timeline, and next steps. This workflow reports the incident; it does not restart a VM.

11
Autonomous CH — 11

Guest OS Failure
Investigation

Stop NGINX inside the web-tier VMs and watch the agent discover the failure from Syslog telemetry, assess the full blast radius across both VMs, and restore the service autonomously on every affected instance.

12
Autonomous CH — 12

Network Security
Investigation

Inject an NSG rule that blocks database traffic. Check whether the agent traces denied flows to the rule, removes it, and verifies recovery.

13
Interactive CH — 13

Routing Failure
Investigation

Introduce an asymmetric routing black hole where return packets never arrive. Drive a diagnostic conversation with the network-traffic-analyst over effective routes and next-hop analysis to find and fix the return path.

14
Autonomous CH — 14

Application Root
Cause Analysis

Trace a Grubify 5xx spike through container logs, Application Insights, and source code to the OOM fault path. Review the GitHub issue linking evidence to code.

15
Autonomous CH — 15

Autonomous
Remediation

Stop the Paris Parking API service. Check whether the agent restarts the VM, validates service and API health, and retries or escalates if recovery fails.

16
Scheduled CH — 16

Daily Network
Health Report

Create a scheduled task that reviews 24 hours of network telemetry every morning and produces a decision-ready summary: denied flows, top talkers, missing VNet coverage, and unusual ports.

17
Scheduled CH — 17

Observability
Freshness Verification

Check VNet Flow Log freshness in Storage and Traffic Analytics. Compare expected VNet coverage with recent records to find missing or stale telemetry.

18
Autonomous CH — 18

Subscription Cost
Optimization Review

Review inventory, spend, utilization, and Azure Advisor findings. Rank savings opportunities against workload criticality and SLAs without changing resources.

19
Capstone CH — 19

Build Your Own
Production-Ready SRE Agent

Bring a real reliability problem, build a focused agent configuration, and demonstrate an end-to-end test. Explain the controls and validation needed before production use.

SQL Server DBA track

Deploy a hardened SQL Server MCP server, then teach Azure SRE Agent to separate database facts from assumptions. Every investigation is bounded, observable, and deliberately non-destructive.

Managed identity SELECT only Estimated plans No auto-tuning
00
Trust boundary DBA — 00

Deploy the Read-Only
DBA Path

Deploy the supplied .NET MCP container, map its managed identity into the least-privilege observer role, secure the Streamable HTTP endpoint, and prove that Azure SRE Agent can inspect SQL without receiving a write path.

01
Discover DBA — 01

Orient to the
Database

Turn catalog metadata into a business map while keeping declared relationships separate from inferred domain meaning.

02
Baseline DBA — 02

Establish a Query
Store Baseline

Seed repeatable activity and define a trustworthy historical observation window before diagnosing regressions.

03
Interpret DBA — 03

Separate Duration
from Pressure

Observe a long-running wait and prevent elapsed time from becoming a false performance diagnosis.

04
Concurrency DBA — 04

Trace a
Blocking Chain

Identify the head blocker, blocked request, wait resource, and transaction age without terminating either session.

05
Tune DBA — 05

Build an Evidence-Based
Index Case

Correlate Query Store, the existing index set, and an estimated plan before recommending a change.

06
Query shape DBA — 06

Diagnose Query
Shape Problems

Find non-SARGable predicates and implicit conversions, then explain their access-path impact without rewriting production code.

07
Plan behavior DBA — 07

Investigate Parameter
Sensitivity

Compare skewed parameter populations, plan history, and runtime distributions before claiming parameter sensitivity.

08
Incident room DBA — 08

Triage a Combined
Database Incident

Correlate concurrent signals, rank findings by demonstrated impact, preserve alternative explanations, and deliver a decision-ready read-only handoff.

09
Capstone DBA — 09

Build Your Own SQL
Server DBA Agent

Design and validate a focused read-only investigation workflow for a database reliability question of your choosing.

Coach Coaches only — do not share with participants. Press Shift+C to hide.

Solution Guides

Mini-lectures, expected agent behavior, common failure modes, and debrief discussion guides. See the Azure Operations index or the SQL Server DBA index.

00
SOL — 00
Prerequisites & Lab Setup
TF deploy walkthrough, manual agent creation pitfalls, workload vs. control-plane split, pre-flight validation.
Open →
01
SOL — 01
Connect Your Codebase
GitHub connector vs. repo scope, apply order, source-boundary refusal demo.
Open →
02
SOL — 02
Explore the Knowledge Base
Retrieval-augmented grounding, the three knowledge families, before/after topology demo.
Open →
03
SOL — 03
Discover Operational Skills
Skill YAML anatomy, the nine certified skills, description-driven routing vs. least-privilege tools.
Open →
04
SOL — 04
Discover Connected Systems
Skills vs. connectors, Microsoft Learn MCP setup, before/after citation demo.
Open →
05
SOL — 05
Discover Specialist Agents
Subagents as scoped domain experts, the specialist roster, narrow tool grants as governance.
Open →
06
SOL — 06
Understand Response Plans
Incident filter routing stack, exact filter/task names, alert-driven vs. chat-driven response.
Open →
07
SOL — 07
Hybrid Ecosystem Telemetry
Azure-native vs. third-party telemetry planes, Berlin MCP connector, cross-plane summary reporting.
Open →
08
SOL — 08
Application Dependency Mapping
Requests vs. dependencies, Mermaid/ASCII topology output, dependency hotspot discovery.
Open →
09
SOL — 09
Daily Application Health Report
SLI/SLO reporting, Healthy/Degraded/Critical scoring, explicit N/A handling for missing telemetry.
Open →
10
SOL — 10
Incident to GitHub Issue
Incident report template, GitHub handoff, and follow-up comments with fresh evidence.
Open →
11
SOL — 11
Guest OS Failure Investigation
Platform health vs. guest-OS health, Syslog/AMA evidence, run-command remediation and blast-radius check.
Open →
12
SOL — 12
Network Security Investigation
Denied-flow forensics via Traffic Analytics, NSG rule identification, autonomous routing path.
Open →
13
SOL — 13
Routing Failure Investigation
UDR precedence, effective routes, asymmetric-path outages, autonomous vs. Review governance debate.
Open →
14
SOL — 14
Application Root Cause Analysis
Trace telemetry to the failing source code and record the evidence in a GitHub issue.
Open →
15
SOL — 15
Autonomous Remediation
Detect → remediate → validate → retry/escalate loop, autonomous MTTR vs. human-driven recovery.
Open →
16
SOL — 16
Daily Network Health Report
Scheduled network reporting across five dimensions. Verify that the specialist follows the report-only instruction.
Open →
17
SOL — 17
Observability Freshness Verification
"Monitoring the monitoring," flow-log ingestion evidence chain, desired-state vs. actual telemetry.
Open →
18
SOL — 18
Subscription Cost Optimization Review
Evidence-backed FinOps review, cost-optimization-agent schedule, and read-only recommendations.
Open →
19
SOL — 19
Build Your Own Production-Ready SRE Agent (Capstone)
Design checklist, building-blocks synthesis, production-readiness criteria, demo facilitation and debrief guide.
Open →
SQL Server DBA solutions