Windows 365 added Resultant Set of Policies, or RSOP, to Monitor Cloud PCs in public preview. Microsoft published the related documentation on November 17, 2026, updated the Monitor Cloud PCs overview on November 18, 2026, and identified Windows 365 Cloud PCs as the affected deployment type.
For Windows 365 administrators, endpoint architects, and IT leaders, the signal is clear: connection-level redirection troubleshooting now has a Microsoft-provided view of effective settings and their contributing policy sources. This is not a new enforcement layer. It is a diagnostic view for explaining an existing connection result.
1. RSOP Exposes Effective Redirection Policies
What changed: Microsoft says RSOP reports whether supported redirection settings were enabled or disabled for a specific Windows 365 Cloud PC connection. It also identifies the policy sources contributing to that result, allowing administrators to investigate why a redirection was allowed or blocked.
The initial public-preview release covers four redirection areas:
- Clipboard: Whether clipboard redirection was enabled or disabled for the selected connection.
- Drive and storage: The effective drive and storage redirection result.
- Printer: Whether printer redirection was available to the connection.
- USB: The effective USB redirection setting and its reported policy sources.
This narrows a common troubleshooting task from reviewing policies in isolation to examining the result attached to a connection. The distinction matters.
Why this matters: Redirection outcomes can be difficult to explain when several policy sources contribute to a connection configuration. According to Microsoft, RSOP connects the observed result with the sources that produced it, giving administrators a direct starting point when users report that clipboard, storage, printer, or USB access was unexpectedly available or unavailable.
However, the preview does not calculate policy precedence or enforce a different result. Microsoft explicitly describes RSOP as reporting rather than a policy evaluation or enforcement engine.
This is not a policy simulator. It is connection evidence.
Admin action: In the Microsoft Intune admin center, navigate to Devices > Monitor Cloud PCs under Manage Windows 365 Cloud PCs. Open View data, select the Connection configuration tab, choose a connection, and review the effective redirection settings and reported policy sources.
Microsoft says no new policy deployment is required. Your team can evaluate the reporting experience without adding another redirection policy to the tenant.
Access requires attention to role configuration. Microsoft notes that only administrators whose roles have no assigned scope tags can access Monitor Cloud PCs. Before using RSOP as an operational troubleshooting step, verify that the responsible support and endpoint teams can open the required monitoring view.
There is also a timing limitation. Microsoft says the values reflect settings evaluated for the selected connection, so the displayed result may differ from current policy settings when policies changed after the connection was established.
Why this matters: Administrators should treat the connection timestamp and later policy changes as part of the investigation. A mismatch does not necessarily indicate faulty reporting; it may represent an older connection evaluated under an earlier configuration.
Because RSOP remains in public preview, your team should validate its output against known connection scenarios before incorporating it into a formal incident or compliance workflow. Preview evidence can accelerate diagnosis, but it should not become the sole basis for a production policy decision.
What Cloud PC Admins Should Do Next
Confirm access immediately. Verify that the administrators responsible for Cloud PC troubleshooting can reach Monitor Cloud PCs and that their roles have no assigned scope tags.
Test the four supported redirection areas. Review known connections involving clipboard, drive and storage, printer, and USB redirection, then compare the reported result with the expected user experience.
Record connection timing. When policies have changed, compare those changes with when the selected connection was established before escalating a suspected configuration mismatch.
Keep enforcement workflows unchanged. Use
RSOPto investigate policy outcomes, not to replace policy evaluation, precedence analysis, or configuration controls.Evaluate before operational adoption. Because the feature is in public preview, document any discrepancies and monitor Microsoft’s Windows 365 documentation before making
RSOPa required support procedure.
