Merge pull request #36084 from oslake/patch-28

Update serverless tier overview with new date and triggers

Author: prmerger-automator[bot]

azure-sql/database/serverless-tier-overview.md

@@ -4,7 +4,7 @@ description: This article describes the new serverless compute tier and compares
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: moslake, mathoma, dfurman, blakhani
-ms.date: 12/12/2025
+ms.date: 12/15/2025
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: conceptual
@@ -207,6 +207,10 @@ Auto-resuming is triggered if any of the following conditions are true at any ti
 
 Monitoring, management, or other solutions performing any of these operations trigger auto-resuming. Auto-resuming is also triggered during the deployment of some service updates that require the database be online.
 
+#### Auto-resume trigger indentification
+
+Auto-resume triggers are exposed in the Azure Monitor activity log for **Resume Databases** operations under the `Caller` property in the JSON of the **Succeeded** event.
+
 ### Connectivity
 
 If a serverless database is paused, the first connection attempt resumes the database and returns an error stating that the database is unavailable with error code 40613. Once the database is resumed, retry the connection. Database clients following [connection retry logic recommendations](/azure/architecture/patterns/retry) should not need to be modified. For connection retry logic options and recommendations, see: