Azure Infrastructure - What Not to Do
summary
Countless teams leave anonymous blob access enabled or forget network planning and then hit overlapping IP spaces during migration; blob anonymous is off by default but mistakes happen. Use Key Vault and managed identity instead of SQL auth, enforce MFA, and run pen tests. Buy reservations or savings plans to cut costs — reservations can save up to 75% on VMs and savings plans ~30% on compute — and set budgets to avoid surprise £7,000+ bills. Test DR with Azure Site Recovery test-failover; some regions suffer 12-hour outages.
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
22mAzure Infrastructure - What Not to Do
20mThe 10 Most Common Azure Mistakes (And How To Fix Them)
32m5 Things to Check Before Running Critical Workloads on Azure VMs
49mAzure DevOps security - Lessons learned
45mCloud Computing: Cloud in a cost-effective way
53mTop 18 Azure security fails and how to avoid them
20mAzure: Maxmise your bang for Buck
46m10 Strategies to keep your Cloud costs under control