Skip to main content
Cloud Computing

Azure Tutorial with Examples.

Microsoft Azure tutorial: Virtual Machines, AKS, Azure Functions, Entra ID, Blob Storage and the wider Microsoft cloud ecosystem.

Architecture at a glance

Click any box to open the lesson that teaches it

Azure architecture at a glance

az CLI → Entra ID → VNet → VMs / Functions → Blob / SQL, watched by Monitor

Azure architecture at a glance An az CLI call runs as an Entra ID identity restricted by an RBAC role assignment, inside a resource group. Compute lives inside a VNet's subnets and NSGs: VMs for servers you manage, Functions for serverless code. Both call Blob Storage for object storage and Azure SQL for a managed database. Bicep and ARM templates provision the whole stack as one file and Azure Monitor watches it with metrics and KQL log queries, with Cost Management and the Well-Architected Framework's five pillars as the final check. Azure CLI subscriptionresource group Entra ID RBAC · roles VNet subnets · NSG VMs NSG · SSH Functions serverless Data Blob Storage containers · tiers Azure SQL server · database Deploys & watches Bicep & ARM templates · deploy Azure Monitor metrics · KQL Cost & reliability Cost Management cost analysis · 5 pillars
How it fits together (5 steps)
  1. Every call starts from the az CLI, confirmed against the right subscription before anything runs, inside a resource group that holds everything created below so it can be deleted as one unit.
  2. That call only works as far as its Entra ID role assignment allows: a role scoped to the wrong resource group gets a real authorization error until the scope is fixed — RBAC roles are separate from Entra ID's own identity-management roles.
  3. Compute lives inside a VNet, where a subnet's NSG has to allow a port before anything reaches it, independently of what the VM's own NSG allows. VMs run a server you SSH into once port 22 is open; Functions run the same kind of code with no server to manage, at the cost of a cold start on the first invocation.
  4. Both call the data layer: Blob Storage holds objects in a container across hot, cool and archive tiers, and Azure SQL runs a managed database you can restore to a point in time.
  5. Two services wrap the whole stack: Bicep and ARM templates deploy every resource above as one declarative file that validates before anything is created, and Azure Monitor collects the metrics and KQL-queried logs that watch it while it runs. Cost Management and the Well-Architected Framework's five pillars are the last check before calling it production-ready.

Beginner

Start here — no prior experience needed

4 lessons

Intermediate

For developers with core concepts down

5 lessons

Advanced

Production-grade patterns for experienced engineers

1 lesson