diff --git a/manage-data/ingest/_snippets/agentless-integrations-faq.md b/manage-data/ingest/_snippets/agentless-integrations-faq.md
index 2a655c364d..bc376bed2b 100644
--- a/manage-data/ingest/_snippets/agentless-integrations-faq.md
+++ b/manage-data/ingest/_snippets/agentless-integrations-faq.md
@@ -78,14 +78,9 @@ No, agentless integrations can not use a specific range of static IP addresses f
 
 ## Do agentless integrations work if I'm using traffic filtering?
 
-::::{applies-switch}
-
-:::{applies-item} serverless: ga
-Agentless integrations do not support traffic filtering.
-:::
-
-:::{applies-item} stack: ga 9.1+
-Agentless integrations support traffic filtering. No additional configuration is necessary.
-:::
+```{applies_to}
+stack: ga 9.1+
+serverless: ga
+```
 
-::::
\ No newline at end of file
+Yes. Agentless integrations support traffic filtering, and no additional configuration is necessary.
\ No newline at end of file
diff --git a/manage-data/ingest/agentless/agentless-integrations.md b/manage-data/ingest/agentless/agentless-integrations.md
index eb766a8f66..b6e927fe4f 100644
--- a/manage-data/ingest/agentless/agentless-integrations.md
+++ b/manage-data/ingest/agentless/agentless-integrations.md
@@ -24,7 +24,6 @@ During technical preview, there are no additional costs associated with deployin
 * Agentless integrations are supported only on {{ech}}, {{sec-serverless}}, and {{obs-serverless}} deployments. 
 * On {{ech}}, agentless integrations require a working [{{fleet-server}}](/reference/fleet/fleet-server.md).
 * To set up a new agentless integration, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
-* For {{serverless-short}} deployments, traffic filtering must be turned off.
 
 ## Generally available (GA) agentless integrations