From 21d2c2b48f65de2fd8810f91a4f3a18e94154eaf Mon Sep 17 00:00:00 2001
From: sravani saluru <31034666+sravanisaluru@users.noreply.github.com>
Date: Wed, 11 Dec 2024 11:46:10 +0530
Subject: [PATCH] Update Set-AzSqlDatabaseAudit.md (#26858)

---
 src/Sql/Sql/help/Set-AzSqlDatabaseAudit.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Sql/Sql/help/Set-AzSqlDatabaseAudit.md b/src/Sql/Sql/help/Set-AzSqlDatabaseAudit.md
index 3f181c422975..48241319bc81 100644
--- a/src/Sql/Sql/help/Set-AzSqlDatabaseAudit.md
+++ b/src/Sql/Sql/help/Set-AzSqlDatabaseAudit.md
@@ -110,12 +110,12 @@ RECEIVE
 REFERENCES  
 The general form for defining an action to be audited is:
 [action] ON [object] BY [principal]
-Note that [object] in the above format can refer to an object like a table, view, or stored procedure, or an entire database or schema. For the latter cases, the forms DATABASE::[dbname] and SCHEMA::[schemaname] are used, respectively.
+Note that [object] in the above format can refer to an object like a table, view, or stored procedure, or an entire database or schema.if the reference object is dropped and recreated ,audit configuration should be resaved. For the latter cases, the forms DATABASE::[dbname] and SCHEMA::[schemaname] are used, respectively.
 For example:  
 SELECT on dbo.myTable by public  
 SELECT on DATABASE::myDatabase by public  
 SELECT on SCHEMA::mySchema by public  
-For more information, see https://learn.microsoft.com/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-actions.
+For more information, see https://learn.microsoft.com/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-actions. 
 
 ```yaml
 Type: System.String[]