Remove details

Author: kilfoyle

docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc

@@ -7,18 +7,13 @@ Beginning in version 8.12.0, you can send {agent} data to a remote {es} cluster.
 
 A remote {es} cluster supports the same <<es-output-settings,output settings>> as your main {es} cluster.
 
-[WARNING] 
-==== 
-There are currently some limitations with using {elastic-defend} when a remote {es} output is configured for an agent. These issues are currently being investigated and are expected to be resolved in an upcoming release:
-
-* {elastic-defend} response actions do not display results in the management cluster, instead the results go to the output cluster.
-* Restrictions on workflows for Endpoint with the {security-app}:
-
-** Endpoint list page - Elastic Endpoint state documents go to the output cluster so the management cluster doesn't have access to their status.
-** Endpoint exceptions - Endpoint exceptions need to be added in the management cluster. Alerts are sent to the output cluster but "Add Endpoint Exception" workflows don't currently work there.
+[NOTE] 
 ====
+Note the following restrictions with the remote {es} output:
 
-NOTE: Using a remote {es} output with a target cluster that has {cloud}/ec-traffic-filtering-deployment-configuration.html[traffic filters] enabled is not currently supported.
+* Using a remote {es} output with a target cluster that has {cloud}/ec-traffic-filtering-deployment-configuration.html[traffic filters] enabled is not currently supported.
+* Using {elastic-defend} is currently not supported when a remote {es} output is configured for an agent.
+====
 
 To configure a remote {es} cluster for your {agent} data: