Merge pull request #9313 from MicrosoftDocs/main

aartig13 · web-flow · commit ac2aa4f6c4cc · 2025-07-10T12:46:00.000-05:00
SQL Server 2022 CU20 (Release Date 07/10) - merge main to live
diff --git a/support/azure/azure-monitor/activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md b/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.
diff --git a/support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md b/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.
diff --git a/support/sql/releases/download-and-install-latest-updates.md b/support/sql/releases/download-and-install-latest-updates.md
@@ -1,7 +1,7 @@
 ---
 title: Latest updates and version history for SQL Server
 description: This article lists various builds or updates that are available for different versions of SQL Server.
-ms.date: 07/08/2025
+ms.date: 07/10/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen
 ms.reviewer: v-six
 ---
@@ -36,7 +36,7 @@ Each of the following links provides information for all of the applicable produ
 
 |Version|Latest service pack|Latest GDR|Latest cumulative update|
 |---|---|---|---|
-|**SQL Server 2022**<br/><br/>- [Build information](#sql-server-2022)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver16&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5058712) <br/>(16.0.1140.6 - July 2025) |[CU19 for 2022](sqlserver-2022/cumulativeupdate19.md) <br/>(16.0.4195.2 - May 2025) <br/><br/>[CU19 + GDR](https://support.microsoft.com/help/5058721) <br/>(16.0.4200.1 - July 2025)|
+|**SQL Server 2022**<br/><br/>- [Build information](#sql-server-2022)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver16&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5058712) <br/>(16.0.1140.6 - July 2025) |[CU20 for 2022](sqlserver-2022/cumulativeupdate20.md) <br/>(16.0.4205.1 - July 2025) <br/><br/>[CU19 + GDR](https://support.microsoft.com/help/5058721) <br/>(16.0.4200.1 - July 2025)|
 |**SQL Server 2019**<br/><br/>- [Build information](#sql-server-2019)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver15&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5058713) <br/>(15.0.2135.5 - July 2025)|[CU32 for 2019](sqlserver-2019/cumulativeupdate32.md) <br/>(15.0.4430.1 - February 2025)<br/><br/>[CU32 + GDR](https://support.microsoft.com/help/5058722) <br/>(15.0.4435.7 - July 2025)|
 |**SQL Server 2017**<br/><br/>- [Build information](#sql-server-2017)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2017&preserve-view=true)|[Azure Connect pack](sqlserver-2017/azureconnect.md) <br/>(14.0.3490.10 - March 2025)|[GDR](https://support.microsoft.com/help/5058716) <br/>(14.0.2075.8 - July 2025)|[CU31 for 2017](sqlserver-2017/cumulativeupdate31.md) <br/>(14.0.3456.2 - September 2022)<br/><br/>[CU31 + GDR](https://support.microsoft.com/help/5058714) <br/>(14.0.3495.9 - July 2025)|
 |**SQL Server 2016**<br/><br/>- [Build information](#sql-server-2016)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2016&preserve-view=true)|[Azure Connect pack](sqlserver-2016/servicepack3-azureconnect.md) <br/>(13.0.7000.253 - May 2022)<br/><br/>[SP3](sqlserver-2016/servicepack3.md) <br/>(13.0.6300.2 - September 2021)<br/><br/>[SP2](sqlserver-2016/servicepack2.md) <br/>(13.0.5026.0 - April 2018)<br/><br/>[SP1](sqlserver-2016/servicepack1.md) <br/>(13.0.4001.0 - November 2016)|[GDR for Azure Connect pack](https://support.microsoft.com/help/5058717) <br/>(13.0.7055.9 - July 2025)<br/><br/>[GDR for SP3](https://support.microsoft.com/help/5058718) <br/>(13.0.6460.7 - July 2025)<br/><br/>[GDR for SP2](https://support.microsoft.com/help/5014365) <br/>(13.0.5108.50 - June 2022)<br/><br/>[GDR for SP1](https://support.microsoft.com/help/4505219) <br/>(13.0.4259.0 - July 2019)<br/><br/>[GDR for RTM](https://support.microsoft.com/help/4058560) <br/>(13.0.1745.2 - January 2018)|[CU17 + GDR for SP2](https://support.microsoft.com/help/5014351) <br/>(13.0.5893.48 - June 2022)<br/><br/>[CU17 for 2016 SP2](sqlserver-2016/servicepack2-cumulativeupdate17.md) <br/>(13.0.5888.11 - March 2021)<br/><br/>[CU15 + GDR for SP1](https://support.microsoft.com/help/4505221) <br/>(13.0.4604.0 - July 2019)<br/><br/>[CU15 for SP1](sqlserver-2016/servicepack1-cumulativeupdate15.md) <br/>(13.0.4574.0 - May 2019)<br/><br/>[CU9 for RTM](sqlserver-2016/rtm-cumulativeupdate9.md) <br/>(13.0.2216.0 - November 2017)|
@@ -57,6 +57,7 @@ Each of the following links provides information for all of the applicable produ
 
 | Build number or version | Service pack | Update    | Knowledge Base number                                            | Release date       |
 |-------------------------|--------------|-----------|-------------------------------------------------------|--------------------|
+| 16.0.4205.1            | None         | CU20| [KB5059390](sqlserver-2022/cumulativeupdate20.md) | July 10, 2025    |
 | 16.0.4200.1             | None         | CU19 + GDR| [KB5058721](https://support.microsoft.com/help/5058721) | July 08, 2025    |
 | 16.0.1140.6             | None         | GDR       | [KB5058712](https://support.microsoft.com/help/5058712) | July 08, 2025    |
 | 16.0.4195.2            | None         | CU19| [KB5054531](sqlserver-2022/cumulativeupdate19.md) | May 15, 2025    |
@@ -666,4 +667,4 @@ Use the version number in the following table to identify the product or service
 ## See also
 
 - [Determine version information of SQL Server components and client tools](components-client-tools-versions.md)
-- [Determine which version and edition of SQL Server Database Engine is running](find-my-sql-version.md)
+- [Determine which version and edition of SQL Server Database Engine is running](find-my-sql-version.md)
diff --git a/support/sql/releases/sqlserver-2022/build-versions.md b/support/sql/releases/sqlserver-2022/build-versions.md
@@ -1,7 +1,7 @@
 ---
 title: SQL Server 2022 build versions (KB5023451)
 description: This article lists cumulative update and GDR builds for SQL Server 2022.
-ms.date: 07/08/2025
+ms.date: 07/10/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5023451
 appliesto:
 - SQL Server 2022
@@ -15,7 +15,8 @@ This article lists the Microsoft SQL Server 2022 builds that were released after
 
 | Cumulative update name | SQL Server build version | SQL Server (sqlservr.exe) file version | Analysis Services build version | Analysis Services (msmdsrv.exe) file version | Knowledge Base number | Release date |
 |---------------|-------------|-----------------|-------------|-----------------|------------------------------------|--------------------|
-| CU19 (Latest) | 16.0.4195.2 | 2022.160.4195.2 | 16.0.43.244 | 2022.160.43.244 | [KB5054531](cumulativeupdate19.md) | May 15, 2025       |
+| CU20 (Latest) | 16.0.4205.1 | 2022.160.4205.1 | 16.0.43.247 | 2022.160.43.247 | [KB5059390](cumulativeupdate20.md) | July 10, 2025       |
+| CU19          | 16.0.4195.2 | 2022.160.4195.2 | 16.0.43.244 | 2022.160.43.244 | [KB5054531](cumulativeupdate19.md) | May 15, 2025       |
 | CU18          | 16.0.4185.3 | 2022.160.4185.3 | 16.0.43.242 | 2022.160.43.242 | [KB5050771](cumulativeupdate18.md) | March 13, 2025     |
 | CU17          | 16.0.4175.1 | 2022.160.4175.1 | 16.0.43.239 | 2022.160.43.239 | [KB5048038](cumulativeupdate17.md) | January 16, 2025   |
 | CU16          | 16.0.4165.4 | 2022.160.4165.4 | 16.0.43.239 | 2022.160.43.239 | [KB5048033](cumulativeupdate16.md) | November 14, 2024  |
@@ -66,4 +67,4 @@ This article lists the Microsoft SQL Server 2022 builds that were released after
 - [Where to find information about the latest SQL Server builds](https://support.microsoft.com/help/957826)
 - [SQL Server Service Packs are no longer supported starting from SQL Server 2017](https://support.microsoft.com/help/4041553)
 - [Naming schema and Fix area descriptions for SQL Server software update packages](../../database-engine/install/windows/naming-schema-and-fix-area.md)
-- [Description of the standard terminology that is used to describe Microsoft software updates](../../../windows-client/deployment/standard-terminology-software-updates.md)
+- [Description of the standard terminology that is used to describe Microsoft software updates](../../../windows-client/deployment/standard-terminology-software-updates.md)
diff --git a/support/sql/releases/sqlserver-2022/cumulativeupdate20.md b/support/sql/releases/sqlserver-2022/cumulativeupdate20.md
diff --git a/support/sql/releases/toc.yml b/support/sql/releases/toc.yml
