Module 1 — Introduction to Azure virtual machines

Grounded in MS Learn: az-104-manage-compute-resourcesIntroduction to Azure virtual machines (learn.introduction-to-azure-virtual-machines)

Overview

First module of the AZ-104 compute path. Learn the decisions you make before creating a virtual machine: what to plan for, the compute/size choice, storage/count of disks, and the tooling used to create and operate the VM.

Units (from learning objectives)

  • Compile a checklist for creating a virtual machine
  • Options to create and manage virtual machines
  • Additional services used to administer VMs (extensions, monitoring, backup)

Learning objectives (authoritative)

  1. Compile a checklist for creating a virtual machine.
  2. Describe the options to create and manage virtual machines.
  3. Describe the additional services available to administer virtual machines.

Concepts introduced

  • Azure Virtual Machine — IaaS computing with full guest-OS control.
  • VM sizes & families — vCPU/memory profile selection.
  • Managed disks — OS + data disk types, ephemeral OS disk.
  • VM extensions — post-deploy guest automation (e.g. Custom Script Extension).
  • Logistics: resource group, region, networking (VNet/subnet), authentication, and availability options ([[]] availability-set / availability-zones planned later).

Key terms & commands

  • Provision: az vm create --resource-group <rg> --name <vm> --image UbuntuLTS --size Standard_D2s_v3 --generate-ssh-keys
  • Manage: az vm start / stop / deallocate / restart / redeploy, az vm list, az vm show
  • Sizes: az vm list-sizes --location <region>
  • Create checklist: resource group → size (right-size vCPU/RAM) → OS + image → disks (type/tier, ephemeral vs persistent) → networking & public IP → auth (SSH keys / password / Entra) → availability (set vs zones vs none) → extensions & monitoring.

Hands-on

  • Create a Linux VM via CLI, connect with SSH, install software via Custom Script Extension rather than manual login.
  • Compare ephemeral vs persistent OS disk behavior (deallocate → restart → data loss on ephemeral).

Exam focus

  • The pre-creation checklist and choosing an appropriate size/family for the workload.
  • Deallocate vs delete: deallocated VM still bills for disks but not CPU; delete removes resources.
  • Recognize VM administration services: extensions, Azure Monitor, backup, Virtual Machine Scale Sets.

Path MOC · azure-vm · vm-sizes · managed-disks · vm-snapshot · azure-vm-extension · Next: VM availability