Skip to content

Commit e920a2e

Browse files
author
amsliu
committed
New article for CI 6615
1 parent 683ccba commit e920a2e

3 files changed

Lines changed: 45 additions & 10 deletions

File tree

support/azure/azure-monitor/activity-logs/config-export/new.md

Lines changed: 0 additions & 8 deletions
This file was deleted.
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
title: Troubleshoot Permission Errors in Activity Log Configuration
3+
description: Troubleshooting guide for permission errors in Activity Log configuration.
4+
ms.date: 07/17/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 Permission Errors in Activity Log Configuration
11+
12+
When configuring the Azure Activity Log to export to Log Analytics, users may encounter permission errors. This issue typically arises due to insufficient permissions assigned to the custom role. Understanding the root cause and applying the correct permissions can resolve this problem efficiently.
13+
14+
## Common Issues and Solutions
15+
16+
- **Authorization Failed**: This error indicates that the user does not have the necessary permissions to perform the action. Verify that the correct permissions are assigned and that the scope is set correctly.
17+
18+
### Step-by-Step Instructions to Resolve Permission Errors
19+
20+
1. **Verify Role Assignments**:
21+
- Navigate to **Azure Portal**.
22+
- Go to **Subscriptions** and select the relevant subscription.
23+
- Click on **Access Control (IAM)** and then **Role assignments**.
24+
- Ensure that the custom role is assigned to the account responsible for creating the diagnostic settings.
25+
26+
2. **Assign Necessary Permissions**:
27+
- Duplicate the **Log Analytics Contributor** role.
28+
- Remove any unnecessary permissions.
29+
- Ensure the **Microsoft.Insights/diagnosticSettings/write** permission is included.
30+
31+
3. **Set Scope Appropriately**:
32+
- Ensure the scope is set to the **subscription level** rather than the resource group level.
33+
34+
4. **Update Credentials**:
35+
- If access was recently granted, update the credentials to reflect the changes.
36+
37+
## Reference
38+
39+
- [Azure Analysis Services Overview](https://learn.microsoft.com/analysis-services/azure-analysis-services/analysis-services-overview?view=asallproducts-allversions)
40+
- [Log Analytics Contributor Role](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/analytics#log-analytics-contributor)
41+
- [Azure Monitor Activity Log](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell)
42+
43+
If the issue persists after following the solution steps, please open a support case for further assistance.

support/azure/azure-monitor/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ items:
1111
href: activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md
1212
- name: Diagnostic Settings Transition from Legacy Solutions
1313
href: activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md
14-
- name: New
15-
href: activity-logs/config-export/new.md
14+
- name: Troubleshoot Permission Errors in Activity Log Configuration
15+
href: activity-logs/config-export/troubleshoot-permission-errors-in-activity-log-configuration.md
1616
- name: Application Insights
1717
items:
1818
- name: OpenTelemetry troubleshooting

0 commit comments

Comments
 (0)