An experimentation platform for improving app resiliency
Explore the benefits of Azure Chaos Studio
Subject your Azure applications to real or simulated faults
Observe how your applications respond to real-world disruptions
Integrate chaos experiments into any phase of quality validation
Use the same tools as Microsoft engineers to build resilience of cloud services
Improve the reliability of your Azure applications
Experiment on your own terms
Gain insights without the chaos of getting started
Go beyond fault injection with reliability validation
Comprehensive security and compliance, built in
-
Microsoft invests more than $1 billion annually on cybersecurity research and development.
-
We employ more than 3,500 security experts who are dedicated to data security and privacy.
-
Azure has more certifications than any other cloud provider. View the comprehensive list.
-
Chaos Studio pricing
Chaos Studio Preview has no upfront costs or fees. Pay as you go based on experiment execution—chaos engineering experiments are charged based on the duration that your experiment actions run across each target or resource.
Get started with an Azure free account
1
Start free. Get $200 credit to use within 30 days. While you have your credit, get free amounts of many of our most popular services, plus free amounts of 55+ other services that are always free.
2
After your credit, move to pay as you go to keep building with the same free services. Pay only if you use more than your free monthly amounts.
3
After 12 months, you'll keep getting 55+ always-free services—and still pay only for what you use beyond your free monthly amounts.
Chaos Studio resources and documentation
Learn more about reliability
Frequently asked questions about Azure Chaos Studio
-
Chaos engineering is the practice of subjecting applications and services to real-world stresses and failures to build and validate resilience to unreliable conditions and missing dependencies.
-
Chaos Studio has a growing library of faults.
View the current list.
-
Chaos experiments require explicit granular permission to inject faults against resources.