Merge pull request #9820 from MicrosoftDocs/main

 New MTRW known issue from Matt Slomka

Author: Cloud-Writer

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/02/2025
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -41,6 +41,7 @@ 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
 
@@ -65,6 +66,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)]

support/azure/azure-monitor/activity-logs/config-export/configuring-azure-activity-log-export-comprehensive-guide.md

@@ -0,0 +1,88 @@
+---
+title: Configuring Azure Activity Log Export
+description: Provides guidance for resolving issues related to configuring the export of Azure activity logs
+ms.date: 10/01/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
+ms.service: azure-monitor
+ms.custom: I can’t configure export of activity logs
+---
+
+# Configure Azure activity log export
+
+This article outlines the steps to successfully configure Azure activity log export. This article also provides solutions to common issues that you might experience, especially if you're transitioning from older methods.
+
+## Configuring activity log export
+
+To configure Azure activity log export, follow these steps.
+
+### Step 1: Verify current configuration
+
+1. Go to the [Azure portal](https://ms.portal.azure.com/auth/login/), and access the **Activity Logs** section.
+1. Check the current export settings to make sure that they align with your requirements.
+
+### Step 2: Update legacy methods
+
+1. If you're using legacy APIs, PowerShell commands, or [log profiles](/answers/questions/1851179/what-will-happen-to-the-azure-activity-logs-soluti), update them to use diagnostic settings.
+1. Use the `Get-AzOperationalInsightsDataSource` command to verify existing data sources.
+
+### Step 3: Configure new export settings
+
+1. Select **Activity log** > **Export Activity Logs**.
+1. Find and select the subscription, and then select **Add diagnostic setting**.
+1. In the **Diagnostic setting name** box, enter a name.
+1. Select all applicable categories and then select **Save**.
+
+> [!NOTE]
+> It usually takes about 30 minutes for the export to begin. For more information, see [Time before telemetry gets to destination](/azure/azure-monitor/platform/diagnostic-settings?tabs=portal#time-before-telemetry-gets-to-destination).
+
+## Common issues and solutions
+
+- **Issue**: Logs aren't appearing in configured destinations.
+- **Solution**: See the following guidance for log analytics, event hubs, and storage accounts.
+
+### For log analytics
+
+1. Navigate to **Log Analytics workspaces**.
+1. Select the workspace and then run the following query:
+
+```powershell
+AzureActivity
+| summarize count() by bin(TimeGenerated,1d)
+```
+
+This should determine the number of logs per day that are being ingested into this workspace.
+
+### For event hubs
+
+1. Navigate to **Event Hubs**.
+1. Select the event hub and then select **Data Explorer**.
+1. Verify the logs are reaching the event hub. 
+
+If the logs aren't reaching the event hub, check for throttling using a metrics blade.
+
+### For storage accounts
+
+1. Navigate to **Storage center | Storage accounts (Blobs)**.
+1. Locate and select the **insights-activity-logs** container.
+
+The logs should be visible.
+
+## Frequently asked questions
+
+**Q1: Why don't the logs appear in the destination?**
+
+**A1:** Make sure that the network is well connected, and verify the permissions for Log Analytics workspace.
+
+**Q2: Why do errors appear in the PowerShell commands?**
+
+**A2:** Make sure that you're using the latest Azure PowerShell module.
+
+## References
+
+- [Azure Monitor documentation](/azure/azure-monitor/fundamentals/overview)
+- [Azure activity logs overview](/azure/azure-monitor/fundamentals/data-sources)
+- [Configure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings?tabs=portal)
+
+[!INCLUDE [azure-help-support](../../../../includes/azure-help-support.md)]

support/azure/azure-monitor/toc.yml

@@ -19,6 +19,9 @@ items:
         href: activity-logs/config-export/troubleshoot-permission-errors-in-activity-log-configuration.md
       - name: Troubleshoot the export of Activity Logs across Azure subscriptions
         href: activity-logs/config-export/troubleshoot-export-of-activity-logs-across-subscriptions.md
+      - name: Configuring Azure Activity Log Export
+        href: activity-logs/config-export/configuring-azure-activity-log-export-comprehensive-guide.md
+
 - name: Application Insights
   items:
   - name: OpenTelemetry troubleshooting