Merge branch 'main' into dynatrace-troubleshoot

Author: v-albemi

.openpublishing.redirection.json

@@ -1,5 +1,40 @@
 {
   "redirections": [
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-user-experience.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-windows-failover-cluster-issues.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-wufb-reports.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-group-policy.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-deployment.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-ad-replication.md",
+      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-active-directory-scenarios#scenario-active-directory-replication-and-topology",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-client/setup-upgrade-and-drivers/prevent-users-connect-usb.md",
+      "redirect_url": "https://gpsearch.azurewebsites.net/#173",
+      "redirect_document_id": false
+    },
     {
       "source_path": "support/power-platform/dataverse/working-with-solutions/failure-converting-to-managed-solution.md",
       "redirect_url": "https://learn.microsoft.com/power-platform/alm/solution-concepts-alm#managed-and-unmanaged-solutions"

Microsoft365/purview/purview/audit-logs/mailbox-audit-logs.md

@@ -1,5 +1,5 @@
 ---
-title: How to use mailbox audit logs in Microsoft 365
+title: Use mailbox audit logs in Microsoft 365
 description: Describes how to use mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing in Microsoft 365 dedicated.
 author: Cloud-Writer
 ms.author: meerak
@@ -18,20 +18,18 @@ search.appverid: MET150
 ms.date: 05/05/2025
 ---
 
-# How to use mailbox audit logs in Microsoft 365
+# Use mailbox audit logs in Microsoft 365
 
-In Microsoft 365, you can run mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
+In Microsoft 365, you can run [mailbox audit logs](/purview/audit-mailboxes) to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
 
 **Note**: For the vNext environment, by default, mailbox audit logs aren't enabled. The feature must be turned on in order for a user to begin a search.
 
-## How to run and check mailbox audit logs
+## Run mailbox audit logs
 
 Mailbox audit logging lets users obtain information about actions that are performed by non-owners and administrators. Mailbox audit logging is available to members of the Audit Reporting Mailbox self-service group only by using Windows Remote PowerShell.
 
 > [!NOTE]
->
-> - By default, only non-owner mailbox audit logging is enabled, and owner mailbox audit logging is disabled. If you have to perform owner mailbox audit logging to investigate a specific issue, you can temporarily enable the process for two weeks.
-> - Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
+> Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
 
 To investigate this issue, create and use a Windows PowerShell script by using the sample script that's provided in Step 1 in this section, and then customize a search. By default, you can investigate actions that are performed by non-owners and administrators. This script exports content in a simplified, comma-separated values (.csv) file to help you troubleshoot reports about items that are missing or that were updated unexpectedly.
 
@@ -205,7 +203,7 @@ The most useful columns of the .csv file are exported. Some of these columns are
 |OperationResult|Status of the operation</br></br>**Note** Operation results include the following: </br>- Failed </br>- PartiallySucceeded </br>- Succeeded |
 |CrossMailboxOperation|Information about whether the operation that's logged is a cross-mailbox operation (for example, copying or moving messages among mailboxes) |
 
-### More information about mailbox audit logging
+### Use Windows Remote PowerShell
 
 - The **Search-MailboxAuditLog**  cmdlet is used in the sample script in Step 1 to search a single mailbox synchronously. You can do this also by running the cmdlet in Windows Remote PowerShell.
 

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

@@ -55,11 +55,14 @@ The following table lists the available diagnostics on **Solutions** pages. You
 
 **Note**: To run these diagnostics, the minimum requirement is that you're an administrator with the Organization Configuration role assigned to you.
 
-| **Issue** | **Checks performed** | **Solutions page** |
-|-|-|-|
-| Email encryption isn't working as expected. Are there any issues with my licenses or settings? | Checks license availability for sensitivity labels. Also checks information protection settings for your tenant, including Information Rights Management (IRM) and transport rule settings. Validates encryption settings. | [Information Protection diagnostics](https://purview.microsoft.com/informationprotection/diagnostics) |
-| A user can't find the sensitivity label they need. Does the label policy apply to them? | Checks which sensitivity labels are available to the user. Diagnostic results include information such as the label names, settings, and where the labels are available. | [Information Protection diagnostics](https://purview.microsoft.com/informationprotection/diagnostics) |
-| A DLP rule isn't enforced for a particular user. Is this user included in the DLP policy? | Checks which DLP policies apply to a user. Diagnostic results include the policy names and where the policies apply. | [DLP diagnostics](https://purview.microsoft.com/datalossprevention/diagnostics) |
+| **Issue** | **Checks performed** | **Commandlet Used** | **Solutions page** |
+|-|-|-|-|
+| Email encryption isn't working as expected. Are there any issues with my licenses or settings? | Checks license availability for sensitivity labels. Also checks information protection settings for your tenant, including Information Rights Management (IRM) and transport rule settings. Validates encryption settings. | [Test-IrmConfiguration](/powershell/module/exchangepowershell/test-irmconfiguration)| [Information Protection diagnostics](https://purview.microsoft.com/informationprotection/diagnostics) |
+| A user can't find the sensitivity label they need. Does the label policy apply to them? | Checks which sensitivity labels are available to the user. Diagnostic results include information such as the label names, settings, and where the labels are available. | [Get-label](/powershell/module/exchangepowershell/get-label) <br> [Get-LabelPolicy](/powershell/module/exchangepowershell/get-labelpolicy) | [Information Protection diagnostics](https://purview.microsoft.com/informationprotection/diagnostics) |
+| A DLP rule isn't enforced for a particular user. Is this user included in the DLP policy? | Checks which DLP policies apply to a user. Diagnostic results include the policy names and where the policies apply.| [Get-DlpCompliancePolicy](/powershell/module/exchangepowershell/get-dlpcompliancepolicy) <br> [Get-DlpComplianceRule](/powershell/module/exchangepowershell/get-dlpcompliancerule) | [DLP diagnostics](https://purview.microsoft.com/datalossprevention/diagnostics) |
+| Endpoint DLP isn’t working as expected. Are there any issues with policy sync on the device? | Check for policy sync issues and provide recommendations on how to resolve them. |[Get-DlpCompliancePolicy](/powershell/module/exchangepowershell/get-dlpcompliancepolicy) | [DLP diagnostics](https://purview.microsoft.com/datalossprevention/diagnostics) |
+| Alerts not working for a DLP rule. Are there any issues with the DLP rule configuration? | Check for alerts and identify whether there are issues with the DLP rule configuration.| [Get-DlpCompliancePolicy](/powershell/module/exchangepowershell/get-dlpcompliancepolicy) <br> [Get-DlpComplianceRule](/powershell/module/exchangepowershell/get-dlpcompliancerule) | [DLP diagnostics](https://purview.microsoft.com/datalossprevention/diagnostics) | 
+| Can't find an alert for an activity or an audit event ? | Check for the alert related to an activity or audit event and investigate why the alert could be missing | [Get-DlpCompliancePolicy](/powershell/module/exchangepowershell/get-dlpcompliancepolicy) <br> [Get-DlpComplianceRule](/powershell/module/exchangepowershell/get-dlpcompliancerule) | [DLP diagnostics](https://purview.microsoft.com/datalossprevention/diagnostics) |
 
 ## Diagnostics on the Help pane
 

Teams/meetings/teams-meeting-with-shared-mailboxes.md

@@ -12,14 +12,17 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 06/23/2025
+ms.date: 10/08/2025
 ---
 # Teams meeting features for shared mailboxes
 
 For Microsoft Teams meetings that are managed by using a shared mailbox, only a limited number of features are available. The following table lists the details of each feature.
 
 > [!NOTE]
-> Shared mailboxes aren't intended for direct login. Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password or signing in by using the shared mailbox user account.
+
+> - Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password.
+> - Don't sign in by using the credentials of the shared mailbox user account. Only users that the shared mailbox is shared with can log in with their user credentials.
+> - To create a Teams meeting in a shared mailbox calendar, a valid Teams license must be assigned either to the shared mailbox or to the user who is logged in to the shared mailbox.
 
 |Available feature|Details|
 |----------|-----------|

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

@@ -1,6 +1,6 @@
 ---
-title: Known issues with Teams Rooms on Android
-description: Provides a list of known issues for Teams Rooms on Android.
+title: Known issues with Teams on Android devices
+description: Provides a list of known issues with Android devices that run Teams.
 ms.author: meerak
 author: Cloud-Writer
 ms.reviewer: sohailta, garyanselme, czawideh
@@ -23,9 +23,9 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 09/03/2025
+ms.date: 10/06/2025
 ---
-# Known issues with Teams Rooms on Android
+# Known issues with Teams on Android devices
 
 <!-- If you get word that one of these issues no longer applies, contact [email protected] to EoL the corresponding KB.  -->
 
@@ -42,9 +42,9 @@ ms.date: 09/03/2025
 | Issue  |  Description | Workaround |
 | --- | --- | --- |
 |Signed out of Teams on Android devices | Teams Rooms on Android, Teams phone devices, Teams panels, and Teams displays are signed out of Teams automatically. | Follow the instructions provided in [Signed out of Teams on Android devices](./signed-out-of-teams-android-devices.md).|
-|Unable to extract log files.|You're trying to extract a log file but either the log files are empty or you see an error message. This behavior can occur when the logs contain partially corrupted zip files or log files.|Contact Microsoft Support by filing a request at [SERVICENOW](https://microsoft.service-now.com/sp?id=sc_cat_item&sys_id=0baac5bcdb0ca414b720f337689619ce&sysparm_category=8b859929136eea002620b0912244b066).|
+|Unable to extract log files.|You're trying to extract a log file but either the log files are empty or you see an error message. This behavior can occur when the logs contain partially corrupted zip files or log files.|Try to extract the log files by using the [7-ZIP](https://www.7-zip.org/) tool instead of the built-in Windows file extraction tool.|
 
-## Issues with Teams phones
+## Issues affecting Teams phones
 
 | Issue  |  Description | Workaround |
 | --- | --- | --- |
@@ -54,6 +54,7 @@ ms.date: 09/03/2025
 |Unable to assign speed dial to line keys on a sidecar|When you assign speed dial contacts to line keys on the sidecar that is connected to a touch phone device, they don't work.|No workaround is available for the speed dial contacts that you assigned by using the sidecar. However the speed dial contacts that're already set up and shared line delegates and other groups are automatically pinned on the sidecar.|
 |Speed dial line key doesn't transfer an active call.|In older Teams Phones versions, you could transfer an active call by selecting a line key that is configured as a speed dial for a specific contact.<br/><br/>Beginning with Teams Phones version 1.7.0 1449/1.0.94.2025165302, you're only able to make an outgoing call to the speed dial after you select it from the **Transfer** menu.|If you want to transfer active calls to specific contacts, configure line keys as speed dials for those contacts and assign the **Transfer** and **Consult Transfer** menu options to the appropriate line keys.|
 |The screen hangs on Yealink phones when the headset is picked up.|On Yealink MP56 phones that are running version 1449/1.0.94.2025248901 of the Teams for Android app, the screen hangs or crashes when you pick up the headset to make an outbound call.|No workaround is available at this time.|
+|Can't see line keys on the home screen.|After you update your Teams Phones to version 1449/1.0.94.2025264001 of the Teams for Android app, you don't see any assigned line keys on the home screen.<br/><br/>This behavior is seen on non-touch phones such as Poly CCX 350 that have either the CAP or Premium CAP licenses.|No workaround is available at this time.|
 
 ## Limitations
 

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

@@ -22,7 +22,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 07/01/2025
+ms.date: 10/07/2025
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -41,13 +41,15 @@ ms.date: 07/01/2025
 |Unable to join some Webex meetings|When you select the **Join** button to join a Cisco Webex meeting from a Teams Rooms on Windows device, you're not connected to the meeting and see the home screen on the device instead.|No workaround is available at this time. Cisco is investigating the issue.|
 |Only see one camera's view even though multi-camera feature is turned on.|Your Teams Rooms on Windows device is configured for multiple cameras. However after the device restarts, remote users might see only the default camera's view.<br/><br/>This issue might occur only in the first meeting after the device restarts. The cameras function as expected in all subsequent meetings.|To work around the issue, end the first meeting after the device restarts, and start a second meeting.|
 |Front of Room view displays a blank, black screen on a remote access tool.|When you access a Teams Rooms on Windows console remotely by using tools such as the Teams Rooms Pro Management Portal (PMP), TeamViewer, Virtual Network Computing (VNC) etc., the Front of Room (FoR) monitors display a black image instead of the expected user interface.<br/><br/>The FoR monitors in the meeting room display the expected screen but show only a black image in the view on the remote access tool.<br/><br/>If you sign in to the Teams Rooms device by using administrator credentials, you see the Windows screen in the FoR view as expected.|Restart your device to update to the latest configuration to fix the issue.|
+|Automatic remediation in Pro Management portal keeps failing.|The built-in remediation in the Microsoft Teams Rooms Pro Management portal to disable the USB peripheral power draining option under Windows USB settings keeps failing with the error message:<br/><br/>`Auto Remediation was unable to resolve this issue.`|To resolve the issue, implement a manual fix as described in [USB Peripheral Power Drain signal is unhealthy](./usb-peripheral-power-drain-status-unhealthy.md).|
 
 ## Hardware issues
 
 | Issue  |  Description | Workaround |
 | --- | --- | --- |
 |During a Coordinated meeting, when the meeting volume is changed by using a room remote, the speaker on a Surface Hub or Teams Rooms device turns on.|For a trusted device such as a Surface Hub or Teams Rooms device that is set up to automatically join a Coordinated meeting when the primary device joins, the speaker turns on when a room remote is used to change the meeting volume. This issue occurs even though the audio settings on the device are turned off, and whether they're enabled or disabled.|Turn off proximity join and room remote capabilities on the trusted devices that automatically join a Coordinated meeting.|
 |The central part of the console on a Teams Rooms device doesn't respond to touch and mouse input.|On some Microsoft Teams Rooms devices such as the Crestron Dell Optiplex 7080 that use a 4k monitor connected as the front-of-room display, the central portion of the display intermittently stops responding to touch and mouse controls.<br/><br/>Despite this issue, the Teams Rooms app is functional and accepts inputs from a connected keyboard.|Contact Microsoft Support for assistance to work around this issue.|
+|Poor audio quality from a Teams Rooms device.|You might experience any of the following audio quality issues from a USB microphone or speaker that's connected to your Teams Rooms device: <ul><li> - Echo sent to remote participants on the call.</li><li> - Low audio quality sent to remote participants on the call.</li><li> - Decrease in audio quality as the call progresses.</li><li> - Low volume in speakers within the room.</li></ul><br/>This issue might be caused when a setting in the audio driver configuration to enhance audio quality is enabled.|To fix the audio quality issue, disable the audio enhancement setting for the attached Teams-certified USB audio device by using the following steps:<ol><li>Select **Settings** on the Teams Rooms device console.</li><li>Select **Windows Settings**, and sign in to the Teams Rooms device as an administrator.</li><li>Open **Control Panel**.</li><li>Select **Hardware and Sound** > **Sound**.</li><li>On the **Playback** tab, select the affected audio device and then select **Properties**.</li><li>Select the **Advanced** tab.</li><li>In the **Signal Enhancements** section, uncheck **Enable audio enhancements**, and then select **OK**.</li><li>Select the **Recording** tab and repeat steps 5, 6 & 7 for the same audio device </li><li>Select **OK** and then close **Control Panel.</li><li>Restart the Teams Rooms device.</li></ol>
 
 ## Limitations
 
@@ -65,6 +67,5 @@ For issues with Teams devices offered by third-party providers, contact their in
 - Logitech: [Logitech Support](https://support.logi.com/hc/)
 - Crestron: [Crestron Support](https://support.crestron.com/)
 - Poly: [Poly Support](https://www.poly.com/us/support)
-- Yealink: [Yealink Support](https://support.yealink.com/portal/home)
 
 [!INCLUDE [Third-party disclaimer](../../includes/third-party-contact-disclaimer.md)]

azure-pipelines.yml

@@ -0,0 +1,19 @@
+# Starter pipeline
+# Start with a minimal pipeline that you can customize to build and deploy your code.
+# Add steps that build, run tests, deploy, and more:
+# https://aka.ms/yaml
+
+trigger:
+- main
+
+pool:
+  vmImage: ubuntu-latest
+
+steps:
+- script: echo Hello, world!
+  displayName: 'Run a one-line script'
+
+- script: |
+    echo Add other tasks to build, test, and deploy your project.
+    echo See https://aka.ms/yaml
+  displayName: 'Run a multi-line script'