Creating a VM in Azure Portal - Visual Walkthrough

Process Flow - Creating a VM in Azure Portal

Login to Azure Portal

↓

Click 'Create a resource'

↓

Select 'Virtual Machine'

↓

Fill VM Basics: Name, Region, Image, Size

↓

Configure Admin Account

↓

Set Networking Options

↓

Review + Create

↓

Click 'Create' to deploy VM

↓

Wait for Deployment Completion

↓

Access VM via SSH or RDP

This flow shows the step-by-step process of creating a virtual machine in Azure Portal, from login to accessing the VM.

Execution Sample

Azure

1. Login to portal.azure.com
2. Click 'Create a resource'
3. Choose 'Virtual Machine'
4. Enter VM details (name, region, image, size)
5. Set admin username and password
6. Review and click 'Create'

This sequence creates a virtual machine in Azure Portal with basic configuration.

Process Table

Step	Action	Input/Selection	Result/State
1	Login to Azure Portal	User credentials	User logged in, portal dashboard shown
2	Click 'Create a resource'	N/A	Marketplace page opens
3	Select 'Virtual Machine'	Search or browse VM	VM creation wizard opens
4	Fill VM Basics	Name: myVM, Region: East US, Image: Ubuntu 22.04 LTS, Size: Standard B1s	VM configuration saved
5	Configure Admin Account	Username: azureuser, Password: ********	Admin credentials set
6	Set Networking	Use default virtual network and subnet	Networking configured
7	Review + Create	Review all settings	Validation passed
8	Click 'Create'	N/A	Deployment starts
9	Wait for Deployment	N/A	VM deployed and running
10	Access VM	SSH to public IP	Connected to VM terminal

💡 VM is deployed and accessible; creation process complete.

Status Tracker

Variable	Start	After Step 4	After Step 5	After Step 7	After Step 9
VM Name	None	myVM	myVM	myVM	myVM
Region	None	East US	East US	East US	East US
Image	None	Ubuntu 22.04 LTS	Ubuntu 22.04 LTS	Ubuntu 22.04 LTS	Ubuntu 22.04 LTS
Size	None	Standard B1s	Standard B1s	Standard B1s	Standard B1s
Admin Username	None	None	azureuser	azureuser	azureuser
Deployment Status	Not started	Not started	Not started	Validation passed	Succeeded

Key Moments - 3 Insights

Why do we need to choose a region when creating a VM?

The region determines where your VM will physically run. It affects latency and compliance. See execution_table step 4 where 'East US' is selected.

What happens if the admin username or password is weak or missing?

The portal will show a validation error and prevent deployment. This is shown in execution_table step 7 where validation must pass before creation.

Why do we wait after clicking 'Create' before accessing the VM?

Deployment takes time to allocate resources and start the VM. Access is only possible after deployment succeeds, as shown in steps 8-10.

Visual Quiz - 3 Questions

Look at the execution_table, what is the VM name after step 4?

A azureuser

B myVM

C Ubuntu 22.04 LTS

D East US

💡 Hint

Check the 'VM Name' row in variable_tracker after step 4.

At which step does the deployment start?

A Step 7

B Step 9

C Step 8

D Step 10

💡 Hint

Look at the 'Action' column in execution_table for when deployment begins.

If the admin password is missing, what will happen during the process?

A Validation will fail at Review + Create step

B Deployment will succeed anyway

C VM will be created without admin access

D Networking configuration will fail

💡 Hint

Refer to key_moments about validation errors before deployment.

Concept Snapshot

Creating a VM in Azure Portal:
1. Login to portal.azure.com
2. Click 'Create a resource' and select 'Virtual Machine'
3. Fill in VM basics: name, region, image, size
4. Set admin username and password
5. Configure networking (default is fine for beginners)
6. Review and click 'Create' to deploy
7. Wait for deployment to complete before accessing VM

Full Transcript

To create a virtual machine in Azure Portal, first log in to portal.azure.com. Then click 'Create a resource' and select 'Virtual Machine' from the marketplace. Fill in the VM basics such as name, region, image, and size. Next, set the admin username and password to secure your VM. Configure networking settings, usually the default virtual network and subnet are fine. Review all your settings carefully and click 'Create' to start deployment. Wait until the deployment finishes successfully. Once done, you can connect to your VM using SSH or RDP depending on the OS. This step-by-step process ensures your VM is properly created and ready to use.

Practice

1. What is the first step when creating a Virtual Machine (VM) in the Azure Portal?

easy

A. Choose the VM name and region

B. Connect to the VM using SSH

C. Select the VM size after creation

D. Install software on the VM

Solution

1. Step 1: Start VM creation in Azure Portal

   When creating a VM, you first open the Azure Portal and start the 'Create a virtual machine' process.

2. Step 2: Enter basic details like name and region

   The first required details are the VM's name and the region where it will be hosted.

3. Final Answer:

   Choose the VM name and region -> Option A

4. Quick Check:

   First step is naming and region selection [OK]

Hint: Name and region come first when creating a VM [OK]

Common Mistakes:

• Trying to connect before VM is created
• Selecting size before naming VM
• Installing software before VM setup

2. Which option correctly describes the step to select the operating system image when creating a VM in Azure Portal?

easy

A. Skip image selection; Azure picks automatically

B. Choose the image after VM creation

C. Upload your own OS image only

D. Select the image during VM setup under 'Image' section

Solution

1. Step 1: Locate the 'Image' section in VM creation

   During VM setup, there is a section called 'Image' where you select the OS image.

2. Step 2: Select a predefined OS image

   You pick from available images like Windows Server or Ubuntu Linux before creating the VM.

3. Final Answer:

   Select the image during VM setup under 'Image' section -> Option D

4. Quick Check:

   Image selection happens during setup [OK]

Hint: Pick OS image during VM setup, not after [OK]

Common Mistakes:

• Thinking image is chosen after VM is created
• Assuming Azure picks image automatically
• Believing you must upload your own image

3. After creating a Linux VM in Azure Portal, which method is used to connect to it?

medium

A. Remote Desktop Protocol (RDP)

B. SSH (Secure Shell)

C. FTP (File Transfer Protocol)

D. HTTP (Hypertext Transfer Protocol)

Solution

1. Step 1: Identify the OS type of the VM

   The VM is Linux-based, which typically uses SSH for secure command-line access.

2. Step 2: Use SSH to connect

   SSH is the standard protocol to connect securely to Linux VMs remotely.

3. Final Answer:

   SSH (Secure Shell) -> Option B

4. Quick Check:

   Linux VM connection uses SSH [OK]

Hint: Linux VMs connect via SSH, Windows via RDP [OK]

Common Mistakes:

• Trying to use RDP on Linux VM
• Using FTP or HTTP to connect to VM
• Confusing protocols for connection

4. You created a Windows VM but cannot connect using Remote Desktop. What is the most likely cause?

medium

A. Network security group (NSG) blocks RDP port 3389

B. The VM size is too small

C. You selected a Linux image by mistake

D. The VM name is invalid

Solution

1. Step 1: Check network security settings

   Remote Desktop uses port 3389, which must be allowed in the VM's network security group (NSG).

2. Step 2: Identify blocked port issue

   If NSG blocks port 3389, RDP connections fail even if VM is running.

3. Final Answer:

   Network security group (NSG) blocks RDP port 3389 -> Option A

4. Quick Check:

   Blocked RDP port causes connection failure [OK]

Hint: Open port 3389 in NSG for Windows VM RDP [OK]

Common Mistakes:

• Assuming VM size affects RDP connection
• Confusing OS image type after creation
• Thinking VM name affects connectivity

5. You want to create a VM in Azure Portal that can be accessed securely from anywhere. Which combination of settings is best?

hard

A. Use a Linux VM, use password authentication, block all inbound ports

B. Use a Windows VM, use password authentication, open port 3389 to all IPs

C. Use a Linux VM, select SSH key authentication, open port 22 in NSG

D. Use a Windows VM, disable NSG, connect via RDP

Solution

1. Step 1: Choose secure authentication method

   SSH key authentication is more secure than passwords for Linux VMs.

2. Step 2: Open only necessary port in NSG

   Opening port 22 for SSH allows secure remote access; avoid opening unnecessary ports.

3. Step 3: Avoid insecure options

   Opening RDP port 3389 to all IPs or disabling NSG reduces security.

4. Final Answer:

   Use a Linux VM, select SSH key authentication, open port 22 in NSG -> Option C

5. Quick Check:

   SSH key + port 22 open = secure access [OK]

Hint: Use SSH keys and open only port 22 for secure Linux VM access [OK]

Common Mistakes:

• Using password authentication over SSH
• Opening RDP port to all IPs
• Disabling NSG for convenience