(Updated) Plan for change: Snapshot-based reset for Windows 365 Flex shared Cloud PCs

Updated July 27, 2026: We have updated the timeline and content. Thank you for your patience. 

[What and Why:]

Starting in early September 2026, Windows 365 Flex shared Cloud PCs will change the default behavior of the reset operation when users sign out.

Today, when a user signs out of a Windows 365 Flex shared Cloud PC, only user data under C:\Users\<username> is removed between user sessions while system data (OS state, installed apps, and runtime changes) persists. 

After early September 2026, both user data and system data will be removed when a user signs out. The Cloud PC automatically resets and reverts to a clean state using a snapshot created during provisioning and refreshed periodically. As a result, each user session starts with a fully clean Cloud PC, with no data carried over between users. 

This change will only be enabled automatically on newly created shared provisioning policies, unless admins explicitly opt out at the policy level. For existing provisioning policies, admins can enable this new experience by editing the policies and reprovisioning the Cloud PCs.

[Rollout Schedule:]

This change will be implemented beginning early September 2026 (previously early July). 

[Impact on Your Organization:]

Who is affected:

• Organizations using Windows 365 Flex in shared mode
• Users of Windows 365 Flex shared Cloud PCs
• Admins managing Windows 365 Flex shared provisioning policies

What will happen:

• A snapshot restore point is captured during provisioning after initial configuration, and policies are applied.
• Snapshots are refreshed every 24 hours for each Cloud PC.
• When a user disconnects or signs-out, the Cloud PC automatically reverts to the most recent snapshot.  
• User impact:
  • Reset between users typically takes a few minutes. After the reset is complete, users can sign in shortly afterward.
  • Reset is still triggered when a user signs out or after a session timeout following a disconnect.
  • With User Experience Settings (UES) enabled, data stored within the user profile (for example, Desktop, Documents, and profile-based app settings) is retained and roams across sessions.
  • Without UES, no files, settings, or app configurations persist after sign-out.
• Admin impact: 
  • Cloud PCs may briefly appear as Unavailable (Servicing) during reset.
  • Snapshots are system-managed and not visible or configurable.
  • Changes made directly on the device (apps, updates, configurations) do not persist after reset.

[Action Required/Recommendations:]

• Review workloads that depend on device-level persistence between users and evaluate if you want to opt-out at the provisioning policy level.
• Identify workflows, scripts, or user habits that depend on changes remaining on the Cloud PC between sessions, and either include that state in the Cloud PC at provisioning (via Intune-managed apps and policies in the Device Provisioning Policy, then reprovision) or store it in cloud storage so it remains available after reset. 
• Set expectations on what UES covers. UES only retains data inside the user's profile. Guide users to save work inside their profile or to OneDrive / a network location. 
• Update internal documentation and helpdesk guidance. 

If no action is taken:

• Your Windows 365 Flex shared Cloud PCs will operate with snapshot-based reset enabled:
  • Devices will reset to the latest snapshot after each session.
  • Local changes made during a session will be removed. 
  • With UES enabled, only data within the user profile persists; otherwise, all data is cleared.

Learn more: Snapshot-based reset for Windows 365 Flex in Shared mode | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.