Azure Portal 101: Deploy a Windows 10 VM Without Ever Touching the CLI

In this guide, we are going to bypass the command line entirely (that is the CLI — Command Line Interface, like PowerShell or Bash). We will use the Azure Portal (GUI) to launch a Windows 10 Virtual Machine (VM) in about 7 minutes.

Cost Note: Azure charges by the minute while your VM is running. Delete everything at the end and your cost will be minimal or zero, especially if you are on a free trial.

A Virtual Machine (VM) is a computer that runs inside another computer — entirely in the cloud. You access it remotely just like a normal PC.

Phase 1: The Setup

1. Sign In: Log into the Azure Portal.
2. Create a Resource: Click the + Create a resource button in the top left.

1. Resource Group: Click "Create new" and name it any name for example MyVMGroup. Virtual Machine Name: Name it DevOps-Lab-01. Region: Select the one closest to you (e.g., East US).

When finish go to the resource group you just created and open it.

Next Select the Service search bar: Type "Windows 10" in the search bar and select the Windows 10 option or the "consumer editions" or "Pro."

Quick Definition: A Region is simply the physical location of the data center where your virtual computer will live.

Phase 2: Configuration & Identity

1. Size: Choose Standard_B2s. It's cost-effective and perfect for learning.

The "Size" selection window showing the B2s option and its estimated monthly cost. Ensure you check the Run with Azure spot discount

This lets Azure use spare capacity to run your VM at a lower cost. It is perfect for learning because we are not running anything critical.

*7. Administrator Account: *

1. Enter a username and
2. A strong password.

⚠️ Important: Save these! You will need them to "log in" to your computer later.

1. *Inbound Port Rules: * Under "Public inbound ports," ensure Allow selected ports is checked and RDP (3389) & Http (80) is selected.

1. Review + Create: Skip the other tabs for now. Click the blue Review + Create button at the bottom.

The Deployment

1. Confirm: Azure will run a validation check. Look for the green "Validation passed" message. Then click Create.

Phase 3: Connecting via Remote Desktop (RDP)
Once the deployment is complete, click Go to resource.

1. Click the Connect button at the top left and select RDP.

1. Click Download RDP File. This file is your "digital key."
2. Open the downloaded file and click Connect.
3. Enter the Username and Password you created in Phase 2.
4. The Certificate Warning: A box will pop up saying the identity cannot be verified. This is normal! Click Yes.

VM running live.

You have just deployed a real cloud computer from scratch no command line needed.

What You Just Learned:
Azure Term : What It Actually Means
Resource Group: A folder for your cloud project
Region: Which data center your VM lives in
VM : A computer that runs inside another computer entirely in the cloud.
RDP: The remote "screen share" protocol
VM Size: How much CPU/RAM your lab computer gets

Next Step: Don't Forget to Clean Up!
When you are finished testing, delete your Resource Group to avoid any unnecessary charges:

1. Go to Resource groups in the Azure Portal.
2. Find MyVMGroup.
3. Click Delete resource group and type the name to confirm.

The Resource Group page showing the "Delete resource group" button and the confirmation text box.

If you found this helpful, kindly share it with someone else starting their DevOps journey. If you are on the same path, I did love to hear how your experience went — drop a comment or reach out.