Azure Global Version Step by Step Guide to Create an Azure VM

Azure Account / 2026-05-20 13:34:56

Creating an Azure VM sounds like one of those tasks that should come with a tasteful warning label, like “May cause mild confusion.” One minute you’re staring at a console full of options; the next minute you’re expecting a fully functioning server to appear as if by magic. The good news: Azure is powerful, and you can absolutely build a VM step by step without becoming a part-time cloud philosopher.

This guide walks you through the process in a clear, practical order. Along the way, you’ll make decisions that matter (region, networking, size, authentication), avoid common mistakes (like opening the wrong ports or picking a tiny disk), and end with a VM you can connect to and use for real work. No vague hand-waving. We’re going to click our way to success.

Before You Start: What You’re Actually Building

A Virtual Machine (VM) in Azure is basically a “computer inside Microsoft’s computers.” You choose an operating system, allocate CPU and memory, decide how much storage you need, set up networking so you can reach it, and secure it so only the right people can log in.

Think of it like ordering a custom office printer: you pick the model (OS), the paper size (disk), the ink capacity (storage), the desk location (region), and who gets access (security rules). Then you plug it into the network so you can actually use it. In cloud terms, you also might choose whether it gets a public IP address, what ports are allowed inbound, and whether you’ll use SSH or RDP to connect.

Step 1: Gather Your Basic Choices

Before you enter the Azure portal and start clicking randomly (tempting, we know), it helps to decide what you want. Not everything needs to be perfect, but a few choices will save you time later.

Pick a Region

Azure is global, but your VM lives in a specific region (like East US, West Europe, Southeast Asia, and so on). Choose a region close to your users or where your other services are running. Lower latency often means a smoother experience.

Choose an Operating System

Most people start with a Windows Server or a Linux distribution (Ubuntu is common). Pick an OS based on your workload, comfort level, and any existing tooling you already use.

If you’re not sure: Linux is often simpler for beginners and is very common for web servers, dev environments, and automation tasks. Windows is great if you need Windows-specific software or want to use RDP-style administration.

Decide How You’ll Connect

In Azure, you usually connect to a VM using either:

SSH for Linux
RDP for Windows

Azure supports key-based authentication for SSH (recommended) and password or key-based options depending on configuration. If you’re using SSH, you’ll typically provide a username and an SSH public key.

Azure Global Version Estimate Your VM Size

The VM size is where you choose how much compute (CPU) and memory you get. If you pick too small, your VM will feel like it’s working through a thick layer of syrup. If you pick too big, you may overspend. Start modestly, especially for testing or learning.

For many beginner scenarios like a small web app, a dev environment, or a learning sandbox, a smaller general-purpose VM often does the job.

Step 2: Sign In to the Azure Portal

Go to the Azure portal and sign in with your Microsoft account or your organization’s credentials. If you don’t have an Azure subscription yet, you’ll need to create one (and yes, it’s usually quicker than it sounds, provided you’re not wrestling with account verification like a dramatic villain).

Step 3: Create a Resource Group

Resource groups are like folders for Azure resources. A VM must belong to a resource group, which helps you manage, organize, and delete related resources together.

In the Azure portal:

Use the search bar and find “Resource groups”
Click “Create”
Name it something sensible (for example, “rg-my-vm-demo”)
Choose the same region you plan to use for the VM, unless you have a reason not to
Click “Review + create” and then “Create”

Pro tip: naming matters later. Future-you will thank present-you when you’re trying to remember what you created three months ago at 1 a.m.

Step 4: Start the VM Creation Wizard

Now you’re ready to create the actual VM. In the Azure portal:

Search for “Virtual machines”
Click “Create”
Select “Azure virtual machine” (not other specialized variants unless you know what you want)

Azure will present a multi-step form. Don’t panic. Think of it like filling out a custom order sheet. The order is important, but you’re not expected to memorize Azure taxonomy before lunch.

Step 5: Configure Basics

The Basics section usually asks for the following:

Subscription: choose your subscription
Resource group: select the one you created
Virtual machine name: pick a name
Region: select where the VM will live

VM Name Tips

Use a name that’s readable and consistent. Example: “vm-linux-dev-01.” Avoid spaces and special characters if possible. Azure is not offended by your creativity, but it does prefer your naming habits to follow rules.

Step 6: Choose the Image (OS + Version)

Next you’ll select the “Image” for the VM. This determines the operating system and often includes a base configuration.

For Linux, you might see Ubuntu Server versions. For Windows, you’ll see Windows Server images.

How to Choose Quickly

If you’re learning: choose the latest stable Ubuntu or a common Windows Server image.
If you’re deploying a known app: match the OS your app supports.
If you have constraints: ensure it aligns with your patching and compliance requirements.

Don’t overthink it initially. You can adjust later, but starting with something conventional reduces the chance you’ll fight missing dependencies on day one.

Step 7: Select Size (CPU and Memory)

Now you choose the VM size. Azure provides recommendations and a table of sizes. In beginner terms, look for something that balances performance and cost.

As a general starting point:

For a small test or development: pick a basic general-purpose size.
For heavier workloads: choose higher CPU/memory sizes.

If you’re unsure, choose a smaller size first. You can resize later (with downtime depending on configuration). The worst outcome is paying a bit for a bigger instance, but the real danger is picking too small and deciding Azure is “slow” when it’s actually your resource allocation doing the heavy lifting.

Step 8: Configure Authentication

This is one of the most important parts because it affects how you log in and how secure your VM is.

For Linux: SSH Public Key (Recommended)

Azure often encourages you to use an SSH key pair. You provide:

A username (like azureuser)
An SSH public key (either generate a new key or paste your existing public key)

If you don’t have a key yet, Azure may offer an option to generate one locally. Use that if available. If you already have an SSH key, you can provide the public key.

For Windows: Password or Other Options

Windows VMs often require you to set an admin username and password. Azure will ask for password complexity requirements. Make it strong, store it safely, and don’t reuse it from other places like a villain using the same lock combo everywhere.

Remember: you’ll need these credentials later when connecting to the VM.

Step 9: Configure Networking

Networking is where beginner mistakes happen. It’s also where you gain control over how accessible your VM is.

Azure networking options typically include:

Virtual network: where the VM’s network settings live
Subnet: segment within the virtual network
Public IP: whether the VM gets a public address
Inbound port rules: which ports are open to incoming traffic

Public IP: Yes, No, and Why

When creating a VM, Azure may offer:

Option to assign a public IP address
Or keep it private (more secure but harder to access without VPN/bastion or other connectivity)

If you’re learning and need to connect right away, a public IP is convenient. Just remember that public means “reachable from the internet,” which makes security rules extra important.

Inbound Ports: Open Only What You Need

Azure Global Version During VM creation, Azure often asks which ports to allow inbound. You might see checkboxes like:

SSH (22) for Linux
RDP (3389) for Windows

For learning purposes, enabling the relevant port can be fine. For real deployments, you’d ideally restrict access further (like allowing only your IP address or using network security groups more carefully).

At minimum, do not open unnecessary ports “just in case.” That’s how you end up with your VM becoming a free sightseeing attraction for random internet noise.

Virtual Network and Subnet Defaults

If you don’t have an existing virtual network, Azure might offer to create one. Using defaults can speed things up. You can refine later if you’re designing a more complex environment.

Step 10: Configure Disks (Storage)

Azure asks you to select OS disk type and size, and sometimes other disk options like caching.

OS Disk Size

For a basic VM, a small OS disk may be enough, but if you plan to install packages, run updates, or deploy a web server with dependencies, you’ll want more space.

If you’re unsure, choose a size that won’t make you constantly manage disk space. Cloud storage growth is not always dramatic, but storage pressure can be a silent productivity killer.

Disk Type

Azure provides disk performance options (like standard or premium). For learning and smaller workloads, defaults usually work. For performance-sensitive workloads, you’ll want to select a disk type appropriate to your needs.

Step 11: Review and Create

Before clicking “Create,” Azure provides a review screen with a summary of your settings. This is your last chance to catch mistakes like:

Wrong region
Wrong VM name
Missing inbound port rules
Authentication issues

Then click “Create.” The deployment might take several minutes. Don’t stare at the screen like you’re willing it to finish with sheer willpower. Deployment sometimes runs on its own schedule.

Azure Global Version Step 12: Wait for Deployment to Complete

Azure Global Version While Azure provisions your VM, you can monitor progress in the portal. Once it completes, Azure will show you details of your VM.

At this stage, your VM exists, but it might not be fully ready to accept connections until the OS finishes initialization. If you try to connect too early, you may get errors. Give it a minute or two.

Step 13: Find Your VM Public IP Address

To connect to your VM, you typically need the public IP address (unless you’re using private connectivity).

In the Azure portal:

Open your Virtual Machine resource
Find the Networking section or overview details
Locate the Public IP address

Write it down. Future-you will not remember it, and your clipboard will mysteriously vanish into the void.

Step 14: Connect to Your VM

Now the fun part: connecting.

Connecting to a Linux VM via SSH

On your local machine, open a terminal. Then use an SSH command like:

If you have a private key file:

ssh -i /path/to/your-key.pem username@public-ip

Replace:

/path/to/your-key.pem with your private key path
username with the admin username you configured
public-ip with your VM’s public IP

When prompted, confirm the connection (the first time you connect, SSH may ask to accept the host key).

Connecting to a Windows VM via RDP

To connect to a Windows VM, you usually use Remote Desktop Protocol (RDP).

In your local environment:

Open Remote Desktop Connection (or “mstsc” on Windows)
Azure Global Version Enter the VM’s public IP address
Connect
When prompted, enter your username and password

If it says it can’t connect, check the inbound rule for RDP (port 3389) and confirm your VM networking settings.

Step 15: Verify the VM Is Actually Working

Once you’re connected, it’s time to do a quick sanity check. You want to confirm:

Azure Global Version Your OS booted correctly

For Linux: Update and Confirm System Health

Typically, you’ll run system updates. For example, on Ubuntu:

Update package lists
Install available upgrades

Then verify:

Disk space (so you don’t run out later)
Memory usage (just to see if the size you picked is enough)
Services (if you plan to run a server)

For Windows: Install Updates and Check Services

On Windows, you’ll want to:

Check Windows Update
Install security updates
Verify basic system settings
Confirm your RDP access remains functional

Also check that you can resolve DNS and access the internet, especially if you plan to install software packages.

Step 16: Optional but Smart Security Improvements

Creating a VM is step one. Keeping it secure is step two. And step three is not accidentally leaving it in “wide-open internet buffet” mode.

Restrict Inbound Access by IP

If you enabled SSH or RDP during setup, you can later restrict who can connect. Instead of allowing inbound traffic from everywhere, you can allow only your IP address or a trusted range.

This helps reduce the number of random connection attempts.

Use Strong Credentials and Disable Passwords (Where Possible)

For SSH, key-based authentication is generally safer than passwords. For Windows, use strong passwords and consider additional security controls as appropriate for your environment.

Consider a Network Security Group

Azure uses network security groups (NSGs) to manage traffic rules more cleanly. You can define inbound and outbound rules at the subnet or NIC level.

In plain terms: NSGs are like bouncers at a club. They decide who gets in and who gets turned away.

Step 17: Configure VM Monitoring (Because Clouds Are Not Telepathic)

Azure provides monitoring tools that help you track performance and availability. It’s a good idea to enable monitoring early so you can see problems before they become dramatic stories you tell later.

Look for options related to metrics and diagnostics. For many setups, enabling logging helps with troubleshooting and auditability.

Step 18: Confirm Costs and Billing Settings

Azure costs depend on VM size, region, usage, and storage. If you’re experimenting, it’s wise to shut down or deallocate the VM when you’re done learning.

In the Azure portal, you can find actions to stop, deallocate, or restart. Deallocating often reduces compute cost, though storage might still incur charges depending on your setup.

Troubleshooting: Common Problems (and Their Fixes)

Even with careful steps, things can go sideways. Here are some common issues and what usually causes them.

“Connection timed out” or “Can’t reach VM”

Most common reasons:

Public IP wasn’t assigned or isn’t correct
Inbound port rule for SSH (22) or RDP (3389) wasn’t enabled
Azure Global Version NSG or firewall rules block access

Fix: verify inbound rules and confirm you used the correct IP address and username.

SSH authentication fails

Common causes:

You used the wrong private key
Username doesn’t match what you set during VM creation
The public key wasn’t properly injected

Fix: confirm key pair alignment and username.

RDP asks for credentials but you can’t log in

Common causes:

Password mismatch
Account locked or wrong username
RDP not enabled through network rules

Fix: confirm credentials; check RDP port access.

Next Steps: Put Your VM to Work

Once you have connectivity, you can begin using the VM for whatever you planned. Typical next steps include:

Install a web server (Nginx, Apache, IIS depending on OS)
Set up a development environment (runtime languages, tools)
Host a small app or service
Configure backups and disaster recovery (for production scenarios)
Automate setup with scripts so you can reproduce your environment

And if you’re learning: congratulations. You’ve already done a thing that many people only admire from afar. Creating a VM is a foundational skill, and you’ll build on it from here.

A Friendly Recap (Because You Deserve One)

Here’s the short version of the journey:

Create a resource group
Start creating an Azure Virtual Machine
Set basics: subscription, VM name, region, resource group
Choose an OS image
Pick a VM size
Configure authentication (SSH key for Linux, password/admin for Windows)
Set up networking (virtual network, public IP, inbound port rules)
Choose disk options
Azure Global Version Review and create
Wait for deployment, find public IP
Connect via SSH or RDP
Verify and apply updates
Improve security and monitoring if needed

Now go forth and create your Azure VM with the confidence of someone who has read the steps and survived the portal maze. If you run into issues, don’t worry—cloud setups are like bicycles: they’re much easier once you understand the basics, and the first wobble is not a sign of failure. It’s just your learning process doing its job.