Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

azure-sql/database/automated-backups-change-settings.md

@@ -10,7 +10,6 @@ ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
 ms.custom:
-  - references_regions
   - devx-track-azurepowershell
   - devx-track-azurecli
   - azure-sql-split

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

@@ -10,7 +10,6 @@ ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
 ms.custom:
-  - references_regions
   - azure-sql-split
   - build-2024
   - ignite-2024
@@ -77,7 +76,7 @@ You can choose one of the following storage redundancies for backups:
 
    :::image type="content" source="media/automated-backups-overview/multi-paired-zrs.svg" alt-text="Diagram showing the zone-redundant storage (ZRS) option.":::
 
-- **Geo-redundant storage (GRS)**: Copies your backups synchronously three times within a single physical location in the primary region by using LRS. Then it copies your data asynchronously three times to a single physical location in the [paired](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies) secondary region. 
+- **Geo-redundant storage (GRS)**: Copies your backups synchronously three times within a single physical location in the primary region by using LRS. Then it copies your data asynchronously three times to a single physical location in the [paired secondary region](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies). 
 
   The result is:
 
@@ -132,7 +131,7 @@ Automatic backups on secondary replicas:
 - Bring improved performance and predictability to the Business Critical service tier.
 
 > [!NOTE]
-> - Create a Microsoft support ticket to disable the feature for your instance. 
+> Create a Microsoft support ticket to disable the feature for your instance. 
 
 ## <a id="restore-capabilities"></a> Restore capabilities and features
 

azure-sql/database/dns-alias-overview.md

@@ -55,7 +55,6 @@ The following properties apply to each DNS alias for your server:
 - *Server is required:* A DNS alias cannot be created unless it references exactly one server, and the server must already exist. An updated alias must always reference exactly one existing server.
   - When you drop a server, the Azure system also drops all DNS aliases that refer to the server.
 - *Not bound to any region:* DNS aliases are not bound to a region. Any DNS aliases can be updated to refer to a server that resides in any geographic region.
-  - However, when updating an alias to refer to another server, both servers must exist in the same Azure *subscription*.
 - *Permissions:* To manage a DNS alias, the user must have *Server Contributor* permissions, or higher. For more information, see [Get started with Azure role-based access control in the Azure portal](/azure/role-based-access-control/overview).
 
 ## Manage your DNS aliases
@@ -100,4 +99,4 @@ Presently, a DNS alias has the following limitations:
 - [Overview of business continuity with Azure SQL Database](business-continuity-high-availability-disaster-recover-hadr-overview.md), including disaster recovery.
 - [Server DNS Aliases API](/rest/api/sql/server-dns-aliases)
 - [PowerShell for DNS Alias to Azure SQL Database](dns-alias-powershell-create.md)
-- [Geo-restore for Azure SQL Database](recovery-using-backups.md#geo-restore)
+- [Geo-restore for Azure SQL Database](recovery-using-backups.md#geo-restore)

azure-sql/database/dtu-benchmark.md

@@ -8,7 +8,6 @@ ms.date: 03/29/2022
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: conceptual
-ms.custom: references_regions
 ---
 # DTU benchmark 
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]

azure-sql/database/high-availability-sla-local-zone-redundancy.md

@@ -5,12 +5,11 @@ description: Learn about the architecture of Azure SQL Database that achieves av
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: rsetlem, mathoma, randolphwest
-ms.date: 11/19/2024
+ms.date: 02/18/2025
 ms.service: azure-sql-database
 ms.subservice: high-availability
 ms.topic: conceptual
 ms.custom:
-  - references_regions
   - azure-sql-split
   - ignite-2024
 monikerRange: "=azuresql || =azuresql-db || =fabricsql"
@@ -55,7 +54,7 @@ Within each of the three availability models, SQL Database supports local redund
 The following table shows the availability options based on service tiers: 
 
 
-| Service tier | High availability model | locally redundant availability | Zone-redundant availability |
+| Service tier | High availability model | Locally redundant availability | Zone-redundant availability |
 |---|---|---| --- |
 | General Purpose (vCore) | Remote storage  |  Yes | Yes |
 | Business Critical (vCore) | Local storage  | Yes | Yes |
@@ -112,7 +111,9 @@ Compute nodes in all Hyperscale layers run on Azure Service Fabric, which contro
 
 For more information on high availability in Hyperscale, see [Database High Availability in Hyperscale](./service-tier-hyperscale.md#database-high-availability-in-hyperscale).
 
-## <a id="zone-redundant-availability"></a>High availability through zone-redundancy
+<a id="zone-redundant-availability"></a>
+
+## High availability through zone-redundancy
 
 Zone-redundant availability ensures your data is spread across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
 
@@ -135,39 +136,8 @@ The zone-redundant version of the high availability architecture for the General
 
 :::image type="content" source="media/high-availability-sla/zone-redundant-for-general-purpose.png" alt-text="Diagram of Zone redundant configuration for General Purpose.":::
 
-Consider the following when configuring your General Purpose databases with zone-redundancy: 
-
-- For General Purpose tier the zone-redundant configuration is Generally Available in the following regions: 
-  - (Africa) South Africa North
-  - (Asia Pacific) Australia East
-  - (Asia Pacific) East Asia
-  - (Asia Pacific) Japan East
-  - (Asia Pacific) Korea Central
-  - (Asia Pacific) Southeast Asia
-  - (Asia Pacific) Central India
-  - (Asia Pacific) China North 3
-  - (Asia Pacific) UAE North
-  - (Europe) France Central
-  - (Europe) Germany West Central
-  - (Europe) Italy North
-  - (Europe) North Europe
-  - (Europe) Norway East
-  - (Europe) Poland Central
-  - (Europe) West Europe
-  - (Europe) UK South
-  - (Europe) Switzerland North
-  - (Europe) Sweden Central
-  - (Middle East) Israel Central
-  - (Middle East) Qatar Central
-  - (North America) Canada Central
-  - (North America) Central US
-  - (North America) East US
-  - (North America) East US 2
-  - (North America) South Central US
-  - (North America) West US 2
-  - (North America) West US 3
-  - (South America) Brazil South
-- For zone redundant availability, choosing a [maintenance window](maintenance-window.md) other than the default is currently available in [select regions](maintenance-window.md#azure-sql-database-region-support-for-maintenance-windows).  
+- For regional availability, see [General purpose zone redundancy feature availability by region for Azure SQL Database](region-availability.md#general-purpose-service-tier-zone-redundancy-availability).
+- For zone redundant availability, choosing a [maintenance window](maintenance-window.md) other than the default is currently available in select regions. For more information, see [Maintenance window availability by region for Azure SQL Database](region-availability.md#maintenance-window-availability).
 - Zone-redundant configuration is only available in SQL Database when standard-series (Gen5) hardware is selected. 
 - Zone-redundancy isn't available for Basic and Standard service tiers in the DTU purchasing model. 
 
@@ -182,13 +152,13 @@ The zone-redundant version of the high availability architecture is illustrated
 Consider the following when configuring your Premium or Business Critical databases with zone-redundancy: 
 
 - For up to date information about the regions that support zone-redundant databases, see [Services support by region](/azure/reliability/availability-zones-region-support).
-- For zone redundant availability, choosing a [maintenance window](./maintenance-window.md) other than the default is currently available in [select regions](maintenance-window.md#azure-sql-database-region-support-for-maintenance-windows).
+- For zone redundant availability, choosing a [maintenance window](maintenance-window.md) other than the default is currently available in select regions. For more information, see [Maintenance window availability by region for Azure SQL Database](region-availability.md#maintenance-window-availability).
 
 ### <a id="hyperscale-service-tier-zone-redundant-availability"></a> Hyperscale service tier
 
 It's possible to configure zone-redundancy for databases in the Hyperscale service tier. To learn more, review [Create zone-redundant Hyperscale database](hyperscale-create-zone-redundant-database.md). 
 
-Enabling this configuration ensures zone-level resiliency through replication across Availability Zones for all Hyperscale layers. By selecting zone-redundancy, you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. All Azure regions that have [Availability Zones](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) support zone redundant Hyperscale database. Zone redundancy support for Hyperscale PRMS and MOPRMS hardware is available in regions listed [here](service-tiers-sql-database-vcore.md#hyperscale-premium-series-availability).
+Enabling this configuration ensures zone-level resiliency through replication across Availability Zones for all Hyperscale layers. By selecting zone-redundancy, you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. All Azure regions that have [Availability Zones](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) support zone redundant Hyperscale database. Zone redundancy support for Hyperscale PRMS and MOPRMS hardware is available in certain regions. For more information, see [Hyperscale premium-series availability by region for Azure SQL Database](region-availability.md#hyperscale-premium-series-availability).
 
 Zone-redundant availability is supported in both Hyperscale standalone databases and Hyperscale elastic pools. For more information, see [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md).
 
@@ -199,7 +169,7 @@ The following diagram demonstrates the underlying architecture for zone redundan
 Consider the following limitations:
 
 - Zone redundant configuration can only be specified during database creation. This setting can't be modified once the resource is provisioned. Use [Database copy](database-copy.md), [point-in-time restore](recovery-using-backups.md#point-in-time-restore), or create a [geo-replica](active-geo-replication-overview.md) to update the zone redundant configuration for an existing Hyperscale database. When using one of these update options, if the target database is in a different region than the source or if the database backup storage redundancy from the target differs from the source database, the [copy operation](database-copy.md#database-copy-for-hyperscale-databases) will be a size of data operation.
-- For zone redundant availability, choosing a [maintenance window](maintenance-window.md) other than the default is currently available in [select regions](maintenance-window.md#azure-sql-database-region-support-for-maintenance-windows).
+- For zone redundant availability, choosing a [maintenance window](maintenance-window.md) other than the default is currently available in select regions. For more information, see [Maintenance window availability by region for Azure SQL Database](region-availability.md#maintenance-window-availability).
 - There's currently no option to specify zone redundancy when migrating a database to Hyperscale using the Azure portal. However, zone redundancy can be specified using Azure PowerShell, Azure CLI, or the REST API when migrating an existing database from another Azure SQL Database service tier to Hyperscale. Here's an example with Azure CLI: 
 
    ```cli

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

@@ -4,13 +4,12 @@ titleSuffix: Azure SQL Database
 description: Learn about automated backups for Hyperscale databases in Azure SQL Database.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.reviewer: dinethi, mathoma, danil, randolphwest, 
+ms.reviewer: dinethi, mathoma, danil, randolphwest
 ms.date: 02/03/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
 ms.custom:
-  - references_regions
   - azure-sql-split
 monikerRange: "=azuresql || =azuresql-db"
 ---
@@ -121,7 +120,7 @@ The following screenshot shows an example cost analysis.
 
 Hyperscale supports configurable storage redundancy. When you're creating a Hyperscale database, you can choose your preferred storage type:  read-access geo-zone-redundant storage (RA-GZRS), read-access geo-redundant storage (RA-GRS), zone-redundant storage (ZRS), or locally redundant storage (LRS).
 
-- **Geo-zone-redundant storage**: Copies your backups synchronously across three Azure availability zones in the primary region. similar to zone-redundant storage(ZRS). In addition, it copies your data asynchronously to a single physical location in the [paired](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies) secondary region. It's currently available in only [certain regions](/azure/storage/common/storage-redundancy#geo-zone-redundant-storage).
+- **Geo-zone-redundant storage**: Copies your backups synchronously across three Azure availability zones in the primary region. similar to zone-redundant storage(ZRS). In addition, it copies your data asynchronously to a single physical location in the [paired secondary region](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies). It's currently available in only [certain regions](/azure/storage/common/storage-redundancy#geo-zone-redundant-storage).
 
 For more information about how the backups are replicated for other storage types, see [backup storage redundancy](automated-backups-overview.md#backup-storage-redundancy).
 

azure-sql/database/maintenance-window.md

@@ -5,12 +5,11 @@ description: Understand how the Azure SQL Database maintenance window can be con
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: urosmil, scottkim, mathoma
-ms.date: 08/06/2024
+ms.date: 02/18/2025
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: conceptual
 ms.custom:
-  - references_regions
   - ignite-2023
   - azure-sql-split
 monikerRange: "=azuresql||=azuresql-db"
@@ -90,75 +89,14 @@ Choosing a maintenance window other than the default is available on all SLOs, *
 
 Other scenarios:
 
-- Maintenance window for Hyperscale elastic pools is in preview and is available in specific regions and configurations. For more information, see [Blog: Maintenance window support for Azure SQL Database Hyperscale elastic pools](https://aka.ms/hsep-fmw).
+- Maintenance window for Hyperscale elastic pools is in preview and is available in specific regions and configurations. For more information, see [Blog: Maintenance window support for Azure SQL Database Hyperscale elastic pools](https://aka.ms/hsep-fmw) and [Feature Availability by Region for Azure SQL Database](region-availability.md#maintenance-window-availability).
 - Maintenance window is supported for named replicas.
 
 <!-- Check Known limitations in azure-sql/database/service-tier-hyperscale.md as well -->
 
 ### Azure SQL Database region support for maintenance windows
 
-Choosing a maintenance window for Azure SQL Database other than the default is currently available in the following regions, organized by purchasing model.
-
-The following table is for databases that are not [zone-redundant](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability). For databases in an [Azure Availability Zone](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability), see [the table for zone-redundant databases.](#ZR-maintenance-window-availability)
-
-| Azure Region | Hyperscale premium-series and premium-series memory optimized | Hyperscale standard-series | All other Azure SQL Database purchasing models and tiers |
-|:---|:---|:---|:---|
-| Australia East | Yes | Yes | Yes |
-| Australia Southeast | | Yes | Yes |
-| Brazil South | | Yes | Yes |
-| Brazil Southeast | | Yes | Yes |
-| Canada Central  | Yes | Yes | Yes |
-| Canada East  | | Yes | Yes |
-| Central India | | Yes | Yes |
-| Central US | Yes | Yes | Yes |
-| China East 2 | | Yes | Yes |
-| China North 2 | | Yes | Yes |
-| East US 1 | Yes | Yes | Yes |
-| East US 2  | Yes | Yes | Yes |
-| East Asia  | | Yes | Yes |
-| France Central  | | Yes | Yes |
-| France South  | | Yes | Yes |
-| Germany West Central | | Yes | Yes |
-| Japan East | Yes | Yes | Yes |
-| Japan West | | Yes | Yes |
-| North Central US | | Yes | Yes |
-| North Europe | Yes | Yes | Yes |
-| South Africa North | | Yes | Yes |
-| South Central US | Yes | Yes | Yes |
-| South India | | Yes | Yes |
-| Southeast Asia | Yes | Yes | Yes |
-| Switzerland North | | Yes | Yes |
-| UAE North | | Yes | Yes |
-| UK South | Yes | Yes | Yes |
-| UK West | | Yes | Yes |
-| US Gov Texas | | Yes | Yes |
-| US Gov Virginia | | Yes | Yes |
-| West Central US | | Yes | Yes |
-| West Europe | Yes | Yes | Yes |
-| West US | Yes | Yes | Yes |
-| West US 2 | Yes | Yes | Yes |
-| West US 3 | Yes | Yes | Yes |
-
-<a id="ZR-maintenance-window-availability"></a>
-
-The following table is for [zone-redundant](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability) databases.
-
-| Azure Region  | Hyperscale premium-series and premium-series memory optimized | Hyperscale standard-series | All other Azure SQL Database purchasing models and tiers in an [Azure Availability Zone](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability) |
-|:---|:---|:---|:---|
-| Australia East | Yes | Yes | Yes |
-| Canada Central  |  Yes | Yes | Yes |
-| Central US |  Yes | Yes | Yes |
-| East US 1  |  Yes | Yes | Yes |
-| East US 2  | | | Yes |
-| France Central | | Yes | Yes |
-| Japan East | | | Yes |
-| North Europe |  Yes | Yes | Yes |
-| South Central US  | | | Yes |
-| Southeast Asia | Yes | Yes |  Yes |
-| UK South | Yes | Yes | Yes |
-| West Europe |  Yes | Yes | Yes |
-| West US 2 | | | Yes |
-| West US 3 | Yes | Yes | Yes |
+For more information, see [Feature Availability by Region for Azure SQL Database](region-availability.md#maintenance-window-availability).
 
 ## Gateway maintenance
 

azure-sql/database/media/service-tiers-sql-database-vcore/request-dc-series.png

@@ -10,7 +10,6 @@ ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
 ms.custom: 
-  - references_regions
   - sqldbrb=2
 monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 ---