Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

.github/workflows/signoff-review.yml

@@ -646,6 +646,8 @@ jobs:
                             # If so, always return success. If not, always keep at pending until approved.
                             if ($ApprovedLabelSet)
                             {
+                                $ActionableComment = $True
+                                
                                 Write-Host "Content team already approved. Returning success."
                                 $Status.state = "success"
                                 $Status.description = $ContentApprovalMessage

docs/database-engine/availability-groups/windows/contained-availability-groups-overview.md

@@ -4,7 +4,7 @@ description: An overview of the contained availability group feature of Always O
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: mathoma, randolphwest
-ms.date: 01/19/2024
+ms.date: 03/16/2025
 ms.service: sql
 ms.subservice: high-availability
 ms.topic: conceptual
@@ -138,11 +138,16 @@ If the backup location is on a network resource, all servers that host replicas
 
 ### Resource governor
 
-Resource governor works at the instance level. Resource governor with a contained availability group isn't applicable.
+In [!INCLUDE[sssql22-md](../../../includes/sssql22-md.md)] before Cumulative Update 18, and in older versions of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], resource governor configuration DDL commands have no effect when executed on a contained availability group connection. Additionally, if resource governor is enabled via an instance connection, it has no effect on the contained availability group connections.
 
-Resource governor configuration DDL commands have no effect when executed on a contained availability group connection.
+Starting with [!INCLUDE[sssql22-md](../../../includes/sssql22-md.md)] Cumulative Update 18, if you configure resource governor on an instance connection, resource consumption on either instance connections or contained availability group connections is governed as expected. If you attempt to configure resource governor on a contained availability group connection, you receive an error.
 
-If resource governor is enabled via an instance connection, it has no effect on the contained availability group connections.
+Resource governor works at the [!INCLUDE[ssde-md](../../../includes/ssde-md.md)] instance level. Resource governor configuration doesn't propagate to availability replicas. You must configure resource governor on each instance hosting an availability replica.
+
+> [!TIP]
+> We recommend that for a given availability group, you use the same resource governor configuration for all availability replicas.
+
+For more information, see [Resource governor](../../../relational-databases/resource-governor/resource-governor.md) and [Resource governor configuration examples and best practices](../../../relational-databases/resource-governor/resource-governor-walkthrough.md).
 
 ### Change data capture
 

docs/relational-databases/resource-governor/resource-governor.md

@@ -4,7 +4,7 @@ description: Learn about the SQL Server resource governor feature that limits th
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dfurman
-ms.date: 01/02/2025
+ms.date: 03/16/2025
 ms.service: sql
 ms.subservice: performance
 ms.topic: conceptual
@@ -49,7 +49,7 @@ Resource governor has the following limitations:
 - Very short queries, such as queries in some OLTP workloads, might not use CPU long enough to apply CPU bandwidth controls. This might skew CPU usage statistics and limit the effectiveness of CPU resource governance.
 - The ability to govern physical I/O applies only to user operations and not system tasks. System tasks perform transaction log, checkpoint, and lazy writer I/O. Resource governor governs user physical reads I/O but not write I/O performed by system tasks.
 - You can't modify resource governance controls for the `internal` resource pool and workload group.
-- Resource governor works at the instance level. Resource governor with a [contained availability group](../../database-engine/availability-groups/windows/contained-availability-groups-overview.md) isn't applicable.
+- If you use contained availability groups, see [Interactions with other features](../../database-engine/availability-groups/windows/contained-availability-groups-overview.md#resource-governor) for more information.
 
 ## Resource concepts