fixed links

Author: guywi-ms

.openpublishing.redirection.azure-monitor.json

@@ -6445,7 +6445,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/azure-monitor/logs/workspace-expression.md",
+            "source_path_from_root": "articles/azure-monitor/logs/resource-expression.md",
             "redirect_url": "/azure/azure-monitor/logs/cross-workspace-query",
             "redirect_document_id": false
         }

articles/azure-monitor/logs/cross-workspace-query.md

@@ -13,7 +13,7 @@ ms.date: 05/30/2023
 
 There are two ways to query data from multiple workspaces, applications, and resources:
 
-* Explicitly by specifying the workspace, app, or resource information using the [workspace()](#use-the-workspace-expression-to-query-across-log-analytics-workspaces), [app()](#use-the-app-expression-to-query-across-classic-application-insights-applications), or [resource()](#use-the-resource-expression-to-correlate-data-between-resources) expressions, as described in this article.
+* Explicitly by specifying the workspace, app, or resource information using the [workspace()](#query-across-log-analytics-workspaces-using-workspace), [app()](#query-across-classic-application-insights-applications-using-app), or [resource()](#correlate-data-between-resources-using-resource) expressions, as described in this article.
 * Implicitly by using [resource-context queries](manage-access.md#access-mode). When you query in the context of a specific resource, resource group, or a subscription, the query retrieves relevant data from all workspaces that contain data for these resources. Resource-context don't retrieve data from classic Application Insights resources.
 
 This article explains how to use the `workspace()`, `app()`, and `resource()` expressions to query data from multiple Log Analytics workspaces, applications, and resources. 

articles/azure-monitor/logs/log-query-overview.md

@@ -72,9 +72,10 @@ Although Azure Monitor uses the same KQL as Azure Data Explorer, there are some
 ### Other operators in Azure Monitor
 The following operators support specific Azure Monitor features and aren't available outside of Azure Monitor:
 
-* [app()](../logs/app-expression.md)
-* [resource()](./resource-expression.md)
-* [workspace()](../logs/workspace-expression.md)
+* [workspace()](../logs/cross-workspace-query.md#query-across-log-analytics-workspaces-using-workspace)
+* [app()](../logs/cross-workspace-query.md#query-across-classic-application-insights-applications-using-app)
+* [resource()](../logs/cross-workspace-query.md#correlate-data-between-resources-using-resource)
+
 
 ## Next steps
 - Walk through a [tutorial on writing queries](/azure/data-explorer/kusto/query/tutorial?pivots=azuremonitor).

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

@@ -455,7 +455,7 @@ A query that spans more than five workspaces is considered a query that consumes
 
 > [!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.
-> - Cross workspace queries having an explicit identifier: workspace ID, or workspace Azure Resource ID, consume less resources and are more performant. See [Gather identifiers for Log Analytics workspaces](./cross-workspace-query.md?tabs=workspace-identifier#gather-identifiers-for-log-analytics-workspaces-and-application-insights-resources)
+> - Cross workspace queries having an explicit identifier: workspace ID, or workspace Azure Resource ID, consume less resources and are more performant. 
 
 ## 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.

articles/sentinel/includes/sentinel-limits-multi-workspace.md

@@ -15,5 +15,5 @@ The following limit applies to multiple workspaces in Microsoft Sentinel. Limits
 |Description                   | Limit        |Dependency|
 -------------------------|--------------------|--------------------|
 | Incident view | 100 concurrently displayed workspaces | |
-| Log query | 100 Sentinel workspaces | [Log Analytics](../../azure-monitor/logs/cross-workspace-query.md#cross-resource-query-limits) |
+| Log query | 100 Sentinel workspaces | [Log Analytics](../../azure-monitor/logs/cross-workspace-query.md#limitations) |
 | Analytics rules | 20 Sentinel workspaces per query | |

includes/azure-monitor-limits-log-queries.md

@@ -16,7 +16,7 @@ ms.custom: "include file"
 |:---|:---|
 | Query language | Azure Monitor uses the same [Kusto Query Language (KQL)](/azure/kusto/query/) as Azure Data Explorer. See [Azure Monitor log query language differences](/azure/data-explorer/kusto/query/) for KQL language elements not supported in Azure Monitor. |
 | Azure regions | Log queries can experience excessive overhead when data spans Log Analytics workspaces in multiple Azure regions. See [Query limits](../articles/azure-monitor/logs/scope.md#query-scope-limits) for details. |
-| Cross resource queries | Maximum number of Application Insights resources and Log Analytics workspaces in a single query limited to 100.<br>Cross-resource query isn't supported in View Designer.<br>Cross-resource query in log alerts is supported in the new scheduledQueryRules API.<br>See [Cross-resource query limits](../articles/azure-monitor/logs/cross-workspace-query.md#cross-resource-query-limits) for details. |
+| Cross resource queries | Maximum number of Application Insights resources and Log Analytics workspaces in a single query limited to 100.<br>Cross-resource query isn't supported in View Designer.<br>Cross-resource query in log alerts is supported in the new scheduledQueryRules API.<br>See [Cross-resource query limits](../articles/azure-monitor/logs/cross-workspace-query.md#limitations) for details. |
 | Log Analytics dashboard queries | Maximum number of records returned in a single Log Analytics dashboard query is 2,000. |
 
 ### User query throttling