From 124ed93c365ed0c8f8d8a24e8ff2ee222f037e95 Mon Sep 17 00:00:00 2001 From: Pascal Winkler Date: Sat, 3 Jan 2026 01:31:10 +0100 Subject: [PATCH] Simplify enrich policy execution instructions Removed redundant explanation about executing enrich policies. --- manage-data/data-store/index-basics.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/manage-data/data-store/index-basics.md b/manage-data/data-store/index-basics.md index e97ff1e96e..0ae09e9f73 100644 --- a/manage-data/data-store/index-basics.md +++ b/manage-data/data-store/index-basics.md @@ -329,10 +329,6 @@ Use the **Enrich Policies** view to add data from your existing indices to incom You must execute a new enrich policy before you can use it with an enrich processor or {{esql}} query. When executed, an enrich policy uses enrich data from the policy's source indices to create a streamlined system index called the enrich index. The policy uses this index to match and enrich incoming documents. -When creating an enrich policy, the UI walks you through the configuration setup and selecting the fields. Before you can use the policy with an enrich processor or {{esql}} query, you must execute the policy. - -When executed, an enrich policy uses enrich data from the policy’s source indices to create a streamlined system index called the enrich index. The policy uses this index to match and enrich incoming documents. - Check out these examples: * [Example: Enrich your data based on geolocation](/manage-data/ingest/transform-enrich/example-enrich-data-based-on-geolocation.md)