Video summary

Azure Step by Step Tutorial for Beginners | Azure Tutorial

Main summary

Key takeaways

Educational

High-level overview

This video is a 2+ hour hands‑on Azure beginner course (15 chapters + 3 labs) from the Quest / QuestPond channel. It teaches Azure fundamentals from basics to intermediate concepts with live demos.

Main course goals:

  • Explain why cloud and cloud service models.
  • Set up an Azure account and use free credits.
  • Build and manage Azure Virtual Machines.
  • Organize resources (Resource Groups, regions, availability zones).
  • Cover high availability, disaster recovery, fault tolerance, scalability and elasticity.
  • Demonstrate VM Scale Sets & autoscale, networking basics (NSG, public IP).
  • Show cost control and clean‑up practices.
  • Provide basic AZ‑900 practice questions.

Key recurring advice:

Be mindful of cost. Always use Resource Groups so you can delete everything after labs. Do labs in small sessions.

Course structure

15 chapters:

  1. Introduction
  2. Why Cloud (the “3 S’s”)
  3. Cloud concepts (scalability, self‑service, pay as you go)
  4. Create Azure account + free credits

  5. IaaS / PaaS / SaaS 6–8. Virtual machines and resource groups

  6. Public / Private / Hybrid cloud

  7. Azure infrastructure topology (geography → region → availability zone → data center)
  8. Lab 2 — Availability zones demo
  9. DR / HA / fault tolerance / scalability / elasticity
  10. Lab 3 — Scalability & elasticity demo (VM Scale Sets + autoscale)
  11. 10 practice questions from AZ‑900
  12. Next steps (Azure DevOps & further lessons)

Three hands‑on labs:

  • VM creation and teardown
  • Availability Zones demo
  • VM Scale Set autoscale demo (scalability & elasticity)

Key concepts & definitions

  • 3 S’s of cloud:

    • Scalability (and automatic scalability)
    • Self‑service (provision via portal/API)
    • Spend / Pay‑as‑you‑go (consumption/rental model; Opex vs Capex)

  • Cloud service models:

    • IaaS (Infrastructure as a Service): VMs, networks, disks — you manage OS and apps.
    • PaaS (Platform as a Service): managed platform to host apps (e.g., App Service) — Azure manages servers.
    • SaaS (Software as a Service): complete software delivered to users (e.g., Office 365).

  • Azure topology:

    • Geography → Region → Availability Zone → Data center (racks and servers).
    • Use Regions and Zones for compliance and availability.

  • Resource Group:

    • Logical container for related Azure resources (VM, NIC, IP, disk). Use for organization and bulk deletion.

  • Availability Zones:

    • Separate physical locations within a region for high availability (deploy redundant VMs in different zones).

  • Availability Set vs Availability Zone:

    • Availability Set: distributes VMs across fault domains & update domains (older model).
    • Availability Zone: physically separate locations (stronger isolation).

  • Disaster Recovery (DR):

    • Recovery from major, long‑lasting failures (can take days/months; not fully automatic).

  • High Availability (HA):

    • Minimize downtime; failover often has some downtime as per SLA.

  • Fault Tolerance:

    • No downtime — synchronous replication / continuous failover.

  • Scalability vs Elasticity:

    • Scalability: add resources when load grows (scale out).
    • Elasticity: remove resources when load falls (scale down) to save cost.

  • Network Security Group (NSG):

    • Firewall rules applied to NIC/subnet; controls ports (e.g., allow RDP port 3389 or SSH 22).

Practical methodology — step‑by‑step (from demos)

  1. Create Azure free account and get $200 USD credit (valid 30 days)

    • Go to Azure → Start your free account → provide credit card for verification.
    • Use free credit for learning; expect small charges after the trial ends.

  2. Naming & organization best practices

    • Create and use Resource Groups per project.
    • Use meaningful names (e.g., country‑project‑location‑role) with hyphens and consistent casing.

  3. Create an Azure Virtual Machine (IaaS) — core steps

    • Portal → Search “Virtual machines” → Create → Fill basics:
      • Subscription, Resource Group, VM name, Region, Availability options (None / Availability Zone / Availability Set).
      • Image: Ubuntu/Linux are free; Windows images include license cost unless BYOL.
      • Size: CPU/RAM — cost varies.
      • Admin credentials: username/password or SSH key.
      • Public IP: decide if you need Internet exposure (public IP costs apply).
    • Select OS disk type (Premium SSD vs HDD) — performance vs cost.
    • Networking: accept defaults or customize vNet, subnet, NIC; NSG and public IP can be created automatically.
    • Tags: add metadata for billing/search.
    • Review estimated costs (right‑hand panel) before Create → monitor “Deployment in progress”.
    • After deployment: go to Resource Group → view all created resources (VM, NIC, IP, disk, NSG).
    • Connect:
      • Windows: use RDP (mstsc) or download .rdp file → enter credentials.
      • If RDP fails, check NSG inbound rules (allow TCP 3389).

  4. Shutdown vs Delete

    • Stopping the VM from inside the OS may still incur some charges (storage, reserved IP).
    • Deallocating (Stop (deallocate) in portal) frees compute costs; disk costs remain.
    • To fully avoid bills, delete the entire Resource Group (removes VM, IP, disk, NIC, NSG). Wait for deletion success notification.

  5. Availability Zones demo (HA)

    • Create VMs in different Availability Zones (e.g., Zone 1 and Zone 2) for redundancy.
    • Manual failover: disassociate public IP from a failed VM and associate with standby VM.
    • For automatic failover, use a Load Balancer.

  6. VM Scale Sets and Autoscale (Scalability & Elasticity demo)

    • Create a Virtual Machine Scale Set (VMSS) to manage multiple instances as a group.
    • Configure autoscale rules:
      • Minimum and maximum instance counts (e.g., min 1, max 5).
      • Scale up: e.g., if average CPU > 50% for N minutes, add an instance.
      • Scale down: e.g., if CPU < 40% for N minutes, remove an instance.
      • Set evaluation interval (e.g., 5 minutes).
    • VMSS may block inbound RDP by default (open port 3389 in NSG if needed).
    • To simulate load: run a CPU‑burning script (PowerShell loop) to trigger autoscale. After sustained load and evaluation period, VMSS scales out; when load drops, it scales in.

  7. Networking and NSG practical tips

    • NSG inbound rules control allowed ports. Permit RDP (TCP 3389) or SSH (TCP 22) as needed.
    • Public IPs are charged; associate/disassociate carefully.

  8. Cost control and billing tips

    • Use Cost Management & Billing → cost analysis at subscription or Resource Group level.
    • Estimated cost shown during resource creation; actual hourly charges apply.
    • Paid images (Windows, RHEL) add per‑hour license costs; BYOL may lower image charge.
    • Delete Resource Group after labs to avoid unexpected charges; confirm deletion completes.
    • Keep resources deallocated when not in use; disks and IP addresses may still incur charges.

Troubleshooting tips & learning suggestions

  • If portal UI changes, use the search bar to find resources quickly.
  • If a lab fails: post a timestamped comment with details; instructor may offer support.
  • Learn in bite‑sized sessions (15–20 minutes) and record progress with timestamps.
  • Watch notifications (top‑right) for deployments and deletions; wait for successful completion.

Promotions, extra resources & calls to action

  • Instructor’s Azure DevOps course offered free (lifetime) if you share the YouTube video on LinkedIn, tag the instructor ID, and notify QuestPond — applies only to the Azure DevOps course.
  • Instructor may release additional lessons if videos hit like thresholds (requested 2,000 likes to release next lab).
  • Quest / QuestPond paid and membership courses (longer 50‑hour training, live classrooms) are available at questpond / quest.com.

Exam & self‑test points

  • The video includes a short AZ‑900 (Azure Fundamentals) practice section with 10 questions covering:
    • IaaS / PaaS / SaaS, CapEx vs OpEx, costs, availability categories, recommended solutions for web apps, HA/DR, scalability examples.
  • Instructor’s stance: hands‑on labs are more valuable than certificates alone, but AZ‑900 is a useful self‑test.

Concise checklist to repeat the core lab safely

  • Create a Resource Group for the lab.
  • Estimate costs in the right panel and pick a sensible VM size.
  • Choose OS image (Linux free; Windows includes license cost unless BYOL).
  • Select region & availability option (none / availability zone / availability set) based on HA needs.
  • Choose disk type (SSD for performance, HDD for lower cost).
  • Ensure NSG inbound rules permit required ports (RDP 3389 or SSH 22).
  • Deploy and test connection via RDP or SSH.
  • Monitor metrics (CPU, etc.) for autoscale triggers.
  • For autoscale: create VM Scale Set, set autoscale rules (thresholds, min/max, evaluation period).
  • After the lab: deallocate to pause compute charges, or delete the Resource Group to remove all resources and stop billing.
  • Always confirm deletion success in notifications.

Speakers & sources

  • Primary speaker/instructor: Quest (Quest / QuestPond) — unnamed presenter who leads lessons and demos.
  • Platforms and references mentioned:
    • Microsoft Azure (portal.azure.com)
    • QuestPond / quest.com
    • YouTube (this lesson & membership)
    • AZ‑900 (Azure Fundamentals)
    • Tools & tech referenced: Virtual Machines (IaaS), App Service (PaaS), Office 365/Tally (SaaS examples), VM Scale Sets, Network Security Groups, Availability Zones, RDP (mstsc), PowerShell (for CPU load), Load Balancer.

Original video