Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
AZ-900 Hands-On: Azure VMs, App Service & Budgets - Part 1
New
4 students

AZ-900 Hands-On: Azure VMs, App Service & Budgets - Part 1

Azure Fundamentals, hands-on: launch a VM, host a live website, and compare IaaS vs PaaS with App Service
Created byCip Rian
Last updated 9/2026
English

What you'll learn

  • Launch a Linux virtual machine in the Azure portal from an empty subscription, and connect to it over SSH from Windows or macOS.
  • Install a web server on that machine and serve a real page on the public internet, at an address you can send to somebody.
  • Read a network security group's rules, and open exactly one port on purpose instead of opening everything until something works.
  • Set a cost budget with an alert before you create anything, then delete every resource you built so nothing keeps billing quietly.
  • Describe what a virtual machine is actually made of: size, image, disks, network interface, and private versus public IP addresses.
  • Deploy a website on Azure App Service with no machine to look after, and say plainly when PaaS is the better answer than IaaS.
  • Explain the Azure resource hierarchy — account, subscription, resource group, resource — and where management groups sit above it.
  • Recognise the compute, networking and cost topics AZ-900 asks about, in the exam's own skills-measured wording.

Course content

4 sections • 17 lectures • 1h 34m total length
  • What You'll Build Today1:33
  • Hands-on Lab - Create Your Free Azure Account7:30
  • The Map You're Inside4:13
  • Hands-on Lab - Your Safety Net: A Budget and Its Alert4:54
  • 5 Questions

Requirements

  • No prior Azure experience, no programming, and no Linux background. If you can use a browser, you can do this.
  • A computer with a browser, and a terminal — we connect to the machine from Windows and from macOS.
  • An Azure account. The Azure free tier account covers everything built in this course.

Description

One workload. Built by you, end to end.

Most AZ-900 preparation asks you to memorise descriptions of things you have never touched. This course does the opposite. You start from an empty Azure subscription and finish with a Linux virtual machine that you created, connected to over SSH, turned into a web server, and put on the public internet at an address you can send to somebody.

Along the way something breaks — on purpose. Your page refuses to load, and nothing you did was wrong. Finding out why is how you learn what a network security group actually is, and why "open everything until it works" is the habit to avoid.

The whole arc:

  • The map you are inside: account, subscription, resource group, resource

  • A cost budget and its alert, set before you create a single thing

  • A Linux VM: size, image, disks, network interface, public and private addresses

  • SSH from Windows or macOS — keys, not passwords

  • A web server, a door that is shut, and the one rule that opens it

  • The same job the easy way: a live website on Azure App Service, with no machine to look after

  • IaaS and PaaS side by side, judged from having built both

  • A full clean-up, on camera, so nothing keeps running behind your back

What you need

If you want to follow along on the hands-on labs, you would need an Azure **free** account; we create one together, right after we start the course. The free tier covers everything here.

No prior Azure experience is assumed. No programming. No Linux. If you can use a browser, you can do this.

Who this course is for:

  • AZ-900 candidates who have read the theory and never once touched the portal.
  • Complete beginners who want to find out whether the cloud is approachable before committing to a full certification course.
  • IT and non-IT professionals who need to talk about Azure compute, networking and cost from first-hand experience rather than from a summary.
  • Anyone who wants one Azure workload built end to end — created, connected, served, secured, budgeted, and then deleted.