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

Author: Learn Build Service GitHub App

azure-sql/capacity-errors-troubleshoot.md

@@ -18,34 +18,31 @@ In this article, learn how to resolve capacity errors when deploying Azure SQL D
 
 ## Exceeded quota 
 
-If you encounter any of the following errors when attempting to deploy your Azure SQL resource, please [request to increase your quota](database/quota-increase-request.md): 
+If you encounter any of the following errors when attempting to deploy your Azure SQL resource, [request to increase your quota](database/quota-increase-request.md): 
 
 - `Server quota limit has been reached for this location. Please select a different location with lower server count.`
 - `Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of xx.`
-- During a scale operation, you may see the following error:    
+- During a scale operation, you might see the following error:    
   `Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of xx. `. 
 
 ## Subscription access
 
-Your subscription may not have access to create a server in the selected region if your subscription has not been registered with the SQL resource provider (RP).  
+Your subscription might not have access to create a server in the selected region if your subscription hasn't been registered with the SQL resource provider (RP).  
 
 If you see the following errors, please [register your subscription with the SQL RP](#register-with-sql-rp):
 - `Your subscription does not have access to create a server in the selected region.`
 - `Provisioning is restricted in this region. Please choose a different region. For exceptions to this rule please open a support request with issue type of 'Service and subscription limits' `
 - `Location 'region name' is not accepting creation of new Windows Azure SQL Database servers for the subscription 'subscription id' at this time`
 
-
 ## Enable region 
 
-Your subscription may not have access to create a server in the selected region if that region has not been enabled. To resolve this, file a [support request to enable a specific region](database/quota-increase-request.md#region) for your subscription. 
+Your subscription might not have access to create a server in the selected region if that region hasn't been enabled. To resolve this, file a [support request to enable a specific region](database/quota-increase-request.md#region) for your subscription. 
 
 If you see the following errors, file a support ticket to enable a specific region: 
 - `Your subscription does not have access to create a server in the selected region.`
 - `Provisioning is restricted in this region. Please choose a different region. For exceptions to this rule please open a support request with issue type of 'Service and subscription limits' `
 - `Location 'region name' is not accepting creation of new Windows Azure SQL Database servers for the subscription 'subscription id' at this time`
 
-
-
 ## Register with SQL RP
 
 To deploy Azure SQL resources, register your subscription with the SQL resource provider (RP). 
@@ -80,7 +77,6 @@ To register your subscription using [Azure PowerShell](/powershell/azure/install
 ```powershell-interactive
 # Register the SQL resource provider to your subscription
 Register-AzResourceProvider -ProviderNamespace Microsoft.Sql
-
 ```
 
 ---
@@ -93,12 +89,12 @@ If you're still experiencing provisioning issues, please open a **Region** acces
 
 Azure Program offerings (Azure Pass, Imagine, Azure for Students, MPN, BizSpark, BizSpark Plus, Microsoft for Startups / Sponsorship Offers, Visual Studio Subscriptions / MSDN) have access to a limited set of regions. 
 
-If your subscription is part of an Azure Program offering, and you would like to request access to any of the following regions, please consider using an alternate region instead: 
+If your subscription is part of an Azure Program offering, and you would like to request access to any of the following regions, consider using an alternate region instead: 
 
-_Australia Central, Australia Central 2, Australia SouthEast, Brazil SouthEast, Canada East, China East, China North, China North 2, France South, Germany North, Japan West, JIO India Central, JIO India West, Korea South, Norway West, South Africa West, South India, Switzerland West, UAE Central , UK West, US DoD Central, US DoD East, US Gov Arizona, US Gov Texas, West Central US, West India._ 
+_Australia Central, Australia Central 2, Australia SouthEast, Brazil SouthEast, Canada East, China East, China North, China North 2, France South, Germany North, Japan West, JIO India Central, JIO India West, Korea South, Norway West, South Africa West, South India, Switzerland West, UAE Central, UK West, US DoD Central, US DoD East, US Gov Arizona, US Gov Texas, West Central US, West India._ 
 
 ## Next steps
 
-After you submit your request, it will be reviewed. You will be contacted with an answer based on the information you provided in the form.
+After you submit your request, it will be reviewed. You'll be contacted with an answer based on the information you provided in the form.
 
 For more information about other Azure limits, see [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits).

azure-sql/database-watcher-overview.md

@@ -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"
 ---
@@ -68,28 +67,8 @@ There is no charge per monitored Azure SQL resource or per user, making database
 
 ## Regional availability
 
-At this time, you can create watchers in the following Azure regions:
+At this time, you can create watchers supported Azure regions for [Azure SQL Database](database/region-availability.md#database-watcher-availability) and [Azure SQL Managed Instance](managed-instance/region-availability.md#database-watcher). 
 
-| Azure geography | Azure region |
-|:--|:--|
-| Asia Pacific | Australia Central |
-| Asia Pacific | Australia East |
-| Asia Pacific | Australia Southeast |
-| Asia Pacific | Japan West |
-| Asia Pacific | Korea Central |
-| Asia Pacific | Southeast Asia |
-| Canada | Canada Central |
-| Canada | Canada East |
-| Europe | Germany West Central |
-| Europe | North Europe |
-| Europe | UK South |
-| Europe | Sweden Central |
-| Europe | West Europe |
-| United States | Central US |
-| United States | East US |
-| United States | East US 2 |
-| United States | North Central US |
-| United States | West US |
 
 > [!TIP]
 > A watcher in one Azure region can monitor targets in another region. Similarly, a watcher and its data store can be located in different regions.
@@ -126,7 +105,7 @@ The following table describes the capabilities of database watcher dashboards in
 
 | Capability | Description |
 |:--|:--|
-| **Estate dashboards** | Visualize high-level monitoring data for multiple monitored resources in a common view. Use **heatmaps** to find top resource consuming databases, elastic pools, or SQL managed instances. </br></br>Use the **top queries** view to find top resource consuming queries across your Azure SQL estate, ranking queries by CPU, duration, execution count, etc. </br></br>Use the subscription, resource group, and resource name filters to focus on subsets of your Azure SQL estate.</br></br>Drill through to detailed dashboards for specific resources. |
+| **Estate dashboards** | Visualize high-level monitoring data for multiple monitored resources in a common view. Use **heatmaps** to find top resource consuming databases, elastic pools, or SQL managed instances. </br></br>Use the **top queries** view to find top resource consuming queries across your Azure SQL estate, ranking queries by CPU, duration, execution count, etc. </br></br>Use the subscription, resource group, and resource name filters to focus on subsets of your Azure SQL estate. </br></br>Drill through to detailed dashboards for specific resources. |
 | **Resource dashboards** | Visualize detailed monitoring data for a database, an elastic pool, or a SQL managed instance, including:</br></br>- Active sessions<br>- Backup history<br>- Common performance counters<br>- Connectivity probes<br>- Database and instance properties and configuration<br>- Geo-replication<br>- Index metadata, usage statistics, warnings, and suggestions<br>- Resource usage<br>- Session and connection statistics<br>- SQL Agent job state and history<br>- Storage consumption and performance<br>- Table metadata<br>- Top queries<br>- Wait statistics<br></br>Use resource dropdowns to quickly switch from one resource to another. Use the **estate** link to zoom out to an estate dashboard. |
 | **Filter by time range** | On each dashboard, set the time range to focus on the desired time interval. Use standard or custom time ranges. Narrow down the time range to an interval of interest by "brushing", or dragging the mouse cursor over a chart to select a shorter time range. |
 | **Historical data** | Depending on the dataset, dashboards show either a summary for the selected time interval, or the latest sample collected in the time interval. </br></br>Toggle between the latest and a historical view to look at data samples earlier in the selected time range. For example, instead of looking at the currently active sessions, review a previous sample of active sessions collected when a spike in resource usage occurred. |
@@ -246,7 +225,7 @@ During preview, database watcher has the following known issues.
 | If a [serverless](./database/serverless-tier-overview.md) database has auto-pause enabled, and is added as a SQL target to a watcher, it might not auto-pause as expected. For a [free offer](./database/free-offer.md) database, this might exhaust the free monthly credit sooner than expected. | If retaining the auto-pause functionality is required, do not use database watcher to monitor serverless databases at this time. |
 | Because of a known issue in Azure SQL Database and Azure SQL Managed Instance, expected data might not be collected from a high availability (HA) readable secondary replica if database replicas change roles, for example after a maintenance event. | Commonly, the issue resolves without any action within one or two days. To resume data collection sooner, restart the watcher. |
 | For Azure SQL Managed Instance, data might not be collected from the readable high availability replica or from a geo-replica if you are using SQL authentication. | There are two workarounds: </br>1. Use the Microsoft Entra ID authentication (preferred). </br>2. Disable the password policy check. Execute `ALTER LOGIN [database-watcher-login-placeholder] WITH CHECK_POLICY = OFF;`, replacing `database-watcher-login-placeholder` with the name of the SQL authentication login of the watcher. Execute this command on the primary replica, and on the geo-replica, if any. |
-| In Azure SQL Managed Instance, data is not collected if the `EXECUTE` permission on the `sys.xp_msver` system stored procedure is revoked or denied to the `public` role. | Grant the `EXECUTE` permission on `sys.xp_msver` to the watcher login.</br></br>On every SQL managed instance added as a SQL target, execute `USE master; CREATE USER [database-watcher-login-placeholder] FOR LOGIN [database-watcher-login-placeholder]; GRANT EXECUTE ON sys.xp_msver TO [database-watcher-login-placeholder];`, replacing `database-watcher-login-placeholder` with the name of the watcher login. |
+| In Azure SQL Managed Instance, data is not collected if the `EXECUTE` permission on the `sys.xp_msver` system stored procedure is revoked or denied to the `public` role. | Grant the `EXECUTE` permission on `sys.xp_msver` to the watcher login. </br></br>On every SQL managed instance added as a SQL target, execute `USE master; CREATE USER [database-watcher-login-placeholder] FOR LOGIN [database-watcher-login-placeholder]; GRANT EXECUTE ON sys.xp_msver TO [database-watcher-login-placeholder];`, replacing `database-watcher-login-placeholder` with the name of the watcher login. |
 | If you create a managed private endpoint for a watcher to connect to a SQL managed instance that is stopped, the provisioning state of the private endpoint is reported as **Failed**, and the watcher cannot connect to the instance. | Delete the managed private endpoint with the **Failed** provisioning state and [start](./managed-instance/instance-stop-start-how-to.md) the SQL managed instance. Once the failed private endpoint is deleted and the instance is running, [re-create](database-watcher-manage.md#create-a-managed-private-endpoint) the managed private endpoint. |
 | Data is not collected if you use a database in Real-Time Analytics as the data store, and the **OneLake availability** option is enabled. | Disable the **OneLake availability** option and restart the watcher to resume data collection. |
 | Because of a known issue in Azure Monitor Alerts, if you edit an alert rule created from a database watcher template, the scope of any fired alert is set to the Azure Data Explorer cluster used as the watcher data store instead of the SQL target that the alert applies to. | Edit the alert rule programmatically, for example using Bicep or an ARM template, and set the `resourceIdColumn` property to the value `resource_id`. For more information, see [Resource Manager template samples for log search alert rules in Azure Monitor](/azure/azure-monitor/alerts/resource-manager-alerts-log). |

azure-sql/database/region-availability.md

@@ -10,10 +10,14 @@ ms.topic: concept-article
 ms.custom:
   - references_regions
 ---
-# Feature availability by region
+# Feature availability by region - Azure SQL Database
 
 [!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
+> [!div class="op_single_selector"]
+> * [Azure SQL Database](region-availability.md?view=azuresql-db&preserve-view=true)
+> * [Azure SQL Managed Instance](../managed-instance/region-availability.md?view=azuresql-mi&preserve-view=true)
+
 This article is a centralized list of the availability of various Azure SQL Database features in [Azure regions](https://azure.microsoft.com/explore/global-infrastructure/geographies/). 
 
 - To view regional availability of Azure SQL Database, see [Azure global infrastructure products by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/table). 
@@ -68,8 +72,6 @@ Standard-series (Gen5) hardware is available in [all public regions worldwide wh
 | US West 2 | [!INCLUDE [yes](../includes/yes.md)]  | [!INCLUDE [yes](../includes/yes.md)]  | [!INCLUDE [yes](../includes/yes.md)]  |
 | US West 3 | [!INCLUDE [yes](../includes/yes.md)]  | [!INCLUDE [yes](../includes/yes.md)]  | [!INCLUDE [yes](../includes/yes.md)]  |
 
-
-
 #### [Asia Pacific](#tab/asia)
 
 | Azure region | Premium-series available | Premium-series memory optimized available | [Availability zone support](high-availability-sla-local-zone-redundancy.md#high-availability-through-zone-redundancy) | 
@@ -345,6 +347,12 @@ Currently, all regions with serverless support 40 vCores and provide [availabili
 
 ---
 
+## Database watcher availability
+
+[Database Watcher](../database-watcher-overview.md) is a feature that helps you monitor the health of your Azure SQL Managed Instance. It is available in the following regions: 
+
+[!INCLUDE [database-watcher](../includes/regional-support/database-watcher.md)]
+
 ## Related content
 
 - [What's new in Azure SQL Database?](doc-changes-updates-release-notes-whats-new.md?view=azuresql-db&preserve-view=true)

azure-sql/includes/regional-support/database-watcher.md

@@ -0,0 +1,38 @@
+---
+author: MashaMSFT
+ms.author: mathoma
+ms.reviewer: randolphwest
+ms.date: 04/16/2025
+ms.service: azure-sql
+ms.topic: include
+---
+#### [Americas](#tab/americas)
+
+- Canada Central
+- Canada East
+- Central US
+- East US
+- East US 2
+- North Central US
+- West US
+
+#### [Asia Pacific](#tab/asia)
+
+- Southeast Asia
+- Australia Central
+- Australia East
+- Australia Southeast
+- Japan West
+- Korea Central
+
+
+#### [Europe, the Middle East, and Africa](#tab/emea)
+
+- North Europe
+- West Europe
+- Germany West Central
+- Sweden Central
+- UK South
+
+
+---

azure-sql/managed-instance/automated-backups-change-settings.md

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

azure-sql/managed-instance/automated-backups-overview.md

@@ -9,7 +9,7 @@ ms.date: 07/12/2023
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: conceptual
-ms.custom: references_regions, azure-sql-split, build-2024
+ms.custom: azure-sql-split, build-2024
 monikerRange: "= azuresql || = azuresql-mi"
 ---
 # Automated backups in Azure SQL Managed Instance