Merge pull request #36183 from MicrosoftDocs/WilliamDAssafMSFT-patch-2

20260107 clarify restore duration

Author: prmerger-automator[bot]

azure-sql/database/hyperscale-automated-backups-overview.md

@@ -5,7 +5,7 @@ description: Learn about automated backups for Hyperscale databases in Azure SQL
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dinethi, mathoma, danil, randolphwest
-ms.date: 02/03/2025
+ms.date: 01/07/2026
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -36,7 +36,7 @@ You can restore a database to any point in time within its backup retention peri
 
 As such, restore isn't a size-of-data operation that remains the same. Restore of a Hyperscale database within the same Azure region finishes in minutes instead of hours or days, even for multi-terabyte databases.
 
-Changing the [storage redundancy](hyperscale-automated-backups-overview.md#data-and-backup-storage-redundancy) when issuing a restore can result in longer restore times as the restore is the size of data, and hence the time is proportional to the database size.
+Changing the [storage redundancy](hyperscale-automated-backups-overview.md#data-and-backup-storage-redundancy) or zone redundancy when issuing a restore can result in longer restore times as the restore is the size of data, and hence the time is proportional to the database size.
 
 Creating new databases by restoring an existing backup or copying the database, also takes advantage of compute and storage separation in Hyperscale. You can create copies for development or testing purposes, even of multi-terabyte databases, in minutes within the same region when you use the same storage type.