Microsoft has added Session State Retention to the Windows 365 What’s New page, now in public preview for eligible Windows 365 Flex dedicated Cloud PCs. The capability targets one of the most visible friction points in the Cloud PC experience: coming back to a disconnected session and finding your work gone.

For IT leaders, this is a quality-of-life change worth tracking — it moves the reconnect experience toward something users never have to think about, and it arrives with configuration decisions that belong in your hands, not Microsoft’s defaults.

1. What Session State Retention Actually Does

Today, an idle Cloud PC eventually powers off — and with it goes the user’s active session. Session State Retention changes that behavior for eligible Windows 365 Flex dedicated Cloud PCs: after a user has been disconnected for a configurable idle period (2 hours by default), the Cloud PC preserves the session state instead of powering off.

On the next connection, users return to their open apps and work exactly where they left off. There is no manual save ritual, no lost context, and no “reopen everything” tax on the workday.

Why this matters: Session loss is one of the top everyday complaints in virtual desktop environments. Eliminating it removes a real productivity drag — and a real helpdesk driver — for Flex dedicated users.

2. How It Complements Intelligent Pre-start

Session State Retention does not stand alone. It is designed to work alongside Intelligent pre-start, which powers the Cloud PC on ahead of time so it is ready when the user needs it.

The pairing is deliberate: Intelligent pre-start handles device readiness (the Cloud PC is on and waiting), while Session State Retention handles session continuity (your work is still in it). Together they push the reconnect model toward one where readiness and continuity are invisible — users do not change how they work, and they do not manage either capability.

Why this matters: Each capability alone solves half the problem. A powered-on Cloud PC with a cold session still costs the user minutes; a preserved session on a powered-off Cloud PC still costs the boot. Combined, the reconnect approaches the local-device experience.

3. What to Validate During the Preview

This is a public preview scoped to eligible Windows 365 Flex dedicated Cloud PCs — not a tenant-wide switch. Before you lean on it operationally:

  • Confirm eligibility for your Flex dedicated Cloud PCs rather than assuming coverage across the estate.
  • Review the idle-period default. A Cloud PC that preserves state instead of powering off is a Cloud PC that stays available longer — make sure the 2-hour default matches your usage patterns and your cost posture before tuning it.
  • Test with real workloads. Session restore fidelity is exactly the kind of behavior that varies by application mix; validate the apps your users actually live in during the preview window.

Why this matters: Preview capabilities change. Testing now means you understand the behavior — and the policy levers — before the feature reaches broad availability and user expectations harden around it.

The Bottom Line

Session State Retention is a focused, sensible improvement: keep the session alive, pair it with a Cloud PC that is already warm, and the reconnect experience disappears into the background. For Windows 365 Flex dedicated environments, it is worth a deliberate preview evaluation now rather than a surprised adoption later.

Need help aligning Windows 365 capability rollouts with your endpoint strategy? Talk to Big Hat Group’s advisory team.