Community tooling, samples, and scenarios for Azure Chaos Studio, the managed fault-injection service for Azure: introduce faults on purpose and observe how your system responds.
This is the open-source companion repo. The service is documented at learn.microsoft.com/azure/chaos-studio. What lives here is community tooling and samples — not the service source.
| Component | Path | What it is |
|---|---|---|
| Copilot CLI plugin + MCP server | copilot-cli-plugin/ |
Create workspaces, configure scenarios, run experiments, and analyze impact — from a conversation or an autonomous agent. Includes the chaos-study skills, which make chaos accessible to your SRE, your engineers, and your agent: guided, conversational help for planning and running targeted experiments without hand-authoring them. Recommended host: Azure SRE Agent; other skill-capable agents (GitHub Copilot CLI, Claude Code, Codex, …) can also load them. |
| Scenarios | scenarios/ |
Shareable custom Scenario definitions (Bicep/JSON) beyond the built-in templates. |
| Samples | samples/ |
Sample apps and infrastructure you can deploy and break to practice. |
Start with the docs: Workspaces · Scenarios · Scenario reports.
We want it. Open an issue for bugs and feature requests, or start a Discussion for questions and ideas.
See CONTRIBUTING.md. This project follows the Microsoft Open Source Code of Conduct and the Microsoft CLA.