diff --git a/explore-analyze/alerts-cases/alerts/alerting-common-issues.md b/explore-analyze/alerts-cases/alerts/alerting-common-issues.md
index 9acdc7a4a1..95abc28c8c 100644
--- a/explore-analyze/alerts-cases/alerts/alerting-common-issues.md
+++ b/explore-analyze/alerts-cases/alerts/alerting-common-issues.md
@@ -60,7 +60,7 @@ Configuration options are available to specialize connections to TLS servers, in
 Rules are taking a long time to run and are impacting the overall health of your deployment.
 
 ::::{important}
-By default, only users with a `superuser` role can query the [preview] {{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
+By default, only users with a `superuser` role can query the {{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
 
 ::::
 
diff --git a/explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md b/explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md
index f7b451eafc..d626709e50 100644
--- a/explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md
+++ b/explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md
@@ -62,7 +62,7 @@ curl -X POST -k \
  -d '{"params":{"subject":"hallo","message":"hallo!","to":["me@example.com"]}}'
 ```
 
-[preview] In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
+{applies_to}`stack: preview` {applies_to}`serverless: preview` In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
 
 ```txt
 npm install -g pmuellr/kbn-action
diff --git a/explore-analyze/alerts-cases/alerts/create-manage-rules.md b/explore-analyze/alerts-cases/alerts/create-manage-rules.md
index 3aa01d0dac..d55a94a686 100644
--- a/explore-analyze/alerts-cases/alerts/create-manage-rules.md
+++ b/explore-analyze/alerts-cases/alerts/create-manage-rules.md
@@ -61,7 +61,7 @@ You can add one or more actions to your rule to generate notifications when its
 
 Each action uses a connector, which provides connection information for a {{kib}} service or third party integration, depending on where you want to send the notifications.
 
-[preview] Some connectors that perform actions within {{kib}}, such as the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), require less configuration. For example, you do not need to set the action frequency or variables.
+{applies_to}`stack: preview` {applies_to}`serverless: preview` Some connectors that perform actions within {{kib}}, such as the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), require less configuration. For example, you do not need to set the action frequency or variables.
 
 After you select a connector, set the action frequency. You can choose to create a summary of alerts on each check interval or on a custom interval. Alternatively, you an choose to run actions for each alert (at each check interval, only when the alert status changes, or at a custom interval).
 
@@ -129,7 +129,7 @@ When you snooze a rule, the rule checks continue to run on a schedule but alerts
 
 When a rule is in a snoozed state, you can cancel or change the duration of this state.
 
-[preview] To temporarily suppress notifications for rules, you can also create a [maintenance window](maintenance-windows.md).
+{applies_to}`stack: preview` {applies_to}`serverless: preview` To temporarily suppress notifications for rules, you can also create a [maintenance window](maintenance-windows.md).
 
 ## View rule details [rule-details]
 
diff --git a/explore-analyze/alerts-cases/alerts/rule-action-variables.md b/explore-analyze/alerts-cases/alerts/rule-action-variables.md
index ead0b1ac3d..84b77c8055 100644
--- a/explore-analyze/alerts-cases/alerts/rule-action-variables.md
+++ b/explore-analyze/alerts-cases/alerts/rule-action-variables.md
@@ -68,23 +68,23 @@ If the rule’s action frequency is a summary of alerts, it passes the following
 
     **Properties of the alerts.all.data objects**:
 
-    `kibana.alert.end`
-    :   Datetime stamp of alert end. [preview]
+    `kibana.alert.end` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert end.
 
-    `kibana.alert.flapping`
-    :   A flag on the alert that indicates whether the alert status is changing repeatedly. [preview]
+    `kibana.alert.flapping` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   A flag on the alert that indicates whether the alert status is changing repeatedly.
 
-    `kibana.alert.instance.id`
-    :   ID of the source that generates the alert. [preview]
+    `kibana.alert.instance.id` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   ID of the source that generates the alert.
 
-    `kibana.alert.reason`
-    :   The reason of the alert (generated with the rule conditions). [preview]
+    `kibana.alert.reason` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   The reason of the alert (generated with the rule conditions).
 
-    `kibana.alert.start`
-    :   Datetime stamp of alert start. [preview]
+    `kibana.alert.start` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert start.
 
-    `kibana.alert.status`
-    :   Alert status (for example, active or OK). [preview]
+    `kibana.alert.status` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Alert status (for example, active or OK).
 
 `alerts.new.count`
 :   The count of new alerts.
@@ -94,23 +94,23 @@ If the rule’s action frequency is a summary of alerts, it passes the following
 
     **Properties of the alerts.new.data objects**:
 
-    `kibana.alert.end`
-    :   Datetime stamp of alert end. [preview]
+    `kibana.alert.end` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert end.
 
-    `kibana.alert.flapping`
-    :   A flag on the alert that indicates whether the alert status is changing repeatedly. [preview]
+    `kibana.alert.flapping` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   A flag on the alert that indicates whether the alert status is changing repeatedly.
 
-    `kibana.alert.instance.id`
-    :   ID of the source that generates the alert. [preview]
+    `kibana.alert.instance.id` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   ID of the source that generates the alert.
 
-    `kibana.alert.reason`
-    :   The reason of the alert (generated with the rule conditions). [preview]
+    `kibana.alert.reason` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   The reason of the alert (generated with the rule conditions).
 
-    `kibana.alert.start`
-    :   Datetime stamp of alert start. [preview]
+    `kibana.alert.start` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert start.
 
-    `kibana.alert.status`
-    :   Alert status (for example, active or OK). [preview]
+    `kibana.alert.status` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Alert status (for example, active or OK).
 
 `alerts.ongoing.count`
 :   The count of ongoing alerts.
@@ -120,23 +120,23 @@ If the rule’s action frequency is a summary of alerts, it passes the following
 
     **Properties of the alerts.ongoing.data objects**:
 
-    `kibana.alert.end`
-    :   Datetime stamp of alert end. [preview]
+    `kibana.alert.end` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert end.
 
-    `kibana.alert.flapping`
-    :   A flag on the alert that indicates whether the alert status is changing repeatedly. [preview]
+    `kibana.alert.flapping` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   A flag on the alert that indicates whether the alert status is changing repeatedly.
 
-    `kibana.alert.instance.id`
-    :   ID of the source that generates the alert. [preview]
+    `kibana.alert.instance.id` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   ID of the source that generates the alert.
 
-    `kibana.alert.reason`
-    :   The reason of the alert (generated with the rule conditions). [preview]
+    `kibana.alert.reason` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   The reason of the alert (generated with the rule conditions).
 
-    `kibana.alert.start`
-    :   Datetime stamp of alert start. [preview]
+    `kibana.alert.start` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert start.
 
-    `kibana.alert.status`
-    :   Alert status (for example, active or OK). [preview]
+    `kibana.alert.status` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Alert status (for example, active or OK).
 
 `alerts.recovered.count`
 :   The count of recovered alerts.
@@ -146,23 +146,23 @@ If the rule’s action frequency is a summary of alerts, it passes the following
 
     **Properties of the alerts.recovered.data objects**:
 
-    `kibana.alert.end`
-    :   Datetime stamp of alert end. [preview]
+    `kibana.alert.end` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert end.
 
-    `kibana.alert.flapping`
-    :   A flag on the alert that indicates whether the alert status is changing repeatedly. [preview]
+    `kibana.alert.flapping` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   A flag on the alert that indicates whether the alert status is changing repeatedly.
 
-    `kibana.alert.instance.id`
-    :   ID of the source that generates the alert. [preview]
+    `kibana.alert.instance.id` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   ID of the source that generates the alert.
 
-    `kibana.alert.reason`
-    :   The reason of the alert (generated with the rule conditions). [preview]
+    `kibana.alert.reason` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   The reason of the alert (generated with the rule conditions).
 
-    `kibana.alert.start`
-    :   Datetime stamp of alert start. [preview]
+    `kibana.alert.start` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Datetime stamp of alert start.
 
-    `kibana.alert.status`
-    :   Alert status (for example, active or OK). [preview]
+    `kibana.alert.status` {applies_to}`stack: preview` {applies_to}`serverless: preview`
+    :   Alert status (for example, active or OK).
 
 ### Action frequency: For each alert [alert-action-variables]
 
diff --git a/explore-analyze/alerts-cases/alerts/rule-types.md b/explore-analyze/alerts-cases/alerts/rule-types.md
index 044e55fdbc..23d3764326 100644
--- a/explore-analyze/alerts-cases/alerts/rule-types.md
+++ b/explore-analyze/alerts-cases/alerts/rule-types.md
@@ -25,7 +25,7 @@ Some rule types are subscription features, while others are free features. For a
 | --- | --- |
 | [{{es}} query](rule-type-es-query.md) | Run a user-configured {{es}} query, compare the number of matches to a configured threshold, and schedule actions to run when the threshold condition is met. |
 | [Index threshold](rule-type-index-threshold.md) | Aggregate field values from documents using {{es}} queries, compare them to threshold values, and schedule actions to run when the thresholds are met. |
-| [{{transform-cap}} rules](../../transforms/transform-alerts.md) | [beta] Run scheduled checks on a {{ctransform}} to check its health. If a {{ctransform}} meets the conditions, an alert is created and the associated action is triggered. |
+| [{{transform-cap}} rules](../../transforms/transform-alerts.md) | {applies_to}`stack: beta` {applies_to}`serverless: beta` Run scheduled checks on a {{ctransform}} to check its health. If a {{ctransform}} meets the conditions, an alert is created and the associated action is triggered. |
 | [Tracking containment](geo-alerting.md) | Run an {{es}} query to determine if any documents are currently contained in any boundaries from a specified boundary index and generate alerts when a rule’s conditions are met. |
 
 ## {{observability}} rules [observability-rules]
@@ -38,8 +38,12 @@ If you create a rule in the {{observability}} app, its alerts are not visible in
 ::::
 
 ## Machine learning rules [ml-rules]
+```{applies_to}
+stack: beta
+serverless: beta
+```
 
-[beta] [{{ml-cap}} rules](../../machine-learning/anomaly-detection/ml-configuring-alerts.md) run scheduled checks on an {{anomaly-job}} to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
+[{{ml-cap}} rules](../../machine-learning/anomaly-detection/ml-configuring-alerts.md) run scheduled checks on an {{anomaly-job}} to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
 
 ## Security rules [security-rules]
 
diff --git a/explore-analyze/alerts-cases/alerts/testing-connectors.md b/explore-analyze/alerts-cases/alerts/testing-connectors.md
index 1d00b3e116..12d512c6a3 100644
--- a/explore-analyze/alerts-cases/alerts/testing-connectors.md
+++ b/explore-analyze/alerts-cases/alerts/testing-connectors.md
@@ -29,7 +29,11 @@ or by directly opening the proper connector edit flyout:
 :screenshot:
 :::
 
-## [preview] Troubleshooting connectors with the `kbn-action` tool [_troubleshooting_connectors_with_the_kbn_action_tool]
+## Troubleshooting connectors with the `kbn-action` tool [_troubleshooting_connectors_with_the_kbn_action_tool]
+```{applies_to}
+stack: preview
+serverless: preview
+```
 
 You can run an email action via [kbn-action](https://github.com/pmuellr/kbn-action). In this example, it is a Cloud hosted deployment of the {{stack}}:
 
diff --git a/explore-analyze/alerts-cases/alerts/view-alerts.md b/explore-analyze/alerts-cases/alerts/view-alerts.md
index 7b4f870bca..09e33160ce 100644
--- a/explore-analyze/alerts-cases/alerts/view-alerts.md
+++ b/explore-analyze/alerts-cases/alerts/view-alerts.md
@@ -13,7 +13,7 @@ products:
 
 When the conditions of a rule are met, it creates an alert. If the rule has actions, they run at the defined frequency. For example, the rule can send email notifications for each alert at a custom interval. For an introduction to the concepts of rules, alerts, and actions, refer to [Alerting](../alerts.md).
 
-You can manage the alerts for each rule in **{{stack-manage-app}}** > **{{rules-ui}}**. Alternatively, manage all your alerts in **{{stack-manage-app}}** > **Alerts**. [preview]
+You can manage the alerts for each rule in **{{stack-manage-app}}** > **{{rules-ui}}**. Alternatively, manage all your alerts in **{{stack-manage-app}}** > **Alerts**.
 
 :::{image} /explore-analyze/images/kibana-stack-management-alerts-page.png
 :alt: Alerts page with multiple alerts
diff --git a/explore-analyze/alerts-cases/cases.md b/explore-analyze/alerts-cases/cases.md
index b67ad1b377..547bb33cae 100644
--- a/explore-analyze/alerts-cases/cases.md
+++ b/explore-analyze/alerts-cases/cases.md
@@ -13,7 +13,7 @@ products:
 
 Cases are used to open and track issues directly in {{kib}}. You can add assignees and tags to your cases, set their severity and status, and add alerts, comments, and visualizations. You can create cases automatically when alerts occur or send cases to external incident management systems by configuring connectors.
 
-You can also optionally add custom fields and case templates. [preview]
+{applies_to}`stack: preview` {applies_to}`serverless: preview` You can also optionally add custom fields and case templates.
 
 :::{image} /explore-analyze/images/kibana-cases-list.png
 :alt: Cases page
diff --git a/explore-analyze/alerts-cases/cases/manage-cases.md b/explore-analyze/alerts-cases/cases/manage-cases.md
index 8a5fb24095..a079c774fc 100644
--- a/explore-analyze/alerts-cases/cases/manage-cases.md
+++ b/explore-analyze/alerts-cases/cases/manage-cases.md
@@ -23,7 +23,7 @@ Open a new case to keep track of issues and share their details with colleagues.
    :screenshot:
    :::
 
-2. If you defined [templates](manage-cases-settings.md#case-templates), you can optionally select one to use its default field values. [preview]
+2. If you defined [templates](manage-cases-settings.md#case-templates), you can optionally select one to use its default field values.
 3. Give the case a name, severity, and description.
    ::::{tip}
    In the `Description` area, you can use [Markdown](https://www.markdownguide.org/cheat-sheet) syntax to create formatted text.
@@ -32,14 +32,10 @@ Open a new case to keep track of issues and share their details with colleagues.
 4. Optionally, add a category, assignees, and tags. You can add users only if they meet the necessary [prerequisites](setup-cases.md).
 5. If you defined any [custom fields](manage-cases-settings.md#case-custom-fields), they appear in the **Additional fields** section.
 
-    :::{admonition} Added in 8.15.0
-    This functionality was added in 8.15.0.
-    :::
-
 6. For the **External incident management system**, select a connector. For more information, refer to [External incident management systems](manage-cases-settings.md#case-connectors).
 7. After you’ve completed all of the required fields, click **Create case**.
 
-[preview] Alternatively, you can configure your rules to automatically create cases by using [case actions](kibana://reference/connectors-kibana/cases-action-type.md). By default, the rule adds all of the alerts within a specified time window to a single case. You can optionally choose a field to group the alerts and create separate cases for each group. You can also choose whether you want the rule to reopen cases or open new ones when the time window elapses.
+{applies_to}`stack: preview` {applies_to}`serverless: preview` Alternatively, you can configure your rules to automatically create cases by using [case actions](kibana://reference/connectors-kibana/cases-action-type.md). By default, the rule adds all of the alerts within a specified time window to a single case. You can optionally choose a field to group the alerts and create separate cases for each group. You can also choose whether you want the rule to reopen cases or open new ones when the time window elapses.
 
 ## Add email notifications [add-case-notifications]
 
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
index c940762052..b73352a450 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
@@ -18,7 +18,7 @@ ELSER is an out-of-domain model which means it does not require fine-tuning on y
 This model is recommended for English language documents and queries. If you want to perform semantic search on non-English language documents, use the [E5](ml-nlp-e5.md) model.
 
 ::::{important}
-While ELSER V2 is generally available, ELSER V1 is in [preview] and will remain in technical preview.
+While ELSER V2 is generally available, ELSER V1 is and will remain in technical preview.
 ::::
 
 ## Tokens - not synonyms [elser-tokens]
diff --git a/explore-analyze/query-filter/languages/sql-jdbc.md b/explore-analyze/query-filter/languages/sql-jdbc.md
index 66d6be6543..4103887142 100644
--- a/explore-analyze/query-filter/languages/sql-jdbc.md
+++ b/explore-analyze/query-filter/languages/sql-jdbc.md
@@ -173,7 +173,7 @@ $$$jdbc-cfg-timezone$$$
 `catalog`
 :   Default catalog (cluster) for queries. If unspecified, the queries execute on the data in the local cluster only.
 
-    [preview] See [{{ccs}}](../../../solutions/search/cross-cluster-search.md).
+    See [{{ccs}}](../../../solutions/search/cross-cluster-search.md).
 
 
 
diff --git a/explore-analyze/query-filter/tools.md b/explore-analyze/query-filter/tools.md
index 25c3bdaa12..40325c0473 100644
--- a/explore-analyze/query-filter/tools.md
+++ b/explore-analyze/query-filter/tools.md
@@ -18,7 +18,7 @@ Access these specialized tools in Kibana and the Serverless UI to develop, debug
 | [Console](tools/console.md) | Interact with the REST APIs of {{es}} and {{kib}}, including sending requests and viewing API documentation. |
 | [{{searchprofiler}}](tools/search-profiler.md) | Inspect and analyze your search queries. |
 | [Grok Debugger](tools/grok-debugger.md) | Build and debug grok patterns before you use them in your data processing pipelines. |
-| [Painless Lab](../scripting/painless-lab.md) | [beta] Test and debug Painless scripts in real-time. |
+| [Painless Lab](../scripting/painless-lab.md) | {applies_to}`stack: beta` {applies_to}`serverless: beta` Test and debug Painless scripts in real-time. |
 | [Playground](tools/playground.md) | Combine your Elasticsearch data with the power of large language models (LLMs) for retrieval augmented generation (RAG), using a chat interface. |
 
 
diff --git a/explore-analyze/report-and-share.md b/explore-analyze/report-and-share.md
index 85ee1df2a4..25509ade3b 100644
--- a/explore-analyze/report-and-share.md
+++ b/explore-analyze/report-and-share.md
@@ -152,7 +152,7 @@ Create and share JSON files for workpads.
 
 ## Embed outside of {{kib}} [_embed_outside_of_kib]
 
-* [beta] **Share on a website** — Download and securely share **Canvas** workpads on any website.
+* {applies_to}`stack: beta` {applies_to}`serverless: beta` **Share on a website** — Download and securely share **Canvas** workpads on any website.
 * **Embed code** — Embed fully interactive dashboards as an iframe on web pages.
 
 ::::{note}
@@ -164,8 +164,12 @@ For {{ech}} deployments, {{kib}} instances require a minimum of 2GB RAM to gener
 
 
 ## Share workpads on a website [add-workpad-website]
+```{applies_to}
+stack: beta
+serverless: beta
+```
 
-[beta] Create and securely share static **Canvas** workpads on a website. To customize the behavior of the workpad on your website, you can choose to autoplay the pages or hide the workpad toolbar.
+Create and securely share static **Canvas** workpads on a website. To customize the behavior of the workpad on your website, you can choose to autoplay the pages or hide the workpad toolbar.
 
 1. Go to **Canvas**.
 2. Open the workpad you want to share.
diff --git a/explore-analyze/visualize/custom-visualizations-with-vega.md b/explore-analyze/visualize/custom-visualizations-with-vega.md
index e886269ace..90ea1799f8 100644
--- a/explore-analyze/visualize/custom-visualizations-with-vega.md
+++ b/explore-analyze/visualize/custom-visualizations-with-vega.md
@@ -1123,7 +1123,7 @@ Learn more about {{kib}} extension, additional **Vega** resources, and examples.
 * Automatic sizing
 * Default theme to match {{kib}}
 * Writing {{es}} queries using the time range and filters from dashboards
-* [preview] Using the Elastic Map Service in Vega maps
+* {applies_to}`stack: preview` {applies_to}`serverless: preview` Using the Elastic Map Service in Vega maps
 * Additional tooltip styling
 * Advanced setting to enable URL loading from any domain
 * Debugging support using the {{kib}} inspector
@@ -1320,8 +1320,12 @@ The `"%timefilter%"` can also be used to specify a single min or max value. The
 
 
 #### Access Elastic Map Service files [vega-esmfiles]
+```{applies_to}
+stack: preview
+serverless: preview
+```
 
-[preview] Access the Elastic Map Service files via the same mechanism:
+Access the Elastic Map Service files using the same mechanism:
 
 ```yaml
 url: {
@@ -1343,8 +1347,12 @@ format: {property: "features"}
 
 
 ### Vega with a Map [vega-with-a-map]
+```{applies_to}
+stack: preview
+serverless: preview
+```
 
-[preview] To enable **Maps**, the graph must specify `type=map` in the host configuration:
+To enable **Maps**, the graph must specify `type=map` in the host configuration:
 
 ```yaml
 {
@@ -1390,7 +1398,7 @@ format: {property: "features"}
 
 The visualization automatically injects a `"projection"`, which you can use to calculate the position of all geo-aware marks. Additionally, you can use `latitude`, `longitude`, and `zoom` signals. These signals can be used in the graph, or can be updated to modify the position of the map.
 
-[preview] You can use the **Vega** [data](https://vega.github.io/vega/docs/data/) element to access [Elastic Maps Service (EMS)](https://www.elastic.co/elastic-maps-service) vector shapes of administrative boundaries in your Vega map by setting `url.data` to `emsFile`:
+{applies_to}`stack: preview` {applies_to}`serverless: preview` You can use the **Vega** [data](https://vega.github.io/vega/docs/data/) element to access [Elastic Maps Service (EMS)](https://www.elastic.co/elastic-maps-service) vector shapes of administrative boundaries in your Vega map by setting `url.data` to `emsFile`:
 
 ```yaml
   "data": [
diff --git a/manage-data/data-store/data-streams/manage-data-stream.md b/manage-data/data-store/data-streams/manage-data-stream.md
index b8d0b3ac0e..bb33d72eb7 100644
--- a/manage-data/data-store/data-streams/manage-data-stream.md
+++ b/manage-data/data-store/data-streams/manage-data-stream.md
@@ -21,4 +21,4 @@ In {{es-serverless}}, indices matching the `logs-*-*` pattern use the logsDB ind
 
 * To view more information about a data stream, such as its generation or its current index lifecycle policy, click the stream’s name. From this view, you can navigate to **Discover** to further explore data within the data stream.
 * To view information about the stream’s backing indices, click the number in the **Indices** column.
-* [preview] To modify the data retention value, select a data stream, open the **Manage**  menu, and click **Edit data retention**.
+* To modify the data retention value, select a data stream, open the **Manage**  menu, and click **Edit data retention**.
\ No newline at end of file
diff --git a/reference/fleet/agent-command-reference.md b/reference/fleet/agent-command-reference.md
index dfbf16bf9a..ca53ea9487 100644
--- a/reference/fleet/agent-command-reference.md
+++ b/reference/fleet/agent-command-reference.md
@@ -710,7 +710,7 @@ See the `--unprivileged` option and [Run {{agent}} without administrative privil
 
     Note that changing to `unprivileged` mode is prevented if the agent is currently enrolled in a policy that includes an integration that requires administrative access, such as the {{elastic-defend}} integration.
 
-    [preview] To run {{agent}} without superuser privileges as a pre-existing user or group, for instance under an Active Directory account, you can specify the user or group, and the password to use.
+    {applies_to}`stack: preview` {applies_to}`serverless: preview` To run {{agent}} without superuser privileges as a pre-existing user or group, for instance under an Active Directory account, you can specify the user or group, and the password to use.
 
     For example:
 
@@ -1038,7 +1038,7 @@ Run {{agent}} without full superuser privileges. This is useful in organizations
 
 Note that changing a running {{agent}} to `unprivileged` mode is prevented if the agent is currently enrolled with a policy that contains the {{elastic-defend}} integration.
 
-[preview] To run {{agent}} without superuser privileges as a pre-existing user or group, for instance under an Active Directory account, add either a `--user` or `--group` parameter together with a `--password` parameter.
+{applies_to}`stack: preview` {applies_to}`serverless: preview` To run {{agent}} without superuser privileges as a pre-existing user or group, for instance under an Active Directory account, add either a `--user` or `--group` parameter together with a `--password` parameter.
 
 
 ### Examples [_examples_19]
@@ -1049,13 +1049,13 @@ Run {{agent}} without administrative privileges:
 elastic-agent unprivileged
 ```
 
-[preview] Run {{agent}} without administrative privileges, as a pre-existing user:
+{applies_to}`stack: preview` {applies_to}`serverless: preview` Run {{agent}} without administrative privileges, as a pre-existing user:
 
 ```shell
 elastic-agent unprivileged --user="my.pathl\username" --password="mypassword"
 ```
 
-[preview] Run {{agent}} without administrative privileges, as a pre-existing group:
+{applies_to}`stack: preview` {applies_to}`serverless: preview` Run {{agent}} without administrative privileges, as a pre-existing group:
 
 ```shell
 elastic-agent unprivileged --group="my.pathl\groupname" --password="mypassword"
diff --git a/reference/fleet/elastic-agent-inputs-list.md b/reference/fleet/elastic-agent-inputs-list.md
index 18c784bb88..ac26e70dbd 100644
--- a/reference/fleet/elastic-agent-inputs-list.md
+++ b/reference/fleet/elastic-agent-inputs-list.md
@@ -19,7 +19,7 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | --- | --- | --- |
 | `audit/auditd` | Receives audit events from the Linux Audit Framework that is a part of the Linux kernel. | [Auditd Module](beats://reference/auditbeat/auditbeat-module-auditd.md) ({{auditbeat}} docs) |
 | `audit/file_integrity` | Sends events when a file is changed (created, updated, or deleted) on disk. The events contain file metadata and hashes. | [File Integrity Module](beats://reference/auditbeat/auditbeat-module-file_integrity.md) ({{auditbeat}} docs) |
-| `audit/system` | [beta] Collects various security related information about a system. All datasets send both periodic state information (e.g. all currently running processes) and real-time changes (e.g. when a new process starts or stops). | [System Module](beats://reference/auditbeat/auditbeat-module-system.md) ({{auditbeat}} docs) |
+| `audit/system` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Collects various security related information about a system. All datasets send both periodic state information (e.g. all currently running processes) and real-time changes (e.g. when a new process starts or stops). | [System Module](beats://reference/auditbeat/auditbeat-module-system.md) ({{auditbeat}} docs) |
 
 ::::
 
@@ -32,11 +32,11 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | `activemq/metrics` | Periodically fetches JMX metrics from Apache ActiveMQ. | [ActiveMQ module](beats://reference/metricbeat/metricbeat-module-activemq.md) ({{metricbeat}} docs) |
 | `apache/metrics` | Periodically fetches metrics from [Apache HTTPD](https://httpd.apache.org/) servers. | [Apache module](beats://reference/metricbeat/metricbeat-module-apache.md) ({{metricbeat}} docs) |
 | `aws/metrics` | Periodically fetches monitoring metrics from AWS CloudWatch using [GetMetricData API](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.md) for AWS services. | [AWS module](beats://reference/metricbeat/metricbeat-module-aws.md) ({{metricbeat}} docs) |
-| `awsfargate/metrics` | [beta] Retrieves various metadata, network metrics, and Docker stats about tasks and containers. | [AWS Fargate module](beats://reference/metricbeat/metricbeat-module-awsfargate.md) ({{metricbeat}} docs) |
+| `awsfargate/metrics` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Retrieves various metadata, network metrics, and Docker stats about tasks and containers. | [AWS Fargate module](beats://reference/metricbeat/metricbeat-module-awsfargate.md) ({{metricbeat}} docs) |
 | `azure/metrics` | Collects and aggregates Azure logs and metrics from a variety of sources into a common data platform where it can be used for analysis, visualization, and alerting. | [Azure module](beats://reference/metricbeat/metricbeat-module-azure.md) ({{metricbeat}} docs) |
 | `beat/metrics` | Collects metrics about any Beat or other software based on libbeat. | [Beat module](beats://reference/metricbeat/metricbeat-module-beat.md) ({{metricbeat}} docs) |
 | `cloudfoundry/metrics` | Connects to Cloud Foundry loggregator to gather container, counter, and value metrics into a common data platform where it can be used for analysis, visualization, and alerting. | [Cloudfoundry module](beats://reference/metricbeat/metricbeat-module-cloudfoundry.md) ({{metricbeat}} docs) |
-| `containerd/metrics` | [beta] Collects cpu, memory and blkio statistics about running containers controlled by containerd runtime. | [Containerd module](beats://reference/metricbeat/metricbeat-module-containerd.md) ({{metricbeat}} docs) |
+| `containerd/metrics` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Collects CPU, memory and blkio statistics about running containers controlled by containerd runtime. | [Containerd module](beats://reference/metricbeat/metricbeat-module-containerd.md) ({{metricbeat}} docs) |
 | `docker/metrics` | Fetches metrics from [Docker](https://www.docker.com/) containers. | [Docker module](beats://reference/metricbeat/metricbeat-module-docker.md) ({{metricbeat}} docs) |
 | `elasticsearch/metrics` | Collects metrics about {{es}}. | [Elasticsearch module](beats://reference/metricbeat/metricbeat-module-elasticsearch.md) ({{metricbeat}} docs) |
 | `etcd/metrics` | This module targets Etcd V2 and V3. When using V2, metrics are collected using [Etcd v2 API](https://coreos.com/etcd/docs/latest/v2/api.md). When using V3, metrics are retrieved from the `/metrics` endpoint as intended for [Etcd v3](https://coreos.com/etcd/docs/latest/metrics.md). | [Etcd module](beats://reference/metricbeat/metricbeat-module-etcd.md) ({{metricbeat}} docs) |
@@ -48,7 +48,7 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | `kafka/metrics` | Collects metrics from the [Apache Kafka](https://kafka.apache.org/intro) event streaming platform. | [Kafka module](beats://reference/metricbeat/metricbeat-module-kafka.md) ({{metricbeat}} docs) |
 | `kibana/metrics` | Collects metrics about {{kib}}. | [{{kib}} module](beats://reference/metricbeat/metricbeat-module-kibana.md) ({{metricbeat}} docs) |
 | `kubernetes/metrics` | As one of the main pieces provided for Kubernetes monitoring, this module is capable of fetching metrics from several components. | [Kubernetes module](beats://reference/metricbeat/metricbeat-module-kubernetes.md) ({{metricbeat}} docs) |
-| `linux/metrics` | [beta] Reports on metrics exclusive to the Linux kernel and GNU/Linux OS. | [Linux module](beats://reference/metricbeat/metricbeat-module-linux.md) ({{metricbeat}} docs) |
+| `linux/metrics` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Reports on metrics exclusive to the Linux kernel and GNU/Linux OS. | [Linux module](beats://reference/metricbeat/metricbeat-module-linux.md) ({{metricbeat}} docs) |
 | `logstash/metrics` | collects metrics about {{ls}}. | [{{ls}} module](beats://reference/metricbeat/metricbeat-module-logstash.md) ({{metricbeat}} docs) |
 | `memcached/metrics` | Collects metrics about the [memcached](https://memcached.org/) memory object caching system. | [Memcached module](beats://reference/metricbeat/metricbeat-module-memcached.md) ({{metricbeat}} docs) |
 | `mongodb/metrics` | Periodically fetches metrics from [MongoDB](https://www.mongodb.com/) servers. | [MongoDB module](beats://reference/metricbeat/metricbeat-module-mongodb.md) ({{metricbeat}} docs) |
@@ -64,7 +64,7 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | `sql/metrics` | Allows you to execute custom queries against an SQL database and store the results in {{es}}. | [SQL module](beats://reference/metricbeat/metricbeat-module-sql.md) ({{metricbeat}} docs) |
 | `stan/metrics` | Uses [STAN monitoring server APIs](https://github.com/nats-io/nats-streaming-server/blob/master/server/monitor.go) to collect metrics. | [Stan module](beats://reference/metricbeat/metricbeat-module-stan.md) ({{metricbeat}} docs) |
 | `statsd/metrics` | Spawns a UDP server and listens for metrics in StatsD compatible format. | [Statsd module](beats://reference/metricbeat/metricbeat-module-statsd.md) ({{metricbeat}} docs) |
-| `syncgateway/metrics` | [beta] Monitor a Sync Gateway instance by using its REST API. | [SyncGateway module](beats://reference/metricbeat/metricbeat-module-syncgateway.md) ({{metricbeat}} docs) |
+| `syncgateway/metrics` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Monitor a Sync Gateway instance by using its REST API. | [SyncGateway module](beats://reference/metricbeat/metricbeat-module-syncgateway.md) ({{metricbeat}} docs) |
 | `system/metrics` | Allows you to monitor your server metrics, including CPU, load, memory, network, processes, sockets, filesystem, fsstat, uptime, and more. | [System module](beats://reference/metricbeat/metricbeat-module-system.md) ({{metricbeat}} docs) |
 | `traefik/metrics` | Periodically fetches metrics from a [Traefik](https://traefik.io/) instance. | [Traefik module](beats://reference/metricbeat/metricbeat-module-traefik.md) ({{metricbeat}} docs) |
 | `uwsgi/metrics` | By default, collects the uWSGI stats metricset, using [StatsServer](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.html). | [uWSGI module](beats://reference/metricbeat/metricbeat-module-uwsgi.md) ({{metricbeat}} docs) |
@@ -95,10 +95,10 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | `event/tcp` | Alias for `tcp`. | n/a |
 | `filestream` | Reads lines from active log files. Replaces and imporoves on the `log` input. | [filestream input](beats://reference/filebeat/filebeat-input-filestream.md) ({{filebeat}} docs) |
 | `gcp-pubsub` | Reads messages from a Google Cloud Pub/Sub topic subscription. | [GCP Pub/Sub input](beats://reference/filebeat/filebeat-input-gcp-pubsub.md) ({{filebeat}} docs) |
-| `gcs` | [beta] Reads content from files stored in buckets which reside on your Google Cloud. | [Google Cloud Storage input](beats://reference/filebeat/filebeat-input-gcs.md) ({{filebeat}} docs) |
-| `http_endpoint` | [beta] Initializes a listening HTTP server that collects incoming HTTP POST requests containing a JSON body. | [HTTP Endpoint input](beats://reference/filebeat/filebeat-input-http_endpoint.md) ({{filebeat}} docs) |
+| `gcs` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Reads content from files stored in buckets which reside on your Google Cloud. | [Google Cloud Storage input](beats://reference/filebeat/filebeat-input-gcs.md) ({{filebeat}} docs) |
+| `http_endpoint` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Initializes a listening HTTP server that collects incoming HTTP POST requests containing a JSON body. | [HTTP Endpoint input](beats://reference/filebeat/filebeat-input-http_endpoint.md) ({{filebeat}} docs) |
 | `httpjson` | Read messages from an HTTP API with JSON payloads. | [HTTP JSON input](beats://reference/filebeat/filebeat-input-httpjson.md) ({{filebeat}} docs) |
-| `journald` | [beta] A system service that collects and stores logging data. | [Journald input](beats://reference/filebeat/filebeat-input-journald.md) ({{filebeat}} docs) |
+| `journald` | {applies_to}`stack: beta` {applies_to}`serverless: beta` A system service that collects and stores logging data. | [Journald input](beats://reference/filebeat/filebeat-input-journald.md) ({{filebeat}} docs) |
 | `kafka` | Reads from topics in a Kafka cluster. | [Kafka input](beats://reference/filebeat/filebeat-input-kafka.md) ({{filebeat}} docs) |
 | `log` | DEPRECATED: Use the `filestream` input instead. | n/a |
 | `logfile` | Alias for `log`. | n/a |
@@ -106,13 +106,13 @@ When you [configure inputs](/reference/fleet/elastic-agent-input-configuration.m
 | `log/syslog` | Alias for `syslog`. | n/a |
 | `mqtt` | Reads data transmitted using lightweight messaging protocol for small and mobile devices, optimized for high-latency or unreliable networks. | [MQTT input](beats://reference/filebeat/filebeat-input-mqtt.md) ({{filebeat}} docs) |
 | `netflow` | Reads NetFlow and IPFIX exported flows and options records over UDP. | [NetFlow input](beats://reference/filebeat/filebeat-input-netflow.md) ({{filebeat}} docs) |
-| `o365audit` | [beta] Retrieves audit messages from Office 365 and Azure AD activity logs. | [Office 365 Management Activity API input](beats://reference/filebeat/filebeat-input-o365audit.md) ({{filebeat}} docs) |
+| `o365audit` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Retrieves audit messages from Office 365 and Azure AD activity logs. | [Office 365 Management Activity API input](beats://reference/filebeat/filebeat-input-o365audit.md) ({{filebeat}} docs) |
 | `osquery` | Collects and decodes the result logs written by [osqueryd](https://osquery.readthedocs.io/en/latest/introduction/using-osqueryd/) in the JSON format. | - |
-| `redis` | [beta] Reads entries from Redis slowlogs. | [Redis input](beats://reference/filebeat/index.md) ({{filebeat}} docs) |
+| `redis` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Reads entries from Redis slowlogs. | [Redis input](beats://reference/filebeat/index.md) ({{filebeat}} docs) |
 | `syslog` | Reads Syslog events as specified by RFC 3164 and RFC 5424, over TCP, UDP, or a Unix stream socket. | [Syslog input](beats://reference/filebeat/filebeat-input-syslog.md) ({{filebeat}} docs) |
 | `tcp` | Reads events over TCP. | [TCP input](beats://reference/filebeat/filebeat-input-tcp.md) ({{filebeat}} docs) |
 | `udp` | Reads events over UDP. | [UDP input](beats://reference/filebeat/filebeat-input-udp.md) ({{filebeat}} docs) |
-| `unix` | [beta] Reads events over a stream-oriented Unix domain socket. | [Unix input](beats://reference/filebeat/index.md) ({{filebeat}} docs) |
+| `unix` | {applies_to}`stack: beta` {applies_to}`serverless: beta` Reads events over a stream-oriented Unix domain socket. | [Unix input](beats://reference/filebeat/index.md) ({{filebeat}} docs) |
 | `winlog` | Reads from one or more event logs using Windows APIs, filters the events based on user-configured criteria, then sends the event data to the configured outputs ({{es}} or {{ls}}). | [Winlogbeat Overview](beats://reference/winlogbeat/index.md) ({{winlogbeat}} docs) |
 
 ::::
diff --git a/solutions/observability/apm/apm-server/configure-logging.md b/solutions/observability/apm/apm-server/configure-logging.md
index 0c4efdefba..55994980e0 100644
--- a/solutions/observability/apm/apm-server/configure-logging.md
+++ b/solutions/observability/apm/apm-server/configure-logging.md
@@ -154,7 +154,10 @@ Enable log file rotation on time intervals in addition to size-based rotation. I
 
 If the log file already exists on startup, immediately rotate it and start writing to a new file instead of appending to the existing one. Defaults to true.
 
-### `logging.files.redirect_stderr` [preview] [_logging_files_redirect_stderr]
+### `logging.files.redirect_stderr` [_logging_files_redirect_stderr]
+```{applies_to}
+stack: preview
+```
 
 When true, diagnostic messages printed to APM Server’s standard error output will also be logged to the log file. This can be helpful in situations were APM Server terminates unexpectedly because an error has been detected by Go’s runtime but diagnostic information is not present in the log file. This feature is only available when logging to files (`logging.to_files` is true). Disabled by default.
 
diff --git a/solutions/observability/apm/applications-ui-settings.md b/solutions/observability/apm/applications-ui-settings.md
index eef469b4e1..64478c7b0c 100644
--- a/solutions/observability/apm/applications-ui-settings.md
+++ b/solutions/observability/apm/applications-ui-settings.md
@@ -29,8 +29,8 @@ stack: ga 9.1
 
 To change APM settings, select **Settings** from any **Applications** page. The following settings are available.
 
-`observability:apmAgentExplorerView`
-:   [beta] Enables the Agent explorer view.
+`observability:apmAgentExplorerView` {applies_to}`stack: beta`
+:   Enables the Agent explorer view.
 
 `observability:apmAWSLambdaPriceFactor`
 :   Set the price per Gb-second for your AWS Lambda functions.
@@ -38,11 +38,11 @@ To change APM settings, select **Settings** from any **Applications** page. The
 `observability:apmAWSLambdaRequestCostPerMillion`
 :   Set the AWS Lambda cost per million requests.
 
-`observability:apmEnableContinuousRollups`
-:   [beta] When continuous rollups are enabled, the UI will select metrics with the appropriate resolution. On larger time ranges, lower resolution metrics will be used, which will improve loading times.
+`observability:apmEnableContinuousRollups` {applies_to}`stack: beta`
+:   When continuous rollups are enabled, the UI will select metrics with the appropriate resolution. On larger time ranges, lower resolution metrics will be used, which will improve loading times.
 
-`observability:apmEnableServiceMetrics`
-:   [beta] Enables the usage of service transaction metrics, which are low cardinality metrics that can be used by certain views like the service inventory for faster loading times.
+`observability:apmEnableServiceMetrics` {applies_to}`stack: beta`
+:   Enables the usage of service transaction metrics, which are low cardinality metrics that can be used by certain views like the service inventory for faster loading times.
 
 `observability:apmLabsButton`
 :   Enable or disable the APM Labs button — a quick way to enable and disable technical preview features in APM.
diff --git a/solutions/observability/incident-management/create-manage-cases.md b/solutions/observability/incident-management/create-manage-cases.md
index 6741d7d647..de5d3c8adc 100644
--- a/solutions/observability/incident-management/create-manage-cases.md
+++ b/solutions/observability/incident-management/create-manage-cases.md
@@ -20,7 +20,7 @@ Open a new case to keep track of issues and share the details with colleagues. T
 
 1. Find **Cases** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. Click **Create case**.
-3. (Optional) If you defined [templates](/solutions/observability/incident-management/configure-case-settings.md#observability-case-templates), select one to use its default field values. [preview]
+3. {applies_to}`stack: preview` {applies_to}`serverless: preview` (Optional) If you defined [templates](/solutions/observability/incident-management/configure-case-settings.md#observability-case-templates), select one to use its default field values.
 4. Give the case a name, severity, and description.
 
     ::::{tip}
diff --git a/solutions/search/cross-cluster-search.md b/solutions/search/cross-cluster-search.md
index 259498c943..23da247c35 100644
--- a/solutions/search/cross-cluster-search.md
+++ b/solutions/search/cross-cluster-search.md
@@ -27,8 +27,8 @@ The following APIs support {{ccs}}:
 * [Resolve Index API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index)
 * [Vector tile search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search-mvt)
 * {applies_to}`stack: preview 9.0, ga 9.1` [ES|QL](elasticsearch://reference/query-languages/esql/esql-cross-clusters.md)
-* [preview] [EQL search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-eql-search)
-* [preview] [SQL search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-sql-query)
+* {applies_to}`stack: preview` [EQL search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-eql-search)
+* {applies_to}`stack: preview` [SQL search](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-sql-query)
 
 
 ## Prerequisites [_prerequisites]
diff --git a/solutions/security/investigate/open-manage-cases.md b/solutions/security/investigate/open-manage-cases.md
index 44104f3e42..7c892b5bbf 100644
--- a/solutions/security/investigate/open-manage-cases.md
+++ b/solutions/security/investigate/open-manage-cases.md
@@ -22,7 +22,7 @@ You can create and manage cases using the UI or the [cases API](https://www.elas
 Open a new case to keep track of security issues and share their details with colleagues.
 
 1. Find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Create case**. If no cases exist, the Cases table will be empty and you’ll be prompted to create one by clicking the **Create case** button inside the table.
-2. If you defined [templates](/solutions/security/investigate/configure-case-settings.md#cases-templates), you can optionally select one to use its default field values. [preview]
+2. {applies_to}`stack: preview` {applies_to}`serverless: preview` If you defined [templates](/solutions/security/investigate/configure-case-settings.md#cases-templates), you can optionally select one to use its default field values.
 3. Give the case a name, assign a severity level, and provide a description. You can use [Markdown](https://www.markdownguide.org/cheat-sheet) syntax in the case description.
 
     ::::{note}
@@ -35,7 +35,7 @@ Open a new case to keep track of security issues and share their details with co
     ::::
 
 4. Optionally, add a category, assignees and relevant tags. You can add users only if they meet the necessary [prerequisites](/solutions/security/investigate/cases-requirements.md).
-5. If you defined [custom fields](/solutions/security/investigate/configure-case-settings.md#cases-ui-custom-fields), they appear in the **Additional fields** section. [preview]
+5. {applies_to}`stack: preview` {applies_to}`serverless: preview` If you defined [custom fields](/solutions/security/investigate/configure-case-settings.md#cases-ui-custom-fields), they appear in the **Additional fields** section.
 6. Choose if you want alert statuses to sync with the case’s status after they are added to the case. This option is enabled by default, but you can turn it off after creating the case.
 7. From **External incident management**, select a [connector](/solutions/security/investigate/configure-case-settings.md#cases-ui-integrations). If you’ve previously added one, that connector displays as the default selection. Otherwise, the default setting is `No connector selected`.
 8. Click **Create case**.
diff --git a/troubleshoot/kibana/alerts.md b/troubleshoot/kibana/alerts.md
index e8c7d4038d..8d5e8c7207 100644
--- a/troubleshoot/kibana/alerts.md
+++ b/troubleshoot/kibana/alerts.md
@@ -67,7 +67,7 @@ curl -X POST -k \
  -d '{"params":{"subject":"hallo","message":"hallo!","to":["me@example.com"]}}'
 ```
 
-[preview] In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
+{applies_to}`stack: preview` {applies_to}`serverless: preview` In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
 
 ```txt
 npm install -g pmuellr/kbn-action
diff --git a/troubleshoot/observability/troubleshoot-your-universal-profiling-agent-deployment.md b/troubleshoot/observability/troubleshoot-your-universal-profiling-agent-deployment.md
index 19872fb8f4..0e29a4c71c 100644
--- a/troubleshoot/observability/troubleshoot-your-universal-profiling-agent-deployment.md
+++ b/troubleshoot/observability/troubleshoot-your-universal-profiling-agent-deployment.md
@@ -183,9 +183,12 @@ The following examples provide a `tolerations` config that you can add to the He
 Some {{k8s}} clusters are configured with hardened security add-ons to limit the blast radius of exploited application vulnerabilities. Different hardening methodologies can impair Universal Profiling Agent operations and may, for example, result in pods continuously restarting after displaying a `CrashLoopBackoff` status.
 
 
-#### {{k8s}} PodSecurityPolicy ([deprecated](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/)) [profiling-kubernetes-podsecuritypolicy]
+#### {{k8s}} PodSecurityPolicy [profiling-kubernetes-podsecuritypolicy]
+```{applies_to}
+stack: deprecated
+```
 
-This {{k8s}} API has been deprecated, but some still use it. A PodSecurityPolicy (PSP) may explicitly prevent the execution of `privileged` containers across the entire cluster.
+This {{k8s}} API [has been deprecated](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/), but some still use it. A PodSecurityPolicy (PSP) may explicitly prevent the execution of `privileged` containers across the entire cluster.
 
 Since Universal Profiling Agent *needs* privileges in most kernels/CRI, you need to build a PSP to allow the Universal Profiling Agent DaemonSet to run.