From a0e5118366ebc2d1bba708e1e4c81073999d854a Mon Sep 17 00:00:00 2001
From: nconvery <119965217+nconvery@users.noreply.github.com>
Date: Fri, 15 Aug 2025 12:04:26 -0400
Subject: [PATCH] Update diagnostic-settings.md

Diagnostic Settings do not automatically resume resource log collection upon recreation of the deleted resource, this is only true for RPs that do not rely on linked notifications
---
 articles/azure-monitor/platform/diagnostic-settings.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/azure-monitor/platform/diagnostic-settings.md b/articles/azure-monitor/platform/diagnostic-settings.md
index 658447ee0e..fae61ee42d 100644
--- a/articles/azure-monitor/platform/diagnostic-settings.md
+++ b/articles/azure-monitor/platform/diagnostic-settings.md
@@ -22,7 +22,7 @@ The following video walks through routing resource platform logs with diagnostic
 > [!VIDEO https://learn-video.azurefd.net/vod/player?id=2e9e11cc-fc03-4caa-8fee-4386abf454bc]
 
 > [!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. 
+> 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. For some resource types this would resume the collection of resource logs as defined in the diagnostic setting. 
 
 ## Sources