mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-07-04 03:33:36 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into perf-test
This commit is contained in:
@ -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).
|
||||||
|
@ -177,7 +177,7 @@ sections:
|
|||||||
*Convenience PIN* provides a simpler way to sign in to Windows than passwords, but it still uses a password for authentication. When the correct convenience PIN is provided to Windows, the password information is loaded from its cache and authenticates the user. Organizations using convenience PINs should move to **Windows Hello for Business**. New Windows deployments should deploy Windows Hello for Business and not convenience PINs.
|
*Convenience PIN* provides a simpler way to sign in to Windows than passwords, but it still uses a password for authentication. When the correct convenience PIN is provided to Windows, the password information is loaded from its cache and authenticates the user. Organizations using convenience PINs should move to **Windows Hello for Business**. New Windows deployments should deploy Windows Hello for Business and not convenience PINs.
|
||||||
- question: Can I use a convenience PIN with Microsoft Entra ID?
|
- question: Can I use a convenience PIN with Microsoft Entra ID?
|
||||||
answer: |
|
answer: |
|
||||||
No. While it's possible to set a convenience PIN on Microsoft Entra joined and Microsoft Entra hybrid joined devices, convenience PIN isn't supported for Microsoft Entra user accounts (including synchronized identities). Convenience PIN is only supported for on-premises Active Directory users and local account users.
|
No. While it's possible to set a convenience PIN on Microsoft Entra joined and Microsoft Entra hybrid joined devices, convenience PIN isn't supported for authenticating Microsoft Entra user accounts (including synchronized identities). Convenience PIN is only supported for authenticating users to on-premises Active Directory and local account users. Organizations that want to authenticate to Microsoft Entra should deploy Windows Hello for Business, which provides users with an Entra credential that can be used to access Entra-protected resources. Organizations that do not use Windows Hello for Business can choose to deploy convenience PINs on their workstations, including Entra Joined or Entra Hybrid Joined workstations used by on-premises or synchronized user accounts, but convenience PIN will not be able to provide authentication or SSO to Entra. The convenience PIN may still be used for logging into the user's PC or for storing other credentials used by the organization, such as certificates or passkeys.
|
||||||
- question: What about virtual smart cards?
|
- question: What about virtual smart cards?
|
||||||
answer: |
|
answer: |
|
||||||
Windows Hello for Business is the modern, two-factor authentication for Windows. Customers using virtual smart cards are strongly encouraged to move to Windows Hello for Business.
|
Windows Hello for Business is the modern, two-factor authentication for Windows. Customers using virtual smart cards are strongly encouraged to move to Windows Hello for Business.
|
||||||
|
@ -8,7 +8,7 @@ author: mestew
|
|||||||
manager: bpardi
|
manager: bpardi
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.date: 05/21/2025
|
ms.date: 06/24/2025
|
||||||
ms.collection:
|
ms.collection:
|
||||||
- highpri
|
- highpri
|
||||||
- tier2
|
- tier2
|
||||||
@ -36,7 +36,7 @@ ESUs doesn't include the following items:
|
|||||||
- New features
|
- New features
|
||||||
- Customer-requested nonsecurity updates
|
- Customer-requested nonsecurity updates
|
||||||
- Design change requests
|
- Design change requests
|
||||||
- General support won't be provided for Windows versions past the end of support date. The Windows 10 ESU only includes support for the license activation, installation, and possible regressions of the ESU itself. To get technical support for the ESU, organizations must have an active [support plan](https://www.microsoft.com/microsoft-unified) in place. <!--9913216-->
|
- General support won't be provided for Windows versions past the end of support date. The Windows 10 ESU only includes support for the license activation, installation, and possible regressions of the ESU itself. To get technical support for these issues related to the ESU, organizations must have an active [support plan](https://www.microsoft.com/microsoft-unified) in place. <!--9913216-->
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user