Updating GZRS support (#36086)

MashaMSFT · web-flow · commit 783b74ae94e9 · 2025-12-31T15:57:11.000-05:00
diff --git a/azure-sql/database/automated-backups-overview.md b/azure-sql/database/automated-backups-overview.md
@@ -1,5 +1,5 @@
 ---
-title: Automatic, geo-redundant backups
+title: Automatic, Geo-Redundant Backups
 titleSuffix: Azure SQL Database
 description: Learn how Azure SQL Database automatically backs up all databases and provides a point-in-time restore capability.
 author: WilliamDAssafMSFT
@@ -8,7 +8,7 @@ ms.reviewer: mathoma, danil, dinethi
 ms.date: 09/25/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
-ms.topic: conceptual
+ms.topic: article
 ms.custom:
   - azure-sql-split
   - ignite-2025
@@ -142,7 +142,7 @@ For information on recovery times, see [RTO and RPO](business-continuity-high-av
 |---|---|---|---|
 | **Types of SQL backup** | Full, differential, log. | Most recent geo-replicated copies of PITR backups. | Only the full backups. |
 | **Retention** | 7 days by default, configurable between 1 and 35 days (except Basic databases, which are configurable between 1 and 7 days). | Enabled by default, same as source.<sup>2</sup>| Not enabled by default. Retention is up to 10 years. |
-| **Azure Storage**  | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant. Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
+| **Azure Storage**  | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant or geo-zone redundant (GZRS). Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
 | **Configure backups as [immutable](/azure/storage/blobs/immutable-storage-overview)** | Not supported | Not supported | [Supported](backup-immutability.md) | 
 | **Restoring a new database in the same region** | Supported | Supported | Supported |
 | **Restoring a new database in another region** | Not supported | Supported in any Azure region | Supported in any Azure region |
diff --git a/azure-sql/database/recovery-using-backups.md b/azure-sql/database/recovery-using-backups.md
@@ -1,5 +1,5 @@
 ---
-title: Restore a database from a backup
+title: Restore a Database from a Backup
 titleSuffix: Azure SQL Database
 description: Learn about point-in-time restore, which enables you to roll back a database in Azure SQL Database up to 35 days.
 author: dnethi
@@ -9,10 +9,10 @@ ms.date: 05/14/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
-monikerRange: "=azuresql || =azuresql-db"
 ms.custom:
   - azure-sql-split
   - sfi-image-nochange
+monikerRange: "=azuresql || =azuresql-db"
 ---
 # Restore a database from a backup in Azure SQL Database
 
@@ -233,7 +233,7 @@ To restore a deleted database by using the REST API:
 Geo-restore uses geo-replicated backups as the source. You can restore a database on any [logical server](logical-servers.md) in any Azure region from the most recent geo-replicated backups. You can request a geo-restore even if an outage has made the database or the entire region inaccessible.
 
 > [!IMPORTANT]  
-> - Geo-restore is available only for databases configured with geo-redundant [backup storage](automated-backups-overview.md#backup-storage-redundancy). If you're not currently using geo-replicated backups for a database, you can change this by [configuring backup storage redundancy](automated-backups-change-settings.md#configure-backup-storage-redundancy).
+> - Geo-restore is available only for databases configured with geo-redundant or geo-zone redundant (GZRS) [backup storage](automated-backups-overview.md#backup-storage-redundancy). If you're not currently using geo-replicated backups for a database, you can change this by [configuring backup storage redundancy](automated-backups-change-settings.md#configure-backup-storage-redundancy).
 > - You can perform geo-restore only on databases that reside in the same subscription.
 
 Geo-restore is the default recovery option when your database is unavailable because of an incident in the hosting region. You can restore the database to a server in any other region.
diff --git a/azure-sql/managed-instance/automated-backups-overview.md b/azure-sql/managed-instance/automated-backups-overview.md
@@ -8,7 +8,7 @@ ms.reviewer: mathoma, wiassaf, mlandzic, strrodic, danil, randolphwest
 ms.date: 06/26/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
-ms.topic: conceptual
+ms.topic: article
 ms.custom:
   - azure-sql-split
   - build-2024
@@ -117,7 +117,7 @@ This table summarizes the capabilities and features of [point-in-time restore](r
 | **Recovery point objective (RPO)** | Approximately 10 minutes, based on compute size and amount of database activity. | Up to 1 hour, based on geo-replication. <sup>1</sup> | One week (or user's policy). |
 | **Recovery time objective (RTO)** | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). |
 | **Retention** | 1 to 35 days. | Enabled by default, same as source. <sup>2</sup> | Not enabled by default. Retention is up to 10 years. |
-| **Azure storage** | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant. Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
+| **Azure storage** | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant or geo-zone redundant (GZRS). Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
 | **Configure backups as [immutable](/azure/storage/blobs/immutable-storage-overview)** | Not supported | Not supported | Not supported |
 | **Update policy** <sup>3</sup> | Must match, or upgrade | Must match, or upgrade | Must match, or upgrade |
 | **Restoring a new database in the same region** | Supported | Supported | Supported |
diff --git a/azure-sql/managed-instance/recovery-using-backups.md b/azure-sql/managed-instance/recovery-using-backups.md
@@ -1,5 +1,5 @@
 ---
-title: Restore a database from a backup
+title: Restore a Database from a Backup
 titleSuffix: Azure SQL Managed Instance
 description: Learn about point-in-time restore, which enables you to roll back a database in Azure SQL Managed Instance up to 35 days.
 author: dinethi
@@ -12,7 +12,7 @@ ms.topic: how-to
 ms.custom:
   - azure-sql-split
   - build-2024
-monikerRange: "=azuresql||=azuresql-mi"
+monikerRange: "=azuresql || =azuresql-mi"
 ---
 # Restore a database from a backup in Azure SQL Managed Instance
 [!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
@@ -163,7 +163,7 @@ If you need to restore an unintentionally deleted SQL managed instance, contact
 ## Geo-restore
 
 > [!IMPORTANT]
-> - Geo-restore is available only for managed instances configured with geo-redundant [backup storage](automated-backups-overview.md#backup-storage-redundancy). If you're not currently using geo-replicated backups for a database, you can change this by [configuring backup storage redundancy](automated-backups-change-settings.md#configure-backup-storage-redundancy).
+> - Geo-restore is available only for managed instances configured with geo-redundant or geo-zone redundant (GZRS) [backup storage](automated-backups-overview.md#backup-storage-redundancy). If you're not currently using geo-replicated backups for a database, you can change this by [configuring backup storage redundancy](automated-backups-change-settings.md#configure-backup-storage-redundancy).
 > - You can perform geo-restore on managed instances that reside in the same subscription only.
 
 Geo-restore is the default recovery option when your database is unavailable because of an incident in the hosting region. You can restore the database to an instance in any other region. You can restore a database on any managed instance in any Azure region from the most recent geo-replicated backups. Geo-restore uses a geo-replicated backup as its source. You can request a geo-restore even if an outage has made the database or datacenter inaccessible.
