Windows 365 Flex Shared Mode (Formerly Frontline): How It Works and Who It Fits
Windows 365 Flex shared mode lets a group of people take turns on a pool of Cloud PCs, with one license covering one Cloud PC and one active session at a time. Each person signs in with their own work account, uses a clean Cloud PC for a shift or a task, and signs out. Their data is deleted and the Cloud PC goes back to the pool for the next person. It is the Windows 365 answer for call centers, retail counters, training rooms, contractors, and any team where the number of people is much bigger than the number of people working at the same moment.
Microsoft sold this product as Windows 365 Frontline until May 2026, so many admins still search for it under the old name. The licensing and features did not change with the rename, but the product has grown: shared mode reached general availability, Cloud Apps arrived, User Experience Sync went live, and snapshot-based reset entered preview. This guide explains how shared mode works, who it fits, how to count licenses, what happens to user data, how to set it up, and where the limits are. Every technical detail comes from Microsoft’s documentation, and we flag anything still in preview.
Key Takeaways
- One license, one Cloud PC, one session. In shared mode, a license provisions a single Cloud PC that a group of users share, and only one person can use it at a time.
- You license for overlap, not headcount. The number of people working at the same moment sets how many licenses you need, not the number of people on the payroll.
- Data does not stay behind. User data is deleted at sign-out unless you redirect it to OneDrive or turn on User Experience Sync.
- Frontline and Flex are the same product. Microsoft renamed Windows 365 Frontline to Windows 365 Flex in May 2026 without changing licensing or capabilities.
- Cloud Apps are an option. Shared mode can publish individual apps instead of a full desktop, which suits single-purpose roles.
- Check the gaps first. Snapshot-based reset is still in preview, Windows Autopatch is not available, and resize and cross-region recovery are listed as not yet supported for Flex.
What Is Windows 365 Flex Shared Mode?
Windows 365 Flex is the version of Windows 365 built for people who do not need a Cloud PC to themselves all day. It has two modes, and the difference between them is the whole story. In dedicated mode, one license covers up to three Cloud PCs, each assigned to a different person, with one of them active at a time. In shared mode, one license covers one Cloud PC that an entire group of users shares, again one person at a time.
The idea behind shared mode is simple. Imagine a support team of 90 people working three eight-hour shifts. At any moment only about 30 of them are on the clock, so giving all 90 a personal Cloud PC means paying for 60 desktops that are idle at any given hour. With shared mode you provision a pool sized for the people who work at once, assign the pool to a group, and let people take whichever Cloud PC is free. When someone signs out, their session ends, their data is removed, and the Cloud PC is ready for the next person.
If you are new to the platform, our overview of how a Cloud PC works covers the basics before you go deeper into shared mode.
Frontline Is Now Flex: What the Rename Changed
Microsoft renamed Windows 365 Frontline to Windows 365 Flex in May 2026. Microsoft’s release notes are explicit that the product, licensing, and capabilities are unchanged and only the name is different. The change reflects how the product is used: it was never limited to frontline workers, and Microsoft now positions it for any worker who does not need a dedicated PC all day.
That matters for three reasons. Older articles and forum answers still say Frontline, and they are still accurate about how the product works. You may see both names in Microsoft’s admin portals while the change rolls through, so do not assume two products. And the terms you will meet now are Flex dedicated mode, Flex shared mode, and Flex Cloud PCs, which this article uses.
The timeline below shows how quickly shared mode has matured, based on Microsoft’s release notes.
| When | What Microsoft released | Status |
|---|---|---|
| March 2025 | Frontline shared mode moved out of preview | General availability |
| September 2025 | Windows 365 Cloud Apps for Flex shared Cloud PCs | Preview, then GA in November 2025 |
| November 2025 | User Experience Sync for shared mode and Cloud Apps | General availability |
| March 2026 | Up to 5,000 Cloud PCs per shared provisioning policy, plus a dozen more regions | Available |
| April 2026 | Snapshot-based reset for shared Cloud PCs | Public preview |
| May 2026 | Frontline renamed to Flex | Rename only |
| June 2026 | GPU-enabled Cloud PCs and more flexible naming templates in shared mode | Available, naming in preview at first |
Shared Mode vs Dedicated Mode
Both modes sit under the same Flex license family, so it is easy to confuse them. The quickest way to tell them apart is to ask one question: does each person need a Cloud PC that is theirs, with their files and settings waiting when they sign in? If yes, you want dedicated mode. If people only need a clean, standard desktop for the length of a shift or a task, you want shared mode.
| Factor | Dedicated mode | Shared mode |
|---|---|---|
| Cloud PCs per license | Up to 3 | 1 |
| Concurrent sessions per license | 1 | 1 |
| User assignment | One user per Cloud PC, assigned through a Microsoft Entra ID group | Any user in the Microsoft Entra ID group |
| Data persistence | Persists between sessions | Deleted after each session, unless User Experience Sync keeps app data and Windows settings in the cloud |
| What limits active sessions | Total Flex licenses in the tenant, excluding shared-mode licenses | Licenses allocated to the group |
| Concurrency buffer | Available, with limited extra sessions per day | Not available |
Dedicated mode fits people who expect a familiar desktop, such as part-time staff on rotating schedules, and our guide to ways to trim your Cloud PC spend covers it alongside the other levers. Shared mode fits when the desktop is a tool, not a personal workspace.
How a Shared Cloud PC Session Works
A shared Cloud PC session has a predictable life, and each stage affects the limits you set.
The user opens Microsoft’s Windows App and connects to the shared Cloud PC. The service picks a free Cloud PC from the pool assigned to the user’s group. Only one person can connect to a given shared Cloud PC at a time, and the maximum number of active sessions equals the number of licenses assigned to the group. If ten licenses are assigned, ten people can work at once, and an eleventh person has to wait for a free Cloud PC.
While the session runs, time limits apply. By default, a shared Cloud PC disconnects an idle session after 15 minutes and signs out a disconnected session after 30 minutes, and Intune policy can change both. When the session ends, the user’s profile is deleted and the profile cache is cleared, and the Cloud PC returns to the pool.
One detail catches many teams out. Disconnected sessions can block new connections when the maximum number of active sessions has been reached. A person who closes their laptop at the end of a shift without signing out keeps a Cloud PC busy until the disconnected-session limit ends their session. That is why sign-out habits and sensible time limits matter more in shared mode than in dedicated mode.
How Shared Mode Licensing Works
Shared mode licensing differs from the per-user model most Microsoft products use, so it is worth slowing down here.
- Licenses are pooled at the tenant level. Flex licenses are not assigned to individual users. In the Microsoft 365 admin center, Flex licenses appear as assigned to zero users, and you use the Windows 365 utilization report to see actual usage.
- Licenses are allocated to groups. The licenses you allocate to a group decide how many shared Cloud PCs it gets and how many people in the group can be active at once.
- Each user still needs prerequisites. Every person who uses a Flex Cloud PC must be licensed for Windows 11 Enterprise or Windows 10 Enterprise, Microsoft Intune, and Microsoft Entra ID P1.
- Many suites already include those prerequisites. Microsoft 365 E3, E5, F3, A3, A5, and Business Premium include them, as do Microsoft 365 Education Student Use Benefit subscriptions.
- Flex is its own product. It is not governed by the eligibility conditions that apply to Microsoft 365 F1 and F3 licenses.
- You buy through the Microsoft 365 admin center. Confirm quantities under Billing, then Your products.
Plan prerequisites by people and Flex licenses by overlap: the prerequisites must cover everyone who signs in, but the Flex licenses only need to cover how many people work at the same time. If you want help working out the right mix, Apps4Rent handles licensing and support for Cloud PC plans as a Microsoft Cloud Solution Provider, and current pricing is listed there.
Who Shared Mode Fits, and Who It Does Not
Microsoft describes shared mode as the right choice for workers who need a Cloud PC for specialized tasks for a short time during the workday and do not need their data to persist, such as customer-facing workers and external contractors. In practice, a few patterns come up again and again.
| Scenario | Fit | Why |
|---|---|---|
| Call center and support desks | Strong | Agents work set shifts on the same apps, and a clean desktop each time reduces drift and support tickets |
| Retail, kiosks, and front counters | Strong | Several staff share a few stations, and Cloud Apps can show only the point-of-sale or booking app |
| External contractors and vendors | Strong | Access ends cleanly, nothing is left on a device they own, and no personal Cloud PC is left to deprovision |
| Training rooms and classes | Strong | Every learner starts from the same clean desktop |
| Seasonal and temporary staff | Good | The pool grows and shrinks with demand, and nobody keeps a license after the season |
| Staff who work full days on a personal desktop | Poor | People expect their files, tabs, and settings to be waiting, which dedicated mode or Enterprise handles better |
| Developers and power users | Poor | They install their own tools and keep long-running state on the machine |
Seasonal staffing deserves a closer look, because it is where many organizations first feel the cost of one-desktop-per-person. If your headcount swings with the calendar, see our guide to seasonal and temporary workforces for how the alternatives compare. And for shared physical desks, a small Cloud PC device built for shared desks pairs naturally with a pool of shared Cloud PCs, since neither one holds data after the session ends.
How Many Licenses Do You Need?
The sizing rule for shared mode is to license for your busiest moment, not for your headcount. Count how many people are signed in at the same time during your peak hour, add room for handoffs, and start there.
Here is how to work it out, step by step.
- Find your peak overlap. Use scheduling or call-center data to find the largest number of people who are signed in together, including the minutes when one shift is leaving and the next is arriving.
- Add handoff room. A person who disconnects without signing out holds a Cloud PC until the disconnected-session limit ends the session. A handful of spare Cloud PCs keeps new arrivals from waiting.
- Split by group. Licenses are allocated per group, so give each team the pool it needs instead of one large shared pool that a single busy team can drain.
Because shared mode has no concurrency buffer, there is no safety valve for a surprise spike. If a team regularly hits its limit, add licenses to that group instead of hoping the limit will flex. One more detail: when you add licenses to a tenant that has both modes, Microsoft provisions dedicated Cloud PCs first.
What Happens to User Data and Settings
Every shared-mode project has to answer this before launch. By default, nothing a user does on a shared Cloud PC is kept: the profile is deleted at sign-out, and user files and settings are not retained. That is good for security and consistency, but it surprises people used to a personal desktop, so plan for it.
OneDrive Known Folder Move
Windows 365 configures OneDrive on shared Cloud PCs with silent sign-in, Known Folder Move for Desktop, Documents, and Pictures, and Files On-Demand. Anything users save in those folders lives in OneDrive, not on the Cloud PC, so it is there for them on any other Cloud PC. For many shared roles, this is all the persistence you need.
User Experience Sync
User Experience Sync is for people who need more than OneDrive folders to follow them. It was built for shared mode and Cloud Apps, and it saves Windows personalization, accessibility settings, application settings and data, and the contents of the user’s profile folder. Each provisioning policy gets a pool of cloud storage and each user a slice, which is attached at sign-in and detached at sign-out.
- Per-user storage: you choose 4, 8, 16, 32, or 64 GB when you enable it.
- Pool size: the pool equals the OS disk size multiplied by the number of Cloud PCs in the assignment. Microsoft’s example is a 128 GB disk across 10 Cloud PCs, which gives a 1.28 TB pool.
- Going over the limit: new users get a temporary profile, and after a seven-day tolerance period the service deletes the storage with the oldest last-attach time.
- What it does not keep: user-installed applications. Only their settings and data are stored, and some non-roamable folders are excluded.
- Not a backup: Microsoft describes it as an experience feature, not a backup or disaster recovery tool. Removing the assignment permanently deletes all user storage.
Decide before launch, because turning it on or off for an existing policy means removing and re-adding the group assignment, which deprovisions every Cloud PC in it. FSLogix profiles do not migrate directly either. For more on how persistence differs across desktop types, see our comparison of persistent and non-persistent desktops.
Snapshot-Based Reset (Preview)
Snapshot-based reset is the newest piece, and Microsoft still labels it a public preview. After each sign-out, it restores the Cloud PC to a clean baseline captured at provisioning and refreshed daily, so one person’s changes never carry over to the next. During a reset the Cloud PC shows as Unavailable (Servicing) and cannot take new connections. Microsoft cites about three minutes for a reset in the preview, so treat that as a preview figure, not a promise.
Reset and reprovisioning work together. Reset gives you a clean state between users, while reprovisioning handles major changes such as OS upgrades and image updates and becomes part of the new baseline. Microsoft’s advice is to avoid patching individual shared Cloud PCs, because changes made at runtime are discarded at reset. Instead, change the image or the app targeting and reprovision the pool.
Cloud Apps or Full Desktop?
When you create a shared provisioning policy, Microsoft asks you to pick an experience type. You can give users a full Cloud PC desktop, or you can publish only the apps they need. The second option, Windows 365 Cloud Apps, is available only for Flex in shared mode. Microsoft moved Cloud Apps to general availability in November 2025, and a Flex license entitles you to stream them from shared-mode Cloud PCs.
| Question | Full desktop | Cloud Apps |
|---|---|---|
| What users see | A complete Windows desktop | Only the published apps, in their own windows |
| Best for | Roles that use several apps, files, and the Start menu | Single-purpose roles such as booking, point of sale, or a line-of-business app |
| Training effort | Low, because it looks like Windows | Very low, because users see one app |
| Attack surface | Larger, with the whole desktop reachable | Smaller, with Task Manager disabled |
If you choose Cloud Apps, the image step can show the applications Windows 365 discovered on your image, and you publish the ones you want after the policy is created. You can also add an app by file path, which reached general availability in August 2026. For a cashier or a booking agent, seeing only the app is often exactly what you want.
How to Set Up Windows 365 Flex Shared Mode
The setup below follows Microsoft’s documented flow. Exact menu labels move around in the Intune admin center, so use these steps as a checklist and confirm the screen names as you go.
-
Step 1: Confirm prerequisites
Make sure everyone who will sign in is licensed for Windows Enterprise, Microsoft Intune, and Microsoft Entra ID P1, and that your region supports shared mode.
-
Step 2: Buy Flex licenses
Purchase Windows 365 Flex licenses in the Microsoft 365 admin center, sized for peak overlap. Do not be alarmed when they show as assigned to zero users, because Flex licenses are pooled at the tenant level.
-
Step 3: Create groups for each team
Create a Microsoft Entra ID security group for each team that will share a pool. Nested groups are not supported for assignments, so add users directly, and keep teams separate so one busy team cannot use up another’s Cloud PCs.
-
Step 4: Create the provisioning policy
In the Intune admin center, create a provisioning policy with Windows 365 Flex as the license type and Shared as the Flex type. Then choose a full Cloud PC desktop or Cloud Apps as the experience type.
-
Step 5: Choose join, network, image, and region
Pick Microsoft Entra join or Hybrid Microsoft Entra join, and a Microsoft hosted network or your own Azure network connection, which must be in the same region for shared mode. Choose a gallery or custom image, a single region group or specific region, and whether to enable User Experience Sync.
-
Step 6: Assign the group and set the size
Assign the Entra ID group, choose a Cloud PC size, enter a friendly name that users will see in Windows App, and set the Cloud PC number for the group. A user with more than one policy always gets the first assigned policy.
-
Step 7: Set session limits and policies in Intune
Create a Settings catalog policy for the idle and disconnected session limits so they match your shifts, add any update, security, and redirection policies your roles need, and assign them to the groups.
-
Step 8: Pilot, then watch the numbers
Start with one team and one shift. Check sign-in times, session behavior, and what users lose at sign-out, then watch the Windows 365 utilization report and turn on the storage alert if you use User Experience Sync.
Microsoft documents each of these stages in detail, including how to create provisioning policies and what each setting does, so keep that page open while you build your first policy.
Defaults and Session Limits Worth Knowing
Windows 365 applies a set of defaults to shared Cloud PCs at provisioning, based on Microsoft’s virtual desktop optimization guidance. You can customize them with Intune, Group Policy, or other management tools. Knowing them in advance saves you from surprises during the pilot.
| Area | Default behavior on shared Cloud PCs |
|---|---|
| Idle sessions | Disconnect after 15 minutes |
| Disconnected sessions | End after 30 minutes, which returns the Cloud PC to the pool |
| Sign-out | Profile deleted and roaming profile cache cleared |
| Sign-in methods | PIN and FIDO security-key sign-in disabled, Windows Hello for Business still available |
| OneDrive | Silent sign-in, Known Folder Move for Desktop, Documents, and Pictures, and Files On-Demand |
| Windows updates | Installed before the first user signs in, and Insider preview builds are blocked |
To change the session limits, create a Settings catalog policy in Intune under Devices, then Configuration. Search for session time limits, or browse to Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits. Set the idle session limit and the disconnected session limit, then assign the policy to the groups that receive your Flex Cloud PCs. Microsoft’s guidance is to pick values that meet your own compliance requirements. A busy call center might shorten the disconnected limit so Cloud PCs return to the pool faster.
Keeping a Shared Pool Healthy
A shared pool is easier to run than a fleet of personal Cloud PCs, but it asks for a different rhythm. Think in terms of images and baselines, not individual machines.
- Update through the image. If you use snapshot-based reset, Microsoft recommends targeting a new app version to the device group and then reprovisioning the pool, so the change is captured in the next snapshot. For Windows quality updates, reprovision from the latest gallery image or a custom image instead of patching Cloud PCs one by one.
- Use scheduled reprovisioning. Windows 365 lets you schedule bulk reprovisioning for shared Cloud PCs, and since June 2025 you can set non-UTC time zones for the schedule.
- Know the Autopatch gap. Windows Autopatch is not available for shared mode, although you can still enroll shared devices in Autopatch manually and apply Windows Update policies.
- Scale with policies. A single shared provisioning policy now supports up to 5,000 Cloud PCs, which is far more than most teams need, so size by team, not by technical limit.
Limits to Check Before You Commit
Shared mode is mature enough for production, but it has edges. Check these items against your requirements before you promise anything to a business team.
| Area | What Microsoft documents | What to do |
|---|---|---|
| Regions and clouds | The Flex introduction page says shared mode is currently available only in Azure Global Cloud, and release notes list a dozen regions added in March 2026 | Confirm your region and cloud before you design |
| Resize and cross-region recovery | The introduction page lists the Resize action and cross-region disaster recovery as not yet supported for Flex, even though both have since shipped for dedicated mode | Check the current status for shared mode before relying on either |
| Concurrency buffer | Not available in shared mode, and excluded for GPU-enabled Cloud PCs | Allocate enough licenses per group |
| Snapshot-based reset | Public preview | Treat it as optional until it reaches general availability |
| Assignments | No nested groups, and only the first assigned policy applies per license | Use flat groups and avoid overlapping policies |
Business continuity deserves its own plan. If your shared pool supports a critical operation, read about the recovery options for Cloud PCs and ask whether each one applies to shared mode today. For roles that have to stay up through a regional outage, the honest answer is sometimes that another desktop type is the safer choice.
Shared Mode vs Other Ways to Deliver Desktops
Shared mode is one of several ways to give many people a Windows desktop. The right choice depends on how much control, persistence, and management effort you want.
| Option | Sharing model | Persistence | Management effort |
|---|---|---|---|
| Flex shared mode | One user per Cloud PC at a time, many users per pool | None by default, optional through User Experience Sync and OneDrive | Low, with Intune policies and no host pools to build |
| Flex dedicated mode | Up to 3 assigned users per license, one active at a time | Yes, per user | Low |
| Windows 365 Enterprise | One Cloud PC per user, always available | Yes | Low |
| Azure Virtual Desktop multi-session | Many users at once on the same virtual machine | Depends on your profile design | Higher, because you manage host pools and scaling |
Choose shared mode when each person needs a full, isolated Windows environment for a short time and you want Microsoft to run the plumbing. Choose multi-session when you have many simultaneous light users and are comfortable managing host pools, and read how Windows 365 compares with Azure Virtual Desktop first. If you would rather have a provider run the servers, session-based hosted desktops are another path.
Security Considerations for Shared Cloud PCs
Shared mode has real security strengths. Nothing a user does is kept after sign-out, so there is little data at rest on a shared Cloud PC, and every session starts from a known state. Each user still signs in with their own Microsoft Entra ID account, so access, auditing, and Conditional Access apply to individuals, not to a shared login. Shared mode also supports Microsoft Purview Customer Key for service encryption.
It is not a free pass, though. Set clipboard, drive, and printer redirection deliberately for each team, because they can move data between the Cloud PC and a user’s own device. Test your multi-factor and Conditional Access flows with real shift workers before launch, since PIN and FIDO sign-in are disabled by default. And give people an approved place to save work, such as OneDrive, because local data is deleted. For deeper hardening, our guide to locking down Cloud PCs covers controls that also apply to a Flex pool.
Get a Shared Cloud PC Plan Built Around Your Shifts
Tell us how many people work at once, and we will size the pool.
Our Microsoft-certified consultants will review your shifts, roles, and apps, recommend the right mix of shared mode, dedicated mode, and Enterprise, and handle the licensing, setup, and support for you.
Frequently Asked Questions
-
What is Windows 365 Flex shared mode?
Windows 365 Flex shared mode is a mode in which one license provisions one Cloud PC that a group of users share, one person at a time. User data is deleted at sign-out, and the Cloud PC returns to the pool for the next person. It suits call centers, kiosks, contractors, and other roles where many people need a desktop but few work at the same moment.
-
Is Windows 365 Frontline the same as Windows 365 Flex?
Yes. Microsoft renamed Windows 365 Frontline to Windows 365 Flex in May 2026. The product, licensing, and capabilities did not change, only the name, so older articles about Frontline shared mode still describe how the product works.
-
Does shared mode keep my files and settings?
Not by default. At sign-out, the user’s profile is deleted and the Cloud PC is released. OneDrive Known Folder Move, which is configured by default, keeps files, and User Experience Sync keeps settings, app data, and profile files, with 4 to 64 GB per user. User-installed applications are not kept.
-
How do I count licenses for shared mode?
Count the largest number of people signed in at the same time, then add a few spare Cloud PCs for shift handoffs, since a disconnected session holds a Cloud PC until its time limit ends. Allocate licenses per group, and use the utilization report after launch to adjust.
-
What Microsoft licenses do users need for Flex?
Each user who connects needs Windows 11 Enterprise or Windows 10 Enterprise, Microsoft Intune, and Microsoft Entra ID P1, in addition to the Flex licenses. Microsoft 365 E3, E5, F3, A3, A5, and Business Premium include those prerequisites.
-
Can shared mode publish just an app instead of a full desktop?
Yes. Windows 365 Cloud Apps is available with Flex in shared mode. When you create the provisioning policy, choose the experience type that lets users access only apps that run on a Cloud PC, and then publish the apps you want.
-
How is Flex shared mode different from Windows 365 Enterprise?
Enterprise gives each user a persistent Cloud PC of their own. Flex shared mode gives a group a smaller pool of Cloud PCs that people use one at a time, with data deleted at sign-out. Shared mode usually fits shift-based work, and Enterprise fits people who work full days on their own desktop.
-
What are the default session timeouts for shared Cloud PCs?
By default, an idle session disconnects after 15 minutes, and a disconnected session ends after 30 minutes. You can change both with an Intune Settings catalog policy for Remote Desktop Services session time limits.
-
Can I resize or add cross-region recovery to a shared Cloud PC?
Microsoft’s Flex introduction page lists the Resize action and cross-region disaster recovery as not yet supported, although both have since arrived for dedicated mode. Check Microsoft’s current documentation for shared mode before you plan around either one.