Azure Learning

configure-app-service-plans

Properties1
tagsaz-104, compute, module, app-service, scaling

2 min read

Module 3 — Configure Azure App Service plans

Grounded in MS Learn: az-104-manage-compute-resources → Configure Azure App Service plans (learn.wwl.configure-app-service-plans)

Overview

Third module of the AZ-104 compute path. Decide which App Service plan pricing tier / SKU to use and how to scale the plan — the container and billing unit that hosts App Service web apps, APIs, and Functions apps.

Learning objectives (authoritative)

  1. Select an appropriate Azure App Service plan pricing tier.
  2. Scale an Azure App Service plan.

Concepts introduced

  • App Service plans — the compute container + billing unit shared by apps on it.
  • Pricing tiers: Free/Shared → Basic → Standard → Premium → Isolated; what features each tier unlocks (autoscale, staging slots, scale-out limits, VNet, zone redundancy, private endpoints).
  • Scaling the plan: scale up (resize worker → more CPU/RAM per instance) and scale out (add instances; autoscale rules from Standard tier).
  • How plan capacity, features, and instance counts affect every app in that plan.

Key terms & commands

  • Create plan: az appservice plan create --resource-group <rg> --name <plan> --sku S1 --is-linux
  • List SKUs: az appservice list-locations / cost-manager SKU grid; region SKU availability via az appservice plan + Portal pricing page.
  • Scale up: change --sku (e.g. S1→P1v3). Scale out: autoscale rules/min–max on the plan.
  • Tier → feature mapping is central: autoscale & staging slots need Standard+; Private Endpoint/VNet integration typically Premium; Isolated = App Service Environment.

Hands-on

  • Provision an S1 plan, host two web apps, then scale out with an autoscale rule on CPU%.
  • Compare a Basic (manual scale, ≤3 instances) vs Premium (autoscale, more instances) behavior.

Exam focus

  • Which features require which tier (memorize the gates: autoscale/staging = Standard+; private endpoints/VNet = Premium; ASE/isolation = Isolated).
  • Scale up vs scale out for App Service and that autoscale is the automated scale-out.
  • Multiple apps on one plan share resources (cost-saving but contention) — isolating critical apps is a design choice.
  • Bigger SKU is not always “better” — pick tier by required features + load.

Path MOC · app-service-plan · app-service · deployment-slots · Next: App Service

Graph View

Backlinks