Merge remote-tracking branch 'upstream/main' into AB#9354-Top-articles--Add-Summary-section

Author: v-tappelgate

Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md

@@ -22,7 +22,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 12/13/2025
+ms.date: 01/26/2026
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -42,6 +42,8 @@ ms.date: 12/13/2025
 |Video participants missing from Front row.|The Front row view doesn't show all the video participants, and they're missing from the overflow area as well.<br/><br/>The Front row view displays a maximum of five attendees on a single screen, and up to nine attendees on a dual screen. When the maximum number of attendees are already shown on the screen, the extra attendees are represented in the overflow view area. However, when two or more participants turn on their cameras, the remaining video streams might not fit in the Front-of-Room display, and they are not accounted for in the overflow area as well. This issue causes those video participants to appear as "missing" from the meeting.|Use a different meeting view than the Front row view.|
 |All video streams turn off on Front row during a meeting.|When you use the Front row view on a Teams Rooms on Windows device, all video streams including the meeting room's video and incoming content turn off in the Front-of-Room display. This issue occurs intermittently when a remote participant turns off their video while content is being shared.|Leave and rejoin the Teams meeting from the Teams Rooms device.|
 |USB devices fail intermittently on Teams Rooms devices.|On Teams Rooms on Windows devices that use Intel PCH 500, 600, or 700 systems, you hear occasional glitches or unexpected clicking or popping noises in an audio stream. You might also see glitches in a video stream momentarily, and occasionally a USB audio or video device might stop working.<br/><br/>These issues occur if your device experiences USB split transaction issues.|Switch to Admin mode on your Teams Rooms on Windows device and perform step 3 listed in the Resolution section of [USB-connected audio or video devices malfunction when connected to specific Intel-based devices](/troubleshoot/windows-client/setup-upgrade-and-drivers/usb-audio-video-devices-malfunction?source=docs#resolution). If the script that you run determines that your device is impacted, perform step 4 to add the registry entry as described.|
+|Multiple issues when identical USB cameras are connected to Teams Rooms.|When you use multiple connected USB cameras of the same make and model with Teams Rooms on Windows, you might experience the following issues:<br/><ul><li>Inability to reliably select or control a specific physical camera.</li><li>Unexpected changes in camera selection, framing behavior, and source switching. </li><li>Change to the active camera setting after it is disconnected and reconnected, or after the Teams Rooms app or the meeting restart.</li><li>Intelligent or enhanced framing experiences target the wrong camera.</li></ul>|No workaround is available at this time.|
+|Teams Rooms device loses internet connectivity after installing a feature update for Windows| A Teams Rooms device that is connected to a network, which requires a proxy can't connect to the internet after installing a feature update for Windows, including an upgrade to Windows 11.<br/><br/>This issue occurs if the proxy setting for internet access on the affected device is configured for the LocalSystem instead of a system-wide proxy. The Windows feature update deletes the LocalSystem settings. This behavior is by design.|If your device has proxy settings set for the LocalSystem user, transfer those settings to the [system-wide proxy settings](/windows/client-management/mdm/networkproxy-csp) that are set and maintained through Mobile Device Management (MDM). Alternatively, you can use the [Set-WinInetProxy](https://www.powershellgallery.com/packages/WinInetProxy/0.1.0) PowerShell cmdlet to configure the system-wide proxy settings.</br></br>When you use system-wide proxy settings, they won't be affected when you install Windows feature updates on the device in future.|
 
 ## Hardware issues
 

support/azure/azure-kubernetes/connectivity/troubleshoot-cluster-connection-issues-api-server.md

@@ -62,6 +62,9 @@ You can take these common troubleshooting steps to check the connectivity to the
     timeout 5 telnet $CLUSTER_FQDN 443 || echo "Connection test completed"
     ```
 
+    > [!NOTE]
+    > When you stop and start an AKS cluster, the API server's IP address can change. If you experience connection issues after a stop/start operation, flush your DNS cache, and verify that the IP address resolves correctly. For more information, see [Stop and start an Azure Kubernetes Service (AKS) cluster](/azure/aks/start-stop-cluster#about-the-cluster-stopstart-feature).
+
 3. If the AKS cluster is private, make sure you run the command from a virtual machine (VM) that can access the AKS cluster's Azure Virtual Network. See [Options for connecting to the private cluster](/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster).
 
 4. If necessary, follow the steps in the troubleshooting article [Client IP address can't access the API server](client-ip-address-cannot-access-api-server.md), so the API server adds your client IP address to the IP ranges it authorizes.

support/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity.md

@@ -4,7 +4,7 @@ description: Troubleshoot problems connecting to and accessing SMB Azure file sh
 services: storage
 ms.service: azure-file-storage
 ms.custom: sap:Connectivity, devx-track-azurepowershell, linux-related-content
-ms.date: 01/07/2026
+ms.date: 01/26/2026
 ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal, justingross
 ---
 # Troubleshoot Azure Files connectivity and access issues (SMB)
@@ -135,6 +135,14 @@ Revert the `LmCompatibilityLevel` value to the default value of 3 in the followi
 
 `HKLM\SYSTEM\CurrentControlSet\Control\Lsa`  
 
+#### Cause 3: The file share name doesn't exist or there is a typo in the share name
+
+Error 67 can occur when the storage account exists and the SMB endpoint is reachable, but the SMB namespace or share path can't be resolved. This isn't a DNS issue, an authentication issue, or a permissions issue.
+
+##### Solution for cause 3
+
+Double check the file share name. Azure file share names must be exact. Check for an extra character, missing characters, or an incorrect share name copied from the Azure portal. Retry mounting the share.
+
 ### <a id="error-64"></a> Error 64 when you mount an Azure file share
 
 When mounting a file share from on-premises or another datacenter, you might see the following error:

support/entra/entra-id/app-integration/401-unauthorized-aspnet-core-web-api.md

@@ -9,7 +9,9 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 
 # 401 Unauthorized errors in ASP.NET Core Web API with Microsoft Entra ID 
 
-When you call an ASP.NET Core Web API that's secured by using Microsoft Entra ID authentication, you might encounter a "401 Unauthorized" error. This article provides guidance for using `JwtBearerEvents` to capture detailed logs to troubleshoot these errors.
+## Summary
+
+This article provides guidance for using JwtBearerEvents to capture detailed logs to troubleshoot a "401 Unauthorized" error when you call an ASP.NET Core Web API that's secured by using Microsoft Entra ID authentication.
 
 ## Symptoms
 

support/mem/configmgr/app-management/deployment-type-changes-deployed-unexpectedly.md

@@ -14,7 +14,7 @@ _Original KB number:_   2683900
 
 ## Symptoms
 
-Consider the following scenario in System Center 2012 Configuration Manager:
+Consider the following scenario in Configuration Manager:
 
 - User A is an administrator who is granted the Application Editor role.
 - User B is an administrator who is granted the Application Deployment role.

support/mem/configmgr/client-management/invalid-data-error-import-mof-file.md

@@ -5,16 +5,16 @@ ms.date: 02/11/2025
 ms.reviewer: kaushika, erinwi, prakask, keiththo, brshaw
 ms.custom: sap:Client Operations\Client Settings
 ---
-# Configuration Manager Sms_def.mof file gives an invalid data error message when you import the file
+# Configuration Manager gives an invalid data error message when you import the MOF file to customize hardware inventory
 
-This article helps you fix a problem in which the Sms_def.mof file doesn't open when you try to import the file to customize your hardware inventory in Microsoft System Center 2012 Configuration Manager.
+This article helps you fix a problem in which the Managed Object Format (MOF) fil doesn't open when you try to import the file to customize your hardware inventory in Configuration Manager.
 
 _Original product version:_   Microsoft System Center 2012 Configuration Manager  
 _Original KB number:_   2690570
 
 ## Symptoms
 
-When you try to import the Sms_def.mof file to customize your hardware inventory in System Center 2012 Configuration Manager, the file does not open. Additionally, you receive an error message that states that the file contains invalid data.
+When you try to import the Managed Object Format (MOF) file to customize your hardware inventory in Configuration Manager, the file does not open. Additionally, you receive an error message that states that the file contains invalid data.
 
 ## Resolution
 

support/mem/configmgr/client-management/remote-control-fails-error-c000012.md

@@ -1,20 +1,20 @@
 ---
 title: Remote control fails with error C000012
-description: Fixes an issue in which remote control fails with error C0000120 in System Center 2012 Configuration Manager.
+description: Fixes an issue in which remote control fails with error C0000120 in Configuration Manager.
 ms.date: 02/11/2025
 ms.reviewer: kaushika, erinwi
 ms.custom: sap:Client Operations\Remote Control
 ---
-# Remote control fails with error C000012 in System Center 2012 Configuration Manager
+# Remote control fails with error C000012 in Configuration Manager
 
-This article helps you resolve an issue in which remote control fails with error C0000120 in System Center 2012 Configuration Manager.
+This article helps you resolve an issue in which remote control fails with error C0000120 in Configuration Manager.
 
 _Original product version:_   System Center 2012 Configuration Manager  
 _Original KB number:_   2716965
 
 ## Symptoms
 
-When attempting to use System Center 2012 Configuration Manager to remote control a system, the connection fails. The remote control log and CmRcService.log indicate the following failure:  
+When attempting to use Configuration Manager to remote control a system, the connection fails. The remote control log and CmRcService.log indicate the following failure:  
 
 > WT_CompleteIO failed. Network shutdown : Unknown error (Error: C0000120; Source: Unknown)
 

support/sql/releases/sqlserver-2025/build-versions.md

@@ -12,7 +12,7 @@ ms.reviewer: v-six
 
 This article lists the Microsoft SQL Server 2025 builds that were released after the release of SQL Server 2025.
 
-## SQL Server 2022 Cumulative Update (CU) builds
+## SQL Server 2025 Cumulative Update (CU) builds
 
 | Cumulative update name | SQL Server build version | SQL Server (sqlservr.exe) file version | Analysis Services build version | Analysis Services (msmdsrv.exe) file version | Knowledge Base number | Release date |
 |---------------|-------------|-----------------|-------------|-----------------|------------------------------------|--------------------|