Merge pull request #112469 from spelluru/sbusnote0423

added note

Author: PRMerger19

articles/service-bus-messaging/private-link-service.md

@@ -18,7 +18,21 @@ A private endpoint is a network interface that connects you privately and secure
 
 For more information, see [What is Azure Private Link?](../private-link/private-link-overview.md)
 
-> [!NOTE]
+>[!WARNING]
+> Implementing private endpoints can prevent other Azure services from interacting with Service Bus.
+>
+> Trusted Microsoft services are not supported when Virtual Networks are implemented.
+>
+> Common Azure scenarios that don't work with Virtual Networks (note that the list is **NOT** exhaustive) -
+> - Integration with Azure Event Grid
+> - Azure IoT Hub Routes
+> - Azure IoT Device Explorer
+>
+> The below Microsoft services are required to be on a virtual network
+> - Azure App Service
+> - Azure Functions
+
+> [!IMPORTANT]
 > This feature is supported with the **premium** tier of Azure Service Bus. For more information about the premium tier, see the [Service Bus Premium and Standard messaging tiers](service-bus-premium-messaging.md) article.
 >
 > This feature is currently in **preview**. 

articles/service-bus-messaging/service-bus-ip-filtering.md

@@ -26,6 +26,20 @@ This feature is helpful in scenarios in which Azure Service Bus should be only a
 ## IP firewall rules
 The IP firewall rules are applied at the Service Bus namespace level. Therefore, the rules apply to all connections from clients using any supported protocol. Any connection attempt from an IP address that does not match an allowed IP rule on the Service Bus namespace is rejected as unauthorized. The response does not mention the IP rule. IP filter rules are applied in order, and the first rule that matches the IP address determines the accept or reject action.
 
+>[!WARNING]
+> Implementing Firewall rules can prevent other Azure services from interacting with Service Bus.
+>
+> Trusted Microsoft services are not supported when IP Filtering (Firewall rules) are implemented, and will be made available soon.
+>
+> Common Azure scenarios that don't work with IP Filtering (note that the list is **NOT** exhaustive) -
+> - Integration with Azure Event Grid
+> - Azure IoT Hub Routes
+> - Azure IoT Device Explorer
+>
+> The following Microsoft services are required to be on a virtual network
+> - Azure App Service
+> - Azure Functions
+
 ## Use Azure portal
 This section shows you how to use the Azure portal to create IP firewall rules for a Service Bus namespace. 
 

articles/service-bus-messaging/service-bus-service-endpoints.md

@@ -21,6 +21,20 @@ Once configured to be bound to at least one virtual network subnet service endpo
 
 The result is a private and isolated relationship between the workloads bound to the subnet and the respective Service Bus namespace, in spite of the observable network address of the messaging service endpoint being in a public IP range.
 
+>[!WARNING]
+> Implementing Virtual Networks integration can prevent other Azure services from interacting with Service Bus.
+>
+> Trusted Microsoft services are not supported when Virtual Networks are implemented.
+>
+> Common Azure scenarios that don't work with Virtual Networks (note that the list is **NOT** exhaustive) -
+> - Integration with Azure Event Grid
+> - Azure IoT Hub Routes
+> - Azure IoT Device Explorer
+>
+> The below Microsoft services are required to be on a virtual network
+> - Azure App Service
+> - Azure Functions
+
 > [!IMPORTANT]
 > Virtual Networks are supported only in [Premium tier](service-bus-premium-messaging.md) Service Bus namespaces.
 >