Merge pull request #21921 from MicrosoftDocs/main

5/03 AM Publish

Author: huypub

azure-sql/database/features-comparison.md

@@ -166,7 +166,7 @@ Azure SQL Database and Azure SQL Managed Instance support various data tools tha
 | [BACPAC file (export)](/sql/relational-databases/data-tier-applications/export-a-data-tier-application) | Yes - see [SQL Database export](database-export.md) | Yes - see [SQL Managed Instance export](database-export.md) |
 | [BACPAC file (import)](/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database) | Yes - see [SQL Database import](database-import.md) | Yes - see [SQL Managed Instance import](database-import.md) |
 | [Data Quality Services (DQS)](/sql/data-quality-services/data-quality-services) | No | No |
-| [Master Data Services (MDS)](/sql/master-data-services/master-data-services-overview-mds) | No | No |
+| [Master Data Services (MDS)](/sql/master-data-services/master-data-services-overview-mds) | No | No. Host MDS on an Azure VM. While SQL Managed Instance cannot run MDS as a service, it can host [MDS databases](/sql/master-data-services/master-data-services-host-database-on-managed-instance) for a MDS service installed on Azure Virtual Machine, using SQL Server authentication. |
 | [SMO](/sql/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide) | [Yes](https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects) | Yes [version 150](https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects) |
 | [SQL Server Data Tools (SSDT)](/sql/ssdt/download-sql-server-data-tools-ssdt) | Yes | Yes |
 | [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) | Yes | Yes [version 18.0 and higher](/sql/ssms/download-sql-server-management-studio-ssms) |

docs/master-data-services/master-data-services-overview-mds.md

@@ -19,7 +19,7 @@ ms.author: lle
 ---
 # Master Data Services Overview (MDS)
 
-[!INCLUDE [SQL Server - Windows only ASDBMI  ](../includes/applies-to-version/sql-windows-only-asdbmi.md)]
+[!INCLUDE [SQL Server - Windows only  ](../includes/applies-to-version/sql-windows-only.md)]
 
 This topic describes the key data organization and management features of [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)]. 
 

docs/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions.md

@@ -115,7 +115,8 @@ Server-level audit action groups are actions similar to [!INCLUDE[ssNoVersion](.
 |TRACE_CHANGE_GROUP|This event is raised for all statements that check for the ALTER TRACE permission. Equivalent to the [Audit Server Alter Trace Event Class](../../../relational-databases/event-classes/audit-server-alter-trace-event-class.md).|  
 |TRANSACTION_GROUP|This event is raised for BEGIN TRANSACTION, ROLLBACK TRANSACTION, and COMMIT TRANSACTION operations, both for explicit calls to those statements and implicit transaction operations. This event is also raised for UNDO operations for individual statements caused by the rollback of a transaction.|  
 |USER_CHANGE_PASSWORD_GROUP|This event is raised whenever the password of a contained database user is changed by using the ALTER USER statement.|  
-|USER_DEFINED_AUDIT_GROUP|This group monitors events raised by using [sp_audit_write (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-audit-write-transact-sql.md). Typically triggers or stored procedures include calls to **sp_audit_write** to enable auditing of important events.|  
+|USER_DEFINED_AUDIT_GROUP|This group monitors events raised by using [sp_audit_write (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-audit-write-transact-sql.md). Typically triggers or stored procedures include calls to **sp_audit_write** to enable auditing of important events.|
+|LEDGER_OPERATION_GROUP | This event is raised for following actions GENERATE LEDGER DIGEST - When you generate a ledger digest ,VERIFY LEDGER - When you verify a ledger digest. **Applies to Azure SQL Database.**|
 
 ### Considerations  
  Server-level action groups cover actions across a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance. For example, any schema object access check in any database is recorded if the appropriate action group is added to a server audit specification. In a database audit specification, only schema object accesses in that database are recorded.  
@@ -160,6 +161,7 @@ Server-level audit action groups are actions similar to [!INCLUDE[ssNoVersion](.
 |SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP|Indicates that a principal successfully logged in to a contained database.|  
 |USER_CHANGE_PASSWORD_GROUP|This event is raised whenever the password of a contained database user is changed by using the ALTER USER statement.|  
 |USER_DEFINED_AUDIT_GROUP|This group monitors events raised by using [sp_audit_write (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-audit-write-transact-sql.md).|  
+|LEDGER_OPERATION_GROUP | This event is raised for following actions ENABLE LEDGER - When you create a new ledger table ,ALTER LEDGER - When you drop a ledger table and ALTER LEDGER CONFIGURATION **Applies to Azure SQL Database.**|
 
 ## Database-Level Audit Actions  
  Database-level actions support the auditing of specific actions directly on database schema and schema objects, such as Tables, Views, Stored Procedures, Functions, Extended Stored Procedures, Queues, Synonyms. Types, XML Schema Collection, Database, and Schema are not audited. The audit of schema objects may be configured on Schema and Database, which means that events on all schema objects contained by the specified schema or database will be audited. The following table describes database-level audit actions.