1st batch of changes requested by neil ghuman

Author: amsliu

support/azure/azure-monitor/activity-logs/config-export/export-directory-level-activity-logs-to-event-hubs.md

@@ -1,7 +1,7 @@
 ---
 title: Export Directory-Level Activity Logs to Event Hubs
 description: Provides guidance for exporting directory-level activity logs to Event Hubs by using Azure management group-level diagnostic settings.
-ms.date: 07/28/2025
+ms.date: 08/04/2025
 ms.reviewer: v-liuamson; v-gsitser; v-sisidhu
 ms.service: azure-monitor
 ms.custom: I can’t configure export of Activity Logs
@@ -16,7 +16,7 @@ You can export directory-level activity logs to an event hub through an API call
 ## Common issues and solutions
 
 - **Issue:** Logs don't appear in Event Hubs.
-  - **Solution:** Double-check the event hub configuration to make sure that the correct namespace and key ID are used.
+  - **Solution:** Double-check the event hub configuration to make sure that the correct namespace is used.
 
 - **Issue:** Permission errors occur when making diagnostic settings.
   - **Solution:** Make sure that you have the necessary permissions to create or update diagnostic settings in Azure.
@@ -29,7 +29,7 @@ You can export directory-level activity logs to an event hub through an API call
 
 3. Select **Add diagnostic setting**, and select the resource that you want to export logs for.
 
-4. Under **Destination details**, select **Event Hub**, and then provide the required **Event Hub namespace** and **Event Hub name** values. Make sure that the **Event Hub key ID** value is entered correctly.
+4. Under **Destination details**, select **Event Hubs**, and then provide the required **Event Hubs namespace** and **Event Hubs name** values.
 
 5. Select **Save** to apply the settings. Check the event hub for incoming data to verify that the logs are exported.
 

support/azure/azure-monitor/activity-logs/config-export/push-subscription-activity-logs-to-sentinel.md

@@ -1,19 +1,19 @@
 ---
-title: Push Subscription Activity Logs to Sentinel
+title: Troubleshoot Pushing Subscription Level Activity Logs to Sentinel
 description: Provides detailed instructions for pushing subscription activity logs to Sentinel.
-ms.date: 07/28/2025
+ms.date: 08/04/2025
 ms.reviewer: v-liuamson; v-gsitser; v-sisidhu
 ms.service: azure-monitor
 ms.custom: I can’t configure export of Activity Logs
 ---
 
-# Push subscription Activity Logs to Sentinel
+# Troubleshoot pushing subscription level Activity Logs to Sentinel
 
 This article provides guidance for how to push subscription activity logs to Microsoft Sentinel by using Microsoft Azure Diagnostic Settings. This process is essential to  monitor and analyze activity logs effectively.
 
 Users might encounter challenges when they try to push subscription activity logs to Sentinel. This guide outlines the steps to configure Azure Diagnostic Settings to achieve seamless data transfer to Sentinel.
 
-### Common issues and solutions
+## Common issues and solutions
 
 - **Issue**: Logs aren't appearing in Sentinel.
   - **Solution**: Make sure that the correct Log Analytics workspace is selected and that the diagnostic settings are correctly configured.
@@ -22,27 +22,29 @@ Users might encounter challenges when they try to push subscription activity log
 
 1. Navigate to the Azure portal.
 
-2. Open Diagnostic Settings:
+1. Open Diagnostic Settings:
    1. Go to the **Azure Monitor** section.
    1. On the menu, select **Diagnostic Settings**.
 
-3. **Configure Diagnostic Settings**:
-   1. Select the resource that you want to configure the logs for.
-   1. Select **Add Diagnostic Setting**.
-   1. Name your setting, and select the logs that you want to send to Sentinel.
+1. **Configure Diagnostic Settings**:
+   1. Select the resource that you want to verify the logs for.
+   1. Select **Edit Diagnostic Setting**.
+   1. Review the diagnostic settings are set correctly.
 
-4. **Select Log Analytics workspace**:
-   1. Under **Destination details**, select **Send to Log Analytics**.
-   1. Select the appropriate Log Analytics workspace that you want to send the logs to.
+1. **Select Log Analytics workspace**:
+   1. Under **Destination details**, select **Log Analytics**.
+   1. Verify the correct Log Analytics workspace is selected.
 
-5. Review your settings, and select **Save** to apply the changes.
+1. Review your settings, and select **Save** to apply the changes.
 
-6. To verify the data transfer, run the following query in your Log Analytics workspace:
+1. To verify the data transfer, run the following query in your Log Analytics workspace:
 
    ```plaintext
    AzureActivity | where SubscriptionId contains "<YourSubscriptionId>"
    ```
 
+1. Validate your [connector settings](/azure/sentinel/connect-services-diagnostic-setting-based#prerequisites).
+
 ## References
 
 - [Azure Sentinel data connectors reference](/azure/sentinel/data-connectors-reference)

support/azure/azure-monitor/toc.yml

@@ -11,12 +11,10 @@ items:
         href: activity-logs/config-export/transition-from-legacy-to-diagnostic-settings.md
       - name: Manage diagnostic settings to transition from legacy solutions
         href: activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md
-      - name: Push subscription Activity Logs to Sentinel
+      - name: Troubleshoot pushing subscription level Activity Logs to Sentinel
         href: activity-logs/config-export/push-subscription-activity-logs-to-sentinel.md
       - name: Export directory-level Activity Logs to Event Hubs
         href: activity-logs/config-export/export-directory-level-activity-logs-to-event-hubs.md
-      - name: Resolve log limit issues in Azure Functions apps
-        href: activity-logs/config-export/resolve-log-limit-issues-in-azure-functions-apps.md
       - name: Understand and manage diagnostic settings retention
         href: activity-logs/config-export/understand-and-manage-diagnostic-settings-retention.md  
       - name: Troubleshoot Azure CLI configuration issues
@@ -55,6 +53,8 @@ items:
       href: app-insights/telemetry/auto-instrumentation-troubleshoot.md
     - name: Troubleshoot high data ingestion
       href: app-insights/telemetry/troubleshoot-high-data-ingestion.md
+    - name: Resolve log limit issues in Azure Functions apps
+      href: activity-logs/config-export/resolve-log-limit-issues-in-azure-functions-apps.md
     - name: Application Insights classic SDK troubleshooting
       items:
       - name: SDK support guidance