5 Things to Check Before Running Critical Workloads on Azure VMs
summary
Five concrete checks before putting critical workloads on Azure VMs: create a storage account before VM and choose redundancy (LRS, GRS or read‑only GRS) — storage has practical limits like a 500 TB limit per account and ~20k IOPS so use multiple accounts (subscriptions allow many, often up to 100) for throughput; enforce virtual network required for internal IPs and choose VIP vs PIP vs dynamic IP, use point‑to‑site or site‑to‑site IPSec for on‑prem links; use an availability set (≥2 VMs) to separate fault and update domains; enable VM backups (Azure Backup preview or existing tools), monitoring, automation and verify compliance via the Azure Trust Center / ISO 27000 18.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:58Five critical aspects overview
- 4:24Storage best practices and limits
- 10:01Networking fundamentals and IP types
- 18:50Storage account demo
- 22:43High availability and backups
- 28:50Operations and monitoring tools
- 30:58Compliance and Q&A
related talks
22mAzure Infrastructure - What Not to Do- 22mAzure Infrastructure - What Not to Do
45mRunning a Real-World, Mission-Critical System on Azure
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
53mTop 18 Azure security fails and how to avoid them
54mAzure Best Practices for Lift and Shift
46mDeep dive into Azure Virtual Machine Scale Sets
15mWell-Architected Framework: Performance Efficiency