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

Author: Learn Build Service GitHub App

azure-sql/database/auditing-setup.md

@@ -5,7 +5,7 @@ description: This article provides an overview of how to set up Auditing and sto
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: mathoma, vanto, randolphwest
-ms.date: 04/01/2025
+ms.date: 05/07/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: how-to
@@ -56,7 +56,7 @@ To configure writing audit logs to a storage account, select **Storage** when yo
 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.
 
 > [!WARNING]  
-> 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.
+> For storage authentication, use Managed Identity. Storage Access Keys pose a security risk because if they're 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.
 
 - 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.
   - 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.
@@ -73,8 +73,12 @@ To configure writing audit logs to an event hub, select **Event Hub**. Select th
 
 :::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":::
 
+When auditing is configured with Azure external monitors (for example, Event Hubs or Log Analytics) as the target, an additional diagnostic settings resource named *SQLSecurityAuditEvents_XXXX-XXXX-XXX* is created, which is critical for the proper functioning of auditing.
+
+If the diagnostic settings are deleted, either intentionally or unintentionally, the auditing functionality will fail silently, and audit logs won't be sent to the target location. To prevent this, configure alerts for the deletion of diagnostic settings to notify users and take necessary actions. For more information on creating action groups and configuring alerts, see [Action groups](/azure/azure-monitor/alerts/action-groups) and [Create or edit an activity log, service health, or resource health alert rule](/azure/azure-monitor/alerts/alerts-create-activity-log-alert-rule).
+
 > [!NOTE]  
-> 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.
+> If you're using multiple targets like storage account, Log Analytics, or Event Hubs, make sure you have permissions for all the targets, or else saving audit configuration would fail as it tries to save the settings for all targets.
 
 ## Related content
 

azure-sql/managed-instance/resource-limits.md

@@ -36,14 +36,16 @@ Hardware generations have different characteristics, as described in the followi
 | **Number of vCores**<br />vCore=1 LP (hyper-thread) | 2<sup>1</sup> -80 vCores | 2<sup>1</sup> -128 vCores | 4-128 vCores |
 | **Max memory (memory/vCore ratio)** | 5.1 GB per vCore - 408 GB maximum<br />Add more vCores to get more memory. | 7 GB per vCore up to 80 vCores - 560 GB maximum | 13.6 GB per vCore up to 64 vCores - 870.4 GB maximum |
 | **Max In-Memory OLTP memory** | Instance limit: 0.8 - 1.65 GB per vCore | Instance limit: 1.1 - 2.3 GB per vCore | Instance limit: 2.2 - 4.5 GB per vCore |
-| **Max instance reserved storage** <sup>2</sup> | **General Purpose:** up to 16 TB<br />**Business Critical:** up to 4 TB | **General Purpose:** up to 16 TB<br />**Business Critical:** up to 16 TB<sup>3</sup> | **General Purpose:** up to 16 TB<br />**Business Critical:** up to 16 TB |
+| **Max instance reserved storage** <sup>2</sup> | **General Purpose:** up to 32 TB<sup>4</sup><br />**Business Critical:** up to 4 TB | **General Purpose:** up to 32 TB<sup>4</sup><br />**Business Critical:** up to 16 TB<sup>3</sup> | **General Purpose:** up to 32 TB<sup>4</sup><br />**Business Critical:** up to 16 TB |
 
 <sup>1</sup> Deploying a 2-vCore instance is only possible inside an [instance pool](instance-pools-overview.md).
 
 <sup>2</sup> Dependent on [the number of vCores](#service-tier-characteristics).
 
 <sup>3</sup> The [following regions](#regional-supports-for-memory-optimized-premium-series-hardware-and-for-premium-series-hardware-with-16-tb-storage) can provide 16 TB of storage, while other regions limit available storage to 5.5 TB.
 
+<sup>4</sup> 16 TB for classic General Purpose. 32 TB only for [Next-gen General Purpose service tier (preview)](service-tiers-next-gen-general-purpose-use.md)
+
 > [!NOTE]  
 > If your workload requires storage sizes greater than the available resource limits for Azure SQL Managed Instance, consider the Azure SQL Database [Hyperscale service tier](../database/service-tier-hyperscale.md).
 
@@ -107,7 +109,7 @@ SQL Managed Instance has two [service tiers](service-tiers-managed-instance-vcor
 
 | Hardware generation | General Purpose | Next-gen General Purpose | Business Critical |
 | --- | --- | --- | --- |
-| **Standard-series (Gen5)** | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for other sizes | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for other sizes | - 1 TB for 4, 8, 16 vCores<br />- 2 TB for 24 vCores<br />- 4 TB for 32, 40, 64, 80 vCores |
+| **Standard-series (Gen5)** | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for other sizes | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for 16, 24 vCores<br />- 32 TB for 32, 40, 64, 80 vCores | - 1 TB for 4, 8, 16 vCores<br />- 2 TB for 24 vCores<br />- 4 TB for 32, 40, 64, 80 vCores |
 | **Premium-series** | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for other sizes | - 2 TB for 4, 6 vCores<br />- 8 TB for 8, 10, 12 vCores<br />- 16 TB for 16, 20, 24 vCores<br />- 32 TB for 32, 40, 48, 56, 64, 80, 96, 128 vCores | - 1 TB for 4, 6 vCores<br />- 2 TB for 8, 10, 12 vCores<br />- 4 TB for 16, 20 vCores<br />- 5.5 TB for 24, 32, 40, 48, 56 vCores<br />- 5.5 TB or 16 TB (depending on the region) for 64, 80, 96, 128 vCores<sup>1</sup> |
 | **Memory optimized premium-series** | - 2 TB for 4 vCores<br />- 8 TB for 8 vCores<br />- 16 TB for other sizes | - 2 TB for 4, 6 vCores<br />- 8 TB for 8, 10, 12 vCores<br />- 16 TB for 16, 20, 24 vCores<br />- 32 TB for 32, 40, 48, 56, 64, 80, 96, 128 vCores | - 1 TB for 4, 6 vCores<br />- 2 TB for 8, 10, 12 vCores<br />- 4 TB for 16, 20 vCores<br />- 5.5 TB for 24 vCores<br />- 5.5 TB or 8 TB (depending on the region) for 32, 40 vCores<sup>2</sup><br />- 12 TB for 48, 56 vCores<br />- 16 TB for 64, 80, 96, 128 vCores |