diff --git a/education/docfx.json b/education/docfx.json index f066cfa6c2..4e97e1ed26 100644 --- a/education/docfx.json +++ b/education/docfx.json @@ -29,7 +29,6 @@ "globalMetadata": { "recommendations": true, "adobe-target": true, - "ms.topic": "article", "ms.collection": [ "education", "tier2" diff --git a/windows/application-management/docfx.json b/windows/application-management/docfx.json index f9544bebe7..72c7168b1a 100644 --- a/windows/application-management/docfx.json +++ b/windows/application-management/docfx.json @@ -42,7 +42,6 @@ "uhfHeaderId": "MSDocsHeader-Windows", "ms.service": "windows-client", "ms.subservice": "itpro-apps", - "ms.topic": "article", "feedback_system": "Standard", "feedback_product_url": "https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332", "_op_documentIdPathDepotMapping": { @@ -53,10 +52,10 @@ }, "titleSuffix": "Windows Application Management", "contributors_to_exclude": [ - "rjagiewich", - "traya1", - "rmca14", - "claydetels19", + "rjagiewich", + "traya1", + "rmca14", + "claydetels19", "jborsecnik", "tiburd", "garycentric", diff --git a/windows/client-management/manage-windows-copilot.md b/windows/client-management/manage-windows-copilot.md index 4f5621f987..8608166976 100644 --- a/windows/client-management/manage-windows-copilot.md +++ b/windows/client-management/manage-windows-copilot.md @@ -3,7 +3,7 @@ title: Manage Copilot in Windows description: Learn how to manage Copilot in Windows for commercial environments using MDM and group policy. Learn about the chat providers available to Copilot in Windows. ms.topic: conceptual ms.subservice: windows-copilot -ms.date: 02/05/2024 +ms.date: 02/09/2024 ms.author: mstewart author: mestew appliesto: @@ -19,7 +19,7 @@ Copilot in Windows provides centralized generative AI assistance to your users r > [!Note] > - Copilot in Windows is currently available as a preview. We will continue to experiment with new ideas and methods using your feedback. -> - Copilot in Windows is being released in preview to select global markets as part of our latest update to Windows 11. The initial markets for the Copilot in Windows preview include North America and parts of Asia and South America. It is our intention to add additional markets over time. +> - Copilot in Windows (in preview) is available in select global markets and will be rolled out to additional markets over time. [Learn more](https://www.microsoft.com/windows/copilot-ai-features#faq). ## Configure Copilot in Windows for commercial environments diff --git a/windows/deployment/update/wufb-reports-do.md b/windows/deployment/update/wufb-reports-do.md index a02d0d0993..eca5fbdfa8 100644 --- a/windows/deployment/update/wufb-reports-do.md +++ b/windows/deployment/update/wufb-reports-do.md @@ -164,7 +164,7 @@ There are many Microsoft [content types](waas-delivery-optimization.md#types-of- ## Frequency Asked Questions - **What time period does the Delivery Optimization data include?** -Data is generated/aggregated for the last 28 days for active devices. +Data is generated/aggregated for the last 28 days for active devices. For Delivery Optimization data to register in the report, the device must have performed some Delivery Optimization action in the 28-day rolling window. This includes device configuration information. - **Data is showing as 'Unknown', what does that mean?** You may see data in the report listed as 'Unknown'. This status indicates that the Delivery Optimization DownloadMode setting is either invalid or empty. diff --git a/windows/hub/docfx.json b/windows/hub/docfx.json index 5f8b9dc5f7..d107b517cb 100644 --- a/windows/hub/docfx.json +++ b/windows/hub/docfx.json @@ -44,7 +44,6 @@ "uhfHeaderId": "MSDocsHeader-Windows", "ms.service": "windows-client", "ms.subservice": "itpro-fundamentals", - "ms.topic": "article", "feedback_system": "Standard", "feedback_product_url": "https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332", "_op_documentIdPathDepotMapping": { @@ -55,10 +54,10 @@ }, "titleSuffix": "Windows for IT Pros", "contributors_to_exclude": [ - "rjagiewich", - "traya1", - "rmca14", - "claydetels19", + "rjagiewich", + "traya1", + "rmca14", + "claydetels19", "jborsecnik", "tiburd", "garycentric", diff --git a/windows/privacy/docfx.json b/windows/privacy/docfx.json index 92b2620ad7..7f47903935 100644 --- a/windows/privacy/docfx.json +++ b/windows/privacy/docfx.json @@ -39,7 +39,6 @@ "uhfHeaderId": "MSDocsHeader-Windows", "ms.service": "windows-client", "ms.subservice": "itpro-privacy", - "ms.topic": "article", "feedback_system": "Standard", "feedback_product_url": "https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332", "_op_documentIdPathDepotMapping": { @@ -50,10 +49,10 @@ }, "titleSuffix": "Windows Privacy", "contributors_to_exclude": [ - "rjagiewich", - "traya1", - "rmca14", - "claydetels19", + "rjagiewich", + "traya1", + "rmca14", + "claydetels19", "jborsecnik", "tiburd", "garycentric", diff --git a/windows/security/identity-protection/hello-for-business/configure.md b/windows/security/identity-protection/hello-for-business/configure.md index 7c498d0bb4..6d581f8f55 100644 --- a/windows/security/identity-protection/hello-for-business/configure.md +++ b/windows/security/identity-protection/hello-for-business/configure.md @@ -13,23 +13,25 @@ This article describes the options to configure Windows Hello for Business in an You can configure Windows Hello for Business by using the following options: -- Configuration Service Provider (CSP): commonly used for devices managed by a Mobile Device Management (MDM) solution, like Microsoft Intune. CSPs can also be configured with [provisioning packages](/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers#csps-in-windows-configuration-designer), which are usually used at deployment time or for unamanged devices. To configure Windows Hello for Business, use the [PassportForWork CSP][CSP-2] +- Configuration Service Provider (CSP): commonly used for devices managed by a Mobile Device Management (MDM) solution, like Microsoft Intune. CSPs can also be configured with [provisioning packages](/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers#csps-in-windows-configuration-designer), which are usually used at deployment time or for unmanaged devices. To configure Windows Hello for Business, use the [PassportForWork CSP][CSP-2] - Group policy (GPO): used for devices that are Active Directory joined or Microsoft Entra hybrid joined, and aren't managed by a device management solution ## Policy precedence Some of the Windows Hello for Business policies are available for both computer and user configuration. The following list describes the policy precedence for Windows Hello for Business: -- *User policies* take precedence over *computer policies*. If a user policy is set, the corresponded computer policy is ignored. If a user policy is not set, the computer policy is used +- *User policies* take precedence over *computer policies*. If a user policy is set, the corresponded computer policy is ignored. If a user policy isn't set, the computer policy is used - Windows Hello for Business policy settings are enforced using the following hierarchy: - - User GPO - - Computer GPO - - User MDM - - Device MDM - - Device Lock policy + - User - GPO + - Computer - GPO + - User - PassportForWork CSP + - Device - PassportForWork CSP + - Exchange Active Sync - [DeviceLock CSP](/windows/client-management/mdm/policy-csp-devicelock) >[!IMPORTANT] ->All devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP. +>If you configure password length and complexity settings defined by the DeviceLock CSP, and PIN length and complexity settings defined by the PassportForWork CSP, Windows enforces the strictest policy out of the set of governing policies. +> +>The DeviceLock CSP utilizes the Exchange ActiveSync Policy (EAS) engine. For more information, see [Exchange ActiveSync Policy Engine Overview](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn282287(v=ws.11)). >[!NOTE] > If a policy isn't explicitly configured to require letters or special characters, users can optionally set an alphanumeric PIN. @@ -63,9 +65,9 @@ For Microsoft Entra joined devices and Microsoft Entra hybrid joined devices enr There are different ways to enable and configure Windows Hello for Business in Intune: - Using a policy applied at the tenant level. The tenant policy: - - Is only applied at enrollment time, and any changes to its configuration won't apply to devices already enrolled in Intune + - Is only applied at enrollment time, and any changes to its configuration doesn't apply to devices already enrolled in Intune - It applies to *all devices* getting enrolled in Intune. For this reason, the policy is usually disabled and Windows Hello for Business is enabled using a policy targeted to a security group -- A device configuration policy that is applied *after* device enrollment. Any changes to the policy will be applied to the devices during regular policy refresh intervals. There are different policy types to choose from: +- A device configuration policy that is applied *after* device enrollment. Any changes to the policy are applied to the devices during regular policy refresh intervals. There are different policy types to choose from: - [Settings catalog][MEM-1] - [Security baselines][MEM-2] - [Custom policy][MEM-3], via the [PassportForWork CSP][MEM-4] @@ -76,16 +78,16 @@ There are different ways to enable and configure Windows Hello for Business in I To check the Windows Hello for Business policy settings applied at enrollment time: -1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). +1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) 1. Select **Devices** > **Windows** > **Windows Enrollment** 1. Select **Windows Hello for Business** -1. Verify the status of **Configure Windows Hello for Business** and any settings that may be configured +1. Verify the status of **Configure Windows Hello for Business** and any settings that might be configured :::image type="content" source="deploy/images/whfb-intune-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="deploy/images/whfb-intune-disable.png"::: ## Policy conflicts from multiple policy sources -Windows Hello for Business is designed to be managed by group policy or MDM, but not a combination of both. Avoid mixing group policy and MDM policy settings for Windows Hello for Business. If you mix group policy and MDM policy settings, the MDM settings are ignored until all group policy settings are cleared. +Windows Hello for Business can be configured by GPO or CSP, but not a combination of both. Avoid mixing GPO and CSP policy settings for Windows Hello for Business. If you mix GPO and CSP policy settings, the CSP settings are ignored until all group policy settings are cleared. > [!IMPORTANT] > The [*MDMWinsOverGP*](/windows/client-management/mdm/policy-csp-controlpolicyconflict#mdmwinsovergp) policy setting doesn't apply to Windows Hello for Business. MDMWinsOverGP only applies to policies in the *Policy CSP*, while the Windows Hello for Business policies are in the *PassportForWork CSP*. diff --git a/windows/security/images/icons/activation.svg b/windows/security/images/icons/activation.svg new file mode 100644 index 0000000000..0060e89a0b --- /dev/null +++ b/windows/security/images/icons/activation.svg @@ -0,0 +1,3 @@ + + + diff --git a/windows/security/images/icons/certificate.svg b/windows/security/images/icons/certificate.svg index 3bd8b81da3..0060e89a0b 100644 --- a/windows/security/images/icons/certificate.svg +++ b/windows/security/images/icons/certificate.svg @@ -1,3 +1,3 @@ - - - \ No newline at end of file + + + diff --git a/windows/security/images/icons/gear.svg b/windows/security/images/icons/gear.svg new file mode 100644 index 0000000000..caca268bea --- /dev/null +++ b/windows/security/images/icons/gear.svg @@ -0,0 +1,10 @@ + + + + + + + + + + diff --git a/windows/security/images/icons/license.svg b/windows/security/images/icons/license.svg index 96ffa5b4eb..4be1c3b5f7 100644 --- a/windows/security/images/icons/license.svg +++ b/windows/security/images/icons/license.svg @@ -1,3 +1,3 @@ - - - \ No newline at end of file + + + diff --git a/windows/security/images/icons/subscription.svg b/windows/security/images/icons/subscription.svg new file mode 100644 index 0000000000..4be1c3b5f7 --- /dev/null +++ b/windows/security/images/icons/subscription.svg @@ -0,0 +1,3 @@ + + + diff --git a/windows/security/images/icons/windows-os.svg b/windows/security/images/icons/windows-os.svg deleted file mode 100644 index da64baf975..0000000000 --- a/windows/security/images/icons/windows-os.svg +++ /dev/null @@ -1,3 +0,0 @@ - - - \ No newline at end of file diff --git a/windows/security/licensing-and-edition-requirements.md b/windows/security/licensing-and-edition-requirements.md index ece47c14a8..e2ef744996 100644 --- a/windows/security/licensing-and-edition-requirements.md +++ b/windows/security/licensing-and-edition-requirements.md @@ -15,11 +15,11 @@ This article lists the security features that are available in Windows. Select one of the two tabs to learn about licensing requirements to use the security features, or to learn about the Windows edition requirements that support them: -#### [:::image type="icon" source="images/icons/certificate.svg" border="false"::: **Licensing requirements**](#tab/licensing) +#### [:::image type="icon" source="images/icons/subscription.svg" border="false"::: **Licensing requirements**](#tab/licensing) [!INCLUDE [licensing-requirements](../../includes/licensing/_licensing-requirements.md)] -#### [:::image type="icon" source="images/icons/windows-os.svg" border="false"::: **Edition requirements**](#tab/edition) +#### [:::image type="icon" source="images/icons/activation.svg" border="false"::: **Edition requirements**](#tab/edition) [!INCLUDE [_edition-requirements](../../includes/licensing/_edition-requirements.md)] diff --git a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/enhanced-phishing-protection.md b/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/enhanced-phishing-protection.md index ff13a406b5..29ae7131f5 100644 --- a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/enhanced-phishing-protection.md +++ b/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/enhanced-phishing-protection.md @@ -49,7 +49,7 @@ Enhanced Phishing Protection can be configured via Microsoft Intune, Group Polic Follow these instructions to configure your devices using either Microsoft Intune, GPO or CSP. -#### [:::image type="icon" source="images/icons/intune.svg"::: **Intune**](#tab/intune) +#### [:::image type="icon" source="../../../images/icons/intune.svg"::: **Intune**](#tab/intune) To configure devices using Microsoft Intune, create a [**Settings catalog** policy][MEM-2], and use the settings listed under the category **`SmartScreen > Enhanced Phishing Protection`**: @@ -61,7 +61,7 @@ To configure devices using Microsoft Intune, create a [**Settings catalog** poli Assign the policy to a security group that contains as members the devices or users that you want to configure. -#### [:::image type="icon" source="images/icons/group-policy.svg"::: **GPO**](#tab/gpo) +#### [:::image type="icon" source="../../../images/icons/group-policy.svg"::: **GPO**](#tab/gpo) Enhanced Phishing Protection can be configured using the following group policy settings found under **Administrative Templates > Windows Components > Windows Defender SmartScreen > Enhanced Phishing Protection**: @@ -71,7 +71,7 @@ Enhanced Phishing Protection can be configured using the following group policy - Notify Password Reuse - Notify Unsafe App -#### [:::image type="icon" source="images/icons/windows-os.svg"::: **CSP**](#tab/csp) +#### [:::image type="icon" source="../../../images/icons/gear.svg"::: **CSP**](#tab/csp) Enhanced Phishing Protection can be configured using the [WebThreatDefense CSP][WIN-1]. @@ -107,7 +107,7 @@ To better help you protect your organization, we recommend turning on and using | Notify Password Reuse | **Disabled** | **Enabled**: Turns on Enhanced Phishing Protection notifications when users reuse their work or school password and encourages them to change their password. | | Notify Unsafe App | **Disabled** | **Enabled**: Turns on Enhanced Phishing Protection notifications when users type their work or school passwords in Notepad and Microsoft 365 Office Apps. | -#### [:::image type="icon" source="images/icons/intune.svg"::: **Intune**](#tab/intune) +#### [:::image type="icon" source="../../../images/icons/intune.svg"::: **Intune**](#tab/intune) | Settings catalog element | Recommended value | |---------------------------|-------------------| @@ -117,7 +117,7 @@ To better help you protect your organization, we recommend turning on and using | Notify Password Reuse | **Enabled** | | Notify Unsafe App | **Enabled** | -#### [:::image type="icon" source="images/icons/group-policy.svg"::: **GPO**](#tab/gpo) +#### [:::image type="icon" source="../../../images/icons/group-policy.svg"::: **GPO**](#tab/gpo) | Group Policy setting | Recommended value | |---------------------------|-------------------| @@ -127,7 +127,7 @@ To better help you protect your organization, we recommend turning on and using | Notify Password Reuse | **Enabled** | | Notify Unsafe App | **Enabled** | -#### [:::image type="icon" source="images/icons/windows-os.svg"::: **CSP**](#tab/csp) +#### [:::image type="icon" source="../../../images/icons/gear.svg"::: **CSP**](#tab/csp) | MDM setting | Recommended value | |-------------------------|-------------------| diff --git a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/group-policy.svg b/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/group-policy.svg deleted file mode 100644 index 95957a5914..0000000000 --- a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/group-policy.svg +++ /dev/null @@ -1,9 +0,0 @@ - - - - - - - - - diff --git a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/intune.svg b/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/intune.svg deleted file mode 100644 index 6e0d938aed..0000000000 --- a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/intune.svg +++ /dev/null @@ -1,24 +0,0 @@ - - - - - - - - - - - - - - - - Icon-intune-329 - - - - - - - - \ No newline at end of file diff --git a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/windows-os.svg b/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/windows-os.svg deleted file mode 100644 index da64baf975..0000000000 --- a/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/images/icons/windows-os.svg +++ /dev/null @@ -1,3 +0,0 @@ - - - \ No newline at end of file diff --git a/windows/security/threat-protection/security-policy-settings/create-global-objects.md b/windows/security/threat-protection/security-policy-settings/create-global-objects.md index 9c2e0740b7..e20df384f0 100644 --- a/windows/security/threat-protection/security-policy-settings/create-global-objects.md +++ b/windows/security/threat-protection/security-policy-settings/create-global-objects.md @@ -82,7 +82,7 @@ This section describes how an attacker might exploit a feature or its configurat ### Vulnerability -The **Create global objects** user right is required for a user account to create global objects in Remote Desktop sessions. Users can still create session-specfic objects without being assigned this user right. Assigning this right can be a security risk. +The **Create global objects** user right is required for a user account to create global file mapping and symbolic link objects. Users can still create session-specfic objects without being assigned this user right. Assigning this right can be a security risk. By default, members of the **Administrators** group, the System account, and services that are started by the Service Control Manager are assigned the **Create global objects** user right. Users who are added to the **Remote Desktop Users** group also have this user right. diff --git a/windows/whats-new/deprecated-features.md b/windows/whats-new/deprecated-features.md index 6a3a4809db..be59977024 100644 --- a/windows/whats-new/deprecated-features.md +++ b/windows/whats-new/deprecated-features.md @@ -1,7 +1,7 @@ --- title: Deprecated features in the Windows client description: Review the list of features that Microsoft is no longer actively developing in Windows 10 and Windows 11. -ms.date: 01/26/2024 +ms.date: 02/09/2024 ms.service: windows-client ms.subservice: itpro-fundamentals ms.localizationpriority: medium @@ -47,7 +47,7 @@ The features in this article are no longer being actively developed, and might b | Feature | Details and mitigation | Deprecation announced | |---|---|---| -| Windows Mixed Reality | [Windows Mixed Reality](/windows/mixed-reality/enthusiast-guide/before-you-start) is deprecated and will be removed in a future release of Windows. This deprecation includes the [Mixed Reality Portal](/windows/mixed-reality/enthusiast-guide/install-windows-mixed-reality) app, and [Windows Mixed Reality for SteamVR](/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality) and Steam VR Beta.

As of November 1, 2026, for consumer editions of Windows and November 1, 2027 for commercial editions of Windows, Windows Mixed Reality will no longer be available for download via the Mixed Reality Portal app, Windows Mixed Reality for SteamVR, and Steam VR beta, and we'll discontinue support. At that time, Windows Mixed Reality will no longer receive security updates, nonsecurity updates, bug fixes, technical support, or online technical content updates. Existing Windows Mixed Reality devices will continue to work with Steam until users upgrade to a version of Windows that doesn't include Windows Mixed Reality.

This deprecation doesn't impact HoloLens. We remain committed to HoloLens and our enterprise customers. | December 2023 | +| Windows Mixed Reality | [Windows Mixed Reality](/windows/mixed-reality/enthusiast-guide/before-you-start) is deprecated and will be removed in Windows 11, version 24H2. This deprecation includes the [Mixed Reality Portal](/windows/mixed-reality/enthusiast-guide/install-windows-mixed-reality) app, [Windows Mixed Reality for SteamVR](/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality), and Steam VR Beta. Existing Windows Mixed Reality devices will continue to work with Steam through November 2026, if users remain on their current released version of Windows 11, version 23H2. After November 2026, Windows Mixed Reality will no longer receive security updates, nonsecurity updates, bug fixes, technical support, or online technical content updates.

This deprecation doesn't affect HoloLens. We remain committed to HoloLens and our enterprise customers. | December 2023 | | Microsoft Defender Application Guard for Edge | [Microsoft Defender Application Guard](/windows/security/application-security/application-isolation/microsoft-defender-application-guard/md-app-guard-overview), including the [Windows Isolated App Launcher APIs](/windows/win32/api/isolatedapplauncher/), is being deprecated for Microsoft Edge for Business and [will no longer be updated](feature-lifecycle.md). Please download the [Microsoft Edge For Business Security Whitepaper](https://edgestatic.azureedge.net/shared/cms/pdfs/Microsoft_Edge_Security_Whitepaper_v2.pdf) to learn more about Edge for Business security capabilities. | December 2023 | | Legacy console mode | The [legacy console mode](/windows/console/legacymode) is deprecated and no longer being updated. In future Windows releases, it will be available as an optional [Feature on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities). This feature won't be installed by default. | December 2023 | | Windows speech recognition | [Windows speech recognition](https://support.microsoft.com/windows/83ff75bd-63eb-0b6c-18d4-6fae94050571) is deprecated and is no longer being developed. This feature is being replaced with [voice access](https://support.microsoft.com/topic/4dcd23ee-f1b9-4fd1-bacc-862ab611f55d). Voice access is available for Windows 11, version 22H2, or later devices. Currently, voice access supports five English locales: English - US, English - UK, English - India, English - New Zealand, English - Canada, and English - Australia. For more information, see [Setup voice access](https://support.microsoft.com/topic/set-up-voice-access-9fc44e29-12bf-4d86-bc4e-e9bb69df9a0e). | December 2023 | diff --git a/windows/whats-new/docfx.json b/windows/whats-new/docfx.json index 21719523a0..e54d096bf9 100644 --- a/windows/whats-new/docfx.json +++ b/windows/whats-new/docfx.json @@ -41,7 +41,6 @@ "zone_pivot_group_filename": "resources/zone-pivot-groups.json", "breadcrumb_path": "/windows/resources/breadcrumb/toc.json", "uhfHeaderId": "MSDocsHeader-Windows", - "ms.topic": "article", "feedback_system": "Standard", "feedback_product_url": "https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332", "_op_documentIdPathDepotMapping": { @@ -52,10 +51,10 @@ }, "titleSuffix": "What's new in Windows", "contributors_to_exclude": [ - "rjagiewich", - "traya1", - "rmca14", - "claydetels19", + "rjagiewich", + "traya1", + "rmca14", + "claydetels19", "jborsecnik", "tiburd", "garycentric",