Edit

Tutorial: Deploy and manage a virtual machine application with Azure CLI (preview)

In this tutorial, you use Azure CLI preview to run a small web application on a Linux virtual machine (VM), confirm that the application survives routine VM operations, and then remove everything you created.

When you finish, you've served a web page from the VM, confirmed that the page returns after the VM stops and starts, and verified that all the tutorial resources are deleted.

In this tutorial, you:

  • Prepare the environment
  • Deploy the virtual machine
  • Run the application
  • Operate the virtual machine
  • Clean up

Prerequisites

  • Bash or zsh on Linux or macOS, or PowerShell 7.6 or later on Windows.
  • Azure CLI preview, installed and signed in as described in Set up and switch sign-in profiles.
  • OpenSSH tools (ssh and ssh-keygen) and, for the Bash path, curl.
  • An existing network security group (NSG) in the VM's region that allows SSH (port 22) and HTTP (port 80) only from your IP address, and outbound access for Ubuntu packages.

You need an Azure subscription. If you don't have one, create a free account.

Verify the SSH host fingerprint when prompted. Don't disable host-key checking.

Set variables

sub="<test-subscription-id>"
location="<region>"
nsg_id="<existing-NSG-resource-ID>"
run=$(date +%Y%m%d%H%M%S)
rg="azclips-app-$run"
vm="app-$run"
pip="$vm-pip"
admin="azadmin"
image="Canonical:0001-com-ubuntu-server-jammy:22_04-lts-gen2:latest"
key="/tmp/$vm-key"

Prepare the environment

az group create --subscription-id "$sub" --name "$rg" --location "$location"
az network public-ip create --subscription-id "$sub" --resource-group "$rg" --name "$pip" --location "$location" --sku Standard --allocation-method Static --version IPv4

Each command returns the new resource with "provisioningState": "Succeeded". The public IP address is static, so it doesn't change when the VM stops and starts.

Deploy the virtual machine

ssh-keygen -t ed25519 -f "$key" -C "azclips-$run"
az vm create --subscription-id "$sub" --resource-group "$rg" --name "$vm" --location "$location" --size Standard_D2s_v3 --image "$image" --admin-username "$admin" --ssh-key-values "$key.pub" --network-interface-name "$vm-nic" --virtual-network-name "$vm-vnet" --address-prefixes 10.0.0.0/16 --subnet-names app --subnet-address-prefixes 10.0.2.0/24 --nsg "$nsg_id" --public-ip-address "$pip"
az vm show --subscription-id "$sub" --resource-group "$rg" --name "$vm"

ssh-keygen prompts for a passphrase and creates a key pair. az vm create waits until the VM is created. The az vm show output includes "provisioningState": "Succeeded".

Run the application

To confirm that the VM works end to end, install the nginx web server and serve a one-line page. A successful web request proves that the VM is running, that its public IP address and network security group let traffic through, and that the application starts on its own after a restart. Any workload that listens on port 80 works the same way.

ip=$(az network public-ip show --subscription-id "$sub" --resource-group "$rg" --name "$pip" --query properties.ipAddress --output tsv)
ssh -i "$key" "$admin@$ip" "sudo apt-get update && sudo apt-get install -y nginx && printf '%s\n' 'AzCLIPS scenario 2 is running' | sudo tee /var/www/html/index.html && sudo systemctl enable --now nginx"
curl -fsS --max-time 30 "http://$ip"

When you connect for the first time, ssh asks you to confirm the host fingerprint. After nginx is installed, the web request returns the page text AzCLIPS scenario 2 is running. In PowerShell, the script prints Page OK.

Operate the virtual machine

az vm stop --subscription-id "$sub" --resource-group "$rg" --name "$vm"
az vm start --subscription-id "$sub" --resource-group "$rg" --name "$vm"
curl -fsS --max-time 30 "http://$ip"

az vm stop and az vm start wait for each operation to finish. After the VM starts, the web request returns AzCLIPS scenario 2 is running again, because nginx is set to start automatically. Allow up to five minutes after each start for the page to return. The application is unavailable while the VM is stopped.

Optional: deallocate and start the VM, then repeat the check. Deallocating also releases the VM's compute resources, so you stop paying for them.

az vm deallocate --subscription-id "$sub" --resource-group "$rg" --name "$vm"
az vm start --subscription-id "$sub" --resource-group "$rg" --name "$vm"
curl -fsS --max-time 30 "http://$ip"

Clean up resources

az vm delete --subscription-id "$sub" --resource-group "$rg" --name "$vm"
az group delete --subscription-id "$sub" --name "$rg"
az group exists --subscription-id "$sub" --name "$rg"
rm -f "$key" "$key.pub"

az group delete waits until the resource group and its resources are deleted. az group exists then returns false.