20260213 metadata, edits

Updated the date to 02/13/2026 and restructured the explanation about the restart operation for clarity.

Author: WilliamDAssafMSFT

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/13/2026
 ms.service: azure-sql-database
 ms.subservice: high-availability
 ms.topic: how-to
@@ -22,7 +22,11 @@ This article provides steps to restart an Azure SQL Database or elastic pool fro
 > [!IMPORTANT]  
 > 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).  Because the restart operation is intrusive and a large number of them could stress the platform, 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.  Check [Azure Service Health](https://learn.microsoft.com/en-us/azure/service-health/overview) for any ongoing issues before using the restart operation.
+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](https://learn.microsoft.com/en-us/azure/service-health/overview) for any ongoing issues.
 
 ## Restart a database