Deploy Arm-based Cobalt 100 VMs using Azure Resource Manager templates
Introduction
Getting started with Azure Resource Manager
Create the Azure Resource Manager template
Deploy the Azure Resource Manager template
Connect to the Cobalt 100 VM and verify Arm64 architecture
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  45 min
Last updated:  29 Jun 2026
Skill level:
  Introductory
Reading time:
  45 min
Last updated:
  29 Jun 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: Containers and Virtualization Microsoft Azure Linux Azure CLI JSON
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
Containers and Virtualization Microsoft Azure Linux Azure CLI JSON

Who is this for?

This is an introductory topic for developers and DevOps engineers who want to automate the deployment of Arm-based Azure Cobalt 100 virtual machines using Azure Resource Manager templates.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Structure an Azure Resource Manager template with parameters, variables, and resources
  • Specify Arm64 architecture and Cobalt 100 Azure VM sizes
  • Deploy the template using Azure CLI and verify the deployment
  • Connect to your Cobalt 100 VM and validate the Arm64 architecture

Prerequisites

Before starting, you will need the following:

  • An Azure subscription with permissions to create resource groups, virtual machines, and networking resources
  • Azure CLI installed on your local machine - see the Azure CLI install guide
  • An SSH key pair for authentication

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll build an Azure Resource Manager template to provision a Linux virtual machine on Azure Cobalt 100 Arm-based infrastructure. First, you’ll define template sections for parameters, variables, resources, and outputs, select an arm64-capable VM size from the Dpsv6 series in a supported region, and deploy the template with the Azure CLI into a new resource group. After deployment, you’ll retrieve the VM’s public IP, connect with SSH using the configured key, and validate the architecture on the instance using standard commands. By the end, you’ll have a repeatable template that creates a Cobalt 100-based VM and associated networking ready for arm64 development.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I confirm the Azure region I selected supports Cobalt 100 VM sizes?
Run az vm list-skus for the target region and filter for the Dpsv6 series. For example: az vm list-skus --location eastus --size Standard_D --all --output table | grep "ps_v6".
Which VM size should I set in the template for a Cobalt 100 instance?
Choose a Dpsv6 series size returned by the SKU query for your region. The output example shows sizes such as Standard_D16ps_v6.
Where do I find the VM’s public IP address after deployment?
Use the value surfaced in the previous deployment step, often provided as a deployment output. You can also view the Public IP resource created in the resource group defined by the template.
What username should I use when connecting with SSH?
Use the admin username defined in your template’s parameters. The example uses azureuser; if your template specifies a different name, use that instead.
What output confirms the VM is running on `arm64`?
Run uname -m and expect aarch64. You can also run lscpu to see Arm 64-bit CPU details.
Next