From 71ce00c4cc26a3904365007b917f59fcc9227738 Mon Sep 17 00:00:00 2001
From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Date: Wed, 16 Oct 2024 19:10:40 -0400
Subject: [PATCH] Add note: integration-level outputs must be at same sub level
 (#1389)

(cherry picked from commit 479eb333417e77cbae62fe00f24142e72714df92)
---
 .../integrations/integration-level-outputs.asciidoc         | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/en/ingest-management/integrations/integration-level-outputs.asciidoc b/docs/en/ingest-management/integrations/integration-level-outputs.asciidoc
index 009b8a0a6..84541f6fa 100644
--- a/docs/en/ingest-management/integrations/integration-level-outputs.asciidoc
+++ b/docs/en/ingest-management/integrations/integration-level-outputs.asciidoc
@@ -1,9 +1,9 @@
 [[integration-level-outputs]]
 = Set integration-level outputs
 
-If you have an `Enterprise` link:https://www.elastic.co/subscriptions[{stack} subscription], you can configure {agent} data to be sent to different outputs for different integration policies.
-Integration-level outputs are very useful for certain scenarios.
-For example:
+If you have an `Enterprise` link:https://www.elastic.co/subscriptions[{stack} subscription], you can configure {agent} data to be sent to different outputs for different integration policies. Note that the output clusters that you send data to must also be on the same subscription level.
+
+Integration-level outputs are very useful for certain scenarios. For example:
 
 * You can may want to send security logs monitored by an {agent} to one {ls} output, while informational logs are sent to a another {ls} output.
 * If you operate multiple {beats} on a system and want to migrate these to {agent}, integration-level outputs enable you to maintain the distinct outputs that are currently used by each Beat.