Merge pull request #9414 from MicrosoftDocs/main

New MTRA known issue

Author: Cloud-Writer

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

@@ -35,6 +35,7 @@ ms.date: 07/22/2025
 | --- | --- | --- |
 |Unable to pair Yealink MeetingBar A40 device with CTP25 touch panel.|You might experience intermittent or failed pairing attempts between a Yealink MeetingBar A40 device and a CTP25 touch panel that are running the following firmware versions:<br/><br/>A40 device: 289.320.0.60<br/>CTP25 touch panel: 311.320.0.55<br/><br/>In some instances, the device might revert to an unpaired state shortly after initialization, or the touch panel might remain stuck on the pairing screen without displaying a code.|No workaround is available at this time.|
 |Logitech Rally Bar device is failing during remote login authentication.|You're able to sign in to a LogiTech VR1009 Rally Bar device locally but it signs out if an attempt is made to log in remotely. In this situation you might see Entra ID error codes 530003, 530002, and others.|No workaround is available at this time.|
+|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 re-trying 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 Rooms 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.|
 
 ## Issues affecting multiple devices
 

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md

@@ -0,0 +1,32 @@
+---
+title: Troubleshoot Deleting Migrated Custom Tables in Log Analytics
+description: Troubleshooting guide to deleting migrated custom tables in Log Analytics.
+ms.date: 07/24/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: Configure and manage Log Analytics tables
+---
+
+# Troubleshoot deleting migrated custom tables in Log Analytics
+
+Users might experience issues when they try to delete custom log tables in Log Analytics if the tables were migrated. This guide provides a solution to effectively resolve these issues.
+
+## Common issues and solutions
+
+- **API Access Issues**: Make sure that you have the necessary permissions to use the API.
+- **Table Not Found**: Verify the correct table name and workspace details.
+
+### Solution: Use Azure Log Analytics API
+
+To delete a migrated custom table, follow these steps by using the Azure Log Analytics API:
+
+1. Navigate to the [Azure portal](https://portal.azure.com), and log in to your Azure account.
+2. Access the **Log Analytics workspaces** section, and select the workspace that contains the table that you want to delete.
+3. Use the **Tables - Delete** API to remove the table. For detailed instructions, refer to the ["References" section](#references).
+4. After you run the API call, check the workspace to verify that the table is successfully deleted.
+
+## References
+
+- [Azure Log Analytics API documentation](/rest/api/loganalytics/)
+
+If the issue persists after you follow these steps, open a support case for further assistance.

support/azure/azure-monitor/toc.yml

@@ -123,6 +123,8 @@ items:
       href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
     - name: Troubleshoot performance logs not populating in Azure Government
       href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
+    - name: Troubleshoot deleting migrated custom tables in Log Analytics
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md
   - name: Log Analytics workspaces
     items:
     - name: Error code 0x80090016 - keyset doesn't exist

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues with monitoring sync health and resolvin
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 06/19/2025
+ms.date: 07/24/2025
 ms.author: kendownie
 ms.custom: sap:File Sync, devx-track-azurepowershell
 ms.reviewer: v-weizhu, vritikanaik
@@ -180,6 +180,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0x80c80018 | -2134376424 | ECS_E_SYNC_FILE_IN_USE | The file can't be synced because it's in use. The file will be synced when it's no longer in use. | No action required. Azure File Sync creates a temporary VSS snapshot once a day on the server to sync files that have open handles. |
 | 0x80c86013 | -2134351853 | ECS_E_SYNC_CLOUD_FILE_IN_USE | The cloud file can't be synced because it's in use. This error occurs when an application holds an open handle to a file in the cloud, preventing sync operations from being performed until the application releases the handle. | Check the open file handles and close them if they're no longer needed. For more information, see [List Handles](/rest/api/storageservices/list-handles) and [Force Close Handles](/rest/api/storageservices/force-close-handles). |
 | 0x80c8031d | -2134375651 | ECS_E_CONCURRENCY_CHECK_FAILED | The file has changed, but the change hasn't yet been detected by sync. Sync will recover after this change is detected. | No action required. |
+| 0x80F2019F | -2160590943 | ECS_E_AZURE_FILE_PATH_TOO_LONG | File path is longer than Azure Files supported path length. | Run the FileSyncErrorsReport.ps1 PowerShell script (located in the agent installation directory of the Azure File Sync agent) to identify failing file paths, then use the [ScanUnsupportedChars](https://github.com/Azure-Samples/azure-files-samples/tree/master/ScanUnsupportedChars) script. |
 | 0x80070002 | -2147024894 | ERROR_FILE_NOT_FOUND | The file was deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
 | 0x80070003 | -2147024893 | ERROR_PATH_NOT_FOUND | Deletion of a file or directory can't be synced because the item was already deleted in the destination and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection runs on the destination and sync detects the item was deleted. |
 | 0x80c80205 | -2134375931 | ECS_E_SYNC_ITEM_SKIP | The file or directory was skipped but will be synced during the next sync session. If this error is reported when downloading the item, the file or directory name is more than likely invalid. | No action required if this error is reported when uploading the file. If the error is reported when downloading the file, rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |