What’s changing
Microsoft has added a security capability called Screen Capture Protection. When it is active, the content of a remote session cannot be captured by screenshot tools or screen recording software running on the client device. The session window is blocked or blanked out in the resulting capture.
The goal is straightforward: reduce the chance that sensitive data displayed in a remote session leaves the managed environment through a screenshot, a recorded video, or malware that quietly grabs screen content. If an attacker or an unauthorised application on the endpoint tries to capture the session, they get nothing useful.
What it does and does not stop
It is worth setting expectations with users and stakeholders before rolling this out. Screen Capture Protection is a control against software-based capture on the device running the session. It is not a complete data loss prevention solution.
- Blocks screenshots and screen recordings of the protected session window taken on the client device
- Does not prevent someone photographing the screen with a phone or camera
- Does not replace information protection, conditional access, or DLP policies
- May affect legitimate workflows such as screen sharing during support calls or training
Enabling and disabling the feature
Screen Capture Protection is intended to be managed centrally rather than left to end users. Configure it through your usual endpoint management channel — policy settings delivered by Intune or Group Policy — so the setting is consistent across the estate and cannot be casually switched off.
Before you commit to a broad rollout, confirm the exact policy name and supported client versions in current Microsoft documentation, as the location and defaults can differ depending on the remote session technology and platform you are using. Do not assume the feature is on by default in your environment; verify it on a test device.
Recommendations for admins
Treat this as a targeted control for sessions that display regulated or confidential data, rather than a blanket setting for every user.
- Pilot with a small group and confirm the behaviour of capture tools, meeting apps, and remote support tooling
- Document the impact on helpdesk workflows so support staff are not caught out when screen sharing fails
- Communicate the change to users, including why screenshots of the session no longer work
- Pair it with broader protections such as conditional access and information protection labels
Source: Microsoft Learn. Summarised independently — check the source for the latest detail.