deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-07-04 19:53:38 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #10953 from MicrosoftDocs/main
Some checks failed
(Scheduled) Publish to live / auto-publish (push) Has been cancelled
Details
(Scheduled) Mark stale pull requests / stale (push) Has been cancelled
Details
(Scheduled) Stale branch removal / stale-branch (push) Has been cancelled
Details

Browse Source 
[AutoPublish] main to live - 06/23 13:33 PDT | 06/24 02:03 IST
This commit is contained in:
m365-skilling-repo-management[bot]
2025-06-23 20:36:58 +00:00
committed by GitHub
parent 41d1939e02 6b7bea0892
commit 5ea7c07f40
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
windows/client-management/manage-recall.md
View File

@ -3,7 +3,7 @@ title: Manage Recall for Windows clients
description: Learn how to manage Recall for commercial environments and about Recall features. description: Learn how to manage Recall for commercial environments and about Recall features.
ms.topic: how-to ms.topic: how-to
ms.subservice: windows-copilot ms.subservice: windows-copilot
ms.date: 06/13/2025 ms.date: 06/23/2025
ms.author: mstewart ms.author: mstewart
author: mestew author: mestew
ms.collection: ms.collection:
@ -185,7 +185,7 @@ Before starting an export, the user must authenticate with Windows Hello and the
> [!Important] > [!Important]
> - This setting applies to devices in the European Economic Area (EEA) only. Export of Recall snapshots is a user-initiated process and is per user. IT admins or other users can't initiate an export on behalf of another. > - This setting applies to devices in the European Economic Area (EEA) only. Export of Recall snapshots is a user-initiated process and is per user. IT admins or other users can't initiate an export on behalf of another.
> - Changes to this policy take effect after device restart. > - Changes to this policy take effect after device restart.
> - Developer documentation will be coming at a later date. > - For information about adding exported Recall snapshots to your application or website, see [Decrypt exported snapshots from Recall](/windows/ai/recall/decrypt-exported-snapshots).
|   | Setting | |   | Setting |
|---|---| |---|---|
@ -226,6 +226,8 @@ If you're a developer and want to launch Recall, you can call the `ms-recall` pr
If your remote desktop connection doesn't support screen capture protection, then it's an easy feature to add. Windows allows applications to exclude their window from being included in screenshot. This DRM flag is set by the application as a property on its window. It's a simple feature for application developers to implement using [SetWindowDisplayAffinity function (winuser.h)](/windows/win32/api/winuser/nf-winuser-setwindowdisplayaffinity). By setting the flag `WDA_EXCLUDEFROMCAPTURE`, the window content won't show up in Recall or any other screenshot application. If your remote desktop connection doesn't support screen capture protection, then it's an easy feature to add. Windows allows applications to exclude their window from being included in screenshot. This DRM flag is set by the application as a property on its window. It's a simple feature for application developers to implement using [SetWindowDisplayAffinity function (winuser.h)](/windows/win32/api/winuser/nf-winuser-setwindowdisplayaffinity). By setting the flag `WDA_EXCLUDEFROMCAPTURE`, the window content won't show up in Recall or any other screenshot application.
If you're a developer and need information about adding exported Recall snapshots to your application or website, see [Decrypt exported snapshots from Recall](/windows/ai/recall/decrypt-exported-snapshots).
## Microsoft's commitment to responsible AI ## Microsoft's commitment to responsible AI
Microsoft has been on a responsible AI journey since 2017, when we defined our principles and approach to ensuring this technology is used in a way that is driven by ethical principles that put people first. For more about our responsible AI journey, the ethical principles that guide us, and the tooling and capabilities we've created to assure that we develop AI technology responsibly, see [Responsible AI](https://www.microsoft.com/ai/responsible-ai). Microsoft has been on a responsible AI journey since 2017, when we defined our principles and approach to ensuring this technology is used in a way that is driven by ethical principles that put people first. For more about our responsible AI journey, the ethical principles that guide us, and the tooling and capabilities we've created to assure that we develop AI technology responsibly, see [Responsible AI](https://www.microsoft.com/ai/responsible-ai).