Merge pull request #35777 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-06 23:30 UTC

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

.openpublishing.redirection.json

@@ -50007,7 +50007,12 @@
     },
     {
       "source_path": "docs/big-data-cluster/deploy-install-azdata-pip.md",
-      "redirect_url": "/sql/azdata/install/deploy-install-azdata-pip",
+      "redirect_url": "/sql/azdata/install/deploy-install-azdata-installer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azdata/install/deploy-install-azdata-pip.md",
+      "redirect_url": "/sql/azdata/install/deploy-install-azdata-installer",
       "redirect_document_id": false
     },
     {

azure-sql/database/backup-immutability-legal-hold.md

@@ -5,7 +5,7 @@ description: Learn how to configure legal hold backup immutability for long-term
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dinethi
-ms.date: 09/29/2025
+ms.date: 11/06/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -35,7 +35,7 @@ For permissions to view, managed, and delete LTR backups, see [Manage Azure SQL
 
 ## Enable legal hold immutability for existing LTR backups
 
-You can enable legal hold immutability on any existing backups. These backups are protected from any edits or deletes until the legal hold is explicitly removed.
+You can enable legal hold immutability on any existing backups in the Azure portal, PowerShell, and Azure CLI. These backups are protected from any edits or deletes until the legal hold is explicitly removed.
 
 > [!IMPORTANT]
 > Legal hold backup immutability can apply only to existing backups. To make future backups automatically immutable, instead use [time-based immutability](backup-immutability-time-based.md).
@@ -56,19 +56,31 @@ You can enable legal hold immutability on any existing backups. These backups ar
 
 **To enable legal hold backup immutability with PowerShell:**
 
+Replace `<backup name>` with the unique identifier of the desired backup.
+
 ```powershell
 Set-AzSqlDatabaseLongTermRetentionBackupLegalHold
     -Location southeastasia
     -ServerName myAzureSQL
     -DatabaseName mysqldb
-    -BackupName 'myLTRbackup-1-24'
+    -BackupName '<backup name>'
+```
+
+#### [Azure CLI](#tab/azure-cli)
+
+**To enable legal hold backup immutability with the Azure CLI:**
+
+Replace `<backup name>` with the unique identifier of the desired backup.
+
+```azurecli
+az sql db ltr-backup set-legal-hold-immutability --resource-group mygroup --location southeastasia --server myserver --database mydb --name "<backup name>"
 ```
 
 ---
 
 ## Remove legal hold immutability
 
-Legal hold immutability on specific backups can be disabled as follows:
+Legal hold immutability on specific backups can be disabled in the Azure portal, PowerShell, and Azure CLI.
 
 #### [Azure portal](#tab/azure-portal)
 
@@ -84,12 +96,24 @@ Legal hold immutability on specific backups can be disabled as follows:
 
 **To remove legal hold immutability from a backup with PowerShell:**
 
+Replace `<backup name>` with the unique identifier of the desired backup.
+
 ```powershell
 Remove-AzSqlDatabaseLongTermRetentionBackupLegalHold
     -Location southeastasia
     -ServerName myAzureSQL
     -DatabaseName mysqldb
-    -BackupName 'myLTRbackup-1-24'
+    -BackupName '<backup name>'
+```
+
+#### [Azure CLI](#tab/azure-cli)
+
+**To remove legal hold immutability from a backup with the Azure CLI:**
+
+Replace `<backup name>` with the unique identifier of the desired backup.
+
+```azurecli
+az sql db ltr-backup remove-legal-hold-immutability --resource-group mygroup --location southeastasia --server myserver --database mydb --name "<backup name>"
 ```
 
 ---

azure-sql/database/backup-immutability-time-based.md

@@ -5,7 +5,7 @@ description: Learn how to configure time-based backup immutability for long-term
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dinethi
-ms.date: 09/29/2025
+ms.date: 11/06/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -38,6 +38,8 @@ For permissions to view, managed, and delete LTR backups, see [Manage Azure SQL
 > [!IMPORTANT]
 > Only backups taken after enabling and locking the policy will be immutable. To make existing backups immutable, instead use [legal hold immutability](backup-immutability-legal-hold.md).
 
+You can create time-based immutability in the Azure portal, PowerShell, and Azure CLI.
+
 #### [Azure portal](#tab/azure-portal)
 
 **To enable and lock time-based immutability from the Azure portal:**
@@ -69,7 +71,13 @@ Set-AzSqlDatabaseBackupLongTermRetentionPolicy
     -TimeBasedImmutabilityMode Locked
 ```
 
+#### [Azure CLI](#tab/azure-cli)
+
+**To enable and lock time-based immutability with Azure CLI:**
 
+```azurecli
+az sql db ltr-policy set --resource-group mygroup --server myserver --name mydb --weekly-retention "P0W" --monthly-retention "P0M" --yearly-retention "P0Y" --tb-immutability Enabled --tb-immutability-mode Locked
+```
 
 ---
 
@@ -82,7 +90,7 @@ For backups that have immutability enabled but not locked, there are two options
 - Lock the immutability.
 - Remove immutability for each backup.
 
-Locking immutability for specific backups can be done as follows:
+Locking immutability for specific backups can be done in the Azure portal, PowerShell, and Azure CLI.
 
 #### [Azure portal](#tab/azure-portal)
 
@@ -101,15 +109,29 @@ Locking immutability for specific backups can be done as follows:
 > [!IMPORTANT]
 > The command needs to be run independently for each of the LTR backups that have immutability enabled but not locked.
 
+Replace `<backup name>` with the unique identifier of the desired backup.
+
 ```powershell
 Lock-AzSqlDatabaseLongTermRetentionBackupImmutability
     -Location southeastasia
     -ServerName myAzureSQL
     -DatabaseName mysqldb
-    -BackupName 'myLTRbackup-1-24'
+    -BackupName '<backup name>'
     -ResourceGroupName testrg
 ```
 
+#### [Azure CLI](#tab/azure-cli)
+
+**To lock time-based immutability on a backup with the Azure CLI:**
+
+> [!IMPORTANT]
+> The command needs to be run independently for each of the LTR backups that have immutability enabled but not locked.
+
+Replace `<backup name>` with the unique identifier of the desired backup.
+
+```azurecli
+az sql db ltr-backup lock-time-based-immutability --resource-group mygroup --location southeastasia --server myserver --database mydb --name "<backup name>"
+```
 
 ---
 
@@ -131,21 +153,32 @@ For backups that have immutability enabled but not locked, the immutability can
 
 **To remove immutability on a backup with PowerShell:**
 
+Replace `<backup name>` with the unique identifier of the desired backup.
+
 ```powershell
 Remove-AzSqlDatabaseLongTermRetentionBackupImmutability
     -Location southeastasia
     -ServerName myAzureSQL
     -DatabaseName mysqldb
-    -BackupName 'myLTRbackup-1-24'
+    -BackupName '<backup name>'
     -ResourceGroupName testrg
 ```
 
+#### [Azure CLI](#tab/azure-cli)
+
+**To remove immutability on a backup with the Azure CLI:**
+
+Replace `<backup name>` with the unique identifier of the desired backup.
+
+```azurecli
+az sql db ltr-backup remove-time-based-immutability --resource-group mygroup --location southeastasia --server myserver --database mydb --name "<backup name>"
+```
 
 ---
 
 ## Disable immutability policy
 
-Immutability can be disabled from the LTR policy configuration page in the Azure portal and PowerShell.
+Immutability can be disabled from the LTR policy configuration page in the Azure portal, PowerShell, and Azure CLI.
 
 Once immutability is disabled, any new LTR backups from this point won't be protected from immutability. Any existing LTR backups however, will continue to be immutable, if already locked as immutable.
 
@@ -173,6 +206,13 @@ Set-AzSqlDatabaseBackupLongTermRetentionPolicy
     -TimeBasedImmutability Disabled
 ```
 
+#### [Azure CLI](#tab/azure-cli)
+
+**To disable a backup immutability policy with the Azure CLI:**
+
+```azurecli
+az sql db ltr-policy set --resource-group mygroup --server myserver --name mydb --weekly-retention "P0W" --monthly-retention "P0M" --yearly-retention "P0Y" --tb-immutability disabled
+```
 
 ---
 

azure-sql/database/high-cpu-diagnose-troubleshoot.md

@@ -294,7 +294,7 @@ Select **Configure** in the top right of the pane to select a different time per
 
 Select a bar in the chart to drill in and see queries running in a specific time period. The **Top Resource Consuming Queries** pane will open. Alternately, you can open **Top Resource Consuming Queries** from the Query Store node under your database in Object Explorer directly.
 
-:::image type="content" source="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png" alt-text="Screenshot shows the Top Resource Consuming Queries pane for Query Store in S S M S." lightbox="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png":::
+:::image type="content" source="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png" alt-text="Screenshot shows the Top Resource Consuming Queries pane for Query Store in SSMS." lightbox="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png":::
 
 In the default view, the **Top Resource Consuming Queries** pane shows queries by **Duration (ms)**. Duration might sometimes be lower than CPU time: queries using parallelism might use much more CPU time than their overall duration. Duration might also be higher than CPU time if wait times are significant. To see queries by CPU time, select the **Metric** dropdown list at the top left of the pane and select **CPU Time(ms)**.
 

azure-sql/database/scripts/vnet-service-endpoint-rule-powershell-create.md

@@ -366,7 +366,7 @@ Or, you might be unsure whether your subnet has the `Microsoft.Sql` type name. Y
 
 Here are the phases of the PowerShell script:
 
-1. Sign in to to your Azure account, needed only once per PowerShell session. Assign variables.
+1. Sign in to your Azure account, needed only once per PowerShell session. Assign variables.
 2. Search for your virtual network, and then for your subnet.
 3. Is your subnet tagged as `Microsoft.Sql` endpoint server type?
 4. Add a Virtual Service endpoint of type name `Microsoft.Sql`, on your subnet.

azure-sql/includes/passwordless/associate-managed-identity-cli.md

@@ -31,7 +31,7 @@ If you are working with Git Bash, be careful of path conversions when using full
 
 # [Azure Spring Apps](#tab/spring-apps-identity)
 
-You can assign a managed identity to your Azure Spring Apps instance using the [az spring app identity assign](/azure/spring-apps/basic-standard/how-to-manage-user-assigned-managed-identities?tabs=azure-cli&pivots=sc-standard) command command in the Azure CLI.
+You can assign a managed identity to your Azure Spring Apps instance using the [az spring app identity assign](/azure/spring-apps/basic-standard/how-to-manage-user-assigned-managed-identities?tabs=azure-cli&pivots=sc-standard) command in the Azure CLI.
 
 ```azurecli
 az spring app identity assign \

azure-sql/includes/sql-managed-instance/azure-sql-managed-instance-link-check-network.md

@@ -26,7 +26,7 @@ To test network connectivity between SQL Server and SQL Managed Instance in SSMS
 1. Connect to the instance that will be the primary replica in SSMS. 
 1. In **Object Explorer**, expand databases, and right-click the database you intend to link with the secondary. Select **Tasks** > **Azure SQL Managed Instance link** > **Test Connection** to open the **Network Checker** wizard: 
 
-   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connection-in-ssms.png" alt-text="Screenshot of object explorer in S S M S, with test connection selected in the database link right-click menu.":::
+   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connection-in-ssms.png" alt-text="Screenshot of object explorer in SSMS, with test connection selected in the database link right-click menu.":::
 
 1. Select **Next** on the **Introduction** page of the **Network Checker** wizard.
 1. If all requirements are met on the **Prerequisites** page, select **Next**. Otherwise resolve any unmet prerequisites, and then select **Re-run Validation**. 
@@ -189,7 +189,7 @@ Use SQL Server Agent on SQL Server to run connectivity tests from SQL Server to
 
 1. Run the script and check the results. You should see results such as the following example:
 
-   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connectivity-results.png" alt-text="Screenshot that shows the output with the test results in S S M S.":::
+   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connectivity-results.png" alt-text="Screenshot that shows the output with the test results in SSMS.":::
 
 1. Verify the results:
 

azure-sql/managed-instance/aad-security-configure-tutorial.md

@@ -206,7 +206,7 @@ Authorization to individual databases works much the same way in SQL Managed Ins
 
 Now that we've created a database called **MyMITestDB** and a login that only has default permissions, the next step is to create a user from that login. At the moment, the login can connect to the SQL managed instance and see all the databases, but it can't interact with the databases. If you sign in with the Microsoft Entra account that has the default permissions and try to expand the newly created database, you'll see the following error:
 
-![Screenshot of an error message from the the SSMS Object Explorer that reads "The database MyMITestDB is not accessible. (ObjectExplorer)".](./media/aad-security-configure-tutorial/ssms-db-not-accessible.png)
+![Screenshot of an error message from the SSMS Object Explorer that reads "The database MyMITestDB is not accessible. (ObjectExplorer)".](./media/aad-security-configure-tutorial/ssms-db-not-accessible.png)
 
 For more information on granting database permissions, see [Getting Started with Database Engine Permissions](/sql/relational-databases/security/authentication-access/getting-started-with-database-engine-permissions).
 

azure-sql/managed-instance/data-virtualization-overview.md

@@ -134,7 +134,7 @@ SECRET = 'sv=2018-03-28&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-04-18T20:42:12Z&st=2
 
 ## External data source
 
-An external data source is an abstraction that that provides an easy reference to a file location across multiple queries. To query public locations, specify the file location when you create an external data source:
+An external data source is an abstraction that provides an easy reference to a file location across multiple queries. To query public locations, specify the file location when you create an external data source:
 
 ```sql
 CREATE EXTERNAL DATA SOURCE MyExternalDataSource

azure-sql/managed-instance/managed-instance-link-configure-how-to-ssms.md

@@ -123,7 +123,7 @@ After the link is created, your database is replicated to the secondary replica.
 
 On either replica, use **Object Explorer** in SSMS to view the **Synchronized** state of the replicated database. 
 
-:::image type="content" source="./media/managed-instance-link-configure-how-to-ssms/check-replicated-database-on-sql-server.png" alt-text="Screenshot that shows the state of the SQL Server database and distributed availability group in S S M S.":::
+:::image type="content" source="./media/managed-instance-link-configure-how-to-ssms/check-replicated-database-on-sql-server.png" alt-text="Screenshot that shows the state of the SQL Server database and distributed availability group in SSMS.":::
 
 Expand **Always On High Availability** and **Availability Groups** to view the distributed availability group created for each link.