Merge remote-tracking branch 'upstream/main' into pr/10533

Author: v-tappelgate

.openpublishing.redirection.developer.json

@@ -5762,7 +5762,7 @@
     },
     {
       "source_path": "support/developer/browsers/welcome-browsers.yml",
-      "redirect_url": "/previous-versions/troubleshoot/browsers/welcome-browsers",
+      "redirect_url": "/troubleshoot/microsoft-edge/welcome-edge",
       "redirect_document_id": false
     },
     {

.openpublishing.redirection.json

@@ -1,6 +1,21 @@
 {
   "redirections": [
-    {
+   {
+      "source_path": "support/windows-server/active-directory/admt-3dot2-installation-incomplete.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/admt-3dot2-installation-incomplete",
+      "redirect_document_id": false
+    },
+   {
+      "source_path": "support/windows-server/active-directory/issues-admt-3dot1-migrate-to-domain.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/issues-admt-3dot1-migrate-to-domain",
+      "redirect_document_id": false
+    },
+   {
+      "source_path": "support/windows-server/active-directory/use-adminpak-remotely-administer-computers.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/use-adminpak-remotely-administer-computers",
+      "redirect_document_id": false
+    },
+   {
       "source_path": "support/mem/configmgr/update-management/high-network-bandwidth-usage.md",
       "redirect_url": "/troubleshoot/mem/configmgr/welcome-configuration-manager",
       "redirect_document_id": false
@@ -12663,6 +12678,10 @@
       "redirect_url": "/dynamics365/field-service/deprecations-field-service#dynamics-365-field-service-integrations-with-microsoft-outlook-teams-viva-connections-and-planner---september-1-2025",
       "redirect_document_id": false
     },
+    {
+      "source_path": "support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md",
+      "redirect_url": "/dynamics365/field-service/update-field-service"
+    },
     {
       "source_path": "support/dynamics-365/finance/tax/tcs-troubleshooting-failed-access-tax-service.md",
       "redirect_url": "/troubleshoot/dynamics-365/finance/welcome-finance",
@@ -14150,6 +14169,18 @@
     {
       "source_path": "support/power-platform/power-automate/desktop-flows/browser-automation/browser-automation-error-after-chromium-update.md",
       "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error"
+    },
+    {
+      "source_path": "support/developer/visualstudio/cpp/libraries/stl-priority-queue-class-custom-type.md",
+      "redirect_url": "/cpp/standard-library/priority-queue-class#use-a-user-defined-data-type-with-the-priority_queue"
+    },
+    {
+      "source_path": "support/developer/visualstudio/cpp/libraries/use-setfind-stl-function.md",
+      "redirect_url": "/cpp/standard-library/set-class#example-of-setfind"
+    },
+    {
+      "source_path": "support/power-platform/ai-builder/power-automate/prevent-users-from-creating-ai-builder-custom-models.md",
+      "redirect_url": "/troubleshoot/power-platform/ai-builder/welcome-ai-builder"
     }
   ]
 }

Microsoft365/purview/purview/diagnostics/purview-compliance-diagnostics.md

@@ -15,7 +15,7 @@ ms.reviewer: shadans, sathyana, meerak, v-shorestris
 appliesto:
   - Microsoft Purview
 search.appverid: MET150
-ms.date: 12/05/2025
+ms.date: 01/20/2026
 ---
 
 # Self-help diagnostics for Microsoft Purview
@@ -129,5 +129,6 @@ The following table lists the available diagnostics on the **Help** pane. You ca
 | [DLP policy and rule configuration for policy tips](https://aka.ms/PillarDLPPolicyTipsDiag)<br> | Troubleshoots common policy tip configuration issues that affect a DLP rule and its policy for Outlook desktop clients and Outlook on the web. | Global admin | [Resolve issues that affect DLP policy tips](/microsoft-365/troubleshoot/data-loss-prevention/data-loss-prevention-policy-tips) |
 | [Sensitivity label configuration](https://aka.ms/PillarMipLabelDiag)<br> | Troubleshoots common issues that affect a sensitivity label. Checks whether a sensitivity label is correctly configured for use in various workloads. | Global admin | [Sensitivity labels are missing in Outlook, Outlook on the web, and other Office apps](/microsoft-365/troubleshoot/sensitivity-labels/sensitivity-labels-missing) |
 | [Microsoft Purview Message Encryption configuration](https://aka.ms/PillarOMEDiag)<br> | Validates the tenant configuration for Microsoft Purview Message Encryption. Identifies any configuration issues. | Any Microsoft 365 admin role | [Resolve Microsoft Purview Message Encryption issues](/microsoft-365/troubleshoot/office-message-encryption/fix-message-encryption-issue-microsoft-purview) |
+| [Validate Audit configuration](https://aka.ms/PillarAuditConfigDiag)<br> | Validates general Audit Configuration. Checks Audit logs for a user and identifies configuration issues. |Global Admin| [Export, configure, and view audit log records](/purview/audit-log-export-records) |
 
 **Note**: Microsoft Support agents can't provide assistance for diagnostics that appear in the **Help** pane. If you encounter any issues, you can use the Feedback link within the diagnostic to report the issue.

Outlook/classic-outlook-for-windows/clienttoc/toc.yml

@@ -333,6 +333,8 @@
           href: ../profiles-and-accounts/error-when-subscribing-to-rss-feed-that-needs-authentication.md
         - name: Can't use EAS to connect Outlook to Exchange
           href: ../profiles-and-accounts/outlook-cannot-use-activesync-connect-exchange.md
+        - name: The Exchange administrator made a change that requires users to restart Outlook
+          href: ../profiles-and-accounts/change-requires-restart.md
         - name: Event 1098 and can't create new profiles
           href: ../profiles-and-accounts/event-1098-and-cannot-create-new-profiles.md
         - name: Focused Inbox disappears

Outlook/classic-outlook-for-windows/profiles-and-accounts/change-requires-restart.md

@@ -0,0 +1,52 @@
+---
+title: Exchange Online admin makes a change that requires users to restart Outlook
+description: Discusses a message that tells users to restart Outlook, but doesn't explain why. The message is prompted by a configuration change by the administrator.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+ms.reviewer: pedrocorreia, v-kccross
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - CSSTroubleshoot
+appliesto:
+- Exchange Online
+- Outlook 2024
+- Outlook 2021
+- Outlook 2019
+- Outlook 2016
+ms.date: 01/16/2026
+---
+
+# Users have to restart Outlook after Exchange Online administrator makes a change
+
+## Summary
+
+This article explains that users of Microsoft classic Outlook for Windows might receive a message to restart Outlook because changes are made by the Microsoft Exchange Online administrator. The message is associated with Event ID 67. The article recommends that administrators correlate the event with the audit log to identify the cause of the message.
+
+## Symptoms
+
+While users work in classic Outlook for Windows, they receive the following message:
+
+> The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook.
+
+After they receive this message, users should select **OK** to dismiss the message window, and then manually restart Outlook. Outlook doesn't automatically restart.
+
+## Cause
+
+This message window might appear for multiple reasons. However, when this issue occurs, Event 67 is recorded in Event Viewer.
+
+To access Event 67, use the following steps:
+
+1. On the affected user's computer, select the **Start** menu or press the Windows logo key on the keyboard.
+1. Type **Event Viewer**, and then select it in the search results.
+1. Select **Windows Logs** > **Application**.
+1. In the **Event ID** column, find and select **Event ID 67**.
+
+   The **General** and **Details** tabs in the **Properties** pane provide information about the event.
+
+   ![Event ID 67 shown in Event Viewer.](media/change-requires-restart/event-67.png)
+
+## Resolution
+
+To identify the changes that might cause the message to appear in Outlook, correlate the details that are provided in Event 67 with the information that's available in the administrator audit log.

Outlook/classic-outlook-for-windows/profiles-and-accounts/media/change-requires-restart/event-67.png

@@ -23,7 +23,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 01/07/2026
+ms.date: 01/27/2026
 ---
 # Known issues with Teams on Android devices
 
@@ -36,6 +36,7 @@ ms.date: 01/07/2026
 |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.|
 |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.|Upgrade to the 1449/1.0.96.2025341701 version of the Teams Rooms app to resolve the issue.|
 |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.|
+|Screen shared from laptop looks blurry on Teams Rooms display.|When you start a full screen share from a laptop that has its resolution set to 1920x1200, the display connected to a Teams Room on Windows device is blurry.|To work around the issue, set the display resolution on the laptop to 1920x1080.|
 
 ## 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/13/2025
+ms.date: 01/27/2026
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -42,6 +42,9 @@ 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.|
+|Screen shared from laptop looks blurry on Teams Rooms display.|When you start a full screen share from a laptop that has its resolution set to 1920x1200, the display connected to a Teams Room on Windows device is blurry.|To work around the issue, set the display resolution on the laptop to 1920x1080.|
 
 ## Hardware issues
 

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

@@ -6504,6 +6504,10 @@
         "source_path": "information-protection/welcome-information-protection.yml",
         "redirect_url": "/troubleshoot/microsoft-365/purview/sensitivity-labels/known-issues-ip-client",
         "redirect_document_id": false
+      },
+        {
+        "source_path": "app-service/faqs-app-service-linux.yml",
+        "redirect_url": "/troubleshoot/azure/app-service/faqs-app-service-linux-new"
       }
   ]
 }

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

@@ -14,6 +14,8 @@ ms.custom: sap:Availability, Performance, and Application Issues, devx-track-js
 ---
 # Best practices and troubleshooting guide for node applications on Azure App Service Windows
 
+## Summary
+
 In this article, you learn best practices and troubleshooting steps for [Windows Node.js applications](/azure/app-service/quickstart-nodejs?pivots=platform-windows) running on Azure App Service (with [iisnode](https://github.com/azure/iisnode)).
 
 > [!WARNING]