Merge remote-tracking branch 'upstream/main' into AB#8339-Troubleshooting-Windows-Multipath-IO-MPIO-and-Disk-Storage-Issues

Author: v-tappelgate

Microsoft365/purview/purview/sensitivity-labels/known-issues-ip-client.md

@@ -8,7 +8,7 @@ ms.author: meerak
 manager: dcscontentpm
 ms.date: 09/04/2025
 ms.topic: troubleshooting
-ms.service: information-protection
+ms.service: purview
 ---
 # Known issues for the information protection client
 

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

@@ -23,7 +23,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 12/01/2025
+ms.date: 12/13/2025
 ---
 # Known issues with Teams on Android devices
 
@@ -35,8 +35,8 @@ ms.date: 12/01/2025
 | --- | --- | --- |
 |Touch console not able to pair with Teams Rooms device.|The touch console that is paired with a Teams Rooms for Android device is unable to stay paired with the Front of Room device, and keeps retrying the pairing process in a loop. Occasionally, you might see the following error message:<br/><br/>**Can't connect to device**|To fix the issue, make sure that the Teams Room for Android device has the latest updates installed, and both the device and the touch console are running the same version of the Teams Rooms for Android app.|
 |Unable to join E2EE meeting using Teams Rooms on Android device.|You're not able use a Teams Rooms on Android device that is paired with a console to join a Teams meeting that is set up with end-to-end encryption (E2EE).|No workaround is available at this time.|
-|Custom background is removed after updating to new version of Teams Rooms app.|After you update to the 1449/1.0.96.2025208203 version of the Teams Rooms on Android app, the custom background is replaced by a purple gradient.|No workaround is available at this time.|
 |Mute/unmute controls don't work.|On Cisco's Teams Rooms on Android devices, the Mute and Unmute functionality doesn't work reliably during a Teams meeting. This issue occurs after you install the 1449/1.0.96.2025328903 version of the Teams Rooms on Android app.|Leave the meeting and rejoin to restore the Mute and Unmute functionality.|
+|Unable to download software updates on Teams Rooms on Android devices.| Your device is running one of the following versions of the Teams Rooms on Android app and you're unable to install software updates on the device:<br/><ul><li>1449/1.0.96.2025328903</li><li>1449/1.0.96.2025325609</li></ul><br/>This issue occurs because the available space on the device is not enough to download software updates to install.|Use the Microsoft Teams admin center to sign out of the device and then sign in again. This action will clear enough space on the device to download software updates.|
 
 ## Issues affecting multiple devices
 

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

@@ -22,7 +22,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 12/03/2025
+ms.date: 12/13/2025
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -41,6 +41,7 @@ ms.date: 12/03/2025
 |Lenovo Teams Rooms devices display BitLocker recovery screen.|When you try to update Windows from 23H2 to 24H2 on a Lenovo Teams Rooms for Windows device that has BitLocker enabled, the update might fail and you see a BitLocker recovery screen instead.|The Windows update to 24H2 on Lenovo devices is [blocked](https://support.microsoft.com/topic/kb5070632-some-devices-are-temporarily-unable-to-upgrade-to-windows-11-version-24h2-or-25h2-c3dd7515-21e6-46ce-9a9d-64a8882ef5ca) due to this issue. <br/><br/>You can safely upgrade the versions of the Teams Rooms app to 5.3.205.0 and 5.4.210.0 on the affected devices that will remain on Windows version 23H2. <br/><br/>If one of these versions of the Teams Rooms app is already installed and the device displays the BitLocker recovery screen, enter the BitLocker recovery key to restore functionality.|
 |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.|
 
 ## Hardware issues
 

support/azure/app-service/web-apps-performance-faqs.md

@@ -1,5 +1,5 @@
 ---
-title: Application performance FAQs
+title: Azure App Service FAQ: Availability, Performance, and Application Issues
 description: Get answers to frequently asked questions about availability, performance, and application issues in Azure App Service.
 author: JarrettRenshaw
 ms.author: jarrettr
@@ -13,31 +13,33 @@ ms.custom: sap:Availability, Performance, and Application Issues
 > [!NOTE]
 > Some of the following guidelines might only work on Windows or Linux App Services. For example, Linux App Services run in 64-bit mode by default.
 
-This article has answers to frequently asked questions (FAQs) about application performance issues for the [Web Apps feature of Azure App Service](https://azure.microsoft.com/services/app-service/web/).
+This article answers common questions about availability, performance, and troubleshooting application issues in the [Web Apps feature of Azure App Service](https://azure.microsoft.com/services/app-service/web/). Use this guide to quickly resolve problems and optimize your app’s reliability.
 
-[!INCLUDE [support-disclaimer](../../includes/support-disclaimer.md)]
+## Where can I learn more about quotas and limits for various App Service plans?
+
+For information about quotas and limits, see [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits).
 
-## Why is my App Service Plan displaying CPU/Memory usage even when all Web Apps are stopped?
+## My App Service Plan displaying CPU/Memory usage even when all Web Apps are stopped
 
 Azure App Service requires continuous system processes that handle several platform operations and features, such as security updates, availability of the SCM console, application monitoring, authentication, and many other vital features of your Web App.
 
 System processes will run on App Service Plans even if there are no Web Apps running or if the App Service Plan contains no Web Apps.
 
 The platform processes will consume a minimum amount of resources (such as CPU, Memory and Disk space), and the same should be accounted during the capacity planning, monitoring, and auto-scaling trigger configuration of an App Service Plan.
 
-## Why is my app slow?
+## My app perfromance is slow
 
 Multiple factors might contribute to slow app performance. For detailed troubleshooting steps, see [Troubleshoot slow web app performance](/azure/app-service/troubleshoot-performance-degradation).
 
 > [!TIP]
 > - Enable the **Always On** setting under **Configuration** > **General settings** to keep your app warm and avoid cold starts. This helps reduce delay after idle time, especially in Basic and higher plans.
 > - Configure a Health check path to monitor app health and automatically replace unresponsive instances. This helps maintain availability and performance. For more information, see [Monitor App Service instances by using Health check](/azure/app-service/monitor-instances-health-check).
 
-## How do I troubleshoot a high CPU-consumption scenario?
+## How do I troubleshoot high CPU consumption?
 
 In some high CPU-consumption scenarios, your app might truly require more computing resources. In that case, consider scaling to a higher service tier so the application gets all the resources it needs. Other times, high CPU consumption might be caused by a bad loop or by a coding practice. Getting insight into what's triggering increased CPU consumption is a two-part process. First, create a process dump, and then analyze the process dump. For more information, see [Capture and analyze a dump file for high CPU consumption for Web Apps](/archive/blogs/asiatech/how-to-capture-dump-when-intermittent-high-cpu-happens-on-azure-web-app).
 
-## How do I troubleshoot a high memory-consumption scenario?
+## How do I troubleshoot high memory consumption?
 
 In some high memory-consumption scenarios, your app might truly require more computing resources. In that case, consider scaling to a higher service tier so the application gets all the resources it needs. Other times, a bug in the code might cause a memory leak. A coding practice might also increase memory consumption. Getting insight into what's triggering high memory consumption is a two-part process. First, create a process dump, and then analyze the process dump. Crash Diagnoser from the Azure Site Extension Gallery can efficiently perform both these steps. For more information, see [Capture and analyze a dump file for intermittent high memory for Web Apps](/archive/blogs/asiatech/how-to-capture-and-analyze-dump-for-intermittent-high-memory-on-azure-web-app).
 
@@ -48,26 +50,22 @@ You can use PowerShell cmdlets to manage and maintain App Service web apps. In o
 > [!NOTE]
 > For current automation scripts, use the latest [Az.Websites](/powershell/module/az.websites) module. The older `AzureRM` module is deprecated.
 
-## How do I view my web app's event logs?
-
-To view your web app's event logs:
+## I need to gather information to troubleshoot my web app
 
+### To view a web app's event logs
 1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. In the menu, select **Debug Console** > **CMD**.
 3. Select the **LogFiles** folder.
 4. To view event logs, select the pencil icon next to **eventlog.xml**.
 5. To download the logs, run the PowerShell cmdlet `Save-AzureWebSiteLog -Name webappname`.
 
-## How do I capture a user-mode memory dump of my web app?
-
-To capture a user-mode memory dump of your web app:
-
+### To capture a user-mode memory dump of a web app
 1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. Select the **Process Explorer** menu.
 3. Right-click the **w3wp.exe** process or your WebJob process.
 4. Select **Download Memory Dump** > **Full Dump**.
 
-## How do I view process-level info for my web app?
+### How to view process-level info for a web app
 
 You have two options for viewing process-level information for your web app:
 
@@ -79,21 +77,12 @@ You have two options for viewing process-level information for your web app:
     2. Select the **Process Explorer** menu.
     3. For the **w3wp.exe** process, select **Properties**.
 
-## When I browse to my app, I see "Error 403 - This web app is stopped." How do I resolve this?
-
-Three conditions can cause this error:
-
-- The web app has reached a billing limit and your site has been disabled.
-- The web app has been stopped in the portal.
-- The web app has reached a resource quota limit that might apply to a Free or Shared scale service plan.
-
-To see what is causing the error and to resolve the issue, follow the steps in [Web Apps: "Error 403 – This web app is stopped"](/archive/blogs/waws/azure-web-apps-error-403-this-web-app-is-stopped).
-
-## Where can I learn more about quotas and limits for various App Service plans?
+### I can't find my log files in the folder structure of my web app when using the Local Cache feature of App Service
+If you use the Local Cache feature of App Service, the folder structure of the LogFiles and Data folders for your App Service instance are affected. When Local Cache is used, subfolders are created in the storage LogFiles and Data folders. The subfolders use the naming pattern "unique identifier" + time stamp. Each subfolder corresponds to a VM instance in which the web app is running or has run.
 
-For information about quotas and limits, see [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits).
+To determine whether you're using Local Cache, check your App Service **Application settings** tab. If Local Cache is being used, the app setting `WEBSITE_LOCAL_CACHE_OPTION` is set to `Always`.
 
-## How do I turn on failed request tracing?
+### To turn on failed request tracing
 
 To turn on failed request tracing, follow these steps:
 
@@ -147,54 +136,10 @@ To turn on failed request tracing, follow these steps:
 15. Select the **LogFiles** folder, and then select the folder with a name that starts with **W3SVC**.
 16. To see the XML file, select the pencil icon.
 
-## I see the message "Worker Process requested recycle due to 'Percent Memory' limit." How do I address this issue?
-
-The maximum available amount of memory for a 32-bit process (even on a 64-bit operating system) is 2 GB. By default, the worker process is set to 32-bit in App Service (for compatibility with legacy web applications).
-
-Consider switching to 64-bit processes so you can take advantage of the additional memory available in your Web Worker role. This action triggers a web app restart, so schedule accordingly.
-
-Also note that a 64-bit environment requires a Basic or Standard service plan. Free and Shared plans always run in a 32-bit environment.
-
-For more information, see [Configure web apps in App Service](/azure/app-service/configure-common).
-
-## Why does my request time out after 230 seconds?
-
-Azure Load Balancer has a default idle timeout setting of four minutes. This setting is generally a reasonable response time limit for a web request. Therefore, App Service returns a timeout to the client if your application does not return a response within approximately 240 seconds (230 seconds on Windows app, 240 seconds on Linux app).　If your web app requires background processing, we recommend using Azure WebJobs. The Azure web app can call WebJobs and be notified when background processing is finished. You can choose from multiple methods for using WebJobs, including queues and triggers.
-
-WebJobs is designed for background processing. You can do as much background processing as you want in a WebJob. For more information about WebJobs, see [Run background tasks with WebJobs](/azure/app-service/webjobs-create).
-
-## ASP.NET Core applications that are hosted in App Service sometimes stop responding. How do I fix this issue?
-
-A known issue with an earlier [Kestrel version](https://github.com/aspnet/KestrelHttpServer/issues/1182) might cause an ASP.NET Core 1.0 app that's hosted in App Service to intermittently stop responding. You might also see this message: "The specified CGI Application encountered an error and the server terminated the process."
-
-This issue is fixed in Kestrel version 1.0.2. This version is included in the ASP.NET Core 1.0.3 update. To resolve this issue, make sure you update your app dependencies to use Kestrel 1.0.2. Alternatively, you can use one of two workarounds that are described in the blog post [ASP.NET Core 1.0 slow perf issues in App Service web apps](/archive/blogs/waws/asp-net-core-slow-perf-issues-on-azure-websites).
-
-## I can't find my log files in the file structure of my web app. How can I find them?
-
-If you use the Local Cache feature of App Service, the folder structure of the LogFiles and Data folders for your App Service instance are affected. When Local Cache is used, subfolders are created in the storage LogFiles and Data folders. The subfolders use the naming pattern "unique identifier" + time stamp. Each subfolder corresponds to a VM instance in which the web app is running or has run.
-
-To determine whether you're using Local Cache, check your App Service **Application settings** tab. If Local Cache is being used, the app setting `WEBSITE_LOCAL_CACHE_OPTION` is set to `Always`.
-
-If you aren't using Local Cache and are experiencing this issue, submit a support request.
-
-## I see the message "An attempt was made to access a socket in a way forbidden by its access permissions." How do I resolve this error?
-
-This error typically occurs if the outbound TCP connections on the VM instance are exhausted. In App Service, limits are enforced for the maximum number of outbound connections that can be made for each VM instance. For more information, see [Cross-VM numerical limits](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#cross-vm-numerical-limits).
-
-This error might also occur if you try to access a local address from your application. For more information, see [Local address requests](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests).
-
-For more information about outbound connections in your web app, see the blog post about [outgoing connections to Azure websites](https://www.freekpaans.nl/2015/08/starving-outgoing-connections-on-windows-azure-web-sites/).
-
-## How do I use Visual Studio to remote debug my App Service web app?
-
-For a detailed walkthrough that shows you how to debug your web app by using Visual Studio, see [Remote debug your App Service web app](/archive/blogs/benjaminperkins/remote-debug-your-azure-app-service-web-app).
-
 ## Additional recommendations for performance and resiliency
 
 - Use Application Insights and Azure Monitor for full-stack observability of your App Service app, including telemetry, dependency tracing, and live metrics.
 
 - If you're deploying in regions that support availability zones, consider enabling zone redundancy to enhance resiliency during regional outages. For more information, see [Reliability in Azure App Service](/azure/reliability/reliability-app-service).
 
 - App Service undergoes routine maintenance to ensure platform reliability. For more control over update behavior, especially in App Service Environment v3, configure upgrade preference.  For more information, see [Routine (planned) maintenance for Azure App Service](/azure/app-service/routine-maintenance).
-
-[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]