diff --git a/docs/en/observability/apm/view-and-analyze/ui-overview/index.asciidoc b/docs/en/observability/apm/view-and-analyze/ui-overview/index.asciidoc
index d371f73c3e..a1d4ea7893 100644
--- a/docs/en/observability/apm/view-and-analyze/ui-overview/index.asciidoc
+++ b/docs/en/observability/apm/view-and-analyze/ui-overview/index.asciidoc
@@ -21,7 +21,6 @@ View an individual service:
 :leveloffset: +1
 
 include::services.asciidoc[]
-include::new-experience-services.asciidoc[]
 include::traces.asciidoc[]
 include::dependencies.asciidoc[]
 include::service-maps.asciidoc[]
diff --git a/docs/en/observability/apm/view-and-analyze/ui-overview/new-experience-services.asciidoc b/docs/en/observability/apm/view-and-analyze/ui-overview/new-experience-services.asciidoc
deleted file mode 100644
index af07f5fc56..0000000000
--- a/docs/en/observability/apm/view-and-analyze/ui-overview/new-experience-services.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[new-experience-services]]
-= New services experience
-
-preview::[]
-
-With this technical preview,
-Elastic expands the **Services** inventory to include services found in logs.
-This means you can monitor the services you care about even if you only have logs
-and aren't ready to instrument your services.
-
-The new **Services** inventory shows services instrumented with APM or OpenTelemetry,
-plus any services declared using `service.name` in your logs:
-
-[role="screenshot"]
-image::images/entity-centric-services-inventory.png[Services inventory that shows APM data and log data]
-
-For instrumented services that also have custom logs, the APM and log data are displayed in the same view.
-For services that only have log data,
-the log data is displayed, and you have the option of adding APM later.
-
-NOTE: The new **Services** inventory requires the Elastic Entity Model (EEM). To learn more, refer to <<elastic-entity-model>>.
-
-[discrete]
-== Turn on the new experience
-
-The new services experience is turned off by default. To turn it on:
-
-. Go to **{observability}** → **Applications** → **Services**.
-. Click **Try out Elastic's new experience!**
-
-If you have the correct privileges, the EEM will be turned on automatically.
-Otherwise, you need to ask your administrator to turn on this feature under **Stack Management**.
-
-To turn off the new experience, click **Restore classic view**.
-You can switch back and forth between the new and classic views whenever you want.
-
-****
-**Does turning on the new experience affect other users?**
-
-No. The settings are applied at the browser level,
-which means that other users need to turn on the new experience if they want to use it.
-****
-
-[discrete]
-== Add services to the inventory
-
-To add services to the inventory, use one of the following approaches:
-
-* Instrument your services with APM or OpenTelemetry.
-To learn how, refer to <<get-started-with-fleet-apm-server>>.
-* Declare `service.name` in your logs. To learn how, <<add-logs-service-name>>.
diff --git a/docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc b/docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc
index 6b3a44b247..95b0b65ba3 100644
--- a/docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc
+++ b/docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc
@@ -14,7 +14,7 @@ In addition to health status, active alerts for each service are prominently dis
 [role="screenshot"]
 image::./images/apm-services-overview.png[Example view of services table the Applications UI in Kibana]
 
-TIP: Want to monitor service logs without instrumenting all your services? Learn about our <<new-experience-services>>.
+TIP: Want to monitor service logs without instrumenting all your services? Learn about our <<inventory>>.
 
 [float]
 [[service-groups]]