Deploy a Cobalt 100 Virtual Machine on Azure
Introduction
Create the Cobalt 100 virtual machine
Open inbound ports in the Network Security Group
Verify connectivity to the Cobalt 100 VM
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  10 min
Last updated:  01 Jul 2026
Skill level:
  Introductory
Reading time:
  10 min
Last updated:
  01 Jul 2026
Author:Joe Stech, Arm
Arm IP:Neoverse
Tags: Containers and Virtualization Microsoft Azure Linux Azure Portal Azure CLI
Author:
  • Joe Stech, Arm
Arm IP:
Neoverse
Tags:
Containers and Virtualization Microsoft Azure Linux Azure Portal Azure CLI

Who is this for?

This is an introductory topic for developers and DevOps engineers who want to deploy an Arm-based virtual machine on Azure and expose an application port to the internet.

What will you learn?

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

  • Deploy an Arm-based Cobalt 100 virtual machine (VM) on Microsoft Azure
  • Connect to the Cobalt 100 VM using SSH
  • Configure an inbound TCP port in the associated Network Security Group (NSG)
  • Verify external connectivity to the newly-opened port

Prerequisites

Before starting, you will need the following:

  • A Microsoft Azure subscription with permissions to create virtual machines and networking resources
  • Basic familiarity with SSH

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 deploy an Arm-based virtual machine (VM) in Microsoft Azure using the Azure portal, select an appropriate VM series, and prepare it for remote access and basic testing. First, you’ll create the VM, then configure the associated Network Security Group to allow inbound SSH (port 22) and an application test port (8080). By the end, you’ll connect over SSH using the VM’s public IP address and validate external connectivity over the configured source IP range by running a service on the chosen port.

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 choose between Dpsv6/Dplsv6 and Epsv6 when creating the VM?
Dpsv6 and Dplsv6 are general-purpose series, while Epsv6 is memory-optimized. Select a series that aligns with the memory needs of your workload.
Where do I find the VM’s public IP address for SSH?
Open the VM resource in the Azure Portal and copy the Public IP address from the Overview page. Use the admin username you set during creation (for example, azureuser) and the path to your SSH private key.
What should I check if SSH times out or is refused?
Verify the Network Security Group has an inbound rule allowing TCP port 22 from your client IP. Also confirm you’re using the correct public IP address and the admin username you chose during VM creation.
Which IP range should I allow when opening port 8080 in the NSG?
For testing, allow traffic from your IP to limit exposure. Adjust the source IP range or choose a different port if your workload requires broader access or a non-default port.
What result should I expect when verifying port 8080 connectivity?
With an application or temporary HTTP server listening on port 8080, connecting to http://[public IP]:8080 should return a response. If it doesn’t, re-check the NSG rule and ensure the service is running on the VM.
Next