Skip to main content

Blog

Windows 365 explained: what it is, how it works, and who it's for

Windows 365 explained: how Cloud PCs work, how it compares to AVD, and what operational gaps appear at scale.

Your CIO wants a cloud desktop strategy. Your Citrix renewal is six months out. Three different teams just sent you three different definitions of "Cloud PC." 

This guide is for IT directors and EUC leaders who need enough Windows 365 fluency to set evaluation criteria before their technical teams start testing. You will walk away knowing what Windows 365 is, how it provisions and delivers desktops, where it fits alongside Azure Virtual Desktop, and what operational gaps show up at scale.

Windows Cloud, Microsoft's umbrella term for Windows 365 and Azure Virtual Desktop, frames that broader portfolio context from the start.

What Windows 365 actually is

Windows 365 is a cloud-based SaaS product from Microsoft that creates a dedicated virtual machine, called a Cloud PC, for each licensed user. Microsoft hosts the Cloud PC in Azure, manages the underlying compute and storage, and charges a fixed per-user fee. You assign a license, and a Cloud PC is provisioned for your user.

Windows 365 sits within Microsoft's cloud desktop portfolio alongside Azure Virtual Desktop, its more configurable virtualization counterpart.

Windows 365 abstracts infrastructure entirely. Your team does not rack servers, manage hypervisors, or troubleshoot capacity. You do not see an Azure compute bill. You do not manage host pools or session hosts. Microsoft manages the underlying service infrastructure for Windows 365, while OS patching on Cloud PCs is the customer or IT administrator's responsibility.

Each Cloud PC is persistent and dedicated. The user gets their own virtual machine with their own apps, settings, and files. Close the lid on your laptop in London, open a browser in Chicago, and your desktop picks up where you left off.

How Cloud PCs are provisioned and accessed

Provisioning is automated and policy-driven, triggered once per user per license assignment.

The provisioning workflow

An admin creates a provisioning policy in Microsoft Intune admin center. The policy defines the network connection, the Cloud PC image, including gallery or custom images, and other configuration options such as region, language, and license type. That policy is assigned to a Microsoft Entra ID security group. When a user who holds a Windows 365 license lands in that group, the service provisions their Cloud PC automatically.

The automated sequence takes roughly 20–30 minutes. The service automatically creates and manages a Cloud PC as a virtual machine in Microsoft's hosted cloud. It connects the Cloud PC to either Microsoft's managed network or your own Azure virtual network, joins the device to Microsoft Entra ID or Hybrid Microsoft Entra ID depending on configuration, completes Intune enrollment, and delivers a desktop ready for sign-in. No admin touches the VM directly. No user credentials are required during enrollment.

The network architecture decision

A Microsoft-hosted network requires no Azure subscription and works for cloud-native, Entra ID-only organizations. An Azure network connection requires a customer-managed virtual network and supports hybrid scenarios where Cloud PCs need line-of-sight to on-premises Active Directory. Hybrid organizations needing on-premises connectivity will use the Azure network connection path. Fully cloud-native organizations can skip it entirely.

How users connect

Users access their Cloud PC through the Windows App, available on Windows, macOS, iOS, Android, and web browsers. The primary web portal is windows.cloud.microsoft. The older windows365.microsoft.com address is deprecated. Windows 365 Link is a stateless thin client for Cloud PC access and is managed through Intune. Microsoft made it generally available on April 2, 2025.

Assign a license, point a user at the Windows App, and the desktop exists. Management platforms like Nerdio Manager for Enterprise provide one console for Windows 365, Intune, and Azure Virtual Desktop, plus application management and image management across both Windows 365 and Azure Virtual Desktop.

Editions, pricing, and which workloads fit

Windows 365 spans multiple editions, each designed for different organizational profiles and worker types.

Editions at a glance

Windows 365 Business supports up to 300 users and is designed for organizations without Intune, Entra ID P1, or an Azure subscription requirements in the same way as Windows 365 Enterprise, though a Windows 365 Business license and Microsoft Entra ID are still required. Purchase directly and manage through the Microsoft 365 Admin Center. It is designed for smaller organizations that want simplicity above all else.

Windows 365 Enterprise is licensed per user and is managed through Intune, with support for Conditional Access. It requires Intune and Entra joined or Hybrid Azure AD joined devices.

Windows 365 Flex (formerly Frontline) targets shift and occasional workers with a shared-capacity licensing model. In Dedicated mode, one license can support up to three Cloud PCs for three named users who never work simultaneously. In Shared mode, one license provisions a single shared Cloud PC, and user data does not persist between sessions, as described in Microsoft's Windows 365 FAQ.

Two additional Windows 365 offerings reached general availability in late 2025. Windows 365 Reserve provides temporary Cloud PC access for hardware delays, ransomware recovery, or short-term projects. Windows 365 Cloud Apps lets organizations deliver specific applications without provisioning a full desktop per user, as described in Microsoft's Cloud Apps announcement.

Pricing structure

Windows 365 Enterprise pricing follows fixed tiers based on vCPU, RAM, and storage. As of May 2026, the Standard plan (2 vCPU, 8 GB RAM, 128 GB storage) runs $41 per user per month, while the Basic plan starts at $31. Premium configurations with 4 vCPU and 16 GB RAM start at $66. GPU-enabled configurations are available in Windows 365 Enterprise and Windows 365 Flex in Dedicated mode only, with pricing through your account team at Microsoft Sales.

The fixed pricing model means costs are predictable by design. Every user pays the same monthly rate regardless of usage. That simplifies budgeting, so optimizing license allocation matters for organizations with variable usage patterns. Nerdio Advisor can flag underutilized licenses, recommend right-sizing, and identify Windows 365 Flex conversion opportunities for users who never overlap.

That predictability covers every user identically, so understanding Azure Virtual Desktop's consumption model matters for mixed workforces. Microsoft's published sizing guidance emphasizes rightsizing Cloud PCs to user needs based on workload and performance demands.

The comparison with Azure Virtual Desktop centers on service cost and service model fit for the worker and the operational model behind it.

How Windows 365 differs from Azure Virtual Desktop

Windows 365 and Azure Virtual Desktop are both Microsoft products. They both run inside Azure, authenticate through Entra ID, and connect through the Windows App. Microsoft presents them as different service models for different operational preferences.

The service model split

Windows 365 is SaaS. Microsoft manages the VMs. You pay a flat rate per user. Azure Virtual Desktop is a platform service where your team manages session host VMs, images, scaling, and network topology. Azure compute, storage, and networking costs are billed on consumption.

Where the capabilities diverge

Azure Virtual Desktop supports multi-session pooled desktops, where multiple users share a single VM through individual sessions. This Windows 10/11 Enterprise multi-session capability is associated with Azure Virtual Desktop and is an important mechanism for driving per-user costs down at scale.

Azure Virtual Desktop also supports RemoteApp and Windows Server session hosts, and it can run on Azure Local. Windows 365 supports App streaming for Windows 365 (single-app access from a Cloud PC), which is similar in concept to RemoteApp.

Windows 365 scales administratively: assign or remove licenses. Azure Virtual Desktop scales dynamically through autoscale plans that start and stop session hosts based on demand.

The decision framework for your evaluation

The platform that you choose should be based on your worker profiles and organizational capacity. A blanket preference usually fails.

  • Full-time daily-use knowledge workers fit Windows 365's fixed cost model well
  • Shift workers and call center agents benefit from Azure Virtual Desktop's multi-session pooled model
  • Temporary contractors who do not need persistent state align with Azure Virtual Desktop's consumption billing
  • Part-time or occasional users fit Windows 365 Flex's concurrent licensing
  • Workloads requiring custom VM sizes, GPU flexibility, or Windows Server use Azure Virtual Desktop

Many enterprises run both platforms together. Because both share the Windows App and Entra ID authentication, end users see a single unified feed regardless of which platform delivers their desktop. Worker persona segmentation is a common pattern in enterprise deployments.

The choice centers on how each service fits inside a broader Windows Cloud strategy. That shared portfolio context shapes how your team manages both day to day.

Where Windows 365 fits in the Windows Cloud portfolio

Windows 365 is part of a broader ecosystem. That ecosystem creates operational surface area, and the management gaps that emerge at scale determine whether the platform works for your organization or creates new problems.

Microsoft Intune is the common management plane across the portfolio for Windows 365. Cloud PCs are provisioned through Intune using provisioning policies created in the Intune admin center. The Windows App is the unified client, replacing the legacy Remote Desktop client.

Windows 365 Boot and switch

Windows 365 Boot lets a physical Windows 11 device boot directly into a Cloud PC. Windows 365 Switch lets users toggle between their local desktop and Cloud PC through Task View.

Boot reached general availability with new capabilities including Connection Center support in September 2025. Windows 365 Switch expanded to support Windows 11 Home edition for BYOD scenarios, as noted in Microsoft's Windows App updates recap.

Cloud PC pools and AI agents

At Ignite 2025, Microsoft highlighted new virtual desktop infrastructure capabilities as organizations explored broader AI-driven automation scenarios.

What changes when you manage Cloud PCs at enterprise scale

Provisioning a handful of Cloud PCs through Intune is straightforward. Managing hundreds or thousands introduces operational challenges that native tooling does not yet cover at enterprise depth.

Monitoring arrived years after launch

Windows 365 launched in August 2021. Native Cloud PC monitoring in the Intune admin center entered public preview in April 2026. Enterprises deploying at scale relied on Intune's built-in reporting and Endpoint Analytics for Cloud PC visibility before more dedicated native monitoring capabilities became available. Advanced monitoring features require either the Intune Suite add-on ($10 per user per month beyond the base subscription) or Microsoft 365 E3/E5, according to 4sysops.

Application deployment lags

Native Intune application delivery can take up to three hours because Intune does not poll continuously. For an organization deploying a critical security patch across 2,000 Cloud PCs, a three-hour delivery window is operationally significant.

License waste is invisible by default

Windows 365 Cloud PCs are always on. Users do not see a shutdown option. Admins can perform power actions such as power on, power off, and restart for Windows 365 Cloud PCs in the Intune admin center, as described in the Cloud PC lifecycle documentation. There is no native mechanism for identifying underutilized licenses or reclaiming them automatically. You pay a fixed amount for licensed capacity regardless of actual usage.

Multi-environment administration splits across consoles

Organizations running both Windows 365 and Azure Virtual Desktop manage two fundamentally different operational models. Windows 365 is Intune-centric. Azure Virtual Desktop is managed primarily through Azure Portal and PowerShell. Native administration still spans multiple surfaces rather than one dedicated console across both products. Admins jump between consoles, and policy consistency across platforms requires manual coordination.

These gaps make the management layer you deploy on top of Windows 365 a factor in whether the platform scales successfully.

Nerdio Manager across Windows 365 and Azure Virtual Desktop

Nerdio Manager sits inside your Azure tenant as an automation and management layer for Windows 365, Intune, and Azure Virtual Desktop. 

It provides a single console across all three, with agentless insights, monitoring, and desktop orchestration that centralizes golden image creation, updates, and distribution for Cloud PCs and Azure Virtual Desktop session hosts from one interface.

That shared layer shows up in platform-specific ways on each path.

On Windows 365: faster app delivery, Intune policy protection, license right-sizing

Nerdio Manager deploys applications to Cloud PCs in  roughly 30 seconds through unified application management, compared to native Intune delivery that can take up to three hours. 

Nerdio Advisor surfaces utilization insights, recommends appropriate Cloud PC sizing and license types, flags underutilized licenses for reclamation, and identifies Windows 365 Flex conversion opportunities. Nerdio also backs up, versions, and restores Intune compliance and configuration policies, which matters because native Intune cannot restore a deleted policy. 

The City of Corona centralized management of Azure Virtual Desktop, Intune, and Windows 365 with Nerdio, while reducing the manual work needed to manage endpoints.

On Azure Virtual Desktop: auto-scaling that cuts Azure compute spend

Nerdio's patented auto-scaling dynamically powers session hosts up and down based on real-time demand.  Sage reported $1.5 million in annual savings and grew from 200 to 1,000 customers without adding headcount after deploying Nerdio Manager for their Azure Virtual Desktop environment.

The shared console matters because many enterprises run both Windows 365 and Azure Virtual Desktop. Without it, your team operates two distinct operational models with two distinct toolsets. Nerdio Manager centralizes common management tasks across both platforms at $3 per Windows 365 user per month.

With that in view, you can set evaluation criteria based on delivery model, worker fit, and day-two operations rather than on provisioning alone.

Setting your evaluation criteria

The CIO's cloud desktop strategy now has a concrete framework: 

  • Windows 365 for predictable, SaaS-delivered desktops
  • Azure Virtual Desktop for consumption-based flexibility
  • Both together for mixed workforces

Your Citrix renewal decision has clear comparison points across cost model, management overhead, and worker persona fit. And your three teams can align on what "Cloud PC" actually means: a dedicated, persistent, Intune-managed virtual machine running in Azure, provisioned through policy and accessed through the Windows App.

Windows 365 and Azure Virtual Desktop are distinct service models, and many enterprises use both together. This approach aligns the platform to the worker type across use cases. The management layer is what determines whether either path works cleanly at scale.

That resolves the three tensions that opened this guide: strategy, renewal timing, and definition. The remaining decision is how you want to manage cloud costs at scale across Windows 365 and Azure Virtual Desktop.

Get a demo to see how Nerdio Manager works across your Windows 365 and Azure Virtual Desktop environment, or try it free in your own Azure tenant.

Frequently asked questions about Windows 365

Ready to get started?