From 9e8a5e741dd8777a31b58b94ac82462b0141e61f Mon Sep 17 00:00:00 2001 From: Darren Turchiarelli <107463700+DarrenTurchiarelli@users.noreply.github.com> Date: Wed, 9 Apr 2025 18:56:53 +1000 Subject: [PATCH] Update diagnostic-settings.md Added an additional line item to the 'Requirements and Limitations' subsection. # When specifying a Log Analytics Workspace as the diagnostic setting log destination, there's no need to explicitly define an identity. This is managed within the Azure platform. --- articles/azure-monitor/essentials/diagnostic-settings.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/articles/azure-monitor/essentials/diagnostic-settings.md b/articles/azure-monitor/essentials/diagnostic-settings.md index 4a6544172c..a7ffc93cc7 100644 --- a/articles/azure-monitor/essentials/diagnostic-settings.md +++ b/articles/azure-monitor/essentials/diagnostic-settings.md @@ -109,6 +109,8 @@ After you set up a diagnostic setting, data should start flowing to your selecte If you're experiencing an issue, you can try disabling the configuration and then reenabling it. Contact Azure support through the Azure portal if you continue to have issues. +When specifying a Log Analytics Workspace as the diagnostic setting log destination, there's no need to explicitly define an identity. This is managed within the Azure platform. + ### Metrics as a source There are certain limitations with exporting metrics: