Chaos Engr at Microsoft with Azure Chaos Studio
summary
Azure Chaos Studio is a fully-managed chaos engineering platform integrated with ARM, Policy and Bicep, currently in public preview and used by 50+ Microsoft cloud services. It injects real faults (VM shutdowns, CPU pressure, AZ down), provides experiment templates for major Azure outages, and enforces permissions and targeting for safety. Examples: Power Platform reproduces region failure to fix failed failover; Key Vault finds autoscale misconfiguration in pre-production. Emphasis is on shifting left, quantifying outage cost, and closing observability gaps.
AI-written summary · about
chapters (20)
- 0:00Chaos engineering at Microsoft
- 1:04Meet the speaker
- 1:47Defining resilience
- 4:41Quality in service lifecycle
- 7:16Cloud-native resilience challenges
- 10:10Shared responsibility in cloud
- 11:54Azure Chaos Studio
- 12:16Scientific method in chaos
- 15:05Shift left vs shift right
- 17:13Production vs pre-production chaos
- 19:01Key features of Chaos Studio
- 21:51Safety in Chaos Studio
- 22:12Chaos engineering at Microsoft
- 24:03Shift left for outages
- 25:30Case study: Power Platform
- 26:34Case study: Azure Key Vault
- 27:39Key insights from Microsoft
- 30:05Confidence in pre-production
- 31:32Culture of quality
- 32:14Closing and resources
related talks
34mResilient Cloud App: Chaos Engineering, Azure Studio
25mImprove Application Resilience using Azure Chaos Studio
32mImplementing Chaos Engineering in Kubernetes
01h 01mEmbrace chaos to achieve stability
18mChaos Engineering: Break It On Purpose
45mApplication reliability with Azure Load Testing and Chaos Studio Q&A
34mStress-Test tools in Azure to optimize your reliability
39mMake Cloud Native Chaos Engineering Easier - Deep Dive into Chaos Mesh