Skip to content

Commit f5e774b

Browse files
Update search-jobs to mention that Lighthouse is not supported
I've seen an uptick of support cases about this scenario, so it would be great if we could add this to the public docs. Here's an example that reached the PG: https://portal.microsofticm.com/imp/v3/incidents/details/508253154/home
1 parent c938879 commit f5e774b

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-monitor/logs/search-jobs.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ This video explains when and how to use search jobs:
2424
|:-------|:---------------------|
2525
| Run a search job | `Microsoft.OperationalInsights/workspaces/tables/write` and `Microsoft.OperationalInsights/workspaces/searchJobs/write` permissions to the Log Analytics workspace, for example, as provided by the [Log Analytics Contributor built-in role](../logs/manage-access.md#built-in-roles). |
2626

27+
> [!NOTE]
28+
> Cross-tenant search jobs are not currently supported, even when Entra ID tenants are managed through Azure Lighthouse.
29+
2730
## When to use search jobs
2831

2932
Use a search job when the log query timeout of 10 minutes isn't sufficient to search through large volumes of data or if you're running a slow query.

0 commit comments

Comments
 (0)