IaaS, PaaS & SaaS
AZ-900 AZ-900 · Describe cloud concepts
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 type | What the provider manages | What you manage | Azure examples |
|---|---|---|---|
| IaaS | Physical hardware, virtualisation | Operating system, runtime, applications, data | Azure Virtual Machines, Azure Virtual Network, managed disks |
| PaaS | Hardware, virtualisation, OS, runtime | Your application code and data | Azure App Service, Azure SQL Database, Azure Functions |
| SaaS | Almost everything | Your data, accounts, and access | Microsoft 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:
- "We need to run our existing application with its specific OS and configuration, unchanged." IaaS — a virtual machine gives full control over the OS.
- "Our developers want to deploy code quickly and never manage servers or operating systems." PaaS — App Service or Functions.
- "We need email and document collaboration for 200 staff, with no infrastructure to run." SaaS — Microsoft 365.
- "We need a database but do not want to install, patch, or back up a database server." PaaS — Azure SQL Database (a managed database, not a VM running SQL Server, which would be IaaS).
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.
Exam traps to watch for
- Confusing Azure SQL Database (PaaS) with SQL Server on a virtual machine (IaaS). The managed database service is PaaS; running the database yourself on a VM is IaaS.
- Calling Microsoft 365 PaaS. Microsoft 365 is SaaS — a finished application you use, not a platform you build on.
- Assuming a company uses only one service type. Real organisations mix IaaS, PaaS, and SaaS per workload; exam questions ask about one workload at a time.
- Thinking SaaS removes the customer's data responsibility. Even with SaaS, the customer owns its data, accounts, and access decisions.
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?
Explanation: IaaS is right: virtual machines give full control over the operating system, which the application's specific OS version and registry settings require. PaaS (App Service) does not let the customer control the OS. SaaS is a finished application, not a place to run a custom one. Serverless Functions run short event-driven code, not an existing application with OS dependencies.
Exam objective: AZ-900 Describe cloud service types: identify appropriate use cases for each cloud service type (IaaS, PaaS, and SaaS)
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?
Explanation: PaaS (for example Azure App Service) is built for this: the provider manages servers, OS, and runtime, and the team deploys code. IaaS would require the team to manage the OS and patching. On-premises hosting is the most work of all. SaaS is a finished application to use, not a platform to deploy custom code on.
Exam objective: AZ-900 Describe cloud service types: describe platform as a service (PaaS)
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?
Explanation: SaaS fits: Microsoft 365 provides email, meetings, and documents as a finished service with per-user pricing and no servers to run. IaaS would mean running mail servers on virtual machines — the opposite of no IT staff. PaaS is for building custom applications, not using email. A private datacenter is the highest-effort option.
Exam objective: AZ-900 Describe cloud service types: describe software as a service (SaaS)
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?
Explanation: Azure SQL Database is a managed (PaaS) database: Microsoft handles patching, backups, and high availability. SQL Server on a VM is IaaS — the customer manages the OS and the database installation. Blob Storage is object storage, not a relational database. Azure Files is a managed file share, not a database.
Exam objective: AZ-900 Describe cloud service types: identify appropriate use cases for each cloud service type (IaaS, PaaS, and SaaS)
Q5.Which of the following is an example of infrastructure as a service (IaaS)?
Explanation: Azure Virtual Machines are IaaS: the provider supplies virtualised infrastructure and the customer manages the OS and above. Microsoft 365 and Dynamics 365 are SaaS finished applications. Azure App Service is PaaS — a platform for deploying code without managing servers.
Exam objective: AZ-900 Describe cloud service types: describe infrastructure as a service (IaaS)
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?
Explanation: In PaaS the provider manages the operating system, including patching — the customer manages only its application code and data. The customer owns the OS only in IaaS. The internet provider has no role. PaaS platforms do run on operating systems; the customer just never manages them.
Exam objective: AZ-900 Describe cloud service types: describe platform as a service (PaaS)
Q7.Which statement about SaaS is correct?
Explanation: In SaaS the provider manages the application and everything beneath it; the customer keeps responsibility for its data, accounts, and access. The customer does not manage servers or the OS, does not install or update the application, and pays a subscription rather than buying and hosting software.
Exam objective: AZ-900 Describe cloud service types: describe software as a service (SaaS)
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?
Explanation: PaaS plus serverless matches the need exactly: deploy code frequently, no servers to manage, automatic scaling and patching handled by the provider. Virtual machines with manual scaling put the OS and scaling work back on the team. A private datacenter is the highest-effort option. Microsoft 365 is a finished office suite, not a platform for building a custom web application.
Exam objective: AZ-900 Describe cloud service types: identify appropriate use cases for each cloud service type (IaaS, PaaS, and SaaS)