Virtual Machine Provisioning

I always thought provisioning a VM from the Azure portal was very easy — just a few clicks and done.
But today I realized there’s a lot more thinking involved behind the scenes 👇
Before creating a VM, we actually need to plan:
• Virtual network and subnet
• VM naming conventions
• Region selection (for better latency and cost optimization)
• Compute + storage pricing
Also, a VM isn’t just “one disk” like I assumed:
• OS Disk (mandatory)
• Temporary Disk (for short-term storage)
• Data Disk (optional, based on requirement)
Security is another key aspect:
Using NSG (Network Security Group), if inbound ports like 80 (HTTP) and 3389 (RDP) are allowed, only that traffic is permitted — everything else is blocked by default.
And when it comes to reliability and scaling:
• Availability Zones → protect from datacenter failures
• Availability Sets → use Fault Domains & Update Domains
• VM Scale Sets (VMSS) → handle scalability and load
👉 Lesson learned: Creating a VM is easy, but designing it properly requires planning, understanding, and the right architecture mindset.