Skip to content

Commit 3db8025

Browse files
authored
Update understanding-and-managing-diagnostic-settings-retention.md
Edit review per CI 6612
1 parent fd702c6 commit 3db8025

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed
Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,33 @@
11
---
22
title: Understanding and Managing Diagnostic Settings Retention
3-
description: Provides guidance on understanding and managing diagnostic settings retention.
3+
description: Provides guidance for understanding and managing diagnostic settings retention.
44
ms.date: 07/17/2025
55
ms.reviewer: v-liuamson; v-gsitser
66
ms.service: azure-monitor
77
ms.custom: I can’t configure export of Activity Logs
88
---
99

10-
# Understanding and Managing Diagnostic Settings Retention
10+
# Understanding and managing diagnostic settings retention
1111

12-
When managing Azure resources, you might encounter issues related to the transition from diagnostic settings storage retention to Azure Storage lifecycle management. This article provides guidance on how to address these issues effectively.
12+
When you manage Azure resources, you might experience issues that are related to the transition from diagnostic settings storage retention to Azure Storage lifecycle management. This article provides guidance to handle these issues effectively.
1313

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

16-
- **Issue Description**: Users may notice that templates are not displayed when attempting to verify resources affected by the transition from legacy solutions to diagnostic settings.
17-
- **Root Cause**: The automatic switch from activity log solutions to diagnostic settings may cause confusion if not properly understood.
16+
- **Issue**: Users might notice that templates are not displayed when they try to verify resources that are affected by the transition from legacy solutions to diagnostic settings.
17+
- **Root cause**: The automatic switch from activity log solutions to diagnostic settings might cause confusion if they're not well understood.
1818

19-
### Step-by-Step Instructions to Resolve Diagnostic Settings Issues
19+
### Instructions to resolve diagnostic settings issues
2020

21-
1. **Verify Resource Impact**:
22-
- Navigate to the Azure portal.
23-
- Go to **All Services** and select **Resource Manager**.
24-
- Click on **Deploy** and then **Templates** in the left pane.
25-
- Confirm if any resources are impacted by the transition.
21+
1. **Verify resource effect**:
22+
- Navigate to the Azure portal > **All Services**.
23+
- Select **Resource Manager**.
24+
- Select **Deploy**, and then select **Templates** in the left pane.
25+
- Check whether any resources are affected by the transition.
2626

27-
2. **Check for Legacy Solutions**:
28-
- Use the following PowerShell command to determine if legacy solutions are in use:
29-
30-
```powershell
27+
2. **Check for legacy solutions**:
28+
- To determine whether legacy solutions are in use, run the following PowerShell command:
29+
30+
```powershell
3131
$WorkspaceName = Get-AzOperationalInsightsWorkspace
3232
foreach ($Name in $WorkspaceName) {
3333
Get-AzOperationalInsightsDataSource -Kind AzureActivityLog -ResourceGroupName $Name.ResourceGroupName -WorkspaceName $Name.Name
@@ -39,9 +39,9 @@ When managing Azure resources, you might encounter issues related to the transit
3939
3. **Automatic Transition**:
4040
- Understand that the transition to diagnostic settings is automatic. If your environment is already using diagnostic settings, no additional steps are necessary.
4141
42-
## Reference
42+
## References
4343
4444
- [Azure Monitor Activity Logs](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell#legacy-collection-methods)
4545
- [Azure Storage Lifecycle Management](https://learn.microsoft.com/azure/storage/blobs/storage-lifecycle-management-concepts)
4646
47-
If the issue persists after following the solution steps, please open a support case for further assistance.
47+
If the issue persists after you follow these steps, open a support case for further assistance.

0 commit comments

Comments
 (0)