Azure Infrastructure - What Not to Do
summary
Lists concrete failures seen in Azure: leaving anonymous blob access enabled, poorly planned networks causing overlapping IP spaces, and barely any penetration testing (about 4% do it). Recommends using Key Vault and managed identity, enforcing MFA, and applying 75% savings via reservations or compute savings plans to avoid surprise bills. Notes free passive SQL DR licensing, failed 5 TB exports, real outages like a 12‑hour Singapore zone event, and always testing DR with Azure Site Recovery test failover so recovery actually works.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:52Azure infrastructure mistakes
- 3:34Locking doors in Azure
- 4:17Azure network planning
- 5:45Azure attack vectors
- 7:12Azure security features
- 8:15Enforcing MFA
- 9:20Azure costs and savings
- 10:23Wrong Azure solutions
- 13:11Azure migration pitfalls
- 14:59Wrong migration path
- 15:42Azure disaster recovery myths
- 16:48Wrong DR strategy
- 17:49Testing DR plans
- 19:36Azure infrastructure pitfalls
- 21:22When not to move to Azure
related talks
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
45mRunning a Real-World, Mission-Critical System on Azure
31mBuilding Big Data Platforms: the Hidden Security Flaws You Need to Be Aware Of
54mDesigning Azure Data Disaster Recovery Strategies
57mDe-risk Your Azure SQL Migration: 5 Critical Considerations
54mAzure Best Practices for Lift and Shift
59mWhat's new on Azure IaaS for SQL Server VMs
43mDefending the Cloud: Securing Your Microsoft Data Workloads