Study guide
1.2 Cloud Service Models (IaaS, PaaS, SaaS)
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
1.2 Cloud Service Models (IaaS, PaaS, SaaS)
Key Takeaways Explain This Topic AI
IaaS (Infrastructure as a Service) gives you virtual hardware — VMs, virtual networks, disks — and the most control; you manage the OS and everything above it.
PaaS (Platform as a Service) provides a managed runtime so you manage your application, data, configuration and identities; Azure handles the OS, patching, and scaling.
SaaS (Software as a Service) delivers a finished application; you manage only your data, identities, and configuration.
Moving IaaS to PaaS to SaaS, the provider manages more and the customer manages less — but the customer ALWAYS owns data, accounts/identities, and devices.
Azure VMs = IaaS; Azure App Service and Azure SQL Database = PaaS; Microsoft 365 and Dynamics 365 = SaaS.
Last updated: October 2026
Quick Answer: Three service models, increasing abstraction: IaaS (you manage the OS and up), PaaS (you manage your app, data, configuration, and identities), SaaS (you just use the software). Azure VMs = IaaS, Azure App Service and Azure SQL Database = PaaS, Microsoft 365 = SaaS.
The service models and the shared responsibility model are core AZ-900 topics. Each model sets a different division of labor between you (the customer) and Microsoft (the provider). The single question that resolves most scenarios is: who manages the operating system?
Infrastructure as a Service (IaaS)
IaaS gives the most flexibility and the most responsibility. Microsoft runs the physical layer; you operate the virtual machine and everything inside it.
Microsoft manages: physical hosts, physical network, data center (power, cooling, security), and the hypervisor.
You manage: operating system, patching, runtime, middleware, applications, network configuration (NSGs, subnets), and data.
Azure examples: Azure Virtual Machines , Azure Virtual Network , Azure Managed Disks , Azure Load Balancer .
Use cases: lift-and-shift migrations, legacy or custom apps needing specific OS builds, full-control dev/test, and high-performance computing (HPC).
Platform as a Service (PaaS)
PaaS supplies a managed development and hosting platform. You deploy code; Azure runs the OS, runtime, and scaling underneath it.
Microsoft manages: everything in IaaS plus the operating system, middleware, runtime, OS patching, and (often) automatic scaling.
You manage: your application code, your data, and limited platform settings.
Azure examples: Azure App Service (web apps/APIs), Azure SQL Database (managed relational DB), Azure Functions (serverless code), Azure Cosmos DB (managed NoSQL).
Use cases: rapidly building web apps and APIs, developers who want zero server maintenance, microservices, and agile prototyping.
Software as a Service (SaaS)
SaaS delivers a complete, ready-to-use application, usually through a browser. You consume; the vendor runs the entire stack.
Microsoft manages: almost all of the application stack — infrastructure, platform, and application maintenance.
You manage: your data, identity and access settings, and device access posture (users, permissions, policies).
Examples: Microsoft 365 (Word, Excel, Teams, Outlook online), Dynamics 365 (CRM/ERP), OneDrive .
Use cases: email and collaboration, CRM, and any need for finished software with no installation or maintenance.
Service Model Comparison
- Aspect IaaS PaaS SaaS
- Customer control Most Moderate Least
- Provider management Least Moderate Most
- You manage the OS? Yes No No
- Flexibility Highest Medium Lowest
- Maintenance burden Highest Medium Lowest
- Azure example Virtual Machines App Service Microsoft 365
- Best for Custom/legacy workloads App development Ready-to-use software
On the Exam: Scenario questions describe responsibilities, not labels. "The team patches the guest OS" = IaaS. "Developers push code and Azure handles servers and scaling" = PaaS. "Staff just sign in and use email" = SaaS.
The Shared Responsibility Model
This model defines which security duties belong to Microsoft and which belong to you. The split slides with the service model, but two rows never move to Microsoft.
- Responsibility On-Prem IaaS PaaS SaaS
- Physical security/hosts/network Customer Microsoft Microsoft Microsoft
- Operating system Customer Customer Microsoft Microsoft
- Network controls Customer Customer Shared Microsoft
- Applications Customer Customer Shared Shared
- Information & data Customer Customer Customer Customer
- Accounts & identities Customer Customer Customer Customer
- Devices (endpoints) Customer Customer Customer Customer
The non-negotiable rule: the customer is always responsible for data, accounts/identities, and devices in every model. Microsoft is always responsible for the physical layer. Everything between them shifts with the model.
Serverless Computing
Serverless extends PaaS by abstracting even the platform sizing. You write a function; Azure provisions, scales from zero to many, and bills per execution.
Azure Functions — event-driven code, billed per execution and per GB-second.
Azure Logic Apps — visual workflow automation, billed per action.
Azure Event Grid — event routing, billed per operation.
Serverless traits: no servers to manage, event-driven triggers (HTTP, timer, queue), automatic scale to zero, and micro-billing for actual run time.
Common Trap: "Managed" does not mean SaaS. Azure SQL Database is PaaS — you still own the data and schema; Microsoft only manages the engine and OS. SaaS means an entire end-user application like Microsoft 365.
Worked Scenario: Choosing a Service Model
A retailer wants to host a custom inventory application written for a specific Linux distribution with kernel modules it compiled itself. Because it needs full control of the operating system and can install arbitrary packages, IaaS (Azure Virtual Machines) is the right fit — PaaS would not expose the kernel. The same retailer also wants a customer-facing web storefront that the development team can push to several times a day without managing patching or load balancers; here PaaS (Azure App Service) is correct because the team only ships code.
Finally, the retailer's staff need email and document collaboration with zero administration of the underlying app; SaaS (Microsoft 365) delivers that. One company, three workloads, three different models — exactly the multi-part mapping AZ-900 presents.
How to Decide Quickly on the Exam
Work down this short decision list and stop at the first match:
Do you only sign in and use a finished app (email, CRM)? ⇒ SaaS .
Do you deploy your own code but never touch the OS, runtime, or scaling? ⇒ PaaS .
Do you install and patch the operating system and manage the VM yourself? ⇒ IaaS .
Cost and Effort Trade-off
- Factor IaaS PaaS SaaS
- Time to deploy an app Slowest (build the OS first) Fast (push code) Instant (already built)
- Operational staff needed Most Less Least
- Customization possible Highest Medium Lowest
- Vendor responsibility for security Lowest Medium Highest
The broad principle: as you move from IaaS toward SaaS you trade control for convenience . Choosing the right point on that spectrum is a common service-model scenario, and the deciding factor is usually how much of the operating system and platform the customer wants to manage.