The direct answer: For Dedicated mode, count personal Cloud PCs and peak concurrent sessions separately. For Shared mode, plan available machines within each group. Every user also needs the prerequisite entitlements and rights for the applications they use. The documentation was checked on 12 October 2026. This is not a general rule allowing user licences to be divided by three.
Check the name as well as the product
Microsoft’s management guide explains the change from Windows 365 Frontline to Windows 365 Flex. Parts of the administration interface may still display the earlier name. Search results therefore use both.
That matters if your team filters devices automatically. A public dynamic-group discussion reports a different device Model value. It is a reason to inspect your rules, not proof that every deployment changed identically. Check actual properties of newly provisioned devices and the group rules relying on them.
An order and design should identify the product, Cloud PC size and mode. “Frontline licence” alone does not specify what will be provisioned.
The two modes have different planning units
According to the Windows 365 Flex overview, one Dedicated licence permits up to three Cloud PCs, each assigned to one user, with one concurrent session. Shared provisions one PC for a group to use sequentially, also with one session. Sign-out removes local user data and releases the PC. Shared has no concurrency buffer.
| Design question | Dedicated mode | Shared mode |
|---|---|---|
| What is assigned? | A personal Cloud PC | Access to a shared pool |
| Basis for quantities | Personal PCs and concurrency | Concurrency in each group |
| Is a personal environment needed between visits? | Usually yes | Verify storage and any cloud restoration of settings |
| What does overlapping work consume? | Shared concurrency allowance | Capacity of the relevant pool |
| What should the pilot test? | Peak sign-in and return to personal work | Handover, profile cleanup and access to saved data |
User Experience Sync is available for Shared. It attaches user storage containing settings, files and app data, then retains that storage in the cloud for the next session. It does not preserve apps installed by the user and is not backup or disaster recovery. Separate local PC cleanup from retained cloud storage. Test the actual app, storage allowance and save location.
A sizing lower bound for Dedicated
For an initial design of one pool using the same configuration, apply two independent constraints. U is the number of users needing personal Cloud PCs. C is the planned maximum number of concurrent sessions. The licence quantity must cover both provisioning and peak operation.
Derived planning lower bound: L ≥ max(ceil(U / 3), C). This is our calculation from the documented rights, not a new Microsoft licensing meter. It does not cover mixed Cloud PC sizes, other modes consuming the tenant’s pool or an operational reserve; add those to the actual design.
Hypothetical example: Thirty-six users require twelve licences to provision their personal PCs. If fourteen people need access simultaneously during a handover, twelve licences do not cover planned normal operation. The lower bound is fourteen. Some provisioning entitlement remains unused; the purchase covers concurrency as well as the possible number of personal PCs.
If only eight people connect simultaneously, the minimum remains twelve because all thirty-six still need personal PCs. Headcount divided by three and concurrency alone can each give the wrong answer. No price or predicted saving is included in this example.
Size Shared by group
Shared fits brief tasks where people do not need their own local environment. Establish which groups actually share a pool. Two groups with separate PCs cannot borrow each other’s capacity in a budget spreadsheet merely because total tenant concurrency appears low.
Hypothetical example: One group normally peaks at seven simultaneous users and a second at four. With separate pools, plan seven and four machines: eleven licences for this design. If the groups peak at different times, that sum may exceed the tenant-wide simultaneous maximum. This is not an arithmetic mistake; the capacity is separated operationally.
Combining groups is reasonable only if they can use compatible configurations, access rules and applications. Membership count does not answer whether the next person will find an available, correctly equipped PC. For a sensitive system, consider what wider group membership permits.
Low average hours can hide a high peak
“Everyone uses it for just two hours a day” says nothing about whether those hours start at the same time. Include handovers, closing periods, team meetings and local application failures that may send more people to Cloud PCs. Also measure how long a session remains occupied after the client disconnects.
The utilisation report shows individual Cloud PC usage over a selected period and helps identify inactive or lightly used machines. Total hours alone do not reveal concurrent sessions. The Connected Windows 365 Flex Cloud PCs report provides size-specific concurrency, current sessions and peak history. Check filters and Shared assignments, then add your pilot observations.
Plan for an ordinary peak with an agreed reserve. The concurrency buffer in supported Dedicated scenarios is intended for limited situations, not daily missing capacity. Shared has no such buffer.
Closing the client is not necessarily signing out
Distinguish closing Windows App, disconnecting and signing out of Windows. Users may consider all three the end of work, but a shared environment must release the session and clean up at the right time.
The Flex management documentation describes Shared defaults of signing out idle sessions after fifteen minutes and ending disconnected sessions after thirty. Management settings can affect the configuration. Size against the behaviour verified in your tenant, not the moment someone closes a window.
In the pilot, have one person finish and sign out, then another connect immediately. Repeat after merely disconnecting. Observe waiting time and file state. Save required documents to the intended persistent storage and verify synchronisation before sign-out. An output left in local Downloads should not become a production discovery.
The Flex pool does not license every user or app
The Flex licensing prerequisites require each user to have Windows Enterprise, Intune and Entra ID P1. Microsoft also lists bundles containing these rights. Flex licences are pooled at tenant level, so administration may show zero users assigned. That alone is not a provisioning error.
Flex has separate product rules and is not governed by Microsoft 365 F1/F3 eligibility conditions. That does not make F3 appropriate for any role. The user’s underlying package must still be valid for their work. See our Microsoft 365 F3 eligibility guide.
Check Word, Excel and other software too. Shared Cloud PCs run Microsoft 365 Apps in shared computer activation mode. Microsoft’s SCA guidance requires an eligible plan for each user; activation by one person does not cover others. Meeting Cloud PC prerequisites is not proof of desktop Office rights. Specialist software may also use separate concurrency, user or virtualisation terms.
What the pilot must establish
- Mode and groups. Identify who needs a personal Cloud PC and who needs brief shared access; record separate pools.
- Provisioning and peak load. Count personal PCs, simultaneous sessions, overlapping work and the chosen PC sizes.
- Session handover. Observe disconnect versus sign-out, waiting time for the next person and actual timeout behaviour.
- Data. Verify where results are saved, whether they synchronise and what survives sign-out.
- Entitlements. Check user prerequisites, the Flex pool, Office and every work app separately.
- Operational threshold. Decide who adds capacity when peaks regularly exceed the design and which measurement triggers that review.
Frequently asked questions
Does one licence allow three people to work simultaneously?
No. Dedicated permits up to three personal Cloud PCs but provides one concurrent session per licence. Shared also provides one session.
Is Shared counted in the same way as Dedicated?
No. Shared provisions one shared PC per licence and requires available capacity in the assigned group. Dedicated also constrains the number of personal PCs.
Why does administration show zero assigned Flex users?
The licences form a tenant pool rather than being individually assigned like ordinary user subscriptions. Inspect quantities, provisioning and utilisation reports.
Is low average daily use enough to size the pool?
No. Low total hours can hide a brief peak during which everyone needs access at once.
Do desktop documents survive a Shared session?
Do not assume so without checking configuration. Shared cleans the local user profile; files may remain in OneDrive or User Experience Sync storage. Test a specific file, its location and its return in the next session.
