In Windows 365, the license is the hardware. Every sizing mistake you would have made in a procurement cycle, you can now make monthly, and a few of the doors only swing one way.
The first article in this series argued that Windows 365 is a decision about who operates the platform. This one is about the decision you keep making after that: what to buy, in what shape, for whom. Windows 365 pricing is built on four variables, vCPU, RAM, storage, and the user model, and the fixed SKUs that combine them are the whole catalog. There is no custom instance type, no reserved capacity negotiation, no spot pricing. That constraint is the product working as designed, and it rewards organizations that treat sizing as an ongoing discipline rather than a one-time guess.
The license is the machine
The mental shift that matters most: a Cloud PC’s size is tied to the license assigned to its user. Change the machine and you are changing the license; change the license and you are changing the machine. This has practical consequences that surface later, in operations, so it pays to design for them now. Resizing a Cloud PC upward, more vCPU, more RAM, more storage, is supported and does not require reprovisioning. Resizing downward is supported for compute and memory only. Storage never shrinks. A 512 GB Cloud PC is a 512 GB commitment for the life of that machine, and the only way back down is a reprovision that destroys the desktop.
Storage is the one-way door. Size compute to today’s workload and storage to your conservative estimate, because only one of them forgives a mistake.
The second consequence is organizational rather than technical. Because resize operations are license operations, the structure of your Entra groups determines how painful they are. Keep the groups that assign Windows 365 licenses separate from the groups that target provisioning policies. When they are the same group, every resize becomes a delicate sequencing exercise; when they are discrete, a resize is a membership change. This is the same argument for deliberate group design that runs through the whole Intune series, showing up in a new place.
On sizing itself, my guidance is unglamorous: size to observed workload behavior, not to job title. The middle SKUs cover the substantial majority of knowledge work. The GPU-enabled SKUs exist for genuine visualization and compute workloads, and they carry two extra constraints worth knowing before you commit: GPU Cloud PCs cannot be resized at all, and in the Flex model they are available in dedicated mode only. If the GPU tier is under consideration, the physical workstation deserves a fair hearing in the same conversation, because the monthly delta compounds.
Flex is a concurrency purchase, not a user purchase
Windows 365 Flex, renamed from Frontline in May 2026 with no change to licensing or features, is the piece of the catalog most worth understanding properly, because it changes what you are actually buying. An Enterprise license buys a user a machine. A Flex license buys your organization a concurrent session, and how you spend that session is a design choice between two modes.
Dedicated mode gives up to three users their own personal, persistent Cloud PCs on a single license, with the constraint that only one of the three can be active at a time. Tenant-wide, your maximum concurrent sessions equal your license count: ten licenses can provision thirty Cloud PCs, ten of them active at once. A concurrency buffer absorbs shift-handoff overlap a limited number of times per day. The machines power off when the user signs out and power on at connection, with predictive prestart smoothing the morning experience. Each user keeps their apps, data, and settings, which is what separates this from the shared-device misery it replaces.
Shared mode is a different instrument. One license provisions one Cloud PC assigned to a group, used by one person at a time, wiped back to a clean state when they sign out. User Experience Sync can carry application settings across sessions, but the model is fundamentally stateless. Shared mode is also the foundation for Windows 365 Cloud Apps, which publish a single application instead of a full desktop, and that is often the honest answer for the tablet-carrying worker who needs one line-of-business app and nothing else. There is no concurrency buffer in shared mode, and as of this writing it is limited to the Azure Global cloud.
Three Flex facts routinely surprise people in planning. First, Flex carries the same licensing prerequisites as Enterprise, Windows Enterprise plus Intune plus Entra ID P1 per user, and it is not governed by the Microsoft 365 F1 or F3 eligibility conditions, so do not assume the frontline suite you already own covers it. Second, Flex licenses show as assigned to zero users in the admin center, because they attach to the concurrency pool rather than to people; the Windows 365 utilization report is where the truth lives, and watching it is how you right-size the pool as shift patterns drift. Third, Flex gives up operational levers Enterprise has: no in-place resize, so the size you provision is the size you keep until reprovisioning, and no cross-region disaster recovery. Sizing Flex therefore means sizing for peak concurrent sessions, not headcount, and getting the SKU right the first time, because the correction is destructive.
Reading the price signals
I deliberately avoid printing dollar figures in articles like this, because they vary by geography and channel and go stale. The structural signals age better. In May 2026 Microsoft cut Windows 365 Business list pricing by twenty percent across all configurations, and in the same breath retired the Windows Hybrid Benefit, the discount that had rewarded Business customers whose primary device already carried a Windows Pro license. Read together, the message is simplification: one lower price, no entitlement arithmetic, aimed squarely at the small-business buyer comparing a Cloud PC against a cheap laptop.
For Enterprise customers on an EA, step-up licenses are the mechanism worth knowing: they convert a lower-configuration subscription to a higher one without paying for both, and they pair with the bulk resize workflow when a whole population outgrows its SKU. That is the shape of the mature Windows 365 estate, in my experience. Not a perfect initial sizing, but a licensing structure, discrete license groups, a watched utilization report, and a step-up path, that makes correction cheap in the direction the platform allows and deliberate in the direction it does not. The next article turns from what you buy to how you build: the provisioning policy, the join type, and the networking decision that determines who actually owns the path your Cloud PCs take to the world.
Windows 365
‹ Previous: [W365 1] What Windows 365 Actually Is, and the Decision It Represents
Next: [W365 3] Designing the Enterprise Deployment ›
