Merge branch 'main' into CI_6856

Author: Simonx Xu

.github/workflows/create-ado-workitem.yml

@@ -0,0 +1,36 @@
+name: Create Azure DevOps CI on PR
+
+on:
+  pull_request:
+    types: [opened]
+
+jobs:
+  create-work-item:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create Azure DevOps Task
+        env:
+          ADO_ORG_URL: https://dev.azure.com/KMOps
+          ADO_PROJECT: ContentExperience
+          ADO_PAT: ${{ secrets.ADO_PAT }}
+        run: |
+          PR_TITLE="${{ github.event.pull_request.title }}"
+          PR_BODY="${{ github.event.pull_request.body }}"
+          PR_URL="${{ github.event.pull_request.html_url }}"
+
+          curl -X POST \
+            -H "Content-Type: application/json-patch+json" \
+            -H "Authorization: Basic $(echo -n ":$ADO_PAT" | base64)" \
+            $ADO_ORG_URL/$ADO_PROJECT/_apis/wit/workitems/$ExternalCI?api-version=6.0 \
+            -d '[
+              {
+                "op": "add",
+                "path": "/fields/System.Title",
+                "value": "PR Opened: '"$PR_TITLE"'"
+              },
+              {
+                "op": "add",
+                "path": "/fields/System.Description",
+                "value": "Pull Request URL: '"$PR_URL"'\n\n'"$PR_BODY"'"
+              }
+            ]'

.openpublishing.redirection.json

@@ -13664,7 +13664,6 @@
       "source_path": "support/dynamics/gp/unapproved-pending-change-order-exist.md",
       "redirect_url": "/troubleshoot/dynamics/gp/welcome-gp"
     },
-    
     {
       "source_path": "support/dynamics/gp/use-banked-paycodes-with-project-accounting.md",
       "redirect_url": "/troubleshoot/dynamics/gp/welcome-gp"
@@ -13688,12 +13687,12 @@
     {
       "source_path": "support/windows-server/active-directory/troubleshoot-errors-join-computer-to-domain.md",
       "redirect_url": "/troubleshoot/windows-server/active-directory/domain-join-networking-errors"
-    },    
+    },
+    {
+      "source_path": "support/power-platform/power-automate/desktop-flows/troubleshoot-excel-errors.md",
+      "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
+    },
     {
-    "source_path": "support/power-platform/power-automate/desktop-flows/troubleshoot-excel-errors.md",
-    "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
-  },
-  {
       "source_path": "support/entra/entra-id/mfa/authorization-request-denied-graph-api.md",
       "redirect_url": "/troubleshoot/entra/entra-id/app-integration/troubleshoot-authorization-requestdenied-graph-api",
       "redirect_document_id": false
@@ -13804,41 +13803,38 @@
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/centralized-configuration-of-activity-logs-to-event-hub.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/exporting-directory-level-activity-logs-to-event-hub.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/pushing-subscription-activity-logs-to-sentinel.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/activity-logs/config-export/push-subscription-activity-logs-to-sentinel"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/resolving-log-limit-issues-in-azure-function-apps.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/understanding-and-managing-diagnostic-settings-retention.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
-    }
-    ,
+    },
     {
       "source_path": "support/sql/database-engine/install/windows/error-install-sql-server-2008-r2.md",
       "redirect_url": "/troubleshoot/sql/database-engine/install/windows/error-install-sql-server"
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/update-or-slipstream-installation.md",
+      "redirect_url": "/sql/database-engine/install-windows/install-sql-server-using-slipstream"
     }
   ]
-}
+}

Exchange/ExchangeOnline/administration/wam-integration-issues.md

@@ -0,0 +1,85 @@
+---
+title: Resolve Issues in Exchange Online PowerShell Module after WAM Integration
+description: Resolves compatibility issues when using Exchange Online PowerShell after Web Account Manager integration.
+author: cloud-writer
+ms.author: meerak
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Administrative Tasks
+  - Exchange Online
+  - CSSTroubleshoot
+manager: dcscontentpm
+search.appverid: 
+  - MET150
+appliesto: 
+  - Exchange Online
+ms.date: 08/21/2025
+ms.reviewer: vivepai, ninob
+---
+# Resolve issues in Exchange Online PowerShell module after WAM integration
+
+Beginning in Exchange Online PowerShell module version 3.7.0, Microsoft is implementing Web Account Manager (WAM) as the default authentication broker for user authentication. Although WAM offers improved security and a streamlined user experience, it might cause compatibility challenges in some situations. This article discusses these situations and provides workarounds for them.
+
+> [!NOTE]
+> Although you can use the **DisableWAM** switch together with the [Connect-ExchangeOnline](/powershell/module/exchangepowershell/connect-exchangeonline) command to disable WAM when you connect to Exchange Online PowerShell, you should use this option only as a temporary method. If you require assistance to resolve issues without having to disable WAM, contact Microsoft Support at [[email protected]](mailto:[email protected]).
+
+## Scenario: Using the RunAs option
+
+### Symptoms
+
+When you run the `Connect-ExchangeOnline` PowerShell command under a different user context than the credentials that were used to sign in to Windows, WAM-based authentication fails.
+
+In this scenario, you receive the following error message:
+
+> One or more errors occurred. (Unknown Status: Unexpected    Error: 0xffffffff80070520    Context: A specified logon session does not exist. It may already have been terminated.    Tag: 0x21420087 (error code -2147023584) (internal error code 557973639))- at Microsoft.Exchange.Management.ExoPowershellSnapin.GetConnectionContext.ProcessRecord()     at System.Management.Automation.CommandProcessor.ProcessRecord();InnerException : Unknown Status: Unexpected    Error: 0xffffffff80070520    Context: A specified logon session does not exist. It may already have been terminated.    Tag: 0x21420087 (error code -2147023584) (internal error code 557973639)…;
+
+### Cause
+
+WAM relies on the active user session to load its plugins and to access cryptographic keys and certificates that are associated with a user profile. If you run PowerShell under a different context, this action isolates the session and prevents WAM from functioning correctly.
+
+### Workaround
+
+For security, you shouldn't use the `RunAs` option to run PowerShell commands. This method bypasses key protections and introduces risks that are associated with impersonation and session isolation.
+
+Run PowerShell only in the same context as that of the signed-in Windows user to ensure compatibility with WAM. You can disable WAM temporarily by using the DisableWAM parameter together with the `Connect-ExchangeOnline` PowerShell command to connect to Exchange Online and then re-enable WAM.
+
+## Scenario: Running GDAP flows
+
+### Symptoms
+
+In certain Granular Delegated Admin Privileges (GDAP) flows, WAM-based authentication causes tokens to miss required WIDS claims.
+
+In this scenario, you receive the following error message:
+
+> The role assigned to user '[email protected]' isn't supported in this scenario.
+
+### Cause
+
+WAM might not correctly populate all the required claims in GDAP flows, especially if you use the `-DelegatedOrganization` parameter.
+
+### Workaround
+
+Disable WAM temporarily to connect to Exchange Online PowerShell in GDAP flows.
+
+Collect diagnostic logs by using the -EnableErrorReporting parameter together with the `Connect-ExchangeOnline` PowerShell command, and send the logs to [[email protected]](mailto:[email protected]).
+
+## Scenario: Using Windows Task Scheduler
+
+### Symptoms
+
+Scripts that use WAM-based authentication fail when they're run in the Windows Task Scheduler by having the **Run whether user is logged on or not** security option enabled.
+
+In this scenario, you receive the following error message:
+
+> One or more errors occurred. (Unknown Status: Unexpected    Error: 0xffffffff80070520    Context: A specified logon session does not exist. It may already have been terminated.    Tag: 0x21420087 (error code -2147023584) (internal error code 557973639))- at Microsoft.Exchange.Management.ExoPowershellSnapin.GetConnectionContext.ProcessRecord()     at System.Management.Automation.CommandProcessor.ProcessRecord();InnerException : Unknown Status: Unexpected    Error: 0xffffffff80070520    Context: A specified logon session does not exist. It may already have been terminated.    Tag: 0x21420087 (error code -2147023584) (internal error code 557973639)…;  
+
+### Cause
+
+WAM requires an active user session in order to function. In inactive sessions, critical components such as **%LOCALAPPDATA%**, cryptographic keys, and certificates are inaccessible.
+
+When the script execution starts, it has to sign in to Exchange Online. However, if the user doesn't sign in to the system, the script sign-in fails because WAM doesn't have the required user information to facilitate the script's sign-in attempt.
+
+### Workaround
+
+To run automated scripts, use certificate-based authentication. This method is secure and recommended. Alternatively, you can run scripts by using scheduling methods that preserve the user session context.

Exchange/ExchangeOnline/onlinetoc/toc.yml

@@ -106,6 +106,8 @@ items:
           href: ../administration/public-folder-permissions-in-exchange-admin-center-show-guid-not-name.md
         - name: Repeated calls against the same folder are slow
           href: ../administration/slow-repeated-calls-against-same-folder.md
+        - name: Resolve validation errors for an archive mailbox
+          href: ../administration/validation-errors-for-mailbox-archive-guid.md          
         - name: Self-help diagnostics
           href: ../administration/self-help-diagnostics.md
         - name: Site mailbox retirement
@@ -126,12 +128,12 @@ items:
           href: ../administration/update-of-client-access-rules-for-office-365-customers.md
         - name: UsageLocation validation error about Enable-UMMailbox
           href: ../administration/enable-ummailbox-cannot-be-performed-error.md
-        - name: Resolve validation errors for an archive mailbox
-          href: ../administration/validation-errors-for-mailbox-archive-guid.md
         - name: View and update address list membership
           href: ../administration/view-update-address-list-membership.md
         - name: Voice mail settings are missing from Options
           href: ../administration/voice-mail-settings-missing-from-options.md
+        - name: WAM integration issues
+          href: ../administration/wam-integration-issues.md
         - name: Windows Mail app not blocked by ActiveSync settings
           href: ../administration/windows-mail-app-not-blocked.md
         - name: WinRM client cannot process the request

Exchange/ExchangeServer/compliance/ediscovery-search-missing-items.md

@@ -15,7 +15,7 @@ ms.reviewer: dpaul
 appliesto: 
   - Exchange Server 2019
 search.appverid: MET150
-ms.date: 01/24/2024
+ms.date: 08/18/2025
 ---
 # Missing items in eDiscovery search results in Exchange Server 2019
 
@@ -46,7 +46,7 @@ In some scenarios, the time stamp information that's passed on to a subsequent p
 
 ## Workaround
 
-To work around this issue, create a setting override to use the **Search Folder** type in the search query setting. The setting override will be retained for 180 days only. To maintain the override, you must re-create it before it expires.
+To work around this issue, create a setting override to use the **Search Folder** type in the search query setting.
 
 1. Run the following cmdlet to create a setting override:
 

Outlook/Client/clienttoc/toc.yml

@@ -273,6 +273,8 @@
           href: ../performance/cannot-open-word-documents-or-excel-spreadsheets.md
         - name: Can't start Outlook in cached mode or create a profile
           href: ../performance/cannot-start-outlook-in-cached-mode-or-create-profile.md
+        - name: Collect performance and network traces
+          href: ../performance/collect-performance-trace.md
         - name: Crashes after installing language packs
           href: ../performance/outlook-2016-crash-event-1000.md
         - name: Error when you copy MSG email message files in Outlook containing multiple attachments or recipients

Outlook/Client/performance/collect-performance-trace.md

@@ -0,0 +1,43 @@
+---
+title: Collect a Performance Trace in New Outlook for Windows
+description: Provides guidance to collect performance and network traces in new Outlook for Windows.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Errors, Crashes, and Performance
+  - Outlook for Windows
+  - CSSTroubleshoot
+ms.reviewer: caithart
+appliesto: 
+  - New Outlook for Windows
+search.appverid: MET150
+ms.date: 08/27/2025
+---
+# Collect a performance trace in new Outlook for Windows
+
+If you contact Microsoft Support to troubleshoot issues that affect new Outlook for Windows, you might be asked to collect a performance trace, a network trace or both. To collect these traces, use the Outlook icon in your system tray, and save the files to your local computer.
+
+The Outlook icon provides the following options to collect a trace.
+
+| Options | Description |
+|--|--|
+| Start Performance Trace | Start monitoring performance indicators, and continue until stopped manually.<br><br>After the trace collection starts, this option changes to **Stop Performance Tracing**. |
+| Record Perf Trace for 1 min | Monitor performance indicators for one minute, and then stop automatically.<br><br>This option might be useful to troubleshoot an unresponsive application to make sure that the trace is saved automatically. |
+| Start Network Trace | Start capturing network logs, and continue until stopped manually.<br><br>After the trace collection starts, this option changes to **Stop Network Tracing**. |
+
+To collect and access a trace, follow these steps:
+
+1. To start a trace, right-click the Outlook icon in the system tray, and then select the appropriate option.
+
+2. After you reproduce the issue, right-click the Outlook icon again, and then select the appropriate option to stop the trace.
+
+3. To access the trace files, open File Explorer, and then navigate to **%localappdata%\Microsoft\Olk\Feedback\Traces**.
+
+   The file name of a trace uses the following format: **WebviewTrace_\<TraceType_n_yyyymmdd_hhmmSSss>.json**
+
+   For example: **WebviewTrace_Performance_1_20250324_215740833.json**
+
+If you're on the phone with Microsoft Support, and you're asked to share the trace files, navigate to **Help** > **Get Diagnostics**, and then select the **Send diagnostics** button. Provide the displayed Support ID so that the Support agent can access the trace information that you collected.

Teams/TOC.yml

@@ -206,8 +206,12 @@ items:
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-410.md
         - name: SIP response code 412
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-412.md
+        - name: SIP response code 415
+          href: ./phone-system/direct-routing/microsoft-sip-response-codes-415.md  
         - name: SIP response code 420
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-420.md
+        - name: SIP response code 422
+          href: ./phone-system/direct-routing/microsoft-sip-response-codes-422.md  
         - name: SIP response code 480
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-480.md
         - name: SIP response code 484
@@ -222,6 +226,8 @@ items:
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-503.md
         - name: SIP response code 504
           href: ./phone-system/direct-routing/microsoft-sip-response-codes-504.md
+    - name: Resolve 10DLC campaign rejection errors
+      href: ./phone-system/sms-calling-errors.md
     - name: Voicemail messages are not delivered
       href: ./phone-system/voicemails-not-delivered.md
   - name: Provisioning

Teams/phone-system/direct-routing/microsoft-sip-response-codes-415.md

@@ -0,0 +1,31 @@
+---
+title: SIP 415 and Microsoft response codes
+description: Lists combinations of Microsoft response code and the SIP 415 error, and provides actions to resolve the errors.
+ms.date: 08/18/2025
+author: Cloud-Writer
+ms.author: meerak
+manager: dcscontentpm
+audience: Admin
+ms.topic: troubleshooting
+search.appverid: 
+  - SPO160
+  - MET150
+appliesto: 
+  - Microsoft Teams
+ms.custom: 
+  - sap:Teams Calling (PSTN)\Direct Routing
+  - CI 6328
+  - CSSTroubleshoot
+ms.reviewer: teddygyabaah
+---
+
+# SIP response code 415
+
+This article provides troubleshooting information for the combination of the SIP 415 error and Microsoft response code 510415.
+
+## 540415 415 Unsupported Media Type
+
+- Microsoft response code: **540415**
+- SIP response code: **415**
+- Suggested actions:  
+  - This error indicates that either the SBC offer is missing or it contains an unsupported media type. For example, the CONTENT-TYPE might be missing or the SBC offer has unsupported data such as `CONTENT-TYPE : application/pidf+xml`. Check the SBC configuration to fix the problem.

Teams/phone-system/direct-routing/microsoft-sip-response-codes-420.md

@@ -1,7 +1,7 @@
 ---
 title: SIP 420 and Microsoft response codes
 description: Lists combinations of Microsoft response codes and the SIP 420 error, and provides actions to resolve the errors.
-ms.date: 11/22/2024
+ms.date: 08/18/2025
 author: Cloud-Writer
 ms.author: meerak
 manager: dcscontentpm
@@ -15,13 +15,21 @@ appliesto:
 ms.custom: 
   - sap:Teams Calling (PSTN)\Direct Routing
   - CI2387
+  - CI 6328
   - CSSTroubleshoot
 ms.reviewer: mikebis
 ---
 
 # SIP response code 420
 
-This article provides troubleshooting information for the combination of the SIP 420 error and Microsoft response code 560420.
+This article provides troubleshooting information for the combination of the SIP 420 error and various Microsoft response codes.
+
+## 540420 420 Bad Extension
+
+- Microsoft response code: **540420**
+- SIP response code: **420**
+- Suggested actions:  
+  - Check the SBC configuration to make sure that it doesn't require an unsupported SIP protocol extension such as REQUIRE : 100rel. SIP messages usually contain information about extensions that aren't supported. If necessary, work with your SBC vendor to verify that the SBC is configured correctly to provide the required SIP protocol extension.
 
 ## 560420 420 Bad Extension