Merge branch 'main' of https://github.com/MicrosoftDocs/SupportArticles-docs-pr into kainawroth-troubleshooting-azuread

kainawroth · kainawroth · commit 65af8f96660a · 2025-10-06T10:44:30.000-07:00
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
@@ -1,8 +1,10 @@
 ---
 title: Troubleshoot Custom Log Table Creation in Azure
 description: Troubleshooting guide for custom log table creation in Azure.
-ms.date: 07/23/2025
-ms.reviewer: v-liuamson; v-gsitser
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
 ms.service: azure-monitor
 ms.custom: Configure and Manage Log analytics tables
 ---
@@ -31,9 +33,11 @@ Users might receive an error message that states "Cannot read properties of unde
 
 5. If the issue persists, try to refresh the Azure portal to make sure that all settings are updated.
 
-## Reference
+## References
 
 - [Create Custom Table in Azure](/azure/azure-monitor/vm/data-collection-log-json#create-custom-table)
 - [Data Collection Rule Best Practices](/azure/azure-monitor/data-collection/data-collection-rule-best-practices)
 
-If the issue persists after you follow these steps, please open a support case for further assistance.
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
@@ -1,8 +1,10 @@
 ---
 title: Troubleshoot Custom Table Creation Errors in Azure
 description: Troubleshooting guide for custom table creation errors in Azure.
-ms.date: 07/23/2025
-ms.reviewer: v-liuamson; v-gsitser
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
 ms.service: azure-monitor
 ms.custom: Configure and Manage Log analytics tables
 ---
@@ -41,4 +43,6 @@ Users might receive an error message that indicates that properties of undefined
 - [Azure Monitor Overview](/azure/azure-monitor/fundamentals/overview)
 - [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request)
 
-If the issue persists after you following these steps, open a support case for further assistance.
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md
@@ -1,8 +1,10 @@
 ---
 title: Troubleshoot Deleting Migrated Custom Tables in Log Analytics
 description: Troubleshooting guide to deleting migrated custom tables in Log Analytics.
-ms.date: 07/24/2025
-ms.reviewer: v-liuamson; v-gsitser
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
 ms.service: azure-monitor
 ms.custom: Configure and manage Log Analytics tables
 ---
@@ -29,4 +31,6 @@ To delete a migrated custom table, follow these steps by using the Azure Log Ana
 
 - [Azure Log Analytics API documentation](/rest/api/loganalytics/)
 
-If the issue persists after you follow these steps, open a support case for further assistance.
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-dns-table-issues.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-dns-table-issues.md
@@ -0,0 +1,46 @@
+---
+title: Tables Aren't Populated in a DNS Solution that's Deployed to a Workspace
+description: Troubleshooting guide for tables that don't get populated after you deploy a DNS solution to a workspace.
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
+ms.service: azure-monitor
+ms.custom: Configure and manage Log Analytics tables
+---
+
+# Tables aren't populated in a DNS solution that's deployed to a workspace
+
+After you deploy a DNS solution to a workspace, you might experience an issue in which the deployment finishes successfully, but the tables don't get populated. This can occur if the table creation isn't defined in the ARM template or if there's insufficient data ingestion.
+
+## Common issues and solutions
+
+- **Issue**: The DNS solution deployment finishes, but tables aren't populated.
+- **Root cause**: Table creation might not be defined in the ARM template, or there may be no data ingestion.
+
+## Resolution
+
+To resolve the issue, follow these steps:
+
+1. Verify the ARM template configuration:
+   1. Check the DNS ARM template to make sure that it includes the definition for the table that you expect to be created.
+   1. Navigate to the [Azure portal](https://portal.azure.com), and access the relevant resource group.
+   1. Open the ARM template, and search for the table definition.
+
+2. Check data ingestion:
+   1. Verify that the Windows DNS Events via AMA Data Connector is installed and connected.
+   1. Go to the **Azure Monitor** section in the Azure portal.
+   1. Verify the data connector status, and make sure logs that are flowing into the workspace.
+
+3. Manual table creation:
+   1. If the table isn't created automatically, consider defining it manually within the ARM template.
+   1. Use the Azure Resource Manager to update the template to have the required table definitions.
+
+## References
+
+- [Azure Monitor documentation](/azure/azure-monitor/)
+- [ARM template documentation](/azure/azure-resource-manager/templates/)
+
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
@@ -1,8 +1,10 @@
 ---
 title: Troubleshoot Performance Logs Not Populating in Azure Government
 description: Troubleshooting guide for performance logs not populating in Azure Government.
-ms.date: 07/24/2025
-ms.reviewer: v-liuamson; v-gsitser
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
 ms.service: azure-monitor
 ms.custom: Configure and Manage Log analytics tables
 ---
@@ -35,4 +37,6 @@ Users might experience issues if performance logs don't populate in Azure Govern
 - [Log Analytics workspace overview](/azure/azure-monitor/logs/log-analytics-workspace-overview)
 - [Create and manage alerts in Azure](/azure/azure-monitor/alerts/alerts-overview)
 
-If the issue persists after you follow these steps, open a support case for further assistance.
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md b/support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
@@ -1,8 +1,10 @@
 ---
 title: Understand and Mitigate High Data Consumption in Log Analytics
 description: Provides instructions to resolve high data usage in Log Analytics.
-ms.date: 07/24/2025
-ms.reviewer: v-liuamson; v-gsitser
+ms.date: 09/30/2025
+author: JarrettRenshaw
+ms.author: jarrettr
+ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
 ms.service: azure-monitor
 ms.custom: Configure and Manage Log analytics tables
 ---
@@ -42,4 +44,6 @@ This article discusses high data consumption that occurs in Log Analytics worksp
 - [Best Practices for Cost Management](/azure/azure-monitor/fundamentals/best-practices-cost)
 - [Cost Management for Logs](/azure/azure-monitor/logs/cost-logs)
 
-If the issue persists after you follow the solution steps, open a support case for further assistance.
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/azure-monitor/toc.yml b/support/azure/azure-monitor/toc.yml
@@ -102,43 +102,42 @@ items:
       href: app-insights/agent/status-monitor-v2-troubleshoot.md
     - name: Troubleshoot Azure Monitor's Change Analysis
       href: app-insights/agent/change-analysis-troubleshoot.md
-  - name: Microsoft Entra authentication
-    href: app-insights/troubleshoot-microsoft-entra-authentication.md
-
-  - name: Log Analytics
+- name: Log Analytics
+  items:
+  - name: Configure and Manage Log analytics tables
     items:
-    - name: Configure and Manage Log analytics tables
-      items:
-      - name: Understand and mitigate high data consumption in Log Analytics
-        href: log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
-      - name: Troubleshoot custom table creation errors in Azure
-        href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
-      - name: Troubleshoot custom log table creation in Azure
-        href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
-      - name: Troubleshoot performance logs not populating in Azure Government
-        href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
-      - name: Troubleshoot deleting migrated custom tables in Log Analytics
-        href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md
-    - name: Log Analytics workspaces
-      items:
-      - name: Error code 0x80090016 - keyset doesn't exist
-        href: log-analytics/workspaces/error-code-0x80090016-keyset-does-not-exist.md
-      - name: Workspace data export FAQ
-        href: log-analytics/workspaces/workspace-data-export-faq.yml
-    - name: Cost management 
-      items:
-      - name: Understand cost and analyze usage report
-        href: log-analytics/billing/understand-log-analytics-workspace-bill.md
-      - name: Investigate unexpected cost increase
-        href: log-analytics/billing/identify-service-cause-unexpected-costs.md
-      - name: Set daily cap to avoid unexpected increase
-        href: log-analytics/billing/set-up-a-daily-cap.md
-      - name: Configure recommended alerts
-        href: log-analytics/billing/workspace-recommended-alerts.md
-      - name: Identify why daily cap exceeded
-        href: log-analytics/billing/why-daily-cap-exceeded.md
-      - name: Configure data retention
-        href: log-analytics/billing/configure-data-retention.md
+    - name: Understand and mitigate high data consumption in Log Analytics
+      href: log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
+    - name: Tables aren't populated in a DNS solution that's deployed to a workspace
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-dns-table-issues.md
+    - name: Troubleshoot custom table creation errors in Azure
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
+    - name: Troubleshoot custom log table creation in Azure
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
+    - name: Troubleshoot performance logs not populating in Azure Government
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
+    - name: Troubleshoot deleting migrated custom tables in Log Analytics
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md
+  - name: Log Analytics workspaces
+    items:
+    - name: Error code 0x80090016 - keyset doesn't exist
+      href: log-analytics/workspaces/error-code-0x80090016-keyset-does-not-exist.md
+    - name: Workspace data export FAQ
+      href: log-analytics/workspaces/workspace-data-export-faq.yml
+  - name: Cost management 
+    items:
+    - name: Understand cost and analyze usage report
+      href: log-analytics/billing/understand-log-analytics-workspace-bill.md
+    - name: Investigate unexpected cost increase
+      href: log-analytics/billing/identify-service-cause-unexpected-costs.md
+    - name: Set daily cap to avoid unexpected increase
+      href: log-analytics/billing/set-up-a-daily-cap.md
+    - name: Configure recommended alerts
+      href: log-analytics/billing/workspace-recommended-alerts.md
+    - name: Identify why daily cap exceeded
+      href: log-analytics/billing/why-daily-cap-exceeded.md
+    - name: Configure data retention
+      href: log-analytics/billing/configure-data-retention.md
 
 
 
diff --git a/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md b/support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md
@@ -33,7 +33,7 @@ You can view lifecycle events for desktop flows in the queue from the monitor ru
 
 ## Cause
 
-When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after six hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.
+When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after twelve hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.
 
 As mentioned in the error message, this error means that the orchestrator can't find an available machine to run the desktop flow. This error occurs before the execution of the desktop flow starts.
 
