Merge pull request #234806 from yossi-y/main

Added recommendation for explicit identifier

Author: prmerger-automator[bot]

articles/azure-monitor/logs/query-optimization.md

@@ -454,7 +454,8 @@ Cross-region and cross-cluster execution of queries requires the system to seria
 A query that spans more than five workspaces is considered a query that consumes excessive resources. Queries can't span more than 100 workspaces.
 
 > [!IMPORTANT]
-> In some multi-workspace scenarios, the CPU and data measurements won't be accurate and will represent the measurement of only a few of the workspaces.
+> - In some multi-workspace scenarios, the CPU and data measurements won't be accurate and will represent the measurement of only a few of the workspaces.
+> - Cross workspace queries having an explicit identifier: workspace ID, or workspace Resource Manager resource ID, consume less resources and are more performant. See [Create a log query across multiple workspaces](./cross-workspace-query.md#identify-workspace-resources)
 
 ## Parallelism
 Azure Monitor Logs uses large clusters of Azure Data Explorer to run queries. These clusters vary in scale and potentially get up to dozens of compute nodes. The system automatically scales the clusters according to workspace placement logic and capacity.