Need to run a custom application but don’t want to buy a server? A virtual machine (VM) gives you a computer you can configure without owning its hardware. Virtualization divides a physical computer’s processors, memory, and storage into separate virtual computers. In Azure, the hardware layer is managed for you; the operating system and software remain yours to choose. section 3.1 section 3.1.1
A VM is an infrastructure-as-a-service (IaaS) option: close enough to the hardware to give you substantial control, without making you maintain a physical server. That makes it useful for software with particular installation requirements, including legacy applications and custom backend processes. You can choose Windows or Linux and adjust capacity as demand grows. section 3.1 section 3.1.4
A growing application
Suppose your project needs a custom application, operating-system control, and room to grow, but has little budget for hardware. Start with a VM sized for current demand. If usage rises, you can increase its size, add VMs, or expand disk capacity. Start small: an oversized VM can spend money on idle capacity. section 3.1 section 3.8
To put a VM to work in Azure:
- Create it in the Azure Portal’s Virtual Machine area, beginning with a subscription, resource group, and name. Azure CLI, PowerShell, and templates are alternatives when you want a different workflow or more automation. section 3.2
- Choose a region, operating-system image, and size with price and capacity in mind. Attach the VM to a virtual network, then plan how you’ll connect: RDP, SSH, or Bastion are available options. section 3.8
- If remote access requires an open port, restrict access with a network security group rather than leaving the door wide open. section 3.8
Control comes with chores. Azure manages the physical servers, network, and storage, but you remain responsible for the VM’s operating system, applications, user and data access, and network access. Azure Automanage can help with updates, monitoring, backups, security, and other recommended configurations; you can also manage these yourself. section 6.2.2 section 3.1.4
Keep checking whether the VM still earns its keep. Auto shutdown can save money when it is not needed; spot instances offer discounts but can be reclaimed, while reserved instances trade a longer commitment for savings. Azure Monitor metrics, logs, and alerts help you spot trouble before users do. section 3.8
