The Big Picture
Agility is the new currency in IT. Traditional server management is plagued by high upfront costs and rigid hardware limits. Azure Virtual Machines (VMs) flip the script, offering a pay-as-you-go model that lets you scale for heavy workloads and shut down when the job is done.
But flexibility requires precision. This guide strips away the complexity, offering a lean, secure, and cost-effective blueprint to get your first VM live in minutes. No fluff—just the essential steps to ensure your cloud journey starts on solid ground.
đź› Prerequisites
Before we start clicking buttons in the portal, ensure you have the following ready to go:
Active Azure Subscription: You’ll need a Microsoft account. If you don't have one, sign up for a Free Trial (usually includes $200 in credits).
Resource Group Access: Ensure you have Contributor or Owner permissions on your subscription to create new resources.SSH Key Pair (For Linux): If you’re deploying a Linux VM, have your public key ready. (Azure can generate one for you, but using your own is best practice).
Remote Desktop Client (For Windows): For Windows VMs, ensure the Remote Desktop Connection (RDP) app is installed on your local machine.
Stable Connection: A reliable internet connection is a must—nothing is more frustrating than a deployment timing out!
Pro-Tip: If you are a student, look into Azure for Students. It doesn't require a credit card and provides free annual credits to help you learn without the bill!
Ready to build?
The foundation is set. Let’s head into the Azure Portal and bring your first Virtual Machine to life.
Steps:
1. On the Azure Portal, search for and select Virtual Machines.
2. Select + Create
3. Select Virtual Machines
Configure your Virtual Machine
Steps:
1. Create a Resource Group and give the Resource Group a name, then select OK to confirm name.
2. Give your Virtual Machine a Name and select the Operating System (Image). In this case, we selected Windows because we are creating a windows VM, and we maintained other Defaults Options.
3. Setup your Administrator Account by creating a Username and Password. Be sure to take note of the criteria required to create the Administrator Account.
4. Configure the Inbound Ports Rules to:
Allow Selected Ports
Select RDP(3389) since this is a standard "doorway" needed to remotely log in amd manage a Windows Virtual Machine from another computer. For security best practice, only the required port for current task is opened/selected.
confirm Licencing to avoid being blocked while creating the Virtual Machine
5. Disable Boot Diagnostics by navigating to the Monitoring Tab, then select Disable
6. Select Review + create and wait for validation to be passed.
7. Once the Validation is passed, select Create.
8. Select Go to resource once the deployment is complete.
9. Connect to the Virtual Machine by selecting Connect, then click the check access to confirm the Virtual Machine access since this is basically about Native RDP.
10. Click Download RDP file to access the virtual Machine created. And in the case of password issue, you can always click the forget password to change it before downloading the RDP created.
11. Access the downloaded RDP file for windowns by clicking the open button at the download space.
12. Click connect to access the Virtual Machine created.
13. Enter the created password for the Aministrator Account then select OK.
14. Confirm the Virtual Machine name the click Yes
Assessing the Virtual Machine created
Open the Browser, download and install Screenpresso
Access sites to confirm if the Virtual Machine is function like a physical PC.
Now click Disconnect to log off the Virtual Machine created and note the username of the Administrator account while trying to disconnect.
Mission Accomplished
You’ve officially moved from local hardware to the global scale of Microsoft Azure. Creating a Virtual Machine is the "Hello World" of cloud infrastructure—now that your instance is live, the power to scale, test, and deploy is entirely in your hands.
Key Takeaways
Security First: You opened Port 3389 (RDP) to connect today, but in a production environment, always restrict this to your specific IP address to prevent unauthorized access.
Cost Management: Azure VMs are billed by the second. If you aren't using your VM, Stop/Deallocate it in the portal to save your credits.
The Power of Snapshots: Now that your VM is working perfectly, consider taking a Snapshot of the disk. It’s your "undo button" if something goes wrong during a future installation.
What’s Your Next Project?
Your VM is a blank canvas. Whether you're hosting a web server, setting up a database, or building a dev sandbox, you've officially taken your first step into the cloud.
Happy Cloud Building!
Top comments (1)
Nice, work!