Skip to content

Commit 71046a0

Browse files
authored
Merge pull request #167627 from DavidTrigano/patch-32
Update auditing-overview.md
2 parents ad4d302 + efc96dd commit 71046a0

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/azure-sql/database/auditing-overview.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
88
author: DavidTrigano
99
ms.author: datrigan
1010
ms.reviewer: vanto
11-
ms.date: 07/22/2021
11+
ms.date: 08/01/2021
1212
ms.custom: azure-synapse, sqldbrb=1
1313
---
1414
# Auditing for Azure SQL Database and Azure Synapse Analytics
@@ -78,6 +78,7 @@ An auditing policy can be defined for a specific database or as a default [serve
7878
- When using Azure AD Authentication, failed logins records will *not* appear in the SQL audit log. To view failed login audit records, you need to visit the [Azure Active Directory portal](../../active-directory/reports-monitoring/concept-sign-ins.md), which logs details of these events.
7979
- Logins are routed by the gateway to the specific instance where the database is located. In the case of AAD logins, the credentials are verified before attempting to use that user to login into the requested database. In the case of failure, the requested database is never accessed, so no auditing occurs. In the case of SQL logins, the credentials are verified on the requested data, so in this case they can be audited. Successful logins, which obviously reach the database, are audited in both cases.
8080
- After you've configured your auditing settings, you can turn on the new threat detection feature and configure emails to receive security alerts. When you use threat detection, you receive proactive alerts on anomalous database activities that can indicate potential security threats. For more information, see [Getting started with threat detection](threat-detection-overview.md).
81+
- After a database with auditing enabled is copied to another Azure SQL logical server, you may receive an email notifying you that the audit failed. This is a known issue and auditing should work as expected on the newly copied database.
8182

8283
## <a id="setup-auditing"></a>Set up auditing for your server
8384

@@ -296,4 +297,4 @@ You can manage Azure SQL Database auditing using [Azure Resource Manager](../../
296297

297298
- Data Exposed episode [What's New in Azure SQL Auditing](https://channel9.msdn.com/Shows/Data-Exposed/Whats-New-in-Azure-SQL-Auditing) on Channel 9.
298299
- [Auditing for SQL Managed Instance](../managed-instance/auditing-configure.md)
299-
- [Auditing for SQL Server](/sql/relational-databases/security/auditing/sql-server-audit-database-engine)
300+
- [Auditing for SQL Server](/sql/relational-databases/security/auditing/sql-server-audit-database-engine)

0 commit comments

Comments
 (0)