7.2 Windows 365 vs Azure Virtual Desktop

Quick Answer: Windows 365 is a software-as-a-service (SaaS) Cloud PC — typically one dedicated desktop per user, billed as a predictable per-user monthly license, with Microsoft managing the fabric. Azure Virtual Desktop (AVD) is an Azure desktop-as-a-service / VDI platform you design: personal or multi-session session hosts, custom images, RemoteApp, and Azure consumption billing. Both stream Windows from the cloud. Users connect with Windows App or a browser.

The April 30, 2025 MS-900 outline asks you to compare the differences between Windows 365 and Azure Virtual Desktop. Microsoft’s own training states the relationship cleanly: the two products are complementary, they both run on Azure infrastructure, they both deliver virtual Windows desktops, and they differ in implementation and who does the operating work. This is a recommend-the-service skill. You will not be asked to calculate vCPU density, design FSLogix storage, or quote a price list. You will be asked whether a company that wants “assign a license, get a personal Cloud PC” and a company that wants “many shift workers on one multi-session VM, billed like other Azure resources” are describing the same product. They are not.

What both products share

Start with the overlap so you do not fail a “which of these is true of both?” stem.

• Both deliver a full Windows desktop experience from the Microsoft cloud to a wide range of client devices (Windows, macOS, iOS, Android, and a web client).
• Both can present Windows 10 or Windows 11 Enterprise-class desktops (AVD can also use Windows Server).
• Users connect with Windows App (the current remote-desktop client) or a browser. Older stems may still say Remote Desktop client; the idea is the same: a remote Windows session, not a local install of Windows.
• Both can be part of a Microsoft 365 endpoint strategy and can work with Microsoft Entra ID and, in enterprise designs, Intune.
• An organization can run both. Knowledge workers who need a persistent personal PC often land on Windows 365. A contact-center or seasonal pool that should share compute often lands on AVD. That mix is official guidance, not a trick.

The exam then scores whether you can name the split: simplicity versus flexibility, 1:1 versus multi-session, SaaS versus an Azure resource you design, and who manages the fabric.

Windows 365: SaaS Cloud PC

Windows 365 is a cloud software-as-a-service that automatically creates a Cloud PC — a highly available virtual machine that gives the user a rich Windows desktop from anywhere. Official Learn: in Windows 365 Enterprise, Business, and Government, end users have a 1:1 relationship with their Cloud PC. It is their PC in the cloud. It persists. Apps, files they store on that desktop, and their Windows profile stay there the way they would on a physical laptop, except the hardware lives in Microsoft’s service.

Administrators do not manually create the virtual machine in the Azure portal as a day-one task. You purchase Windows 365 licenses, assign a license to a user in an Entra group, and attach a provisioning policy. The service creates the Cloud PC. Billing for human-use Cloud PCs is a per-user, per-month model. Microsoft’s point is predictability: you are not watching hourly VM meters the way you do for a classic host pool. Additional network usage charges can apply, especially when Enterprise uses a customer Azure virtual network; do not memorize unpublished dollar amounts.

Editions you can name at fundamentals level:

• Windows 365 Business — simplified deployment for smaller organizations (Microsoft documents a 300-seat scale target) that want ready-to-use Cloud PCs.
• Windows 365 Enterprise — unlimited seats, custom images, and full Intune management.
• Windows 365 Government — the US government community cloud path.

Microsoft later added Windows 365 Flex (nonconcurrent sharing to save cost) and preview agent SKUs. Those exist. For the April 30, 2025 comparison skill, treat the default Cloud PC as 1:1 and persistent. If a stem says “each user should get their own always-available Cloud PC for a fixed monthly fee,” the product is Windows 365, not Flex trivia.

Windows 365 is the simple answer. Microsoft operates the virtualization fabric — the hosts, the broker, the gateway experience inside the service. Enterprise admins still choose images, network join type (Entra join, or hybrid join with a customer virtual network), and Intune policies. They do not become Azure Virtual Desktop architects.

Azure Virtual Desktop: the platform you design

Azure Virtual Desktop is a desktop and app virtualization service that runs on Azure. Official highlights you should be able to repeat:

• Deliver Windows 11, Windows 10, or Windows Server.
• Use single-session (one user, one VM — a personal desktop) or multi-session (several users on one VM).
• Windows 11 and Windows 10 Enterprise multi-session is exclusive to Azure Virtual Desktop (or Windows Server). That is the density feature Windows 365’s default 1:1 Cloud PC does not try to be.
• Offer a full desktop or RemoteApp (publish individual applications without a full desktop).
• Bring your own image, optimize Microsoft 365 Apps for multi-user, and autoscale session hosts by time of day or demand.
• You manage the session-host virtual machines and images in your Azure subscription. Microsoft manages the control plane (broker, gateway, diagnostics). You do not build your own Remote Desktop gateway farm the way classic on-premises RDS required.

Microsoft Learn’s comparison module labels AVD a platform-as-a-service (PaaS) model: more granular customization, more hands-on administration. Windows 365 is the SaaS model. MS-900 language in the field also calls AVD desktop as a service (DaaS) or cloud VDI. Use whichever phrase the stem uses; the contrast is the same. AVD is not “Microsoft assigns a license and a Cloud PC appears.” AVD is “you create a host pool, add session hosts, create application groups and a workspace, assign users, and pay Azure for compute, storage, and networking.”

That consumption model is the cost flexibility. Turn session hosts off at night, pack shift workers onto multi-session VMs, or burst for a seasonal project. It is also the admin cost: someone must understand Azure networking, images, FSLogix-style profiles for pooled desktops, and scaling plans. If the stem says the company has no VDI specialists and wants a fixed monthly per-user fee, do not pick AVD.

The exam comparison table

Commit this table. It is the April 30, 2025 skill in one view.

Who manages the fabric is the line students blur. In Windows 365, Microsoft is responsible for creating and hosting the Cloud PC as a service. You still own identity, the user’s data, Intune policy, and (in Enterprise) the image and virtual network you choose. In AVD, the virtual machines are resources in your Azure subscription. You patch or replace those session hosts, pick SKU size, and decide when they run. Microsoft still runs the AVD control plane so you are not rebuilding a remote-desktop gateway. “Microsoft manages everything in AVD” is false. “You build the Cloud PC VMs by hand in Windows 365 Business” is also false.

When to recommend which

Translate the business sentence before you look at the options.

• “We want each knowledge worker to have a personal Windows desktop in the cloud that is always theirs, and finance wants a fixed per-user monthly cost.” → Windows 365.
• “We have no VDI team. Assign a license in Entra and let Microsoft stand the PC up.” → Windows 365.
• “Twenty call-center agents work staggered shifts and can share session hosts to save compute.” → Azure Virtual Desktop multi-session.
• “Users should launch only the line-of-business app, not a full desktop.” → Azure Virtual Desktop RemoteApp. Windows 365 is a full Cloud PC.
• “We need a custom image, FSLogix-style pooled profiles, and autoscale that shuts hosts off overnight.” → Azure Virtual Desktop.
• “Some executives need a persistent Cloud PC and the seasonal warehouse crew should be multi-session.” → both. That is a valid official answer when the stem offers it.

Windows 365 is not “AVD with a prettier name.” AVD is not “Windows 365 if you have Azure.” The products share a cloud desktop outcome. They do not share the operating model.

Realistic exam-style scenarios

Fixed cost, personal PC. A 200-person professional-services firm wants every consultant to open the same Windows desktop from a home laptop or an iPad. Leadership will not approve a variable Azure bill. Windows 365 with per-user monthly licensing. Do not design an AVD host pool “because it also has Windows.”

Shift density. A retailer hires 400 holiday associates who need Edge and a register app eight hours a day, not a dedicated VM each. Azure Virtual Desktop with Windows 11 Enterprise multi-session and autoscale. A 1:1 Cloud PC for every associate is the expensive, overly simple answer.

App-only. Finance wants SAP GUI published without giving contractors a full desktop. AVD RemoteApp. Windows 365 still delivers a complete Cloud PC.

Who clicks what. An Intune administrator can assign Windows 365 licenses and provisioning policies without living in the Azure portal. An AVD administrator lives in host pools and session hosts. If the stem says the only Azure skill on staff is “we created a resource group once,” prefer Windows 365 unless they explicitly need multi-session or RemoteApp.

Client confusion. A user asks whether they need a different app to open a Cloud PC versus an AVD desktop. Windows App (or the browser) can reach both. The client is not the differentiator. The service model is.

Not on-premises RDS. Replacing a datacenter Remote Desktop Services farm can be Azure Virtual Desktop (Microsoft even lists “replace existing RDS” as an AVD highlight). That is not Windows Autopilot, and it is not “install Intune on the old session hosts.”

Exam traps

• Do not invent prices. Remember per-user monthly versus Azure consumption. Microsoft publishes pricing pages; MS-900 does not require a dollar figure.
• 1:1 is the Windows 365 default, not a law of physics for every Microsoft desktop. AVD can also do personal desktops. Multi-session is the AVD-only Enterprise Windows capability you should reach for when the stem is about sharing a VM.
• SaaS versus platform. Windows 365 is the finished Cloud PC product. AVD is the Azure resource graph you assemble.
• Microsoft does not manage your AVD session hosts. It manages the control plane. You manage the VMs and images.
• Windows App is not a third product that replaces either service. It is how users connect to both.
• Autopilot and Autopatch are not Cloud PCs. Autopilot provisions a physical (or reset) Windows device. Autopatch updates it. Neither one is Windows 365.
• Intune is not a virtual desktop. Intune can manage a Cloud PC or a physical PC. It does not host the desktop.

Official sources

• What is Windows 365? — SaaS Cloud PC, 1:1 in Enterprise/Business/Government, per-user monthly billing
• What is Azure Virtual Desktop? — Azure virtualization service, multi-session, RemoteApp, you manage session hosts
• Compare Windows 365 Cloud PCs to Azure Virtual Desktop — official SaaS versus PaaS comparison table
• Windows App — current client for Windows 365, Azure Virtual Desktop, and related remote Windows
• Study guide for Exam MS-900 — compare Windows 365 and Azure Virtual Desktop