Merge pull request #36622 from mhyon/20260211-restart-database-for-hs

20260211 Hyperscale supported and notes about usage

Author: prmerger-automator[bot]

azure-sql/database/restart-database.md

@@ -5,7 +5,7 @@ description: Learn about restarting a database or elastic pool in Azure SQL Data
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mahyon, randolphwest
-ms.date: 10/21/2025
+ms.date: 02/25/2026
 ms.service: azure-sql-database
 ms.subservice: high-availability
 ms.topic: how-to
@@ -20,9 +20,13 @@ monikerRange: "=azuresql || =azuresql-db"
 This article provides steps to restart an Azure SQL Database or elastic pool from the Azure portal.
 
 > [!IMPORTANT]  
-> The restart feature in the Azure portal is in preview and not recommended for production use. Hyperscale databases and Hyperscale elastic pools aren't supported in this preview.
+> The restart feature in the Azure portal is in preview and not recommended for production use.
 
-The restart operation is designed to resolve transient issues that might affect database connectivity or performance. Restarting a database or elastic pool temporarily takes it offline, causing a brief interruption in service. However, it doesn't affect the data stored within the database. The restart operation utilizes the same APIs that can be used to [test your application fault resiliency](high-availability-sla-local-zone-redundancy.md#test-application-fault-resiliency).
+The restart operation is designed to resolve transient issues that might affect database connectivity or performance. Restarting a database or elastic pool temporarily takes it offline, causing a brief interruption in service. However, it doesn't affect the data stored within the database. The restart operation utilizes the same APIs that can be used to [test your application fault resiliency](high-availability-sla-local-zone-redundancy.md#test-application-fault-resiliency). 
+
+Only one failover call is allowed every 15 minutes for each database or elastic pool. 
+
+The restart operation is not recommended for use when there are wide-spread service issues. Before initiating a restart, check [Azure Service Health](/azure/service-health/overview) for any ongoing issues.
 
 ## Restart a database