█
LastWrite
  • > Curriculum
  • > Pricing
  • > For Educators
  • > About
  • > Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
LastWrite

Structured computer science lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 LastWrite. All rights reserved.
Curriculum/DevOps and Infrastructure/Cloud Platforms — Microsoft Azure/Azure Core Services
40 minBeginner

Azure Core Services

After this lesson, you will be able to: Recognise the core Azure services and what each is for: Virtual Machines, Blob Storage, Azure SQL, Functions, Entra ID, App Service.

Azure has 200+ services. This lesson covers the daily-driver 6 + the 'these have AWS equivalents' map.

Prerequisites:Azure vs AWS

Compute: Virtual Machines, App Service, Functions, Container Apps

Virtual Machines (VMs): Azure's EC2 equivalent. Pick OS + size; manage everything. App Service: managed PaaS for web apps. Deploy from git / zip / container. AWS's Elastic Beanstalk + App Runner cousin. The most-used Azure compute. Azure Functions: serverless functions. Triggers (HTTP, queue, timer, blob); pay per invocation. Lambda equivalent. Container Apps: managed Kubernetes-on-rails (built on AKS). Like Fargate / Cloud Run. AKS (Azure Kubernetes Service): full K8s, covered in do-azure-08.

Storage: Blob Storage, Files, Disks

Blob Storage: object storage. S3 equivalent. Tiers: Hot, Cool, Archive (each cheaper but slower to retrieve). Azure Files: SMB / NFS file shares. Mount from VMs or AKS Pods. EFS equivalent. Disks: managed disks for VMs. SSD / Premium SSD / Ultra Disk tiers. EBS equivalent. Cost-saving move: lifecycle rules on Blob Storage move old files to Cool / Archive automatically.

Database: Azure SQL Database, Cosmos DB, Database for Postgres / MySQL

Azure SQL Database: managed Microsoft SQL Server. Azure Database for Postgres / MySQL: managed open-source DBs. Cosmos DB: globally distributed multi-model NoSQL (DynamoDB equivalent, but more flexible APIs). Azure Cache for Redis: managed Redis. For most learners: Postgres flexible-server is the go-to.

Identity: Entra ID (formerly Azure AD)

Entra ID is the killer Azure service. Workforce identity + SSO + conditional access + MFA + B2B/B2C. Even AWS-heavy enterprises use Entra ID as the identity provider that federates INTO AWS. Used by Microsoft 365, GitHub Enterprise, Slack, Salesforce, virtually every enterprise SaaS for SSO. We cover it deeply in do-azure-03.

Networking: Virtual Network (VNet), Application Gateway, Front Door

VNet: VPC equivalent. Subnets, NSGs, peering. Application Gateway: L7 load balancer (= ALB). Plus a WAF tier for security. Front Door: global edge + CDN + WAF. CloudFront + Cloudflare equivalent. Load Balancer: L4 (= NLB). Same conceptual model as AWS; different names + slightly different UI.

Observability: Application Insights + Log Analytics + Monitor

Azure Monitor = the meta-service. Includes: Application Insights: APM (instrument code; see traces + perf). Log Analytics: aggregated logs queryable with KQL (Kusto Query Language, strong query DSL). Metrics: built-in time-series. Alerts: fire on metric or log thresholds. Tight integration: every Azure resource emits metrics + activity logs by default. Compare to AWS where you have to opt-in resource by resource.

Quick Check

You want to host a Next.js app with minimal Azure ops. What's the simplest service?

Pick the easy choice.

Sign in and purchase access to unlock this lesson.

Sign in to purchase
←Azure vs AWS
Back to Cloud Platforms — Microsoft Azure
Azure Networking→