Merge pull request #10355 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-11 22:00 UTC

Author: learn-build-service-prod[bot]

support/azure/information-protection/troubleshoot-aip-issues.md

@@ -2,7 +2,7 @@
 title: How to troubleshoot Azure Information Protection policy issues
 description: Discusses how to troubleshoot Azure Information Protection policy issues.
 ms.date: 04/07/2022
-ms.service: information-protection
+ms.service: azure-information-protection
 ms.author: jarrettr
 author: JarrettRenshaw
 ms.reviewer: 

support/azure/information-protection/welcome-information-protection.yml

@@ -7,7 +7,7 @@ metadata:
   title: Troubleshoot common issues with Azure Information Protection
   description: Documentation for troubleshooting common issues with Azure Information Protection. # Required; article description that is displayed in search results. < 160 chars.
   services: azure
-  ms.service: information-protection #Required; service per approved list. service slug assigned to your service by ACOM.
+  ms.service: azure-information-protection
   ms.topic: landing-page # Required
   author: JarrettRenshaw  #Required; your GitHub user alias, with correct capitalization.
   ms.author: jarrettr #Required; microsoft alias of author; optional team alias.

support/azure/virtual-machines/linux/linux-azure-guest-agent-tools-vmassist.md

@@ -4,10 +4,10 @@ description: Provides script-based tool to help diagnose and resolve Azure Guest
 author: JarrettRenshaw
 ms.author: jarrettr
 manager: dcscontentpm
-ms.date: 10/24/2025
+ms.date: 12/04/2025
 ms.reviewer: v-jsitser, scotro, v-ryanberg
 ms.service: azure-virtual-machines
-ms.custom: sap:zzzz
+ms.custom: sap:VM Extensions not operating correctly
 ---
 #  Troubleshooting Tool for Linux Guest Agent - VM assist
 
@@ -59,7 +59,7 @@ If no issues are discovered during the base checks by using bash, the Python scr
 
 ## How to run the tool
 
-The VM assist scripting is run initially from the documentation. Subsequently, you can run the bash script directly: `vmassist.sh` as root or by using `sudo`.
+Go to the following GitHub location and follow the instructions there to [download, install, and run the tool](https://github.com/Azure/azure-support-scripts/blob/master/vmassist/linux/README.md). Subsequently, you can run the bash script directly: `vmassist.sh` as root or by using `sudo`.
 
 If you open a support request, please include both of these files to aid the support agent who assists you.
 

support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md

@@ -24,9 +24,10 @@ Before you install updates by using the Configuration Manager console, review th
 
 Review the following update checklists for actions to take before you start the update:
 
+- [Checklist for installing update 2509](/intune/configmgr/core/servers/manage/checklist-for-installing-update-2509)
 - [Checklist for installing update 2503](/intune/configmgr/core/servers/manage/checklist-for-installing-update-2503)
 - [Checklist for installing update 2409](/intune/configmgr/core/servers/manage/checklist-for-installing-update-2409)
-- [Checklist for installing update 2403](/intune/configmgr/core/servers/manage/checklist-for-installing-update-2403)
+
 
 ### Step 2: Run the prerequisite checker before you install an update
 
@@ -88,6 +89,7 @@ For reference, the following table lists well-known update package GUIDs. The li
 | Configuration Manager 2409 HFRU | 345A6BE1-3D07-43ED-B6E5-FAC0889DA04C |
 | Configuration Manager 2503 | AA928926-5C76-4DE0-B51F-0FE4D365DFE2 |
 | Configuration Manager 2503 HFRU | 6B0783D9-B8A2-4848-82F6-8EFE956F4988|
+| Configuration Manager 2509 | 420E3E18-73C5-4BE9-88B0-6F1E30A012CA |
 
 ### Identify the installation stage of the update
 
@@ -331,7 +333,7 @@ Correlate the returned version information to other sources such as the version
 | SQL DB | fnCurrentSiteVersion | 5.00.*nnnn*.1000 |
 | SQL DB | fnSetupFullVersion | 5.00.*nnnn*.10*mm* |
 | SQL DB | fnCurrentSiteVersion_INT/fnCurrentSiteVersion_INT_TABLE | 500*nnnn* |
-| Registry | `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\Full Version` | 5.00.*nnnn*.1000 |
+| Registry | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\Full Version | 5.00.*nnnn*.1000 |
 | SQL DB | Sites.Version | 5.00.*nnnn*.1000 |
 | SMSExec.exe | Product Version | 5.00.*nnnn*.10*mm* |
 
@@ -1390,7 +1392,7 @@ In the console, go to **Monitoring** > **Overview** > **Database Replication**.
 
 The CMUpdate process is the main driver of update package installation. It hosts the CONFIGURATION_MANAGER_UPDATE service. If CMUpdate fails, the installation stops responding at a specific stage, and CMUpdate.log might repeatedly record the same activity. To investigate this issue, open Event Viewer, and review the Windows Application log for Event ID 1000 (Process crash).
 
-Security software can also cause this behavior by preventing the updated CMUpdate binary from running, or by stopping the process. To investigate this issue, turn off the security software, and then try again to update. If the issue persists, use the [ProcDump](/sysinternals/downloads/procdump) tool to collect a process memory dump file. Download and install the tool, and then run the following command at a command prompt:
+Security software can also cause this behavior by preventing the updated CMUpdate binary from running, or by stopping the process. To investigate this issue, turn off the security software, and then try again to update. If the issue persists, use the [ProcDump](/sysinternals/downloads/procdump) tool to collect a process memory dump file. Download and unpack the tool, and then run the following command at a command prompt:
 
 ```console
 procdump -ma -e cmupdate.exe