Azure Infrastructure - What Not to Do
summary
Covers concrete failures seen in Azure deployments and fixes: misconfigured blob storage or anonymous access, overlapping IP blocks from poor network planning, and lift‑and‑shift migrations that kill latency. Recommends Azure Key Vault and Managed Identity instead of SQL auth, enforce MFA, use budgets and Azure Reservations or Savings Plans to cut costs (reservations up to ~75%, compute savings ~30%), enable Hybrid Benefit and free SQL DR licensing where applicable, pick and test an appropriate DR solution such as Azure Backup or Azure Site Recovery and run test failovers.
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)
53mTop 18 Azure security fails and how to avoid them
32m5 Things to Check Before Running Critical Workloads on Azure VMs
45mRunning a Real-World, Mission-Critical System on Azure
46mI Find Your Lack of Azure Disturbing
49mWhat to look out for when migrating your data to the cloud; is it REALLY the right choice?
49mAzure DevOps security - Lessons learned