diff --git a/content/en/network_monitoring/cloud_network_monitoring/setup.md b/content/en/network_monitoring/cloud_network_monitoring/setup.md
index 1222eed45ae41..5c95234fe7462 100644
--- a/content/en/network_monitoring/cloud_network_monitoring/setup.md
+++ b/content/en/network_monitoring/cloud_network_monitoring/setup.md
@@ -90,7 +90,7 @@ Cloud Network Monitoring supports use of the following provisioning systems:
 
 ## Setup
 
-Given this tool's focus and strength is in analyzing traffic _between_ network endpoints and mapping network dependencies, it is recommended to install it on a meaningful subset of your infrastructure and a **_minimum of 2 hosts_** to maximize value.
+Cloud Network Monitoring is designed to analyze traffic _between_ network endpoints and map network dependencies. Datadog recommends installing CNM on a meaningful subset of your infrastructure and a **_minimum of 2 hosts_** to maximize value.
 
 {{< tabs >}}
 {{% tab "Agent (Linux)" %}}
@@ -395,11 +395,10 @@ If you already have the [Agent running with a manifest][4]:
 [5]: https://github.com/DataDog/helm-charts/blob/main/charts/datadog/values.yaml#L1519-L1523
 {{% /tab %}}
 {{% tab "Operator" %}}
-<div class="alert alert-warning">The Datadog Operator is Generally Available with the `1.0.0` version, and it reconciles the version `v2alpha1` of the DatadogAgent Custom Resource. </div>
 
-[The Datadog Operator][1] is a way to deploy the Datadog Agent on Kubernetes and OpenShift. It reports deployment status, health, and errors in its Custom Resource status, and it limits the risk of misconfiguration thanks to higher-level configuration options.
+[The Datadog Operator][1] simplifies deploying the Datadog Agent on Kubernetes and OpenShift. It provides deployment status, health, and error reporting through its Custom Resource status, while reducing the risk of misconfiguration with higher-level configuration options.
 
-To enable Cloud Network Monitoring in Operator, use the following configuration:
+To enable Cloud Network Monitoring on the Datadog Operator, use the following configuration:
 
 ```yaml
 apiVersion: datadoghq.com/v2alpha1
@@ -412,7 +411,7 @@ spec:
       enabled: true
 ```
 
-[1]: https://github.com/DataDog/datadog-operator
+[1]: /containers/datadog_operator 
 {{% /tab %}}
 {{% tab "Docker" %}}
 
@@ -474,10 +473,55 @@ services:
 [1]: https://app.datadoghq.com/organization-settings/api-keys
 {{% /tab %}}
 {{% tab "ECS" %}}
-To set up on Amazon ECS, see the [Amazon ECS][1] documentation page.
+To set up CNM on Amazon ECS, see the [Amazon ECS][1] documentation page.
 
 
 [1]: /agent/amazon_ecs/#network-performance-monitoring-collection-linux-only
+{{% /tab %}}
+
+{{% tab "ECS Fargate" %}}
+
+<div class="alert alert-info">ECS Fargate for CNM is in Preview. Reach out to your Datadog representative to sign up.</div>
+
+To enable Cloud Network Monitoring on ECS Fargate, use the following instructions:
+
+**Requires Agent version `7.58` or higher**.
+
+- For a new Fargate deployment, configure the Datadog Agent to monitor Fargate on ECS by enabling [process collection][1] on your Fargate hosts.
+
+- For existing deployments, update your `task.json` file to include the following configuration settings:
+
+```json
+{
+ "containerDefinitions": [
+   (...)
+     "environment": [
+       (...)
+       {
+         "name": "DD_SYSTEM_PROBE_NETWORK_ENABLED",
+         "value": "true"
+       },
+       {
+          "name": "DD_NETWORK_CONFIG_ENABLE_EBPFLESS",
+          "value": "true"
+       },
+       {
+          "name": "DD_PROCESS_AGENT_ENABLED",
+          "value": "true"
+       }      
+     ],
+     "linuxParameters": {
+      "capabilities": {
+        "add": [
+          "SYS_PTRACE"
+        ]
+      }
+    },
+ ],
+}
+```
+[1]: /integrations/ecs_fargate/?tab=webui#process-collection 
+
 {{% /tab %}}
 {{< /tabs >}}