Merge pull request #9305 from amsliu/v-liuamson-CI6473-and-CI6474

Update the articles for CI 6473 and CI 6474. PR approved by JarrettRenshaw.

Author: Amson Liu

support/azure/azure-monitor/activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md

@@ -8,4 +8,79 @@ ms.custom: I can’t configure export of Activity Logs
 ---
 # Diagnostic Settings Transition from Legacy Solutions
 
-This article is currently being updated.
+## Resolve Transition Issues from Legacy Azure Activity Log Solutions
+
+This article addresses the transition from legacy solutions for forwarding Azure activity logs to new diagnostic settings. The legacy solution will be retired on September 30, 2026, and this change will occur automatically without disrupting your workflow. However, if you have automation using the legacy API, you will need to update it.
+
+### Step-by-Step Instructions to Resolve Transition Issues
+
+1. **Verify Current Configuration**
+   - Navigate to **Azure Portal**.
+   - Go to **Monitor** > **Activity Log** > **Export Activity Log**.
+   - Select your subscription from the dropdown and ensure a diagnostic setting is configured.
+
+2. **Update Automation Scripts**
+   - If you have scripts using the legacy API, update them to use the **diagnostic settings API** by September 30, 2026.
+   - Refer to the [Azure Diagnostic Settings API Documentation](https://learn.microsoft.com/azure/azure-monitor/essentials/activity-log?tabs=powershell#legacy-collection-methods) for guidance.
+
+3. **Check Log Analytics Workspace**
+   - Ensure the destination Log Analytics Workspace is active.
+   - If the workspace is inactive, change the destination to an active subscription.
+
+4. **Run PowerShell Script to List Diagnostic Settings**
+   - Open **Azure Cloud Shell** or any PowerShell connected to your tenant.
+   - Run the following script to list all diagnostic settings across your subscriptions:
+  
+```powershell
+     # Install and login with Connect-AzAccount
+     If ($null -eq (Get-Command -Name Get-CloudDrive -ErrorAction SilentlyContinue)) {
+         If ($null -eq (Get-Module Az -ListAvailable -ErrorAction SilentlyContinue)){
+             Write-Host Installing Az module from default repository
+             Install-Module -Name Az -AllowClobber
+         }
+         Write-Host Importing Az
+         Import-Module -Name Az
+         Write-Host Connecting to Az
+         Connect-AzAccount
+     }
+     # Get all Azure Subscriptions
+     $Subs = Get-AzSubscription
+     # Set array
+     $DiagResults = @()
+     # Loop through all Azure Subscriptions
+     foreach ($Sub in $Subs) {
+         Set-AzContext $Sub.id | Out-Null
+         Write-Host Processing Subscription: ($Sub).name
+         # Get all Azure resources for current subscription
+         $Resources = Get-AZResource
+         # Get all Azure resources which have Diagnostic settings enabled and configured
+         foreach ($res in $Resources) {
+             $resId = $res.ResourceId
+             $DiagSettings = Get-AzDiagnosticSetting -ResourceId $resId -WarningAction SilentlyContinue -ErrorAction SilentlyContinue | Where-Object { $_.Id -ne $null }
+             foreach ($diag in $DiagSettings) {
+                 # Store all results for resource in PS Object
+                 $item = [PSCustomObject]@{
+                     ResourceName = $res.name
+                     DiagnosticSettingsName = $diag.name
+                     StorageAccountName = $diag.StorageAccountId
+                     EventHubName = $diag.EventHubAuthorizationRuleId
+                     WorkspaceName = $diag.WorkspaceId
+                     Subscription = $Sub.Name
+                     ResourceId = $resId
+                     DiagnosticSettingsId = $diag.Id
+                 }
+                 Write-Host $item
+                 # Add PS Object to array
+                 $DiagResults += $item
+             }
+         }
+     }
+     # Save Diagnostic settings to CSV as tabular data
+     $DiagResults | Export-Csv -Force -Path .\AzureResourceDiagnosticSettings-$(get-date -f yyyy-MM-dd-HHmm).csv
+```
+
+## Reference
+- [Azure Diagnostic Settings Documentation](https://learn.microsoft.com/azure/azure-monitor/essentials/activity-log?tabs=powershell#legacy-collection-methods)
+- [Azure Monitor Overview](https://learn.microsoft.com/azure/azure-monitor/overview)
+
+If the issue persists after following the solution steps, please open a support case for further assistance.

support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md

@@ -8,4 +8,37 @@ ms.custom: I can’t configure export of Activity Logs
 ---
 # Understanding and Transitioning from Legacy to Diagnostic Settings for Azure Activity Logs
 
-This article is currently being updated.
+When Azure announced the transition from legacy solutions to diagnostic settings for forwarding activity logs, users received notifications about necessary updates. This article provides guidance on how to manage this transition effectively.
+
+### Introduction
+Azure is retiring the legacy solution for forwarding activity logs and replacing it with diagnostic settings. This change is automatic, but users with automation relying on the legacy API need to update their configurations. This guide will help you verify your current setup and make necessary adjustments.
+
+### Step-by-Step Instructions to Transition to Diagnostic Settings
+
+1. **Verify Existing Log Profiles**
+   - Use the **Get-AzLogProfile** command in Azure PowerShell or the **az monitor log-profiles list** command in Azure CLI to check for existing log profiles.
+   - If these commands return no results, no legacy log profiles are configured, and no action is needed.
+
+2. **Update Automation Scripts**
+   - If you have automation scripts using the legacy API, update them to use the diagnostic settings API by September 30, 2026.
+   - Refer to the [Azure Monitor documentation](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring) for detailed instructions.
+
+3. **Manual Transition to Diagnostic Settings**
+   - For users with legacy log profiles, manually transition to diagnostic settings by following the steps outlined in the Azure documentation.
+   - Ensure all configurations are updated before the retirement date to avoid disruptions.
+
+### Common Issues and Solutions
+
+- **Issue:** Unable to find existing log profiles.
+  - **Solution:** Ensure you are using the correct commands and have the necessary permissions to access log profiles.
+
+- **Issue:** Automation scripts fail after the transition.
+  - **Solution:** Double-check that all scripts are updated to use the new diagnostic settings API.
+
+### Reference
+
+- [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring)
+- [Get-AzLogProfile Command](https://learn.microsoft.com/powershell/module/az.monitor/get-azlogprofile?view=azps-14.0.0)
+- [Azure CLI Log Profiles](https://learn.microsoft.com/cli/azure/monitor/log-profiles?view=azure-cli-latest#az-monitor-log-profiles-list)
+
+If the issue persists after following the solution steps, please open a support case for further assistance.