Skip to content

Commit f2a83c8

Browse files
authored
Update troubleshoot-permission-errors-in-activity-log-configuration.md
Edit review per CI 6615
1 parent e920a2e commit f2a83c8

1 file changed

Lines changed: 17 additions & 19 deletions

File tree

support/azure/azure-monitor/activity-logs/config-export/troubleshoot-permission-errors-in-activity-log-configuration.md

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,37 +7,35 @@ ms.service: azure-monitor
77
ms.custom: I can’t configure export of Activity Logs
88
---
99

10-
# Troubleshoot Permission Errors in Activity Log Configuration
10+
# Troubleshoot permission errors in Activity Log configuration
1111

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.
12+
Users might experience permission errors when they configure the Azure Activity Log to export to Log Analytics. This issue typically occurs because insufficient permissions are assigned to the custom role. This article helps you determine the root cause of the errors and apply the correct permissions to resolve the issue efficiently.
1313

14-
## Common Issues and Solutions
14+
## Common issues and solutions
1515

1616
- **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.
1717

18-
### Step-by-Step Instructions to Resolve Permission Errors
18+
### Instructions to resolve permission errors
1919

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.
20+
**Step 1: Verify role assignments**
21+
1. Navigate to **Azure Portal**.
22+
1. Go to **Subscriptions** and select the relevant subscription.
23+
1. Select **Access Control (IAM)** > **Role assignments**.
24+
1. Make sure that the custom role is assigned to the account that's responsible for creating the diagnostic settings.
2525

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.
26+
**Step 2: Assign necessary permissions**
27+
1. Duplicate the **Log Analytics Contributor** role.
28+
1. Remove any unnecessary permissions.
29+
1. Make sure that the **Microsoft.Insights/diagnosticSettings/write** permission is included.
3030

31-
3. **Set Scope Appropriately**:
32-
- Ensure the scope is set to the **subscription level** rather than the resource group level.
31+
**Step 3: Set scope appropriately** - Make sure that the scope is set to the **subscription level** instead of the resource group level.
3332

34-
4. **Update Credentials**:
35-
- If access was recently granted, update the credentials to reflect the changes.
33+
**Step 4: Update credentials** - If access was recently granted, update the credentials to reflect the changes.
3634

37-
## Reference
35+
## References
3836

3937
- [Azure Analysis Services Overview](https://learn.microsoft.com/analysis-services/azure-analysis-services/analysis-services-overview?view=asallproducts-allversions)
4038
- [Log Analytics Contributor Role](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/analytics#log-analytics-contributor)
4139
- [Azure Monitor Activity Log](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell)
4240

43-
If the issue persists after following the solution steps, please open a support case for further assistance.
41+
If the issue persists after you follow these steps, open a support case for further assistance.

0 commit comments

Comments
 (0)