Blog
SaaS vs. PaaS vs. IaaS vs. DaaS: how the four cloud service models differ
SaaS, PaaS, IaaS, and DaaS defined: see how each model splits management responsibility and where Windows 365 and Azure Virtual Desktop fit.
Table of Contents
- The four cloud service models defined
- What you keep managing under each model
- Where Windows 365 and Azure Virtual Desktop fit in the taxonomy
- The classification determines the cost model
- Choosing a model comes down to operational labor
- Where Nerdio Manager fits across Windows Cloud paths
- What the service model decision means for your desktop estate
- Frequently asked questions about SaaS vs. PaaS vs. IaaS vs. DaaS
Friday's recommendation deck has to answer one question: which cloud model replaces the aging Citrix estate, and why. Then someone in the steering meeting asks whether a cloud desktop is "just SaaS," and four acronyms (SaaS, PaaS, IaaS, and DaaS, or Desktop as a Service) start clouding the answer.
This guide is written for the IT and end-user computing leaders building that business case for Windows Cloud, Microsoft's umbrella for Windows 365 and Azure Virtual Desktop, along with the Microsoft Intune work that surrounds both.
Each of the four models is really a decision about how much management responsibility your team keeps, and that split is what the deck actually has to defend.
The four cloud service models defined
Each model describes who operates which layer of the computing stack, from applications down to the physical datacenter. NIST Special Publication 800-145, published by Peter Mell and Timothy Grance in 2011, is still the globally accepted standard for SaaS, PaaS, and IaaS. DaaS arrived later and sits in its own Gartner market category.
Software as a service (SaaS)
SaaS delivers ready-to-use applications over the internet. Under the NIST cloud definition, the consumer uses "the provider's applications running on a cloud infrastructure" and "does not manage or control the underlying cloud infrastructure."
Microsoft's shared responsibility guidance names Microsoft 365 and Dynamics 365 as the canonical examples. You subscribe and sign in; the application is already assembled. Your operating work moves to the data and the user access.
Platform as a service (PaaS)
For developers, PaaS is the cloud model that keeps the server layer out of the sprint plan. It delivers a managed platform for running your applications. The consumer deploys "consumer-created or acquired applications" onto the provider's infrastructure without touching the operating system or servers underneath, per NIST.
Azure App Service and Azure SQL Database are Microsoft's PaaS workhorses. Developers ship code; Microsoft runs everything below it. That makes PaaS primarily a developer lane, not an infrastructure lane. In cloud service model terms, Azure Virtual Desktop also lives here, running on virtual machines your team stands up and manages, with an Azure Virtual Desktop agent that lets users connect.
Infrastructure as a service (IaaS)
IaaS keeps the most operational control in your hands. NIST defines it as provisioning "processing, storage, networks, and other fundamental computing resources" where the consumer can "deploy and run arbitrary software, which can include operating systems and applications." Azure Virtual Machines is the obvious example. Microsoft's responsibility ends at the hypervisor layer; everything above it, including guest OS patching, is yours. IaaS buys control, but it also keeps server operations on your team.
Desktop as a service (DaaS)
Desktop as a Service is the cloud service model built around the desktop estate. The Gartner DaaS definition describes it as "the provision of virtual desktops by public cloud or other service providers," with desktop experiences delivered "from virtual machines (VMs) accessed using a remote display protocol." Here, DaaS means Desktop as a Service. Data as a Service and Device as a Service use the same acronym. The NIST acronym warning calls the collision "confusing." Microsoft's cloud desktop products are Windows 365 and Azure Virtual Desktop; both appear in Gartner's DaaS market category.
Outside of Gartner's market bucket, DaaS implies a fully managed desktop service, which fits Windows 365 but not Azure Virtual Desktop (which is considered a PaaS).
Vendors usually draw these four models as a pyramid of abstraction. For buyers, a better reading is a contract because each tier specifies which team, yours or Microsoft's, operates each layer. That contract is worth reading closely before you sign it.
What you keep managing under each model
Data stays on your plate under every service model. Under every model, Microsoft's shared responsibility documentation keeps customer data, configurations and settings, and identities and users in the customer column. Microsoft's Cloud Adoption Framework states that: "As you move from [SaaS] to [IaaS], you gain control and give up speed."
For Azure Virtual Desktop, Microsoft states that "most components are Microsoft-managed, but session hosts and some supporting services and components are customer-managed or partner-managed." You "only manage the image and virtual machines you use for the sessions in your Azure subscription, not the infrastructure." Windows 365 pushes the OS and VM layers further into Microsoft's column, and management runs through Microsoft Intune day-to-day.
For teams comparing Windows Cloud paths, Nerdio Manager for Enterprise sits in the customer-managed layer rather than replacing Microsoft's service model.
For regulated industries, virtual desktop infrastructure (VDI) can support compliance strategies by centralizing desktops and reducing reliance on traditional endpoint computing. That design supports a compliance strategy while certification remains separate, and per Microsoft, "Compliance is a shared responsibility between Microsoft, you, and your tenants."
The standard spectrum runs from SaaS to IaaS, and Microsoft's two cloud desktop products occupy different points on it.
Where Windows 365 and Azure Virtual Desktop fit in the taxonomy
Windows 365 and Azure Virtual Desktop belong to Windows Cloud, Microsoft's umbrella for cloud-hosted Windows desktops, but they land in different service model tiers. That split shapes how each product is operated and paid for. Microsoft's own documentation uses different labels for the two products because they package responsibility differently, which is why the taxonomy looks inconsistent at first read.
Windows 365 shows up under SaaS and DaaS
Microsoft Learn describes Windows 365 as "a cloud-based software-as-a-service (SaaS)" that provisions Cloud PCs, while Microsoft's FastTrack documentation calls the same product a "desktop-as-a-service (DaaS) solution." Both labels point to the same reality. Windows 365 arrives as a preconfigured service where Microsoft handles the underlying platform. Microsoft CEO Satya Nadella framed the SaaS parallel at the Windows 365 launch, saying "Just like applications were brought to the cloud with SaaS, we are now bringing the operating system to the cloud."
Azure Virtual Desktop lands in PaaS territory
The Azure Architecture Center says Azure Virtual Desktop "provides a platform as a service (PaaS)-style solution," and a Microsoft Q&A staff summary compresses the taxonomy further, listing Azure VMs as IaaS, Azure Virtual Desktop as PaaS, and Windows 365 as "SaaS (DaaS)."
That labeling matches how the product actually works. Your team assembles the environment on top of the AVD platform while Microsoft runs the broker and gateway underneath.
Gartner's DaaS market definition captures the full range by spanning offerings "available either preconfigured as a service or as a platform customers assemble and manage themselves." Windows 365 is the preconfigured service. Azure Virtual Desktop is the platform you assemble.
Both compete in the Gartner Magic Quadrant for DaaS
Even with the taxonomy split, both products compete in the Gartner Magic Quadrant for Desktop as a Service, where Microsoft has held a Leader position for three consecutive years in the 2025 report. Many enterprises run both, using preconfigured Cloud PCs for dedicated full-time users and pooled multi-session host pools for variable workloads. The tier each product occupies dictates how the invoice arrives.
The classification determines the cost model
Windows 365 bills like the SaaS tier it occupies. Azure Virtual Desktop bills like the infrastructure you assemble it from. That single difference drives most cost planning decisions in a Windows Cloud deployment.
Windows 365 uses flat per-user subscription pricing
Windows 365 charges a flat per-user, per-month subscription. Its "hosted on behalf of" architecture, per Microsoft, "lets a Microsoft service provide software-as-a-service and user licensed services as opposed to standard consumption-based services." Finance sees one line item per assigned user.
May 2026 Enterprise Cloud PC pricing runs from $28.00 per user per month (2 vCPU, 4 GB RAM, 64 GB storage) up to $158.00 (8 vCPU, 32 GB RAM, 512 GB storage) before needing to contact sales for larger purchases. Microsoft also cut Windows 365 Business list prices by 20% across all Cloud PC configurations, per a May 2026 announcement.
Predictability is the product's core budget value. If 500 users each need a dedicated desktop, you know your monthly spend before you provision a single Cloud PC.
Azure Virtual Desktop uses Azure consumption billing
Azure Virtual Desktop exposes Azure consumption billing directly. You pay for the infrastructure your desktops consume, with compute billed by the second and storage and networking metered separately, and no upfront commitments. Eligible licenses (Microsoft 365 E3/E5/E7, F3, Business Premium, and Windows 11/10 Enterprise E3/E5) include access rights, so the Windows entitlement adds no extra cost for those users.
The consumption model rewards discipline. Session hosts that are stopped and deallocated stop accruing compute charges, and pooled multi-session host pools drive per-user costs down through density. Azure Virtual Desktop pricing hinges on workload and utilization more than on the SKU you pick.
A complete comparison needs three cost layers
Keep Azure compute, storage, and networking separate from Microsoft OS and access entitlements and from any third-party management layer. Management software can add a per-user platform cost while reducing Azure consumption or administrative labor. It sits apart from Microsoft access rights and VM spend.
Which model wins on cost depends on cloud desktop patterns. Azure Virtual Desktop typically wins for variable schedules and high user density. Windows 365 often fits predictable, full-time usage where the fixed per-user cost gives budget certainty and Intune-based management keeps day-to-day administration in a familiar control plane.
Choosing a model comes down to operational labor
Operational labor usually decides whether teams stay on legacy VDI, host desktops on IaaS, or adopt DaaS. The work shows up as staffing and patching first. Then it appears in desktop orchestration and capacity planning. The technology comparison is table stakes; the labor comparison is the recommendation.
- On-premises VDI still fits when: compliance posture demands full infrastructure control, existing Citrix or Omnissa Horizon (formerly VMware Horizon) hardware and licenses are paid for with no refresh cycle imminent, and you hold the in-house virtualization expertise to justify the labor.
- IaaS-hosted desktops fit when: you need OS-level control and full-stack customization without on-premises hardware, or when legacy applications require persistent desktops or individual admin rights that session-based delivery can't support.
- DaaS fits when: rapid provisioning and fewer infrastructure components to patch are the goals, especially for seasonal or fluctuating headcount that benefits from elastic provisioning.
Market data points the same way. Gartner's 2025 Magic Quadrant captures the direction: "Net-new desktop virtualization deployments are almost exclusively DaaS." Revenue growth in the on-premises VDI market has been flat at around 2%, with user counts declining. The staffing signal is just as blunt. In a Gartner Peer Community survey, 54% of respondents adopted DaaS because IT lacked the skills to manage a VDI solution, and 68% were most satisfied with its scalability.
DaaS thins the work while leaving concrete management tasks on your team. For Azure Virtual Desktop, that retained work spans the Azure Portal, PowerShell, and Microsoft Intune. Gartner's 2025 Critical Capabilities research notes that "DaaS removes some of the operational complexity of virtual desktops; however, it can introduce other factors (e.g., variable costs, lack of configuration flexibility, network complexity)."
On Azure Virtual Desktop, the native auto-scaling service supports one scaling plan per host pool, Microsoft's documentation advises against combining it with other scaling tools, and lists dynamic auto-scaling preview for pooled multi-session host pools. On Windows 365, every assigned user needs an Intune license to receive user policies, and managing Cloud PCs means managing Intune policy and application delivery day-to-day.
Those configuration surfaces are the retained work that purpose-built management platforms such as Nerdio Manager automate.
Where Nerdio Manager fits across Windows Cloud paths
Nerdio Manager automates the customer-managed layer that Microsoft's shared responsibility model leaves with your team. One console covers Windows 365, Microsoft Intune, and Azure Virtual Desktop, and it handles the endpoint policy, image, application, license, and cost work that the taxonomy does not remove.
One console for Windows 365, Intune, and Azure Virtual Desktop
Nerdio Manager handles image updates, host pool scaling, storage tiering, and cost control from a single interface. Administrators run those workflows without moving between the Azure Portal, Microsoft Intune, Entra ID, PowerShell, and custom scripts. Unified Application Management (UAM) deploys applications to Cloud PCs in around 30 seconds compared to up to 3 hours with native Intune.
License, right-sizing, and cost automation
Nerdio Advisor flags oversized Cloud PCs so your team can right-size them and reclaim underused licenses. Nerdio Manager also supports Intune policy backup and restore. Patented auto-scaling stops and deallocates idle Azure Virtual Desktop session hosts to reduce compute charges, and it switches storage tiers for stopped-and-deallocated hosts during off-hours to reduce storage costs. An independent benchmark test from Dr. Benny Tritsch measured custom image updates at 88% less time and 91% fewer clicks than native tooling. Fewer manual steps also means fewer configuration errors across host pools.
Consistent policy across mixed Windows Cloud estates
Many enterprises run both Windows Cloud paths, and policy consistency matters in that mixed estate. For Windows 365, that means repeatable UAM deployment and Intune policy backup, with Cloud PC right-sizing and license reclamation handled the same way. For Azure Virtual Desktop, it means repeatable image updates and host pool cost controls, with auto-scaling rules and storage tiering applied consistently. Each workload keeps the service model and cost model that fit its users.
What the service model decision means for your desktop estate
Gartner sized the DaaS market at $4.3 billion for 2025, growing to $6.0 billion by 2029 at a 7.9% CAGR, per its August 2025 Magic Quadrant. Next to Gartner's 2025 forecasts for SaaS ($299.071 billion), IaaS ($211.856 billion), and PaaS ($208.644 billion), DaaS is the smallest tier on the chart and the one your end-user computing strategy actually lives in.
The same Magic Quadrant observes that DaaS "is now deployed within most organizations, generally to only a minority of employees within those organizations." The category has landed; the scale-out is still ahead.
Your recommendation deck should center on responsibility, with the acronym glossary kept in a supporting role. SaaS and PaaS questions belong to your application teams. The desktop question is which Windows Cloud path fits which workload. The next decision is who handles golden images, Intune policy, and scaling discipline. In Gartner's DaaS market category, Azure Virtual Desktop moves the broker, gateway, and underlying cloud infrastructure to Microsoft, but still leaves session hosts, images, policy, and scaling discipline with your team. Planning for the work it leaves behind is what makes the model deliver what the deck promised.
Whether your recommendation lands on Windows 365, Azure Virtual Desktop, or both, the management work the shared responsibility model leaves with your team is the part worth automating from day one. Get a demo to see how Nerdio Manager works across your Windows 365 and Azure Virtual Desktop environment, or try it free in your Azure tenant.
Frequently asked questions about SaaS vs. PaaS vs. IaaS vs. DaaS
Resources
Learn more about Nerdio Manager
