Microsoft Azure Learning Journey

Azure Virtual Machines: More Than a Server in the Cloud

A VM gives you control of the operating system—and responsibility for what runs inside it.

5 min read · 995 words
Microsoft AzureAzure ComputeContainersCloud ArchitectureDevOps
Azure Virtual Machines: More Than a Server in the Cloud cover image

A team lifts a legacy service into a virtual machine and expects the cloud provider to keep the operating system patched, the disk backed up, and the application available. Azure supplies compute infrastructure; it does not operate the guest OS for you. The VM is a flexible choice, but it transfers real operational work to your team.

What you’ll learn

Where this fits

Module 14 and Phase 4, Part 1. Phase 3 covered network paths; this phase chooses where workloads execute. Next: Handle Traffic Spikes with Azure VM Scale Sets.

Prerequisites

What an Azure VM includes

An Azure VM is a compute resource attached to supporting resources: a virtual network interface, operating-system disk, optional data disks, and often public or private IP resources. Azure supplies the hypervisor and physical infrastructure. You administer the guest operating system, packages, runtime, firewall, application, and patching policy.

Azure VM
├── Compute size + image
├── OS disk + optional data disks
├── Network interface -> subnet / NSG / routes
└── Optional public IP, diagnostics, backup, identity

Choose the machine, not just the price

An image defines an operating-system baseline. A VM size controls vCPU, memory, and other hardware characteristics. Compare expected load, memory pressure, disk throughput, network performance, and available quotas. Sizes and availability vary by region and subscription. A size appearing in a list does not guarantee quota or capacity.

Managed disks have performance and redundancy tiers. Separate OS, data, and temporary data according to durability requirements. Temporary disk contents are not durable storage. Backups and snapshots need their own retention, access, and restore plan.

Availability and maintenance

Availability zones, availability sets, and VM scale sets solve different availability and fleet-management problems. A single VM is a single instance of application capacity even if its disk is highly durable. For service continuity, design multiple instances, health checks, and data recovery.

Azure manages physical hosts and maintenance operations, but you still need to monitor and patch the guest OS. Use Azure Update Manager or a tested configuration-management approach. Boot diagnostics, serial console, and VM extensions can help operate a machine, but extensions run with significant VM privileges and should be governed.

Power state is not billing state

Stopping an OS from inside the VM can leave the VM allocated; compute charges can continue. A VM stopped/deallocated through Azure releases compute allocation, but attached disks and other resources can still incur charges. Never assume “stopped” means “free.” Confirm the displayed power state and review all attached resources.

Hands-on: compare sizes in a region

This command is read-only and lists size metadata for a region:

LOCATION="eastus"
az vm list-sizes --location "$LOCATION" \
  --query "[].{name:name, vCPUs:numberOfCores, memoryMB:memoryInMB}" \
  --output table

Use the output to compare candidate sizes, then check current regional availability, quota, and workload limits before deployment.

✅ Checkpoint: You can explain why a size listing is not a capacity guarantee and name the resources that remain billable after deallocation.

Security and cost

Troubleshooting

Five-pillar readiness checklist

Cleanup

No Azure resources were created. No cleanup is needed.

Key takeaways

Next: Handle Traffic Spikes with Azure VM Scale Sets.

Series navigation: Previous: Build a Private Azure Network · Current: Phase 4, Part 1 · Next: VM Scale Sets

References

Share this article

LinkedIn post draft