You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Troubleshoot Export of Activity Logs across Azure Subscriptions
3
+
description: Troubleshooting guide for resolving issues that affect exporting activity logs across Azure subscriptions.
4
+
ms.date: 07/23/2025
5
+
ms.reviewer: v-liuamson; v-gsitser
6
+
ms.service: azure-monitor
7
+
ms.custom: I can’t configure export of Activity Logs
8
+
---
9
+
10
+
# Troubleshoot the export of activity logs across Azure subscriptions
11
+
12
+
Users might experience permission-related issues that prevent successful log transfer when they try to export activity logs from one Microsoft Azure subscription to another. This guide provides troubleshooting steps to resolve these issues and successfully export logs between subscriptions.
13
+
14
+
## Common issues and solutions
15
+
16
+
-**Permission Configuration**: Make sure that the shared access policy for the event hub namespace includes **Manage**, **Send**, and **Listen** permissions. These permissions are crucial for streaming logs to Event Hubs.
17
+
-**Diagnostic Settings**: Verify that the diagnostic settings are correctly configured to use the appropriate event hubs policy name. Navigate to the diagnostic settings, note the event hub policy name, and check the permissions in the event hub namespace.
18
+
-**Role Assignment**: Verify that the Azure system-assigned managed identity has the necessary role assignments. Use the Azure CLI to list role assignments and verify that the **Azure Event Hubs Data Sender** role is assigned.
19
+
20
+
### Instructions to resolve export issues
21
+
22
+
1. Verify shared access policy permissions:
23
+
1. Open the diagnostic settings in Azure.
24
+
1. Note the event hub policy name that's used.
25
+
1. Navigate to the event hub namespace and open the **Shared Access Policy** tab.
26
+
1. Make sure that the **Manage**, **Send**, and **Listen** permissions are selected.
27
+
28
+
2. Check the role assignments:
29
+
1. Go to **Access Control (IAM)** on the event hub namespace or resource group.
30
+
1. Look for any Microsoft Insights or Azure Monitor-related identities that have the **Azure Event Hubs Data Sender** role.
31
+
1. To list role assignments, run the following command in Azure CLI:
32
+
33
+
```bash
34
+
az role assignment list --scope <EventHubNamespaceResourceID> --output table
35
+
```
36
+
37
+
3. Verify data ingestion:
38
+
1. Make sure that data is being ingested into the event hub as expected.
39
+
1. If the issue persists, consider scheduling a remote session for further investigation.
40
+
41
+
## References
42
+
43
+
- [Authorize access to Azure Event Hubs](/azure/event-hubs/authorize-access-event-hubs)
44
+
- [Diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings)
0 commit comments