Merge pull request #293955 from austinmccollum/patch-1

clarify use of explicit identifiers

Author: prmerger-automator[bot]

articles/sentinel/extend-sentinel-across-workspaces-tenants.md

@@ -25,9 +25,7 @@ Microsoft Sentinel supports a [multiple workspace incident view](./multiple-work
 
 Query [multiple workspaces](/azure/azure-monitor/logs/cross-workspace-query) to search and correlate data from multiple workspaces in a single query.
 
-- Use the [`workspace( )` expression](/azure/azure-monitor/logs/cross-workspace-query#query-across-log-analytics-workspaces-using-workspace), with the workspace identifier as the argument, to refer to a table in a different workspace.
-
-   - See [important information](/azure/azure-monitor/logs/cross-workspace-query#arguments) about the use of identifier formats to ensure proper performance.
+- Use the [`workspace( )` expression](/azure/azure-monitor/logs/cross-workspace-query#query-across-log-analytics-workspaces-using-workspace), with the workspace identifier as the argument, to refer to a table in a different workspace. Use explicit identifier formats to ensure best performance. For more information, see [Identifier formats for cross workspace queries](/azure/azure-monitor/logs/cross-workspace-query#arguments).
 
 - Use the [union operator](/kusto/query/union-operator?view=microsoft-sentinel&preserve-view=true) alongside the `workspace( )` expression to apply a query across tables in multiple workspaces.