Merge pull request #7874 from MicrosoftDocs/main

Publish main to live on 2/13 @ 10:30 am

windows/deployment/TOC.yml

@@ -65,6 +65,8 @@
               href: /windows/whats-new/feature-lifecycle?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
             - name: Deprecated features
               href: /windows/whats-new/deprecated-features?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
+            - name: Resources for deprecated features
+              href: /windows/whats-new/deprecated-features-resources?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json              
             - name: Removed features
               href: /windows/whats-new/removed-features?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json   
     - name: Prepare

windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md

@@ -91,7 +91,7 @@ When the assignment is complete, the **Ring assigned by** column changes to **Ad
 Windows Autopatch monitors device membership in its deployment rings, except for the **Modern Workplace Devices-Windows Autopatch-Test** ring, to provide automated deployment ring remediation functions to mitigate the risk of not having its managed devices being part of one of its deployment rings. These automated functions help mitigate risk of potentially having devices in a vulnerable state, and exposed to security threats in case they're not receiving update deployments due to either:
 
 - Changes performed by the IT admin on objects created by the Windows Autopatch tenant enrollment process, or
-- An issue occurred which prevented devices from getting a deployment rings assigned during the [device registration process](../deploy/windows-autopatch-device-registration-overview.md).
+- An issue occurred which prevented devices from getting a deployment ring assigned during the [device registration process](../deploy/windows-autopatch-device-registration-overview.md).
 
 There are two automated deployment ring remediation functions:
 

windows/whats-new/TOC.yml

@@ -31,5 +31,7 @@
       href: feature-lifecycle.md
     - name: Deprecated Windows features
       href: deprecated-features.md
+    - name: Resources for deprecated features
+      href: deprecated-features-resources.md       
     - name: Removed Windows features
       href: removed-features.md

windows/whats-new/deprecated-features-resources.md

@@ -0,0 +1,72 @@
+---
+title: Resources for deprecated features in the Windows client
+description: Resources and details for deprecated features in the Windows Client.
+ms.date: 12/10/2022
+ms.prod: windows-client
+ms.technology: itpro-fundamentals
+ms.localizationpriority: medium
+author: mestew
+ms.author: mstewart
+manager: aaroncz
+ms.reviewer: 
+ms.topic: reference
+---
+
+# Resources for deprecated features
+
+**Applies to**
+
+- Windows 10
+- Windows 11
+
+This article provides additional resources about [deprecated features for Windows client](deprecated-features.md) that may be needed by IT professionals. The following information is provided to help IT professionals plan for the removal of deprecated features:
+
+## Microsoft Support Diagnostic Tool resources
+
+The [Microsoft Support Diagnostic Tool (MSDT)](/windows-server/administration/windows-commands/msdt) gathers diagnostic data for analysis by support professionals. MSDT is the engine used to run legacy Windows built-in troubleshooters. There are currently 28 built-in troubleshooters for MSDT. Half of the built-in troubleshooters have already been [redirected](#redirected-msdt-troubleshooters) to the Get Help platform, while the other half will be [retired](#retired-msdt-troubleshooters).  
+
+If you're using MSDT to run [custom troubleshooting packages](/previous-versions/windows/desktop/wintt/package-schema), it will be available as a [Feature on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) before the tool is fully retired in 2025. This change will allow you to continue to use MSDT to run custom troubleshooting packages while transitioning to a new platform. [Contact Microsoft support](https://support.microsoft.com/contactus) for Windows if you require additional assistance.
+
+### Redirected MSDT troubleshooters
+
+The following troubleshooters will automatically be redirected when you access them from **Start** > **Settings** > **System** > **Troubleshoot**:
+
+- Background Intelligent Transfer Service (BITS)
+- Bluetooth
+- Internet Connections
+- Network Adapter
+- Playing Audio
+- Printer
+- Program Compatibility Troubleshooter
+- Recording Audio
+- Video Playback
+- Windows Network Diagnostics
+- Windows Media Player DVD
+- Windows Media Player Library
+- Windows Media Player Settings
+- Windows Update
+
+### Retired MSDT troubleshooters
+
+The following troubleshooters will be removed in a future release of Windows:
+
+- Connection to a Workplace using DirectAccess
+- Devices and Printers
+- Hardware and Devices
+- HomeGroup
+- Incoming Connections
+- Internet Explorer Performance
+- Internet Explorer Safety
+- Keyboard
+- Power
+- Search and Indexing
+- Speech
+- System Maintenance
+- Shared Folders
+- Windows Store Apps
+
+## Next steps
+
+- [Windows feature lifecycle](feature-lifecycle.md)
+- [Deprecated Windows features](deprecated-features.md)
+- [Removed Windows features](removed-features.md)

windows/whats-new/deprecated-features.md

@@ -36,6 +36,7 @@ The features in this article are no longer being actively developed, and might b
 
 |Feature    |  Details and mitigation  | Deprecation announced |
 | ----------- | --------------------- | ---- |
+| Microsoft Support Diagnostic Tool (MSDT) <!--6968128--> | [MSDT](/windows-server/administration/windows-commands/msdt) is deprecated and will be removed in a future release of Windows. MSDT is used to gather diagnostic data for analysis by support professionals. For more information, see [***Blog post placeholder***](https://learn.microsoft.com) and [Resources for deprecated features](deprecated-features-resources.md) | January 2023 |
 | Universal Windows Platform (UWP) Applications for 32-bit Arm <!--7116112-->| This change is applicable only to devices with an Arm processor, for example Snapdragon processors from Qualcomm. If you have a PC built with a processor from Intel or AMD, this content is not applicable. If you are not sure which type of processor you have, check **Settings** > **System** > **About**.</br> </br> Support for 32-bit Arm versions of applications will be removed in a future release of Windows 11. After this change, for the small number of applications affected, app features might be different and you might notice a difference in performance. For more technical details about this change, see [Update app architecture from Arm32 to Arm64](/windows/arm/arm32-to-arm64). | January 2023 |
 | Update Compliance <!--7260188-->| [Update Compliance](/windows/deployment/update/update-compliance-monitor), a cloud-based service for the Windows client, is no longer being developed. This service has been replaced with [Windows Update for Business reports](/windows/deployment/update/wufb-reports-overview), which provides reporting on client compliance with Microsoft updates from the Azure portal. | November 2022|
 | Windows Information Protection <!-- 6010051 --> | [Windows Information Protection](/windows/security/information-protection/windows-information-protection/protect-enterprise-data-using-wip) will no longer be developed in future versions of Windows. For more information, see [Announcing sunset of Windows Information Protection (WIP)](https://go.microsoft.com/fwlink/?linkid=2202124).<br> <br>For your data protection needs, Microsoft recommends that you use [Microsoft Purview Information Protection](/microsoft-365/compliance/information-protection) and [Microsoft Purview Data Loss Prevention](/microsoft-365/compliance/dlp-learn-about-dlp). | July 2022 |