Merge pull request #36151 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-31 23:30 UTC

Author: learn-build-service-prod[bot]

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 |

azure-sql/database/azure-sql-python-quickstart.md

@@ -226,7 +226,7 @@ The app is ready to be tested locally.
     uvicorn app:app --reload
     ```
 
-1. On the Swagger UI page for the app [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs), expand the POST method and select **Try it out**.
+1. On the Swagger UI page for the app `http://127.0.0.1:8000/docs`, expand the POST method and select **Try it out**.
 
     You can also use try `/redoc` to see another form of generated documentation for the API.
 

azure-sql/database/connect-query-java.md

@@ -20,7 +20,7 @@ monikerRange: "=azuresql || =azuresql-db"
 
 [!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-This article demonstrates creating a sample application that uses Java and [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity) to store and retrieve information in [Azure SQL Database](/azure/sql-database/).
+This article demonstrates creating a sample application that uses Java and [JDBC](https://wikipedia.org/wiki/Java_Database_Connectivity) to store and retrieve information in [Azure SQL Database](/azure/sql-database/).
 
 JDBC is the standard Java API to connect to traditional relational databases.
 

azure-sql/database/dynamic-data-masking-configure-portal.md

@@ -23,7 +23,7 @@ This article shows you how to implement [dynamic data masking](dynamic-data-mask
 
 ## Enable dynamic data masking
 
-1. Launch the Azure portal at [https://portal.azure.com](https://portal.azure.com).
+1. Launch the [Azure portal](https://portal.azure.com).
 1. Go to your database resource in the Azure portal. 
 1. Under the **Security** section, select **Dynamic Data Masking**. 
 1. In the **Dynamic Data Masking** configuration page, you might see some database columns that the recommendations engine has flagged for masking. In order to accept the recommendations, select **Add Mask** for one or more columns, and a mask is created based on the default type for this column. You can change the masking function by selecting on the masking rule and editing the masking field format to a different format of your choice. Select **Save** to save your settings. In the following screenshot, you can see recommended dynamic data masks for the sample `AdventureWorksLT` database.

azure-sql/database/elastic-jobs-overview.md

@@ -303,7 +303,7 @@ Set the number of concurrent databases a job runs on by setting the `sp_add_jobs
 
 ### Idempotent scripts
 
-An elastic job's T-SQL scripts must be [idempotent](https://en.wikipedia.org/wiki/Idempotence). **Idempotent** means that if the script succeeds, and it's run again, the same result occurs. A script can fail due to transient network issues. In that case, the job will automatically retry running the script a preset number of times before desisting. An idempotent script has the same result even if it's been successfully run twice (or more).
+An elastic job's T-SQL scripts must be [idempotent](https://wikipedia.org/wiki/Idempotence). **Idempotent** means that if the script succeeds, and it's run again, the same result occurs. A script can fail due to transient network issues. In that case, the job will automatically retry running the script a preset number of times before desisting. An idempotent script has the same result even if it's been successfully run twice (or more).
 
 A simple tactic is to test for the existence of an object before creating it. The following is a hypothetical example:
 

azure-sql/database/elastic-transactions-overview.md

@@ -8,7 +8,7 @@ ms.reviewer: scoriani, mathoma
 ms.date: 06/13/2025
 ms.service: azure-sql
 ms.subservice: scale-out
-ms.topic: conceptual
+ms.topic: article
 monikerRange: "=azuresql || =azuresql-db || =azuresql-mi"
 ms.custom:
   - sqldbrb=1
@@ -269,13 +269,13 @@ These DMVs are particularly useful:
 
 The following limitations currently apply to elastic database transactions in *Azure SQL Database*:
 
-- Only transactions across databases in SQL Database are supported. Other [X/Open XA](https://en.wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of SQL Database can't participate in elastic database transactions. That means that elastic database transactions can't stretch across on-premises SQL Server and Azure SQL Database. For distributed transactions on premises, continue to use MSDTC.
+- Only transactions across databases in SQL Database are supported. Other [X/Open XA](https://wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of SQL Database can't participate in elastic database transactions. That means that elastic database transactions can't stretch across on-premises SQL Server and Azure SQL Database. For distributed transactions on premises, continue to use MSDTC.
 - Only client-coordinated transactions from a .NET application are supported. Server-side support for T-SQL such as `BEGIN DISTRIBUTED TRANSACTION` is planned, but not yet available.
 - Transactions across WCF services aren't supported. For example, you have a WCF service method that executes a transaction. Enclosing the call within a transaction scope will fail as a [System.ServiceModel.ProtocolException](/dotnet/api/system.servicemodel.protocolexception).
 
 The following limitations currently apply to distributed transactions (also known as elastic transactions or natively supported distributed transactions) in *Azure SQL Managed Instance*:
 
-- With this technology, only transactions across databases in managed instances are supported. For all other scenarios that might include [X/Open XA](https://en.wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of Azure SQL Managed Instance you should configure [Distributed Transaction Coordinator (DTC) for Azure SQL Managed Instance](../managed-instance/distributed-transaction-coordinator-dtc.md).
+- With this technology, only transactions across databases in managed instances are supported. For all other scenarios that might include [X/Open XA](https://wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of Azure SQL Managed Instance you should configure [Distributed Transaction Coordinator (DTC) for Azure SQL Managed Instance](../managed-instance/distributed-transaction-coordinator-dtc.md).
 - Transactions across WCF services aren't supported. For example, you have a WCF service method that executes a transaction. Enclosing the call within a transaction scope will fail as a [System.ServiceModel.ProtocolException](/dotnet/api/system.servicemodel.protocolexception).
 - Azure SQL Managed Instance must be part of a [Set up trust between instances with server trust group (Azure SQL Managed Instance)](../managed-instance/server-trust-group-overview.md) in order to participate in distributed transaction.
 - Limitations of [Set up trust between instances with server trust group (Azure SQL Managed Instance)](../managed-instance/server-trust-group-overview.md) affect distributed transactions.

azure-sql/database/maintenance-window-configure.md

@@ -54,7 +54,7 @@ The following examples show how to configure the maintenance window using Azure
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to <https://shell.azure.com>.
 
 When Cloud Shell opens, verify that **PowerShell** is selected for your environment. Subsequent sessions will use Azure CLI in a PowerShell environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 
@@ -133,7 +133,7 @@ The following examples show how to configure the maintenance window using Azure
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to <https://shell.azure.com>.
 
 When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.
 

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.

azure-sql/database/security-best-practice.md

@@ -770,7 +770,7 @@ This section helps you find security measures to protect against certain attack
 
 ### Security threat: Data exfiltration
 
-Data exfiltration is the unauthorized copying, transfer, or retrieval of data from a computer or server. See a definition for [data exfiltration](https://en.wikipedia.org/wiki/Data_exfiltration) on Wikipedia.
+Data exfiltration is the unauthorized copying, transfer, or retrieval of data from a computer or server. See a definition for [data exfiltration](https://wikipedia.org/wiki/Data_exfiltration) on Wikipedia.
 
 Connecting to server over a public endpoint presents a data exfiltration risk as it requires customers open their firewalls to public IPs.
 

azure-sql/includes/cli-launch-cloud-shell-sign-in.md

@@ -9,7 +9,7 @@ ms.topic: include
 
 The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
 
-To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com](https://shell.azure.com).
+To open the Cloud Shell, select **Try it** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to <https://shell.azure.com>.
 
 When Cloud Shell opens, verify that **Bash** is selected for your environment. Subsequent sessions will use Azure CLI in a Bash environment. Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press **Enter** to run it.