Merge pull request #9464 from ProfessorKendrick/observability-updates

Amson Liu · web-flow · commit aaab4867580e · 2025-08-13T10:44:39.000-04:00
AB#7089: Azure Native Integrations updates
diff --git a/support/azure/partner-solutions/.openpublishing.redirection.azure.json b/support/azure/partner-solutions/.openpublishing.redirection.azure.json
@@ -0,0 +1,9 @@
+{
+    "redirections": [
+      {
+        "source_path": "welcome-native-integrations.yml",
+        "redirect_url": "index.yml",
+        "redirect_document_id": false
+      }
+    ]
+}
diff --git a/support/azure/partner-solutions/diagnostic-settings-manual-update.md b/support/azure/partner-solutions/diagnostic-settings-manual-update.md
@@ -0,0 +1,38 @@
+---
+title: Manual Updates to Diagnostic Settings Created via Tag Rules
+description: "Understand the limitations and behavior when manually updating diagnostic settings that are created based on tag rules in Azure."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.date: 08/04/2025
+ai-usage: ai-assisted
+---
+
+# Manual Updates to Diagnostic Settings Created via Tag Rules
+
+This article explains the behavior and limitations when attempting to manually update diagnostic settings that are created automatically based on tag rules in Azure.
+
+## Symptoms
+
+- Changes made to log categories in the diagnostic settings page don't persist.
+- Unchecked log categories revert to their default settings after saving.
+- Modifying destination details results in a new diagnostic setting being created with the original configuration.
+- Unable to customize diagnostic settings other than those defined by tag rules.
+
+## Cause
+
+Diagnostic settings created via tag rules are managed automatically. Manual changes to log categories through the Azure portal aren't supported. Even if you uncheck log categories and save, the settings will revert to the defaults specified by the tag rules. If you modify destination details, a new diagnostic setting is created with the original configuration, subject to the Azure limitation of a maximum of five diagnostic settings per resource.
+
+## Solution
+
+- To change the configuration, update the tag rules that govern the diagnostic settings.
+- If you need to modify destination details, ensure you don't exceed the maximum of five diagnostic settings per resource.
+
+> [!TIP]
+> For more information about diagnostic settings and tag rules, see [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings).
+
+## Related content
+
+- [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)
+- [Resource tag rules in Azure](/azure/azure-resource-manager/management/tag-resources)
diff --git a/support/azure/partner-solutions/diagnostic-settings.md b/support/azure/partner-solutions/diagnostic-settings.md
@@ -0,0 +1,47 @@
+---
+title: Diagnostic Settings Not Created as Expected After Moving a Resource
+description: "Resolve issues where diagnostic settings are missing or not created as expected after moving, renaming, or recreating Azure resources."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.date: 08/04/2025
+ai-usage: ai-assisted
+---
+
+# Diagnostic Settings Not Created as Expected After Moving a Resource
+
+This article helps you resolve issues where diagnostic settings are missing or not created as expected after moving, renaming, or recreating an Azure resource.
+
+## Symptoms
+
+- After moving, renaming, or recreating a resource, expected diagnostic settings are missing.
+- Log and metric data isn't being collected or forwarded as previously configured.
+- Diagnostic settings don't appear on the resource after migration or recreation.
+
+## Cause
+
+When you move, rename, or migrate a resource across resource groups or subscriptions, diagnostic settings aren't always moved with the resource. If you delete a resource and then recreate it with the same name, the diagnostic settings from the deleted resource might be automatically included with the new resource, depending on the resource type and configuration. This can result in either missing diagnostic settings or unexpected settings being applied.
+
+## Solution
+
+To ensure diagnostic settings behave as expected when moving, renaming, or recreating resources:
+
+1. **Before moving, renaming, or deleting a resource:**
+    - Go to the [Azure portal](https://portal.azure.com) and sign in.
+    - Locate the resource you plan to move, rename, or delete.
+    - In the left-hand menu, select **Diagnostic settings** under the **Monitoring** section.
+    - Review and delete all diagnostic settings associated with the resource.
+
+2. **After moving or recreating a resource:**
+    - Verify that the diagnostic settings are present and configured as needed.
+    - If diagnostic settings are missing, manually recreate them to resume log and metric collection.
+    - If unexpected diagnostic settings are present, review and update or remove them as appropriate.
+
+> [!TIP]
+> Always delete diagnostic settings for resources you plan to delete or no longer use. This helps keep your environment clean and prevents unexpected data collection or forwarding.
+
+## Related content
+
+- [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)
+- [Lock resources using the Azure portal](/azure/azure-resource-manager/management/manage-resources-portal)
diff --git a/support/azure/partner-solutions/index.yml b/support/azure/partner-solutions/index.yml
@@ -25,7 +25,21 @@ landingContent:
             url: marketplace-purchases-errors.md
 
 # Card
-  - title:  Azure Native New Relic Service
+  - title: Observability partners
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Diagnostic settings manual update
+            url: diagnostic-settings-manual-update.md
+          - text: Diagnostic settings not created
+            url: diagnostic-settings.md
+          - text: Log forwarding persists
+            url: log-forwarding-persists.md
+          - text: Log limitations
+            url: log-limitations.md
+
+# Card
+  - title:  New Relic
     linkLists:
       - linkListType: how-to-guide
         links:
diff --git a/support/azure/partner-solutions/log-forwarding-persists.md b/support/azure/partner-solutions/log-forwarding-persists.md
@@ -0,0 +1,43 @@
+---
+title: Log Forwarding Persists After Service Is Disabled
+description: "Learn how to resolve persistent log forwarding in Azure when a service is disabled but diagnostic settings remain active due to a delete lock."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution 
+ms.date: 08/04/2025
+ai-usage: ai-assisted
+---
+
+# Log Forwarding Persists After Service Is Disabled
+
+This article addresses a scenario where log forwarding continues unexpectedly after an Azure Native Integrations service is disabled. It explains the underlying cause and provides steps to resolve the issue by managing resource locks in Azure.
+
+> [!TIP]
+> If the delete lock is removed *after* the service has already been deleted, the diagnostic settings must be manually cleaned up to stop log forwarding.
+
+## Symptoms
+
+Logs continue to be emitted and diagnostic settings remain active on monitored resources, even after the service is disabled or tag rules are modified to exclude certain resources.
+
+## Cause
+
+A delete lock is applied to the resource or the resource group containing the resource. This lock prevents the cleanup of diagnostic settings, which causes logs to continue being forwarded.
+
+## Solution
+
+To remove the delete lock from the affected resource or resource group:
+
+1. Go to [Azure Portal](https://portal.azure.com) and sign in using your Azure credentials.
+1. Use the **Search** bar at the top of the portal to locate the specific **resource** or **resource group**.
+1. Select the resource name to open its **Overview** page.
+1. In the left-hand menu, under the **Settings** section, select **Locks**.
+1. You’ll see a list of any **management locks** applied to the resource.
+1. Look for a lock with **Lock type: Delete** (often labeled as `CanNotDelete`).
+1. Select the **ellipsis (⋯)** next to the lock entry.
+1. Choose **Delete** from the dropdown menu.
+1. Confirm the deletion when prompted.
+
+## Related content
+[Lock resources using the Azure portal](/azure/azure-resource-manager/management/manage-resources-portal)
+[Configure locks - Azure portal](/azure/azure-resource-manager/management/lock-resources?tabs=json)
diff --git a/support/azure/partner-solutions/log-limitations.md b/support/azure/partner-solutions/log-limitations.md
@@ -0,0 +1,83 @@
+---
+title: Troubleshoot log emission and diagnostic settings limitations for Azure partner service integration
+description: "Learn how to identify and resolve issues with log emission and diagnostic settings when integrating Azure resources with partner solutions."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: partner-services
+ms.topic: troubleshooting-general
+ms.date: 08/04/2025
+ai.usage: ai-assisted
+
+#customer intent: As an Azure administrator, I want to understand and resolve issues with log emission and diagnostic settings for partner service integrations so that I can ensure logs are properly sent and monitored.
+
+---
+
+# Troubleshoot log emission and diagnostic settings limitations for Azure partner service integration
+
+This article helps you identify and resolve issues that prevent Azure resources from emitting logs to partner services. It covers common causes, limitations of diagnostic settings, and steps to verify and correct configuration issues.
+
+## Prerequisites
+
+- Access to the Azure portal.
+- Sufficient permissions to view and modify diagnostic settings on Azure resources.
+- Knowledge of the partner solution integration requirements.
+
+## Potential quick workarounds
+
+1. Remove unused diagnostic settings if the resource has reached the maximum allowed.
+1. Confirm that the resource type supports diagnostic settings and log categories.
+
+## Troubleshooting checklist
+
+### Verify resource log support
+
+- Navigate to the Azure portal and select the affected resource.
+- Go to **Diagnostic settings**.
+- Check if you can add a new diagnostic setting. If not, the resource may not support log emission.
+
+### Check diagnostic settings limit
+
+- Each Azure resource supports up to five diagnostic settings.
+- If you see an error about reaching the maximum, remove unused settings before adding new ones.
+
+### Confirm metrics export limitation
+
+- Metrics data export is not supported for partner solutions via Azure Monitor diagnostic settings. Only log data can be sent.
+
+## Causes and/or solutions
+
+### Cause: Resource does not support log emission
+
+Some Azure resource types do not emit logs because they lack monitoring log categories.
+
+**Solution:**
+
+1. Review the [Azure Monitor supported resource log categories](/azure/azure-monitor/essentials/resource-logs-categories).
+1. If your resource is not listed, it cannot emit logs to partner services.
+
+### Cause: Diagnostic settings limit reached
+
+Each resource can have a maximum of five diagnostic settings.
+
+**Solution:**
+
+1. Remove unused diagnostic settings from the resource.
+1. Add a new diagnostic setting for the partner service.
+
+### Cause: Metrics data not exported
+
+Export of metrics data is not currently supported for partner solutions.
+
+**Solution:**
+- Only log data can be sent to the partner service. No action is needed for metrics.
+
+## Advanced troubleshooting and data collection
+
+- Collect screenshots of the diagnostic settings pane for the affected resource.
+- Note any error messages or warnings shown when configuring diagnostic settings.
+- Gather the resource type and region information for support escalation.
+
+## Related content
+
+- [Azure Monitor supported resource log categories](/azure/azure-monitor/essentials/resource-logs-categories)
+- [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)
diff --git a/support/azure/partner-solutions/toc.yml b/support/azure/partner-solutions/toc.yml
@@ -2,8 +2,46 @@
   href: welcome-native-integrations.yml
 - name: Marketplace purchase errors
   href: marketplace-purchases-errors.md
-- name: Azure Native New Relic Service
+- name: Datadog
+  items: 
+    - name: Diagnostic settings manual update
+      href: diagnostic-settings-manual-update.md
+    - name: Diagnostic settings not created
+      href: diagnostic-settings.md
+    - name: Log forwarding persists
+      href: log-forwarding-persists.md
+    - name: Log limitations
+      href: log-limitations.md
+- name: Dynatrace
+  items: 
+    - name: Diagnostic settings manual update
+      href: diagnostic-settings-manual-update.md
+    - name: Diagnostic settings not created
+      href: diagnostic-settings.md
+    - name: Log forwarding persists
+      href: log-forwarding-persists.md
+    - name: Log limitations
+      href: log-limitations.md
+- name: Elastic
   items:
+    - name: Diagnostic settings manual update
+      href: diagnostic-settings-manual-update.md 
+    - name: Diagnostic settings not created
+      href: diagnostic-settings.md
+    - name: Log forwarding persists
+      href: log-forwarding-persists.md
+    - name: Log limitations
+      href: log-limitations.md
+- name: New Relic
+  items:
+    - name: Diagnostic settings manual update
+      href: diagnostic-settings-manual-update.md
+    - name: Diagnostic settings not created
+      href: diagnostic-settings.md
     - name: Ingestion key rotation resolution
       href: ingestion-key-rotation-log-flow.md
+    - name: Log forwarding persists
+      href: log-forwarding-persists.md
+    - name: Log limitations
+      href: log-limitations.md
 
