diff --git a/docs/reference/query-languages/esql/esql-cross-clusters.md b/docs/reference/query-languages/esql/esql-cross-clusters.md
index 9c67a2e8e47eb..9a01315465013 100644
--- a/docs/reference/query-languages/esql/esql-cross-clusters.md
+++ b/docs/reference/query-languages/esql/esql-cross-clusters.md
@@ -413,6 +413,13 @@ FROM my-index-000001,cluster_one:my-index-000001,cluster_two:my-index-000001
 ```
 
 
+## LOOKUP JOIN across clusters [ccq-lookup-join]
+
+{{esql}} [`LOOKUP JOIN`](/reference/query-languages/esql/esql-lookup-join.md#cross-cluster-support) is supported in cross-cluster queries. By default, {{esql}} resolves the lookup index on every cluster in the query and each cluster joins against its own local index with that name. In this case, the lookup index must exist on every cluster being queried. This follows the same pattern as [remote mode Enrich](#esql-enrich-remote).
+
+{applies_to}`stack: ga 9.6+` If the lookup index is missing from one or more remote clusters, use [coordinator mode](/reference/query-languages/esql/esql-lookup-join.md#coordinator-mode) to join against a local cluster lookup index copy.
+
+
 ## Excluding clusters or indices from {{esql}} query [ccq-exclude]
 
 Use exclusions in the `FROM` command to omit an entire remote cluster or specific indices from a query.