YouTube Video
Azure CTO Mark Russinovich talks to Adam Bogobowicz on what it actually takes to keep the cloud resilient, from a 2014 near-outage to the new risks AI agents introduce.
In 2014, a small performance fix for Xbox nearly took down Azure worldwide. Microsoft Azure CTO Mark Russinovich uses that story to open a much bigger conversation about what resilience actually means at cloud scale, and how that definition keeps changing.
From there, the conversation moves through how Azure tests for failure on purpose, how machine learning redefined what "healthy" means for a service, and what physically breaks inside a data center running millions of servers. The back half of the conversation turns to the newest challenge: AI is non-deterministic, which breaks the assumptions on which Azure's resilience practices were built, and Mark walks through the guardrails, trust models, and accountability questions that come with it. The conversation closes on how resilience is a cost decision, no longer just an engineering concern, and where the Well-Architected Framework and Cloud Adoption Framework fit.
Resources
- Read the companion article: Your Architecture Diagram is not Your Resilience https://azure.microsoft.com/en-us/blog/your-architecture-diagram-is-not-your-resilience/
- Explore the Well-Architected Framework: https://learn.microsoft.com/azure/well-architected
- Explore the Cloud Adoption Framework: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/
- Learn about Azure Chaos Studio: https://learn.microsoft.com/en-us/azure/chaos-studio/
Chapters
0:00 When Azure almost went down worldwide
1:15 How a small Xbox fix broke storage worldwide
3:18 How does Azure deploy changes safely now?
4:15 How does Azure test for failure on purpose?
5:55 How does Azure define a healthy service?
8:50 What actually breaks inside an Azure data center?
11:30 How AI speeds up Azure incident response
12:55 Why AI breaks Azure's old resilience assumptions
14:40 How Azure keeps AI agents in check
16:23 Can you trust what the AI just did?
20:32 Why humans stay accountable for AI actions
23:37 Where to learn Azure's resilience frameworks
24:54 How much should you pay for resilience?
26:00 Why the previous era of documentation is ending
In 2014, a small performance fix for Xbox nearly took down Azure worldwide. Microsoft Azure CTO Mark Russinovich uses that story to open a much bigger conversation about what resilience actually means at cloud scale, and how that definition keeps changing.
From there, the conversation moves through how Azure tests for failure on purpose, how machine learning redefined what "healthy" means for a service, and what physically breaks inside a data center running millions of servers. The back half of the conversation turns to the newest challenge: AI is non-deterministic, which breaks the assumptions on which Azure's resilience practices were built, and Mark walks through the guardrails, trust models, and accountability questions that come with it. The conversation closes on how resilience is a cost decision, no longer just an engineering concern, and where the Well-Architected Framework and Cloud Adoption Framework fit.
Resources
- Read the companion article: Your Architecture Diagram is not Your Resilience https://azure.microsoft.com/en-us/blog/your-architecture-diagram-is-not-your-resilience/
- Explore the Well-Architected Framework: https://learn.microsoft.com/azure/well-architected
- Explore the Cloud Adoption Framework: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/
- Learn about Azure Chaos Studio: https://learn.microsoft.com/en-us/azure/chaos-studio/
Chapters
0:00 When Azure almost went down worldwide
1:15 How a small Xbox fix broke storage worldwide
3:18 How does Azure deploy changes safely now?
4:15 How does Azure test for failure on purpose?
5:55 How does Azure define a healthy service?
8:50 What actually breaks inside an Azure data center?
11:30 How AI speeds up Azure incident response
12:55 Why AI breaks Azure's old resilience assumptions
14:40 How Azure keeps AI agents in check
16:23 Can you trust what the AI just did?
20:32 Why humans stay accountable for AI actions
23:37 Where to learn Azure's resilience frameworks
24:54 How much should you pay for resilience?
26:00 Why the previous era of documentation is ending
SOCIAL SHARE CARD GENERATOR