diff --git a/manage-data/_snippets/create-lifecycle-policy.md b/manage-data/_snippets/create-lifecycle-policy.md
index 51e07892dc..317279d533 100644
--- a/manage-data/_snippets/create-lifecycle-policy.md
+++ b/manage-data/_snippets/create-lifecycle-policy.md
@@ -10,13 +10,17 @@ The `min_age` value is relative to the rollover time, not the index creation tim
 ::::
 
 
-You can create the policy in {{kib}} or with the [create or update policy](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle) API. 
+You can create the policy in {{kib}} or with the [create or update policy](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle) API.
 
 ::::{tab-set}
 :group: kibana-api
 :::{tab-item} {{kib}}
 :sync: kibana
-To create the policy from {{kib}}, open the menu and go to **Stack Management > Index Lifecycle Policies**. Click **Create policy**.
+
+To create the policy from {{kib}}:
+
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click **Create policy**.
 
 By default, only the hot index lifecycle phase is enabled. Enable each additional lifecycle phase that you'd like.
 
diff --git a/manage-data/data-store/data-streams/set-up-data-stream.md b/manage-data/data-store/data-streams/set-up-data-stream.md
index c17bc3b1cb..beda1314a8 100644
--- a/manage-data/data-store/data-streams/set-up-data-stream.md
+++ b/manage-data/data-store/data-streams/set-up-data-stream.md
@@ -33,7 +33,10 @@ For {{fleet}} and {{agent}}, refer to [](/reference/fleet/data-streams.md). For
 
 While optional, we recommend using {{ilm-init}} to automate the management of your data stream’s backing indices. {{ilm-init}} requires an index lifecycle policy.
 
-To create an index lifecycle policy in {{kib}}, open the main menu and go to **Stack Management > Index Lifecycle Policies**. Click **Create policy**.
+To create an index lifecycle policy in {{kib}}:
+
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click **Create policy**.
 
 You can also use the [create lifecycle policy API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle).
 
@@ -104,8 +107,10 @@ If you’re unsure how to map your fields, use [runtime fields](../mapping/defin
 
 ::::
 
+To create a component template in {{kib}}:
 
-To create a component template in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Index Templates** view, click **Create component template**.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create component template**.
 
 You can also use the [create component template API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-component-template).
 
@@ -157,7 +162,10 @@ Use your component templates to create an index template. Specify:
 * Any component templates that contain your mappings and index settings.
 * A priority higher than `200` to avoid collisions with built-in templates. See [Avoid index pattern collisions](../templates.md#avoid-index-pattern-collisions).
 
-To create an index template in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Index Templates** view, click **Create template**.
+To create an index template in {{kib}}:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create template**.
 
 You can also use the [create index template API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-index-template). Include the `data_stream` object to enable data streams.
 
@@ -202,7 +210,7 @@ You can also manually create the stream using the [create data stream API](https
 PUT _data_stream/my-data-stream
 ```
 
-After it's been created, you can view and manage this and other data streams from the **Stack Management > Index Management** view. Refer to [Manage a data stream](./manage-data-stream.md) for details.
+After it's been created, you can view and manage this and other data streams from the **Index Management** view. Refer to [Manage a data stream](./manage-data-stream.md) for details.
 
 ## Secure the data stream [secure-data-stream]
 
@@ -224,7 +232,10 @@ POST _data_stream/_migrate/my-time-series-data
 
 ## Get information about a data stream [get-info-about-data-stream]
 
-To get information about a data stream in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Data Streams** view, click the data stream’s name.
+To get information about a data stream in {{kib}}:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Data Streams** tab, click the data stream’s name.
 
 You can also use the [get data stream API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-data-stream).
 
@@ -235,7 +246,10 @@ GET _data_stream/my-data-stream
 
 ## Delete a data stream [delete-data-stream]
 
-To delete a data stream and its backing indices in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Data Streams** view, click the trash icon. The icon only displays if you have the `delete_index` [security privilege](elasticsearch://reference/elasticsearch/security-privileges.md) for the data stream.
+To delete a data stream and its backing indices in {{kib}}:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Data Streams** view, click the trash icon. The icon only displays if you have the `delete_index` [security privilege](elasticsearch://reference/elasticsearch/security-privileges.md) for the data stream.
 
 You can also use the [delete data stream API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-delete-data-stream).
 
diff --git a/manage-data/images/elasticsearch-reference-management-enrich-policies.png b/manage-data/images/elasticsearch-reference-management-enrich-policies.png
index 75911842ae..b01a48a7ce 100644
Binary files a/manage-data/images/elasticsearch-reference-management-enrich-policies.png and b/manage-data/images/elasticsearch-reference-management-enrich-policies.png differ
diff --git a/manage-data/ingest/transform-enrich/example-parse-logs.md b/manage-data/ingest/transform-enrich/example-parse-logs.md
index 4ba3831227..ed9903a256 100644
--- a/manage-data/ingest/transform-enrich/example-parse-logs.md
+++ b/manage-data/ingest/transform-enrich/example-parse-logs.md
@@ -24,7 +24,7 @@ The logs you want to parse look similar to this:
 
 These logs contain a timestamp, IP address, and user agent. You want to give these three items their own field in {{es}} for faster searches and visualizations. You also want to know where the request is coming from.
 
-1. In {{kib}}, open the main menu and click **Stack Management** > **Ingest Pipelines**.
+1. In {{kib}}, go to the **Ingest Pipelines** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
     :::{image} /manage-data/images/elasticsearch-reference-ingest-pipeline-list.png
     :alt: Kibana's Ingest Pipelines list view
diff --git a/manage-data/ingest/transform-enrich/ingest-pipelines.md b/manage-data/ingest/transform-enrich/ingest-pipelines.md
index 2c9e71af14..e5883c7413 100644
--- a/manage-data/ingest/transform-enrich/ingest-pipelines.md
+++ b/manage-data/ingest/transform-enrich/ingest-pipelines.md
@@ -29,7 +29,9 @@ You can create and manage ingest pipelines using {{kib}}'s **Ingest Pipelines**
 
 ## Create and manage pipelines [create-manage-ingest-pipelines]
 
-In {{kib}}, open the main menu and click **Stack Management > Ingest Pipelines**. From the list view, you can:
+In {{kib}}, go to the **Ingest Pipelines** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+From the list view, you can:
 
 * View a list of your pipelines and drill down into details
 * Edit or clone existing pipelines
@@ -457,7 +459,7 @@ PUT _ingest/pipeline/my-pipeline
 }
 ```
 1. All processors in this pipeline will use the `classic` access pattern.
-2. The logic for resolving field paths used by processors to read and write values to ingest documents is based on the access pattern. 
+2. The logic for resolving field paths used by processors to read and write values to ingest documents is based on the access pattern.
 
 ### Classic field access pattern [access-source-pattern-classic]
 
@@ -503,7 +505,7 @@ POST /_ingest/pipeline/_simulate
 1. Explicitly declaring to use the `classic` access pattern in the pipeline. This is the default value.
 2. We are reading a value from the field `foo.bar`.
 3. We are writing its value to the field `a.b.c.d`.
-4. This document uses nested json objects in its structure. 
+4. This document uses nested json objects in its structure.
 5. This document uses dotted field names in its structure.
 
 ```console-result
@@ -514,7 +516,7 @@ POST /_ingest/pipeline/_simulate
             "_id": "id",
             "_index": "index",
             "_version": "-3",
-            "_source": { 
+            "_source": {
               "foo": {
                 "bar": "baz" <1>
               },
@@ -551,14 +553,14 @@ POST /_ingest/pipeline/_simulate
 2. The value from the `foo.bar` field is written to a nested json structure at field `a.b.c.d`. The processor creates objects for each field in the path.
 3. The second document uses a dotted field name for `foo.bar`. The `classic` access pattern does not recognize dotted field names, and so nothing is copied.
 
-If the documents you are ingesting contain dotted field names, to read them with the `classic` access pattern, you must use the [`dot_expander`](elasticsearch://reference/enrich-processor/dot-expand-processor.md) processor. This approach is not always reasonable though. Consider the following document: 
+If the documents you are ingesting contain dotted field names, to read them with the `classic` access pattern, you must use the [`dot_expander`](elasticsearch://reference/enrich-processor/dot-expand-processor.md) processor. This approach is not always reasonable though. Consider the following document:
 
 ```json
 {
   "event": {
     "tags": {
       "http.host": "localhost:9200",
-      "http.host.name": "localhost", 
+      "http.host.name": "localhost",
       "http.host.port": 9200
     }
   }
@@ -623,7 +625,7 @@ POST /_ingest/pipeline/_simulate
             "_id": "id",
             "_index": "index",
             "_version": "-3",
-            "_source": { 
+            "_source": {
               "foo": {
                 "bar": "baz" <1>
               },
diff --git a/manage-data/ingest/transform-enrich/logstash-pipelines.md b/manage-data/ingest/transform-enrich/logstash-pipelines.md
index 8237ec89be..9da26526c0 100644
--- a/manage-data/ingest/transform-enrich/logstash-pipelines.md
+++ b/manage-data/ingest/transform-enrich/logstash-pipelines.md
@@ -12,7 +12,7 @@ products:
 
 This content applies to: [![Elasticsearch](/manage-data/images/serverless-es-badge.svg "")](../../../solutions/search.md) [![Observability](/manage-data/images/serverless-obs-badge.svg "")](../../../solutions/observability.md) [![Security](/manage-data/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md)
 
-In **{{project-settings}} → {{manage-app}} → {{ls-pipelines-app}}**, you can control multiple {{ls}} instances and pipeline configurations.
+On the **{{ls-pipelines-app}}** management page, you can control multiple {{ls}} instances and pipeline configurations.
 
 :::{image} /manage-data/images/serverless-logstash-pipelines-management.png
 :alt: {{ls-pipelines-app}}"
@@ -31,7 +31,9 @@ After you configure {{ls}} to use centralized pipeline management, you can no lo
 ## Manage pipelines [logstash-pipelines-manage-pipelines]
 
 1. [Configure centralized pipeline management](logstash://reference/configuring-centralized-pipelines.md).
-2. To add a new pipeline, go to **{{project-settings}} → {{manage-app}} → {{ls-pipelines-app}}** and click **Create pipeline**. Provide the following details, then click **Create and deploy**.
+1. To add a new pipeline, go to the **{{ls-pipelines-app}}** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click **Create pipeline**.
+1. Provide the following details, then click **Create and deploy**.
 
     Pipeline ID
     :   A name that uniquely identifies the pipeline. This is the ID that you used when you configured centralized pipeline management and specified a list of pipeline IDs in the `xpack.management.pipeline.id` setting.
diff --git a/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md b/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md
index 89e0bcabeb..48cda42fc9 100644
--- a/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md
+++ b/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md
@@ -17,7 +17,7 @@ Follow these steps to configure or remove data stream lifecycle settings for an
 
 Note that these steps are for data stream lifecycle only. For the steps to configure {{ilm}}, refer to the [{{ilm-init}} documentation](/manage-data/lifecycle/index-lifecycle-management.md). For a comparison between the two, refer to [](/manage-data/lifecycle.md).
 
-## Set a data stream’s lifecycle [set-lifecycle] 
+## Set a data stream’s lifecycle [set-lifecycle]
 
 To add or to change the retention period of your data stream you can use the **Index Management** tools in {{kib}} or the {{es}} [lifecycle API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-data-lifecycle).
 
@@ -29,7 +29,8 @@ To add or to change the retention period of your data stream you can use the **I
 
 To change the data retention settings for a data stream:
 
-1. Go to **Stack Management > Index Management** and open the **Data Streams** tab.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Data Streams** tab.
 1. Use the search tool to find the data stream you're looking for.
 1. Select the data stream to view its details.
 1. In the data stream details pane, select **Manage > Edit data retention** to adjust the settings. You can do any of the following:
@@ -70,7 +71,7 @@ To change the data retention settings for a data stream:
 :::
 :::::
 
-The changes in the lifecycle are applied on all backing indices of the data stream. 
+The changes in the lifecycle are applied on all backing indices of the data stream.
 
 You can see the effect of the change in {{kib}} or using the {{es}} [explain API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-explain-data-lifecycle):
 
@@ -80,7 +81,8 @@ You can see the effect of the change in {{kib}} or using the {{es}} [explain API
 :sync: kibana
 To check the data retention settings for a data stream:
 
-1. Go to **Stack Management > Index Management** and open the **Data Streams** tab.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Data Streams** tab.
 1. Use the search tool to find the data stream you're looking for.
 1. Select the data stream to view its details. The flyout shows the data retention settings for the data stream. Note that if the data stream is currently managed by an [{{ilm-init}} policy](/manage-data/lifecycle/index-lifecycle-management.md), the **Effective data retention** may differ from the retention value that you've set in the data stream, as indicated by the **Data retention**.
 
@@ -144,9 +146,9 @@ The response will look like:
 :::
 :::::
 
-## Remove the lifecycle for a data stream [delete-lifecycle] 
+## Remove the lifecycle for a data stream [delete-lifecycle]
 
-To remove the lifecycle of a data stream you can use the **Index Management** tools in {{kib}} or the {{es}} [delete lifecycle API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-delete-data-lifecycle). 
+To remove the lifecycle of a data stream you can use the **Index Management** tools in {{kib}} or the {{es}} [delete lifecycle API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-delete-data-lifecycle).
 
 
 :::::{tab-set}
@@ -156,7 +158,8 @@ To remove the lifecycle of a data stream you can use the **Index Management** to
 
 To remove a data stream's lifecycle:
 
-1. Go to **Stack Management > Index Management** and open the **Data Streams** tab.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Data Streams** tab.
 1. Use the search tool to find the data stream you're looking for.
 1. Select the data stream to view its details.
 1. In the data stream details pane, select **Manage > Edit data retention**.
diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md
index 1ca58e33e7..4aeb86e70f 100644
--- a/manage-data/lifecycle/data-tiers.md
+++ b/manage-data/lifecycle/data-tiers.md
@@ -428,7 +428,7 @@ When data reaches the `cold` or `frozen` phases, it is automatically converted t
 
 9. Delete the searchable snapshots by following these steps:
 
-    1. Open Kibana and navigate to Management > Data > Snapshot and Restore > Snapshots (or go to `<kibana-endpoint>/app/management/data/snapshot_restore/snapshots`)
+    1. Open Kibana, go to the **Snapshot and Restore** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and go to the **Snapshots** tab. (Alternatively, go to `<kibana-endpoint>/app/management/data/snapshot_restore/snapshots`.)
     2. Search for `*<ilm-policy-name>*`
     3. Bulk select the snapshots and delete them
 
@@ -494,7 +494,7 @@ This setting will not unallocate a currently allocated shard, but might prevent
 
 ### Automatic data tier migration [data-tier-migration]
 
-{{ilm-init}} automatically transitions managed indices through the available data tiers using the [migrate](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md) action. By default, this action is automatically injected in every phase. 
+{{ilm-init}} automatically transitions managed indices through the available data tiers using the [migrate](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md) action. By default, this action is automatically injected in every phase.
 
 ### Disable data tier allocation [data-tier-allocation]
 You can explicitly disable data allocation for  data tier migration in an ILM policy with the following setting:
@@ -520,7 +520,7 @@ For example:
       },
 ```
 
-Defining the `migrate` action with `"enabled": false` for a data tier [disables automatic {{ilm-init}} shard migration](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md#ilm-disable-migrate-ex). This is useful if, for example, you’re using the [allocate action](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-allocate.md) to manually specify allocation rules.          
+Defining the `migrate` action with `"enabled": false` for a data tier [disables automatic {{ilm-init}} shard migration](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-migrate.md#ilm-disable-migrate-ex). This is useful if, for example, you’re using the [allocate action](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-allocate.md) to manually specify allocation rules.
 
-#### Important Note: 
+#### Important Note:
 Do not disable automatic {{ilm-init}} migration without manually defining {{ilm-init}} allocation rules. If data migration is disabled without allocation rules defined, this can prevent data from moving to the specified data tier, even though the data has successfully moved through the {{ilm-init}} policy with a status of `complete`.
diff --git a/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md b/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md
index e2bb845e20..b692490118 100644
--- a/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md
+++ b/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md
@@ -49,7 +49,8 @@ A lifecycle policy defines a set of index lifecycle phases and the actions to pe
 :sync: kibana
 To add an ILM policy to an {{es}} cluster:
 
-1. Go to **Stack Management > Index Lifecycle Policies**, and select **Create policy**.
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Select **Create policy**.
 
     ![Create policy page](/manage-data/images/elasticsearch-reference-create-policy.png "")
 
@@ -58,7 +59,7 @@ To add an ILM policy to an {{es}} cluster:
 1. In the **Hot phase**, by default an ILM-managed index [rolls over](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-rollover.md) when either:
     * It reaches 30 days of age.
     * One or more primary shards reach 50 GB in size.
-  
+
     Disable **Use recommended defaults** to adjust these values or to roll over based on the size of the primary shard, the number of documents in the primary shard, or the total number of documents in the index.
 
     ::::{important}
@@ -117,7 +118,7 @@ The rollover action implicitly rolls over a data stream or alias if one or more
 To use a lifecycle policy that triggers a rollover action, you need to configure the policy in the index template used to create each new index. You specify the name of the policy and the alias used to reference the rolling indices.
 
 :::{tip}
-If you already have an index template to which you'd like to add an {{ilm-init}} policy, you can do this from **Stack Management > Index Lifecycle Policies**. Search for and select the policy you want, and from the **Actions** menu, select **Add to index template**.
+If you already have an index template to which you'd like to add an {{ilm-init}} policy, you can do this from the **Index Lifecycle Policies** management page. Search for and select the policy you want, and from the **Actions** menu, select **Add to index template**.
 :::
 
 ::::{tab-set}
@@ -126,11 +127,12 @@ If you already have an index template to which you'd like to add an {{ilm-init}}
 :sync: kibana
 To add an index template to a cluster and apply the lifecycle policy to indices matching the template:
 
-1. Go to **Stack Management > Index Management**. In the **Index Templates** tab, select **Create template**.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, select **Create template**.
 
     ![Create template page](/manage-data/images/elasticsearch-reference-create-template-wizard-my_template.png "")
 
-1. On the **Logistics** page: 
+1. On the **Logistics** page:
     1. Specify a name for the template.
     1. Specify a pattern to match the indices you want to manage with the lifecycle policy. For example, `my-index-*`.
     1. If you're storing continuously generated, append-only data, you can opt to create [data streams](/manage-data/data-store/data-streams.md) instead of indices for more efficient storage.
@@ -144,7 +146,7 @@ To add an index template to a cluster and apply the lifecycle policy to indices
         * The [index mode](elasticsearch://reference/elasticsearch/index-settings/time-series.md) to use for the created indices.
         * The template priority, version, and any metadata.
         * Whether or not to overwrite the `action.auto_create_index` cluster setting.
-        
+
         Refer to the [Create or update index template API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-index-template) documentation for details about these options.
 
 1. On the **Component templates** page, use the search and filter tools to select any [component templates](/manage-data/data-store/templates.md#component-templates) to include in the index template. The index template will inherit the settings, mappings, and aliases defined in the component templates and apply them to indices when they're created.
@@ -225,7 +227,8 @@ When you enable {{ilm}} for {{beats}}, {{agent}}, or for the {{agent}} or {{ls}}
 :sync: kibana
 To create the initial managed index:
 
-1. Go to **Stack Management > Index Management**. In the **Indices** tab, select **Create index**.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Indices** tab, select **Create index**.
 1. Specify a name for the index that matches the index template pattern and that ends with a number. For example, `test-000001`.
 1. Leave the **Index mode** set to the default **Standard**.
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data.md b/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data.md
index 04f4ec6a20..906710b674 100644
--- a/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data.md
+++ b/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data.md
@@ -49,14 +49,15 @@ To find the data streams associated with an installed integration:
 ::::{dropdown} Find the data streams managed in {{fleet}}
 To find all of the data streams that are managed in {{fleet}}:
 
-1. In {{kib}} go to **Management > {{fleet}}** and select the **Data streams** tab.
+1. In {{kib}}, go to the **{{fleet}}** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Select the **Data streams** tab.
 
 1. Use the search field and dropdown menus to filter the list. You can filter by the data stream type, dataset, namespace, or by the integration that the data stream belongs to.
 
     ![Integration assets](/manage-data/images/ilm-fleet-data-streams.png "")
 ::::
 
-For any data stream that you're interested in, you can [view its current lifecycle status](/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md), including details about its associated ILM policy. 
+For any data stream that you're interested in, you can [view its current lifecycle status](/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md), including details about its associated ILM policy.
 
 After you've identified one or more data streams for which you'd like to customize how the data is managed over time, refer to our tutorials:
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/policy-apply.md b/manage-data/lifecycle/index-lifecycle-management/policy-apply.md
index d08089caa6..d50d10a1f9 100644
--- a/manage-data/lifecycle/index-lifecycle-management/policy-apply.md
+++ b/manage-data/lifecycle/index-lifecycle-management/policy-apply.md
@@ -31,7 +31,8 @@ You can do this procedure in {{kib}} or using the {{es}} API.
 
 To apply a lifecycle policy to an existing index:
 
-1. Go to **Stack Management > Index Management**. In the **Indices** tab, search for and select an index. Enable **Include hidden indices** to see the full list of indices.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Indices** tab, search for and select an index. Enable **Include hidden indices** to see the full list of indices.
 
 1. From the **Manage index** dropdown menu select **Add lifecycle policy**.
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/policy-updates.md b/manage-data/lifecycle/index-lifecycle-management/policy-updates.md
index 844277ec06..81eeac2f7a 100644
--- a/manage-data/lifecycle/index-lifecycle-management/policy-updates.md
+++ b/manage-data/lifecycle/index-lifecycle-management/policy-updates.md
@@ -45,7 +45,8 @@ Avoid changing any managed policies that are shipped with {{es}}, such as `logs@
 :sync: kibana
 To update a lifecycle policy:
 
-1. Go to **Stack Management > Index Lifecycle Policies** and use the search tool to find the lifecycle policy that you want to update.
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Use the search tool to find the lifecycle policy that you want to update.
 
    You can deselect the **Include managed system policies** option to filter out managed policies from the list, since it's strongly recommended not to update these.
 
@@ -112,8 +113,9 @@ For example, in certain cases the [`forcemerge`](elasticsearch://reference/elast
 :sync: kibana
 To switch an index’s lifecycle policy:
 
-1. Go to **Stack Management > Index Management**. In the **Indices** tab, search for and select the index that you that you want to switch to a new policy. You can use the **Lifecycle status** filter to narrow the list.
-    
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Indices** tab, search for and select the index that you that you want to switch to a new policy. You can use the **Lifecycle status** filter to narrow the list.
+
 1. From the **Manage index** dropdown menu, select **Remove lifecycle policy**. Confirm your choice before the ILM policy is removed.
 
 1. From the **Manage index** dropdown menu, select **Add lifecycle policy**, and then select a new policy to apply.
diff --git a/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md b/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md
index 132efe3ad0..d74c49e20e 100644
--- a/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md
+++ b/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md
@@ -24,7 +24,8 @@ If you're investigating an {{ilm-init}}-related problem, refer to [Troubleshoot
 :sync: kibana
 **To view the current lifecycle status for one or more indices:**
 
-1. Go to **Stack Management > Index Management** and open the **Indices** tab.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Indices** tab.
 1. Enable **Include hidden indices** to view all indices, including those managed by ILM. Note that if you're using data streams, you can find the data stream associated with any index listed in the **Data stream** column.
 1. Use the search tool to find the index you're looking for. You can also filter the results by lifecycle status and lifecycle phase.
 1. Select the index to view details.
@@ -40,7 +41,8 @@ To learn how to create a specialized ILM policy for any data stream, such as tho
 
 **To view the current lifecycle status for a datastream:**
 
-1. Go to **Stack Management > Index Management** and open the **Data Streams** tab.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Data Streams** tab.
 1. Use the search tool to find the data stream you're looking for.
 1. Select the data stream to view details. The flyout that opens includes direct links to the ILM policy and the index template.
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
index b2bfd8d5fd..992cb591b0 100644
--- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
+++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
@@ -20,7 +20,7 @@ When you [configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-m
 
 To update the automatic rollover setting in an {{ilm-init}} policy:
 
-1. Go to **Stack Management > Index Lifecycle Policies**.
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
 1. Select a policy to update, and from the **Actions** menu select **Edit**.
 
@@ -39,7 +39,7 @@ You can update this setting manually to skip rollover if, for instance, you need
 
 If an index’s lifecycle policy is removed, this setting is also removed.
 
-::::{important} 
+::::{important}
 When `index.lifecycle.indexing_complete` is set to `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md).
 ::::
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
index 1c0cbe95c1..0e8cb5b0b9 100644
--- a/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
+++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
@@ -84,7 +84,7 @@ You should never edit managed policies directly. Changes to managed policies mig
 
 To save the `logs@lifecycle` policy as a new policy in {{kib}}:
 
-1. Open the menu and go to **Stack Management** > **Index Lifecycle Policies**.
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. Toggle **Include managed system policies**.
 3. Select the `logs@lifecycle` policy.
 4. On the **Edit policy logs** page, toggle **Save as new policy**, and then provide a new name for the policy, for example, `logs-custom`.
diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-general-content-with-data-streams.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-general-content-with-data-streams.md
index a9fedc6f25..91c5714cb8 100644
--- a/manage-data/lifecycle/index-lifecycle-management/tutorial-general-content-with-data-streams.md
+++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-general-content-with-data-streams.md
@@ -39,7 +39,10 @@ You can create an ingest pipeline that uses the [`set` enrich processor](elastic
 :group: kibana-api
 :::{tab-item} {{kib}}
 :sync: kibana
-To add an ingest pipeline in {{kib}}, go to **Stack Management > Ingest Pipelines**, and then select **Create pipeline > New pipeline**.
+To add an ingest pipeline in {{kib}}:
+
+1. Go to the **Ingest Pipelines** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Select **Create pipeline > New pipeline**.
 
 Configure the pipeline with a name, description, and a **Set** processor that adds the `@timestamp` field with a value of `{{_ingest.timestamp}}`.
 
@@ -76,18 +79,21 @@ A lifecycle policy specifies the phases in the index lifecycle and the actions t
 
 For example, you might define a policy named `indextods` that is configured to roll over when the shard size reaches 10 GB.
 
-You can create the policy in {{kib}} or with the [create or update policy](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle) API. 
+You can create the policy in {{kib}} or with the [create or update policy](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle) API.
 
 ::::{tab-set}
 :group: kibana-api
 :::{tab-item} {{kib}}
 :sync: kibana
-To create the policy in {{kib}}, open the menu and go to **Stack Management > Index Lifecycle Policies**. Click **Create policy**.
+To create the policy in {{kib}}:
+
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click **Create policy**.
 
 In the **Hot phase**, by default, an ILM-managed index [rolls over](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-rollover.md) when either:
 * It reaches 30 days of age.
 * One or more primary shards reach 50 GB in size.
-  
+
 Disable **Use recommended defaults** to adjust these values and roll over when the primary shard reaches 10GB.
 
 :::{image} /manage-data/images/elasticsearch-reference-tutorial-ilm-rollover-general-content-create-policy.png
@@ -132,7 +138,7 @@ When creating the index template, specify the following details:
 * the name of the lifecycle policy, which in our example is `indextods`
 * the ingest pipeline that enriches the data by adding the `@timestamp` field, which in our example is `ingest_time_1`
 * that the template is data stream enabled by including the `data_stream` definition
-* the index pattern, which ensures that this template will be applied to matching indices and in our example is `movetods` 
+* the index pattern, which ensures that this template will be applied to matching indices and in our example is `movetods`
 
 You can create the template in {{kib}} or with the [create or update index template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-index-template) API.
 
@@ -142,11 +148,12 @@ You can create the template in {{kib}} or with the [create or update index templ
 :sync: kibana
 To create an index template in Kibana, complete these steps:
 
-1. Go to **Stack Management > Index Management**. In the **Index Templates** tab, select **Create template**.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, select **Create template**.
 
     ![Create template page](/manage-data/images/elasticsearch-reference-tutorial-ilm-rollover-general-content-create-template.png "")
 
-1. On the **Logistics** page: 
+1. On the **Logistics** page:
     1. Specify the name of the template. For example `index_to_dot`.
     1. Specify a pattern to match the indices you want to manage with the lifecycle policy. For example, `movetodos`.
     1. Turn on the **Create data streams** toggle.
@@ -190,7 +197,7 @@ To create an index template in Kibana, complete these steps:
 
 The newly created index template will be used for all new indices with names that match the specified pattern, and for each of these, the specified ILM policy will be applied.
 
-For more information about configuring templates in Kibana, refer to [Manage index templates](/manage-data/data-store/index-basics.md#index-management-manage-index-templates). 
+For more information about configuring templates in Kibana, refer to [Manage index templates](/manage-data/data-store/index-basics.md#index-management-manage-index-templates).
 :::
 
 :::{tab-item} API
@@ -265,7 +272,7 @@ POST /_reindex
   "dest": {
     "index": "movetods",
     "op_type": "create"
-    
+
   }
 }
 ```
diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-with-data-streams.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-with-data-streams.md
index 51a0150a6d..5075df6344 100644
--- a/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-with-data-streams.md
+++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-with-data-streams.md
@@ -38,7 +38,10 @@ Use the {{kib}} **Create template** wizard to add a template or the [Create or u
 :group: kibana-api
 :::{tab-item} {{kib}}
 :sync: kibana
-To add an index template to a cluster using the wizard, go to **Stack Management > Index Management**. In the **Index Templates** tab, click **Create template** and follow the instructions.
+To add an index template to a cluster using the wizard:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create template** and follow the instructions.
 
 ![Create template page](/manage-data/images/elasticsearch-reference-create-index-template.png "")
 
@@ -46,7 +49,7 @@ You specify the name of the lifecycle policy that you want to apply to the data
 
 ![Create template page](/manage-data/images/elasticsearch-reference-tutorial-ilm-datastreams-tutorial-create-index-template.png "")
 
-:::{tip} 
+:::{tip}
 To learn about which index template options you can specify, refer to [Create an index template to apply the lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template).
 :::
 :::
diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-without-data-streams.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-without-data-streams.md
index a5e437e7ea..311422bfcf 100644
--- a/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-without-data-streams.md
+++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-time-series-without-data-streams.md
@@ -38,11 +38,15 @@ To enable automatic rollover, the template configures two {{ilm-init}} settings:
 :group: kibana-api
 :::{tab-item} {{kib}}
 :sync: kibana
-To use the {{kib}} **Create template** wizard to add the template, go to **Stack Management > Index Management**. In the **Index Templates** tab, click **Create template**.
+
+To use the {{kib}} **Create template** wizard to add the template:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create template**.
 
 ![Create template page](/manage-data/images/elasticsearch-reference-create-template-wizard.png "")
 
-:::{tip} 
+:::{tip}
 For more information about the available index template options that you can specify, refer to [Create an index template to apply the lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template).
 :::
 :::
diff --git a/manage-data/migrate.md b/manage-data/migrate.md
index ab26835fbd..3ed4028d93 100644
--- a/manage-data/migrate.md
+++ b/manage-data/migrate.md
@@ -44,7 +44,7 @@ Restore from a snapshot
 
 :::{admonition} Migrating system {{es}} indices
 In {{es}} 8.0 and later versions, to back up and restore system indices and system data streams such as `.kibana` or `.security`, you must snapshot and restore the related feature's [feature state](/deploy-manage/tools/snapshot-and-restore.md#feature-state).
-    
+
 Refer to [Migrate system indices](./migrate/migrate-internal-indices.md) to learn how to restore the internal {{es}} system indices from a snapshot.
 :::
 
@@ -128,8 +128,8 @@ System indices can be restored by including their corresponding [feature states]
 
 This method is especially useful when:
 
-* You want to fully replicate the source cluster or when remote reindexing is not possible, for example if the source cluster is in a degraded or unreachable state. 
-* Your old cluster contains mostly static data, allowing you to snapshot the source cluster, restore in the new cluster, and continue operations. 
+* You want to fully replicate the source cluster or when remote reindexing is not possible, for example if the source cluster is in a degraded or unreachable state.
+* Your old cluster contains mostly static data, allowing you to snapshot the source cluster, restore in the new cluster, and continue operations.
 
 When your source cluster is actively ingesting data, such as logs, metrics, or traces, and you need a seamless migration with minimal downtime, consider using the [minimal downtime migration](migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md).
 
@@ -182,7 +182,7 @@ If your new {{ech}} or {{ece}} deployment cannot connect to the same repository
     * **Azure Blob Storage**
         * [Store credentials in the keystore](/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md#ec-configure-azure-keystore).
         * [Create the repository](/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md#ec-create-azure-repository).
-    
+
     ::::{important}
     Although these instructions are focused on {{ech}}, you should follow the same steps for {{ece}} by configuring the repository directly **at the deployment level**.
 
@@ -200,7 +200,7 @@ For details about the contents of a snapshot, refer to [](/deploy-manage/tools/s
 
 To start the restore process:
 
-1. Open Kibana and go to **Management** > **Snapshot and Restore**.
+1. Open Kibana and go to the **Snapshot and Restore** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. Under the **Snapshots** tab, you can find the available snapshots from your newly added snapshot repository. Select any snapshot to view its details, and from there you can choose to restore it.
 3. Select **Restore**.
 4. Select the index or indices you wish to restore.
diff --git a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
index c412860f4a..b412ad4b22 100644
--- a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
+++ b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
@@ -127,7 +127,10 @@ If you use {{fleet}} or {{agent}}, edit one of {{es}}'s built-in lifecycle polic
 
 You can customize these policies based on your performance, resilience, and retention requirements.
 
-To edit a policy in {{kib}}, open the main menu and go to **Stack Management > Index Lifecycle Policies**. Click the policy you’d like to edit.
+To edit a policy in {{kib}}:
+
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click the policy you’d like to edit.
 
 You can also use the [update lifecycle policy API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle).
 
@@ -183,7 +186,10 @@ PUT _ilm/policy/logs
 ::::::
 
 ::::::{tab-item} Custom application
-To create a policy in {{kib}}, open the main menu and go to **Stack Management > Index Lifecycle Policies**. Click **Create policy**.
+To create a policy in {{kib}}:
+
+1. Go to the **Index Lifecycle Policies** management page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Click **Create policy**.
 
 You can also use the [update lifecycle policy API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-put-lifecycle).
 
@@ -261,8 +267,10 @@ If you’re unsure how to map your fields, use [runtime fields](data-store/mappi
 
 ::::
 
+To create a component template in {{kib}}:
 
-To create a component template in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Index Templates** view, click **Create component template**.
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create component template**.
 
 You can also use the [create component template API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-component-template).
 
@@ -314,7 +322,10 @@ Use your component templates to create an index template. Specify:
 * Any component templates that contain your mappings and index settings.
 * A priority higher than `200` to avoid collisions with built-in templates. See [Avoid index pattern collisions](data-store/templates.md#avoid-index-pattern-collisions).
 
-To create an index template in {{kib}}, open the main menu and go to **Stack Management > Index Management**. In the **Index Templates** view, click **Create template**.
+To create an index template in {{kib}}:
+
+1. Go to the **Index Management** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. In the **Index Templates** tab, click **Create template**.
 
 You can also use the [create index template API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-index-template). Include the `data_stream` object to enable data streams.