diff --git a/articles/azure-monitor/platform/diagnostic-settings.md b/articles/azure-monitor/platform/diagnostic-settings.md
index 6a4245d3c6..c120510ea0 100644
--- a/articles/azure-monitor/platform/diagnostic-settings.md
+++ b/articles/azure-monitor/platform/diagnostic-settings.md
@@ -189,6 +189,11 @@ The following sample template creates a diagnostic setting to send all audit log
 > [!WARNING] 
 > Delete any diagnostic settings for a resource if you delete or rename that resource, or if you migrate it across resource groups or subscriptions. If the diagnostic setting isn't removed and this resource is recreated, any diagnostic settings for the deleted resource could be applied to the new one. This would resume the collection of resource logs as defined in the diagnostic setting. 
 
+> [!WARNING]
+> From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data.
+> This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data.  
+> This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK.
+
 
    
 ## Category groups