EEdukron DevOps Library
Microsoft AzureIntermediate8 submodules

Azure Compute Services

Choose and operate the right Azure compute model, from virtual machines to managed application, function, container, and Kubernetes platforms.

How this module works

From concept to production evidence

Select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Learning outcomes

  • Compare IaaS, PaaS, serverless, containers, and Kubernetes
  • Design availability and scaling
  • Match workloads to Azure compute services
  • Plan identity, networking, deployment, and monitoring
  • Explain operational trade-offs

Flow diagram

Azure Compute Services end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Profile workloadAzure Compute Services stage 1: profile workload with an auditable result before the next stage begins.
  2. 02
    Select compute modelAzure Compute Services stage 2: select compute model with an auditable result before the next stage begins.
  3. 03
    Design availabilityAzure Compute Services stage 3: design availability with an auditable result before the next stage begins.
  4. 04
    Deploy securelyAzure Compute Services stage 4: deploy securely with an auditable result before the next stage begins.
  5. 05
    Scale and observeAzure Compute Services stage 5: scale and observe with an auditable result before the next stage begins.
  6. 06
    Optimize operationsAzure Compute Services stage 6: optimize operations with an auditable result before the next stage begins.

Integrated hands-on lab

Select and deploy Azure compute

  1. Profile three workload types
  2. Create a compute decision matrix
  3. Deploy one workload
  4. Configure scaling and health checks
  5. Measure reliability and cost

Complete module contents

8 full submodule notes

Read in order
01

Virtual Machines

Virtual Machines provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
02

VM Scale Sets

VM Scale Sets provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
03

Availability Sets

Availability Sets turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
04

App Service

App Service provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
05

Azure Functions

Azure Functions turns a manual or repeated decision into versioned, parameterized, testable, and observable execution within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
06

Container Instances

Container Instances moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
07

Azure Container Apps

Azure Container Apps moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes
08

AKS

AKS provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Compute Services. It is not an isolated definition: its value appears when it supports select compute based on workload shape, control requirements, scaling model, startup behavior, networking, state, operational responsibility, and cost rather than familiarity alone.

Open full notes