Merge remote-tracking branch 'upstream/main' into CI-8544

Author: ryanberg-aquent

Microsoft365/admin/admin/admintoc/toc.yml

@@ -136,6 +136,10 @@
       href: ../miscellaneous/support-cases-for-gcc-high-dod.md
     - name: Reports show anonymous user names
       href: ../miscellaneous/reports-show-anonymous-user-name.md    
+  - name: Orchestrated Migration
+    items:
+    - name: Resolve Orchestrated Migration errors
+      href: ../orchestrated-migration/resolve-orchestrated-migration-errors.md
   - name: Sign-in
     items:
     - name: Can't sign in to Microsoft cloud service

Microsoft365/admin/admin/orchestrated-migration/resolve-orchestrated-migration-errors.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
 

Microsoft365/purview/purview/sensitivity-labels/known-issues-ip-client.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-android.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
 

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

@@ -6495,6 +6495,15 @@
         {
         "source_path": "virtual-machines/windows/vm-stops-at-please-wait-for-group-policy-client.md",
         "redirect_url": "/troubleshoot/virtual-machines/windows/please-wait-for-the-group-policy-client"
+      },
+        {
+        "source_path": "information-protection/troubleshoot-aip-issues.md",
+        "redirect_url": "/troubleshoot/microsoft-365/purview/sensitivity-labels/known-issues-ip-client"
+      },
+        {
+        "source_path": "information-protection/welcome-information-protection.yml",
+        "redirect_url": "/troubleshoot/microsoft-365/purview/sensitivity-labels/known-issues-ip-client",
+        "redirect_document_id": false
       }
   ]
 }

support/azure/.openpublishing.redirection.azure.json

@@ -277,6 +277,4 @@ Follow these links to learn more about Node.js applications on Azure App Service
 * [Exploring the Super Secret Kudu Debug Console](https://www.youtube.com/watch?v=-VjqyvA2XjM)
 
 
-[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
-
 [!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/app-service/app-service-web-nodejs-best-practices-troubleshoot-guide.md

@@ -273,6 +273,4 @@ You might have noticed the **Configure Action** option in the previous screensho
 
 There are other options for troubleshooting and diagnosing performance issues on the Azure App Service platform. This article focuses on memory dump collection and makes some recommendations for approaching the diagnosis by using these methods. If you have already studied, experienced, and perfected your collection procedures, and they work well for you, you should continue to use those procedures.
 
-[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
-
 [ap]: https://portal.azure.com

support/azure/app-service/capture-memory-dumps-app-service.md

@@ -0,0 +1,53 @@
+---
+title: Error 403 - This web app is stopped message
+description: This article provides guidance on addressing the "Error 403 - This web app is stopped" message. 
+author: JarrettRenshaw
+manager: dcscontentpm
+ms.topic: troubleshooting-general
+ms.date: 12/17/2025
+ms.author: jarrettr
+ms.reviewer: v-ryanberg
+ms.service: azure-app-service
+ms.custom: sap:Availability, Performance, and Application Issues
+---
+# "Error 403 - This web app is stopped" message 
+
+This article provides guidance on addressing the "Error 403 - This web app is stopped" message in Azure App Service.
+
+## Symptom
+
+When browsing to an Azure web site, you encounter the following message: "Error 403 - This web app is stopped."
+
+## Cause
+
+There are three possible conditions:
+
+- The site has reached a [billing limit](#billing-limit) and is disabled.
+- The website has been [stopped in the portal](#website-stopped-in-the-portal).
+- The website has reached a [resource quota limit](#website-has-reached-a-resource-quota-limit).
+
+## Resolution
+
+### Billing limit
+
+This can occur when your Azure subscription has a spending limit. When the limit is reached, your site is suspended. 
+
+To verify this, browse to the [Azure Account Portal](https://account.windowsazure.com/Home/Index) and select **Account Center**. 
+
+If this is the issue, see [What do I do if my Azure subscription becomes disabled?](https://azure.microsoft.com/documentation/articles/billing-subscription-become-disable/) for information on how to resolve subscription limits.
+
+### Website stopped in the portal
+
+In [Azure portal](https://portal.azure.com/), check the status of your site. If it reads **Stopped**, select **Start**.
+
+### Website has reached a resource quota limit
+
+In Azure portal, navigate to the **Quotas** blade and determine your quota status. 
+
+There are two recovery options if you reach a usage quota:
+
+- Wait until the quota is reset. Under each quota, you see **Resets in X hours X minutes**. This is the quota measurement period. If you choose to wait, the site isn't be functional until this time expires. For example, the **Data Out** quota is applied once per day. If the quota is reached in the first hour of the measurement period (one day), your site will be offline for 23 hours until the quota is reset.
+
+- Scale up the web hosting plan. Quotas only apply to the Free and Shared web hosting plans. Upgrading your plan can solve the limit issue. For more information, see [Azure plan](https://azure.microsoft.com/pricing/offers/ms-azr-0017g/) and [Pricing calculator](https://azure.microsoft.com/pricing/calculator/).
+
+

support/azure/app-service/error-403-web-app-stopped-message.md

@@ -17,6 +17,12 @@ items:
           href: ./capture-memory-dumps-app-service.md
         - name: Availability, performance, and application FAQs
           href: web-apps-performance-faqs.md
+        - name: Error 403 - This web app is stopped message
+          href: error-403-web-app-stopped-message.md  
+        - name: Worker Process requested recycle due to Percent Memory limit message 
+          href: worker-process-percent-memory-limit-message.md
+        - name: Web request times out in App Service
+          href: web-request-times-out-app-service.md  
         - name: Troubleshoot instance-related issues
           href: troubleshoot-instance-related-issues-on-azure-app-service.md
         - name: Troubleshoot temporary storage