From 6a726fbad3dc6fb91facea664602b274e0b3dc32 Mon Sep 17 00:00:00 2001
From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
Date: Thu, 2 Oct 2025 19:30:56 -0400
Subject: [PATCH] Removes note (#7081)

(cherry picked from commit 2b0f34ac129743453918f5bffbb8d4789b1b7c08)
---
 docs/detections/alert-suppression.asciidoc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/detections/alert-suppression.asciidoc b/docs/detections/alert-suppression.asciidoc
index 320d74ef18..5af1f146a7 100644
--- a/docs/detections/alert-suppression.asciidoc
+++ b/docs/detections/alert-suppression.asciidoc
@@ -23,8 +23,6 @@ Normally, when a rule meets its criteria repeatedly, it creates multiple alerts,
 
 The {security-app} displays several indicators in the Alerts table and the alert details flyout when a detection alert is created with alert suppression enabled. You can view the original events associated with suppressed alerts by investigating the alert in Timeline.
 
-NOTE: Alert suppression is not available for Elastic prebuilt rules. However, if you want to suppress alerts for a prebuilt rule, you can duplicate it, then configure alert suppression on the duplicated rule.
-
 === Configure alert suppression
 
 You can configure alert suppression when you create or edit a supported rule type. Refer to documentation for creating <<create-custom-rule,custom query>>, <<create-threshold-rule, threshold>>, <<create-eql-rule,event correlation>>, <<create-new-terms-rule,new terms>>, <<create-esql-rule,{esql}>>, or <<create-ml-rule,{ml}>> rules for detailed instructions.