Windows 365 Cloud PC Settings Reaches General Availability — What It Means for IT Admins

Microsoft has been steadily building toward a unified settings experience for Windows 365 throughout 2026. First came the navigation reorganization in April that created a dedicated Settings area in the Intune admin center. Then the Remote connection experience entered preview in March. Settings policy reranking showed up as a preview just last week. Now, the pieces have come together: Cloud PC Settings is generally available in Microsoft Intune.

This isn’t just a feature shipping — it’s the graduation of an entire management framework from preview to production. If you’re managing Windows 365 Cloud PCs today, this changes how you should think about configuration.

What Cloud PC Settings GA Actually Delivers

The GA announcement confirms that administrators can now configure four distinct object types through the Cloud PC Settings framework:

1. Cloud PC Configurations

These are the policies that govern how Cloud PCs behave at the system level — think of them as the device configuration profiles specific to Cloud PCs. This includes settings around provisioning behavior, image selection, and system-level policies that apply to Cloud PCs as a managed device class within Intune.

2. Windows App Settings

Windows App — the client application users interact with to connect to their Cloud PCs — now has its own configurable settings object. Admins can control how the Windows App behaves on endpoint devices, including connection preferences, display settings, and client-side behaviors. This is particularly important for BYOD scenarios where the Windows App runs on unmanaged or personally owned devices.

3. Remote Connection Experience

Previously announced as a public preview in March 2026, the Remote connection experience is now part of the GA settings framework. This enables IT administrators to configure connection-level settings that apply just-in-time when users connect to targeted Cloud PCs. These settings can be assigned to specific device groups through Microsoft Intune to tailor and manage how users interact with their Cloud PC during remote sessions.

Key capabilities include:

Dynamic control of clipboard, printer, drive, and USB redirection behavior
Policy enforcement based on user identity, device compliance, and network conditions
Server-side policy enforcement for BYOD scenarios — no reliance on client-side controls

4. User Settings

User settings provide admin control over what end users can do with their Cloud PCs:

Enable local admin — Elevate users to local administrator of their own Cloud PCs
Enable user-initiated reset — Allow users to wipe and reprovision their own Cloud PCs
Allow user-initiated restore — Let users restore their Cloud PCs to available backup versions
Cross-region disaster recovery — Protect Cloud PCs during regional outages

Settings can be applied before or after a Cloud PC is assigned, and changes take effect when the user next logs on. User settings don’t apply to Windows 365 Flex Cloud PCs in shared mode.

Why This Matters: From Scattered to Centralized

Before this GA, managing Cloud PC configuration meant navigating multiple areas of the Intune admin center. User settings lived in one place. Remote connection settings were in preview under a different blade. Windows App configuration was handled through Intune app protection policies or Group Policy. Cloud PC configurations were part of the provisioning workflow.

The Cloud PC Settings framework brings all four object types under a single management surface with a consistent policy model:

Create a settings policy → choose the object type → configure → assign to groups
Rerank policies to control precedence when conflicts exist (announced as preview last week)
Monitor policy application through Intune’s existing reporting

This is the same pattern Intune uses for device configuration profiles, compliance policies, and app protection policies. Windows 365 configuration now follows the same mental model — create, assign, monitor — that Intune admins already know.

The Settings Policy Reranking Connection

The “Rerank settings policies” feature announced the week of July 6 as a public preview is directly related to this GA. When you have multiple settings policies assigned to the same user or device group, conflicts can arise — one policy enables local admin while another disables it, or two remote connection experience policies specify different clipboard redirection rules.

Reranking lets administrators:

Drag and drop policies to change their priority
Move policies up or down in the list
Explicitly define which policy takes precedence

This capability only makes sense in the context of a multi-policy framework — which is exactly what the Cloud PC Settings GA establishes. The fact that reranking shipped as a preview the week before the settings framework went GA suggests Microsoft planned this as a coordinated release.

Practical Implications for IT Admins

For Existing Windows 365 Deployments

If you’re already managing Cloud PCs, you likely have existing user settings, provisioning policies, and possibly remote connection experience policies configured during the preview period. The GA milestone means:

Production support — These settings are now backed by GA-level SLAs and support. If something breaks, you can open a support ticket with confidence.
Stable API surface — The Graph API endpoints for managing Cloud PC settings are now stable. If you’ve been automating configuration through PowerShell or Graph, you can build on them without worrying about breaking changes.
Documentation is finalized — The settings overview documentation now reflects the GA feature set, making it easier to train new admins.

For New Windows 365 Deployments

If you’re just starting with Windows 365, the Cloud PC Settings framework is your starting point — not the legacy scattered configuration points. Plan your configuration architecture around the four object types from day one:

Map your requirements to object types — Which settings are device-level (Cloud PC configurations)? Which are user-level (User settings)? Which are connection-level (Remote connection experience)? Which are client-level (Windows App settings)?
Design your policy structure — Group-based assignment is the primary mechanism. Consider how many policies you need and how they’ll be scoped.
Plan for conflicts — With multiple policy types potentially overlapping, understand the reranking capability and how precedence works.

For Organizations Using Windows 365 Flex

User settings don’t apply to Windows 365 Flex Cloud PCs in shared mode — that’s an important distinction. If you’re managing Flex shared environments, your configuration focus should be on:

Cloud PC configurations (device-level)
Windows App settings (client-level)
Remote connection experience (connection-level)
Cloud Apps-specific settings within provisioning policies

For Security and Compliance Teams

The Remote connection experience being part of the GA settings framework is significant for security teams. The context-based redirection capabilities — dynamically controlling clipboard, printer, drives, and USB based on user identity, device compliance, and network conditions — are now production-ready. This enables:

Conditional access-style controls for remote sessions — Restrict clipboard access when connecting from non-compliant devices
Network-aware policy enforcement — Allow file transfer on corporate networks, block on public Wi-Fi
BYOD data protection — Server-side enforcement means policies can’t be bypassed by client-side configuration changes

What IT Admins Should Do Now

Audit your current configuration:

Document existing user settings, remote connection experience policies, and any preview-era configurations
Identify which settings are currently managed through legacy paths that should move to the Cloud PC Settings framework

Plan your policy architecture:

Map each configuration requirement to one of the four object types
Design group-based assignment strategies that minimize policy count while maintaining granularity
Consider how reranking will be used to resolve conflicts

Test the GA experience:

Create new settings policies in a test/pilot group
Validate that policy application works as expected across all four object types
Test reranking behavior when multiple policies target the same group

Update documentation and runbooks:

Replace references to legacy configuration paths with the new Cloud PC Settings framework
Document the policy architecture you’ve designed
Train help desk and operations teams on the new settings model

Evaluate security posture:

If you haven’t already, evaluate context-based redirection for your BYOD scenarios
Review whether current clipboard, printer, drive, and USB redirection policies are appropriate
Consider whether network-aware policy enforcement adds value for your environment

The Bigger Picture

The Cloud PC Settings GA is the latest in a series of Intune integration milestones for Windows 365:

Navigation reorganization (April 2026, GA) — Dedicated Windows 365 area in Intune with Settings as a first-class navigation item
Remote connection experience (March 2026, preview → now GA) — Connection-level policy control
Settings policy reranking (July 6, 2026, preview) — Conflict resolution for multi-policy environments
Cloud PC Settings GA (July 13, 2026) — The framework itself reaches production maturity

This trajectory is clear: Microsoft is making Windows 365 a first-class Intune workload with a management experience that mirrors how other Intune-managed devices work. The days of Windows 365 being a bolt-on to Intune are over. Configuration, compliance, app delivery, and monitoring for Cloud PCs now follow the same patterns as physical devices.

For organizations investing in Windows 365 — whether Enterprise, Flex, or Reserve — this is a foundational change. Build your operational procedures around the Cloud PC Settings framework now, and you’ll benefit from the consistency and automation capabilities that come with it.

Action Items Summary

Audit existing Cloud PC configuration and identify what should move to the new settings framework
Design your policy architecture across the four object types (Cloud PC configurations, Windows App settings, Remote connection experience, User settings)
Test the GA experience in a pilot group, including policy reranking for conflict resolution
Evaluate context-based redirection for BYOD security scenarios
Update documentation, runbooks, and training materials to reflect the new framework

Big Hat Group helps organizations deploy and optimize Windows 365 and Microsoft Intune environments. Need help with Cloud PC Settings architecture, policy design, or Intune integration? Get in touch.