This chapter covers Azure App Service, Azure's primary PaaS offering for building and hosting web applications. AZ-900 tests this under objective 2.2, and App Service is a commonly used example when the exam distinguishes PaaS from IaaS.
Jump to a section
A simple way to picture Azure App Service
Building a website on a virtual machine is like renting a bare commercial lot and constructing the storefront yourself — you handle the building, utilities, and upkeep. Azure App Service is more like renting a fully built, fully staffed storefront: the building, power, and basic maintenance are already handled, and you just bring your product (your application code) and start operating. You still control what's sold and how the store is arranged inside, but you're not responsible for maintaining the building itself.
What App Service is
Azure App Service is a fully managed platform for building, deploying, and hosting web applications, REST APIs, and mobile backends. As a PaaS offering, Azure manages the underlying operating system and runtime, letting the customer focus on their application code rather than infrastructure.
How it works
A developer deploys their application code to App Service, which runs it on Azure-managed infrastructure. App Service handles tasks like patching the operating system, managing the runtime environment, and providing built-in features like automatic scaling and load balancing, without the customer needing to configure servers directly.
Key features
Multiple language and framework support: including .NET, Java, Node.js, Python, and others.
Deployment options: code can be deployed directly, through continuous integration pipelines, or as a container.
Built-in scaling: App Service can scale up (more powerful resources) or scale out (more instances) based on demand.
Custom domains and SSL: applications can be configured with custom domain names and secure connections.
How it compares to using a Virtual Machine
Hosting a web application on a VM (IaaS) means the customer manages the operating system, web server software, and everything else. App Service (PaaS) removes that management burden, at the cost of less low-level control over the environment — a tradeoff worth understanding when comparing the two approaches for a given workload.
Create an App Service instance
An App Service plan and web app are created, specifying the language/runtime and the pricing tier, which determines available resources and features.
Deploy application code
Code is deployed directly, through a CI/CD pipeline, or as a container image, without the developer needing to configure the underlying server manually.
Configure scaling settings
App Service can be configured to scale up (larger instance) or scale out (more instances) automatically based on demand, or manually as needed.
Manage application-level settings
The customer manages application configuration, custom domains, and their application's data — Azure manages the operating system and runtime beneath it.
A development team building a new customer-facing web application uses App Service so they can focus entirely on writing their application code, without needing to provision, patch, or maintain any servers themselves.
A separate team migrating from an on-premises web server to Azure considers whether to use a Virtual Machine (to closely replicate their existing setup) or App Service (to reduce ongoing management overhead) — illustrating the IaaS-versus-PaaS tradeoff in a real decision, where App Service is often chosen when the team doesn't need OS-level customization.
Objective 2.2 frequently uses App Service as the canonical example of PaaS, often contrasted directly against Virtual Machines as the canonical IaaS example.
A common wrong answer is describing App Service as requiring the customer to manage the operating system — it doesn't; that's the key distinction from a VM. Another common trap is assuming App Service only supports one programming language — it supports multiple languages and frameworks.
Stable terms: App Service, PaaS. Recognizing App Service as a PaaS example, and knowing that Azure manages the OS and runtime while the customer manages the application and data, is one of the most reliably tested facts in this objective.
Memory trick: App Service = PaaS = bring your code, Azure handles the platform underneath it.
Azure App Service is a PaaS offering for building and hosting web applications, APIs, and mobile backends.
Azure manages the operating system and runtime for App Service; the customer manages their application code and data.
App Service supports multiple programming languages and frameworks, and includes built-in scaling capabilities.
App Service is commonly contrasted with Virtual Machines to illustrate the difference between PaaS and IaaS.
These come up on the exam all the time. Here's how to tell them apart.
Azure App Service (PaaS)
Azure manages OS and runtime
Customer focuses on application code and data
Built-in scaling and deployment features
Less low-level control
Azure Virtual Machine (IaaS)
Customer manages OS and above
Customer configures the entire environment
Scaling requires more manual configuration
More low-level control
Mistake
App Service requires the customer to manage the operating system.
Correct
As a PaaS offering, Azure manages the operating system and runtime for App Service — the customer focuses on their application code and data.
Mistake
App Service only supports one programming language.
Correct
App Service supports multiple languages and frameworks, including .NET, Java, Node.js, Python, and others.
Mistake
App Service can't scale automatically.
Correct
App Service includes built-in scaling capabilities, letting it scale up or out based on demand, either automatically or manually configured.
It's Azure's fully managed PaaS offering for building, deploying, and hosting web applications, REST APIs, and mobile backends. Azure manages the underlying operating system and runtime, so developers can focus on their application code.
No — that's the key benefit of App Service as a PaaS offering. Azure manages the operating system and runtime environment; the customer manages their application and its data.
App Service supports multiple languages and frameworks, including .NET, Java, Node.js, Python, and others, along with support for deploying containerized applications.
You've just covered Azure App Service — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?