Ubuntu 22.04 arm64

Option A: Azure Portal

• Open the Azure Marketplace and search for "Ubuntu 22.04 LTS Arm64 SecureAnyCloud"
• Select the image and choose Create
• Configure the basics:
• Subscription: Select your Azure subscription
• Resource Group: Create new or select existing
• Virtual machine name: Enter a name for your VM
• Region: Select your preferred Azure region
• Size: Standard_D2ps_v6 recommended (an Arm64 size)
• Under Administrator account, select SSH public key and enter your key
• Under Inbound port rules, allow SSH (port 22)
• Select Review + create, then Create

Option B: Azure CLI

Accept the Marketplace terms, then create the VM:

az vm image terms accept --urn sac1647283583153:ubuntu-22-04-arm64:default:latest
az vm create \
  --resource-group myResourceGroup \
  --name my-ubuntu-arm64-vm \
  --image sac1647283583153:ubuntu-22-04-arm64:default:latest \
  --size Standard_D2ps_v6 \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

The --size must be an Arm64 family (Standard_D2ps_v6 above). Azure rejects an x86 size for an Arm image at create time.

Run these commands on your own workstation, not on the VM. Find the public IP, then connect:

az vm show --resource-group myResourceGroup --name my-ubuntu-arm64-vm --show-details --query publicIps -o tsv ssh azureuser@<vm-ip>

There is no password to enter. If SSH asks for one, the key you supplied at create time is not the key your client is offering.

Check that the machine runs the Ubuntu 22.04 LTS release you expect, and confirm that it is running on Arm:

grep -E '^(NAME|VERSION|ID|VERSION_ID|PRETTY_NAME)=' /etc/os-release uname -srm dpkg --print-architecture

Expected output:

NAME="Ubuntu" VERSION="22.04.5 LTS (Jammy Jellyfish)" ID=ubuntu VERSION_ID="22.04" PRETTY_NAME="Ubuntu 22.04.5 LTS" Linux 6.8.0-1064-azure aarch64 arm64

aarch64 from uname and arm64 from dpkg both confirm this is the native 64-bit Arm build, not an emulated or x86 image.

The image is fully updated at build time. Confirm that no upgrades are pending and that the update path is intact:

apt-get -s -o APT::Get::Always-Include-Phased-Updates=true dist-upgrade | grep -c '^Inst ' | sed 's/^/pending upgrades: /' apt-mark showhold dpkg -l | awk '/linux-image-[0-9]/{print $2, $3}'

Expected output shows pending upgrades: 0, no held packages, and the installed Arm kernel:

pending upgrades: 0 linux-image-6.8.0-1064-azure 6.8.0-1064.72~22.04.1

The Always-Include-Phased-Updates=true flag matters on Ubuntu. Without it, a plain check can silently hide phased security updates held back on this particular machine.

This image also arms unattended-upgrades, so security updates are downloaded and applied on a timer without any action from you. You can still run updates on your own schedule:

sudo apt-get update && sudo apt-get -y dist-upgrade

Reboot if a new kernel was installed:

sudo systemctl reboot

Confirm that AppArmor is enforcing, root is locked, and SSH accepts keys only:

sudo aa-status --enabled && echo "apparmor: enabled"
sudo passwd -S root
sudo sshd -T | grep -E '^(permitrootlogin|passwordauthentication|pubkeyauthentication) '

Expected output:

apparmor: enabled root L 08/06/2026 0 99999 7 -1 permitrootlogin without-password pubkeyauthentication yes passwordauthentication no

without-password is how OpenSSH reports the prohibit-password setting. Both names mean the same thing: root may not authenticate with a password. The L from passwd -S means the root account is locked.

Confirm that the Azure Linux Agent, cloud-init and time synchronisation are healthy and that unattended security updates are armed. Then check your resources:

systemctl is-active walinuxagent 2>/dev/null || systemctl is-active waagent cloud-init --version
systemctl is-enabled apt-daily-upgrade.timer apt-config dump | grep -E 'APT::Periodic::(Update-Package-Lists|Unattended-Upgrade) '
systemctl is-active chrony df -h / free -h

The Azure Linux Agent lets Azure provision your SSH key, resize the OS disk, run extensions and report VM health, so it should always be active.

The apt-daily-upgrade.timer unit being enabled, together with Unattended-Upgrade "1" in the apt periodic config, keeps the machine applying security updates on its own after launch.

The Azure Network Security Group (NSG) controls inbound and outbound traffic. It is the first and usually the only place you need to open a port. The image advertises a single inbound port, SSH on 22.

ufw (the Uncomplicated Firewall) is available on this image but left inactive by default. It does not filter traffic, so your NSG rules take effect exactly as written, with no second layer to keep in sync. Confirm what is listening before you open anything:

ss -tlnp

On a fresh machine, the main listener is sshd on port 22. Only port 22 is advertised for inbound access, and the Azure NSG governs what is actually reachable from outside.

If your policy requires a host firewall as well, enable the one that is already installed. Add the SSH rule first, before you enable ufw, so you do not lock yourself out:

sudo ufw allow OpenSSH
sudo ufw allow 443/tcp
sudo ufw enable

Once ufw is running, open each port in both the Azure NSG and ufw before traffic can reach your service.

The Ubuntu archive carries the application packages. Search it, then install what you need:

apt-cache search nginx 2>/dev/null | sed -n '1,5p'

Install a package and enable it in the usual way, for example sudo apt-get install -y nginx followed by sudo systemctl enable --now nginx.

Everything in the archive is built for Arm, so apt resolves arm64 packages automatically. Nothing extra needs configuring for the architecture.

The image ships with no human accounts at all, so azureuser is the only login until you add one. To add another administrator:

• Create the account with sudo adduser <name>.
• Add it to the sudo group with sudo usermod -aG sudo <name>.
• Copy your public key into /home/<name>/.ssh/authorized_keys, with mode 600 and the .ssh directory mode 700, owned by that user.

Then check the sudo group:

getent group sudo