From 84439f3f225f0f9fb35e054b00b1676e407cab5a Mon Sep 17 00:00:00 2001
From: ajaiswals <97758648+ajaiswals@users.noreply.github.com>
Date: Mon, 13 Jan 2025 08:26:26 -0800
Subject: [PATCH] Update ms-azure-event-hubs-source.md

Removing IP restriction messaging. Improvements are made to support it.
---
 .../azure-monitoring/ms-azure-event-hubs-source.md             | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md
index 353396ef6d..68c72b6d4b 100644
--- a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md
+++ b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md
@@ -7,9 +7,6 @@ description: The Azure Event Hubs Source for Logs provides a secure endpoint to
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import ForwardToSiem from '/docs/reuse/forward-to-siem.md';
 
-:::note
-Azure Event Hubs for Logs is preferred for higher throughput but does not support IP restrictions. We recommend using the [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source) if you have IP address restrictions on Event Hubs. If you require higher throughput and have IP address restrictions on Event Hubs, consider splitting your Event Hubs into smaller namespaces, each staying within the 1MB/s (86GB/day) limit, and create a Cloud-to-Cloud collection method for each namespace.
-:::
 
 The Azure Event Hubs Source provides a secure endpoint to receive data from Azure Event Hubs. It securely stores the required authentication, scheduling, and state tracking information.