Study guide

2.4 Azure App Service, Containers, and Serverless

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

2.4 Azure App Service, Containers, and Serverless

Key Takeaways Explain This Topic AI

Azure App Service is PaaS web hosting: you deploy code and Azure manages the OS, patching, load balancing, and scaling for web apps, REST APIs, and mobile backends.

Azure Container Instances (ACI) is the fastest way to run a single container with per-second billing and no orchestration; Azure Kubernetes Service (AKS) manages many containers at scale.

On the AKS Free tier, cluster management is free and you pay for the worker-node VMs that run your pods (the Standard and Premium tiers charge for cluster management); Azure Container Apps is serverless containers that scale to zero.

Azure Functions is serverless event-driven code billed per execution on a serverless plan (Flex Consumption is recommended; the Consumption plan is legacy); Azure Logic Apps is low-code workflow automation billed per action.

Exam scenarios test the key differentiator: full OS control = VMs, managed web app = App Service, single container = ACI, orchestration = AKS, event-driven code = Functions, workflow = Logic Apps.

Last updated: October 2026

Quick Answer: App Service = managed PaaS web hosting. Container Instances = one container, no orchestration. Kubernetes Service = managed orchestration for many containers. Container Apps = serverless containers that scale to zero. Functions = event-driven code billed per run. Logic Apps = visual workflow automation billed per action.

Azure App Service (PaaS)

Azure App Service is a fully managed platform for hosting web applications, REST APIs, and mobile backends. You push code (or a container) and Azure provides the OS, the web server, patching, autoscale, and load balancing. It supports .NET, Java, Node.js, PHP, Python, and Ruby on Windows or Linux.

Standout features: deployment slots for staging and zero-downtime swaps (blue-green releases), built-in continuous integration/continuous delivery (CI/CD) from GitHub or Azure DevOps, free managed TLS/SSL certificates , custom domains, and built-in authentication with Microsoft Entra ID and social providers.

Apps run inside an App Service Plan , which defines the underlying compute and pricing tier:

  • Tier Use case Autoscale Custom domain
  • Free / Shared Dev/test No Shared host only
  • Basic Low-traffic production Manual scale only Yes
  • Standard Production with autoscale Yes Yes
  • Premium (v3) High throughput, more instances Yes Yes
  • Isolated Dedicated, network-isolated Yes Yes

On the Exam: All apps in the same App Service Plan share its CPU and memory, so co-locating a noisy app can starve the others. Deployment slots are the App Service answer to "test in production-like staging, then swap with no downtime."

Containers in Azure

A container packages an app with its dependencies so it runs identically everywhere. Azure offers three hosting tiers of increasing capability.

Azure Container Instances (ACI)

The simplest, fastest way to run a container — no VMs, no cluster. Containers start in seconds , bill per second , and are ideal for short tasks, simple jobs, build steps, and burst capacity. There is no built-in orchestration, autohealing, or rolling-update logic.

Azure Kubernetes Service (AKS)

Managed Kubernetes for running many containers at scale. On the Free tier , cluster management (the control plane) is free and you pay for the worker-node VMs that run your pods; the Standard and Premium tiers add a paid uptime SLA for cluster management. AKS adds pod and node autoscaling, self-healing, rolling upgrades, and Azure Monitor Container Insights. Choose AKS for complex microservices and enterprise container estates.

Azure Container Apps

A serverless container platform built on Kubernetes that hides cluster management entirely. It supports event-driven autoscaling (HTTP traffic, queue length, custom metrics) and scale to zero , so you pay nothing when idle. It is the middle ground: more power than ACI, far less operational overhead than AKS.

  • Serverless Computing
  • Azure Functions

Azure Functions runs small pieces of code ("functions") in response to events — an HTTP request, a timer, a new queue message, or a blob upload. It scales automatically from zero to many instances and, on the right plan, you pay only while code runs.

Plan Billing Scaling Best for

Flex Consumption Pay for on-demand executions; scale to zero Auto, event-driven (up to 1,000 instances) Spiky/intermittent event workloads (recommended serverless plan)

Consumption (legacy) Per execution + GB-seconds; scale to zero Auto, event-driven Existing apps; Linux hosting on this plan retires 30 September 2028

Premium Pre-warmed instances (no cold start) Auto, with always-ready instances Low latency, VNet integration

Dedicated (App Service) App Service Plan rate Manual/auto within the plan Reusing existing App Service capacity

Functions are stateless by default; Durable Functions add stateful orchestration. On the exam, "pay only when the code runs" and "scale to zero" point to a serverless plan; Microsoft recommends Flex Consumption for new function apps.

Azure Logic Apps

Azure Logic Apps is a low-code/no-code service for building workflows that connect apps, data, and services. You assemble logic in a visual designer using 1,400+ prebuilt connectors (Microsoft 365, Salesforce, SAP, ServiceNow, and more) and are billed per action executed. Compared with Functions (you write code), Logic Apps is the "drag-and-drop integration" answer — for example, "when an email with an attachment arrives, save it to OneDrive and post to Teams."

Choosing the Right Compute Service

  • Service Type Manage the OS? Best for Pricing model
  • Azure VMs IaaS Yes Lift-and-shift, full OS control Per-minute compute
  • App Service PaaS No Web apps and APIs App Service Plan
  • Container Instances PaaS No A single short-lived container Per second
  • Kubernetes Service Managed Worker nodes Complex microservices Worker-node VMs
  • Container Apps Serverless No Event-driven containers, scale to zero Per second + scale to zero
  • Functions Serverless No Event-driven code Per execution
  • Logic Apps Serverless No Workflow / integration Per action
  • Common Traps

ACI vs AKS: one simple container → ACI; many containers needing orchestration, self-healing, and rolling updates → AKS.

Functions vs Logic Apps: writing code → Functions; connecting SaaS services with a visual designer → Logic Apps.

On the AKS Free tier , cluster management is free and the cost is the worker-node VMs; Standard and Premium tiers charge for cluster management.

App Service still hides the OS even when you deploy a custom container, so "no OS management" can still mean App Service.

On the Exam: Read for the key differentiator — full OS control (VMs), managed web hosting (App Service), event-driven code (Functions), or container orchestration (AKS). One phrase usually decides the answer.