Skip to content

Commit 2745163

Browse files
Merge pull request #33516 from sravanisaluru/patch-29
Update auditing-setup.md
2 parents 2f1876d + da4f4ab commit 2745163

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

azure-sql/database/auditing-setup.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ titleSuffix: Azure SQL Database & Azure Synapse Analytics
44
description: This article provides an overview of how to set up Auditing and storing those audits to an Azure storage account, Log Analytics workspace, or Event Hubs destination.
55
author: sravanisaluru
66
ms.author: srsaluru
7-
ms.reviewer: mathoma, vanto
8-
ms.date: 09/17/2024
7+
ms.reviewer: mathoma, vanto, randolphwest
8+
ms.date: 04/01/2025
99
ms.service: azure-sql-database
1010
ms.subservice: security
1111
ms.topic: how-to
@@ -53,8 +53,10 @@ To configure writing audit logs to a storage account, select **Storage** when yo
5353

5454
:::image type="content" source="media/auditing-setup/auditing-select-storage.png" alt-text="Screenshot that shows storage account authentication types for Auditing." lightbox="media/auditing-setup/auditing-select-storage.png":::
5555

56-
> [!NOTE]
57-
> If you are deploying from the Azure portal, make sure that the storage account is in the same region as your database and server. If you are deploying through other methods, the storage account can be in any region.
56+
If you're deploying from the Azure portal, make sure that the storage account is in the same region as your database and server. If you're deploying through other methods, the storage account can be in any region.
57+
58+
> [!WARNING]
59+
> For storage authentication, use Managed Identity. Storage Access Keys pose a security risk because if they are compromised, unauthorized individuals can gain access to your storage account, potentially reading, writing, or deleting your data. To mitigate these risks, it's essential to rotate your keys regularly and use Azure Key Vault to manage and rotate your keys securely.
5860
5961
- The default value for retention period is 0 (unlimited retention). You can change this value by moving the **Retention (Days)** slider in **Advanced properties** when configuring the storage account for auditing.
6062
- If you change retention period from 0 (unlimited retention) to any other value, the retention will only apply to logs written after the retention value was changed. Logs written during the period when retention days were set to unlimited retention are preserved, even after retention is enabled.
@@ -72,15 +74,11 @@ To configure writing audit logs to an event hub, select **Event Hub**. Select th
7274
:::image type="content" source="media/auditing-setup/auditing-select-event-hub.png" alt-text="Screenshot showing the Event hub." lightbox="media/auditing-setup/auditing-select-event-hub.png":::
7375

7476
> [!NOTE]
75-
> If you are using multiple targets like storage account, log analytics, or event hub, make sure you have permissions for all the targets else saving audit configuration would fail as it will try to save the settings for all targets.
76-
77-
## Next steps
78-
79-
> [!div class="nextstepaction"]
80-
> [Use Auditing to analyze audit logs and reports](auditing-analyze-audit-logs.md)
77+
> If you're using multiple targets like storage account, log analytics, or event hub, make sure you have permissions for all the targets else saving audit configuration would fail as it will try to save the settings for all targets.
8178
8279
## Related content
8380

81+
- [Use Auditing to analyze audit logs and reports](auditing-analyze-audit-logs.md)
8482
- [Auditing for Azure SQL Database and Azure Synapse Analytics](auditing-overview.md)
8583
- [What's New in Azure SQL Auditing](/Shows/Data-Exposed/Whats-New-in-Azure-SQL-Auditing)
8684
- [Get started with Azure SQL Managed Instance auditing](../managed-instance/auditing-configure.md)

0 commit comments

Comments
 (0)