IaaS, PaaS & SaaS

AZ-900 AZ-900 · Describe cloud concepts

By Abu Anns · Last updated 20 November 2026Exam version: AZ-900 (skills measured as of July 20, 2026)

Three ways to consume the cloud

Cloud services come in three types — infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS) — and the exam expects you to describe each, name Azure examples, and pick the right one for a situation. The three types are really one sliding scale: how much does the provider manage, and how much do you manage? IaaS gives you the most control and the most work; SaaS gives you the least control and the least work; PaaS sits in the middle.

Service typeWhat the provider managesWhat you manageAzure examples
IaaSPhysical hardware, virtualisationOperating system, runtime, applications, dataAzure Virtual Machines, Azure Virtual Network, managed disks
PaaSHardware, virtualisation, OS, runtimeYour application code and dataAzure App Service, Azure SQL Database, Azure Functions
SaaSAlmost everythingYour data, accounts, and accessMicrosoft 365, Dynamics 365

Infrastructure as a service (IaaS)

With IaaS, the provider supplies virtualised computing infrastructure — virtual machines, virtual networks, storage — and the customer manages everything from the operating system upward. It is the closest cloud equivalent to owning servers: you choose the OS, install and patch it, configure the runtime, and deploy your applications. The provider's job is the physical layer and the virtualisation that carves physical hardware into virtual machines. IaaS fits when you need maximum control: migrating an existing application unchanged ("lift and shift"), running software with specific OS requirements, or testing infrastructure configurations. The cost of that control is work — patching, hardening, and maintaining the OS is your job, as the shared responsibility guide explains.

Platform as a service (PaaS)

With PaaS, the provider supplies the whole platform — hardware, OS, runtime, middleware — and the customer supplies only the application and its data. The classic Azure example is Azure App Service: you deploy your web application's code, and Microsoft runs the servers, the OS, the runtime, patching, and scaling. Azure SQL Database is PaaS for databases: you get a database, not a server to install a database on; backups, patching, and high availability are built in. Azure Functions is serverless PaaS taken further, as the previous guide describes. PaaS fits when a team wants to build and ship applications without managing infrastructure — faster development, automatic scaling, and no OS patching, in exchange for less control over the underlying environment. If a scenario says "the developers want to focus on code, not servers", the answer is PaaS.

Software as a service (SaaS)

With SaaS, the provider supplies a finished application, and the customer simply uses it through a browser or an app. Microsoft 365 (Outlook, Word, Teams, SharePoint online) is the flagship example; Dynamics 365 is the business-applications example. The customer configures settings, manages its users and data, and pays per user — and never sees a server, an OS, or an update process. SaaS fits when the need is a standard business capability rather than something custom: email, collaboration, customer relationship management. The trade-off is the mirror of IaaS: almost no management work, but almost no control over how the application works or when it changes.

Choosing between them: the exam's favourite question shape

Scenario questions give you a need and ask for the service type. Work through the need:

Watch for the two classic traps. First, Azure SQL Database vs SQL Server on a VM: the first is PaaS (Microsoft manages the platform), the second is IaaS (you manage the OS and the SQL installation). The exam uses this pair precisely because the names sound similar. Second, virtual machines vs containers vs functions: VMs are IaaS, while Functions are PaaS/serverless, and containers sit between — the compute guide covers this in detail.

Worked example: one company, all three types

A mid-sized company runs its email on Microsoft 365 (SaaS), its customer-facing web application on Azure App Service (PaaS), and a legacy stock-control system on Azure virtual machines (IaaS) because the software requires a specific old operating system. Nothing about this mix is unusual — most organisations use all three at once, choosing per workload. The email needs no customisation, so SaaS wins. The web app is custom code, so the developers take PaaS and skip server management. The legacy system cannot run on a managed platform, so IaaS is the only option. When the exam asks which service type a company "uses", remember the answer is usually per workload, not per company.

The responsibility thread

Service types and the shared responsibility model are the same idea viewed from two sides. Moving from IaaS to PaaS to SaaS moves the management line upward: the provider takes the OS, then the runtime, then the application. What never moves is the customer's responsibility for its data, its accounts, and who can access what. If you remember one sentence for this whole domain, make it this one: the higher up the stack you buy, the less you manage — but your data is always yours.

Migration strategies and service types

When a company moves existing workloads to Azure, the service type it lands on usually follows a migration strategy. Rehost ("lift and shift") moves an application unchanged onto virtual machines — the IaaS path, fastest and least disruptive. Refactor makes small changes so the application can run on a managed platform — the PaaS path, trading a little rework for much less ongoing management. Replace drops a custom-built system in favour of a SaaS product that does the same job — the biggest change in how the team works, and the least infrastructure to run. The exam does not test these strategy names directly, but they explain why a scenario's constraints point to a service type: "move it unchanged and quickly" is rehost/IaaS, "we want less to manage" is refactor/PaaS, and "we just need the capability" is replace/SaaS.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company wants to migrate its existing application to Azure without changing it. The application requires a specific version of Windows Server and custom registry settings. Which service type should the company use?

Report an error

Q2.A development team wants to deploy a web application quickly. They want to write code only — no servers to provision, no operating systems to patch, and automatic scaling. Which service type best fits?

Report an error

Q3.A company with 150 employees needs email, calendars, video meetings, and shared documents. It has no IT staff to run servers and wants a per-user monthly price. Which service type should it choose?

Report an error

Q4.A company needs a relational database for a new application. It does not want to install, patch, or back up a database server. Which Azure option is the PaaS choice?

Report an error

Q5.Which of the following is an example of infrastructure as a service (IaaS)?

Report an error

Q6.A company runs its website on Azure App Service (PaaS). A new security patch is released for the underlying operating system. Who applies it?

Report an error

Q7.Which statement about SaaS is correct?

Report an error

Q8.A startup is building a brand-new web application from scratch. The developers want to deploy code several times a day and never think about servers, scaling, or patching. Which combination best fits their needs?

Report an error