Fix UUF documentation issues: links, permissions, code, portal UI, setup wizard (#36666)

* Fix UUF content issues: broken link, priority clarification, DNS suffix guidance

* Apply suggestions from PR review

---------

Co-authored-by: Stacy Chambers <102548089+Stacyrch140@users.noreply.github.com>

Author: MashaMSFT

azure-sql/database/reservations-discount-overview.md

@@ -2,10 +2,10 @@
 title: Save on compute costs with Azure Reservations
 titleSuffix: Azure SQL Database & SQL Managed Instance
 description: Learn how to buy Azure SQL Database and SQL Managed Instance reservations to save on your compute costs.
-author: rajeshsetlem
-ms.author: rsetlem
+author: WilliamDAssafMSFT
+ms.author: wiassaf
 ms.reviewer: wiassaf, mathoma
-ms.date: 12/01/2025
+ms.date: 02/23/2026
 ms.service: azure-sql
 ms.subservice: service-overview
 ms.topic: how-to
@@ -93,6 +93,9 @@ Carefully evaluate your compute needs and reservation strategy to optimize costs
 
     :::image type="content" source="./media/reserved-capacity-overview/sql-reserved-vcores-purchase.png" alt-text="Screenshot before submitting the reservation purchase.":::
 
+    > [!NOTE]
+    > The **Elastic pool** in the SQL Database name is the name of the Azure SQL resource, and does not imply that reservations are available for elastic pools.
+
     The following table describes the required fields.
 
     | Field      | Description|

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

@@ -5,7 +5,7 @@ description: Change point-in-time restore and backup redundancy options for auto
 author: dinethi
 ms.author: dinethi
 ms.reviewer: wiassaf, mathoma, strrodic, mlandzic
-ms.date: 07/08/2025
+ms.date: 02/23/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -127,15 +127,16 @@ For more information, see the [Backup retention PowerShell command](/powershell/
 #### Sample request
 
 ```http
-PUT https://management.azure.com/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/resourceGroup/providers/Microsoft.Sql/managedInstances/testManagedInstance/databases/testDatabase/backupShortTermRetentionPolicies/default?api-version=2017-10-01-preview
+PATCH https://management.azure.com/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/resourceGroup/providers/Microsoft.Sql/managedInstances/testSQLMI/databases/testdb/backupShortTermRetentionPolicies/default?api-version=2023-08-01
+
 ```
 
 #### Request body
 
 ```json
 {
-  "properties":{
-    "retentionDays":28
+  "properties": {
+    "retentionDays": 14
   }
 }
 ```
@@ -146,15 +147,22 @@ Status code: 200
 
 ```json
 {
-  "id": "/subscriptions/00000000-1111-2222-3333-444444444444/providers/Microsoft.Sql/resourceGroups/resourceGroup/managedInstances/testserver/databases/testDatabase/backupShortTermRetentionPolicies/default",
+  "id": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/resourceGroup/providers/Microsoft.Sql/managedInstances/testSQLMI/databases/testdb/backupShortTermRetentionPolicies/default",
   "name": "default",
-  "type": "Microsoft.Sql/resourceGroups/managedInstances/databases/backupShortTermRetentionPolicies",
+  "type": "Microsoft.Sql/managedInstances/databases/backupShortTermRetentionPolicies",
   "properties": {
-    "retentionDays": 28
+    "retentionDays": 14
   }
 }
 ```
 
+Status code: 202
+
+```http
+Location: https://management.azure.com/subscriptions/00000000-1111-2222-3333-444444444444/providers/Microsoft.Sql/locations/westus/managedShortTermRetentionPolicyOperationResults/00000000-1111-2222-3333-444444444444?api-version=2017-03-01-preview
+```
+
+
 For more information, see the [Backup retention REST API](/rest/api/sql/managed-backup-short-term-retention-policies).
 
 ---

azure-sql/managed-instance/public-endpoint-configure.md

@@ -169,7 +169,7 @@ Use the Azure portal to allow public traffic within the network security group.
    |**Destination port ranges**     |3342         |Scope destination port to 3342, which is the SQL managed instance public TDS endpoint |
    |**Protocol**     |TCP         |SQL Managed Instance uses TCP protocol for TDS |
    |**Action**     |Allow         |Allow inbound traffic to SQL managed instance through the public endpoint |
-   |**Priority**     |1300         |Make sure this rule is higher priority than the **deny_all_inbound** rule |
+   |**Priority**     |1300         |Make sure this rule has a lower priority number than the **deny_all_inbound** rule (lower numbers = higher priority, for example, 1300 is higher priority than 2000) |
 
    :::image type="content" source="./media/public-endpoint-configure/mi-nsg-rules.png" alt-text="Screenshot shows the Inbound security rules with your new public_endpoint_inbound rule above the deny_all_inbound rule.":::
 

azure-sql/managed-instance/sql-managed-instance-paas-overview.md

@@ -58,8 +58,7 @@ The following table provides key capabilities of Azure SQL Managed Instance:
 | Isolated environment ([Connectivity architecture for Azure SQL Managed Instance](connectivity-architecture-overview.md), single tenant service, dedicated compute and storage)<br />Adheres to the same compliance standards as Azure SQL Database<br />[Transparent data encryption (TDE)](/sql/relational-databases/security/encryption/transparent-data-encryption-azure-sql)<br />[Use Microsoft Entra authentication](../database/authentication-aad-overview.md), single sign-on support<br />[Microsoft Entra server principals (logins)](/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current&preserve-view=true)<br />[What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?](winauth-azuread-overview.md)<br />[Get started with Azure SQL Managed Instance auditing](auditing-configure.md)<br />[Configure Advanced Threat Protection in Azure SQL Managed Instance](threat-detection-configure.md) | Azure Resource Manager API for automating service provisioning and scaling<br />Azure portal functionality for manual service provisioning and scaling<br />Data Migration Service |
 
 > [!IMPORTANT]  
-> Azure SQL Managed Instance is certified against a number of compliance standards. For more information, see the [Azure Compliance Offerings](https://servicetrust.microsoft.com/ViewPage/MSComplianceGuideV3?command=Download&downloadType=Document&downloadId=44bbae63-bf4d-4e3b-9d3d-c96fb25ec363&tab=7027ead0-3d6b-11e9-b9e1-290b1eb4cdeb&docTab=7027ead0-3d6b-11e9-b9e1-290b1eb4cdeb_FAQ_and_White_Papers), where you can find the most current list of Azure SQL Managed Instance compliance certifications, listed under **Azure SQL Database**.
-
+> Azure SQL Managed Instance is certified against a number of compliance standards. For more information, see the [Microsoft Trust Center](https://www.microsoft.com/trust-center/compliance/compliance-overview), where you can find the most current list of Azure SQL Managed Instance compliance certifications.
 The following table shows characteristics of SQL Managed Instance:
 
 | Feature | Description |

azure-sql/virtual-machines/windows/automated-backup.md

@@ -4,7 +4,7 @@ description: This article explains the Automated Backup feature for SQL Server 2
 author: AbdullahMSFT
 ms.author: amamun
 ms.reviewer: mathoma
-ms.date: 09/22/2025
+ms.date: 02/23/2026
 ms.service: azure-vm-sql-server
 ms.subservice: backup
 ms.topic: how-to
@@ -134,9 +134,11 @@ The following Azure portal screenshot shows the **Automated Backup** settings wh
 
 For existing SQL Server virtual machines, go to the [SQL virtual machines resource](manage-sql-vm-portal.md#access-the-resource) and then select **Backups** to configure your Automated Backups.
 
-Select **Enable** to configure your Automated Backup settings.
+Select **Enable** on the **Automated Backup** tile to configure your Automated Backup settings: 
 
-You can configure the retention period (up to 90 days), the container for the storage account where you want to store your backups, the encryption, and the backup schedule. By default, the schedule is automated.
+:::image type="content" source="media/automated-backup/select-automated-backup.png" alt-text="Screenshot of how to select automated backup on the backup blade for your SQL VM in the Azure portal." lightbox="media/automated-backup/select-automated-backup.png":::
+
+On the **Backups** page, select **Enable** to turn on Automated Backup. You can configure the retention period (up to 90 days), the container for the storage account where you want to store your backups, the encryption, and the backup schedule. By default, the schedule is automated. Configure the settings as needed: 
 
 :::image type="content" source="./media/automated-backup/sql-server-configuration.png" alt-text="Screenshot of Automated Backup for existing VMs in the portal.":::
 
@@ -148,18 +150,18 @@ When finished, select the **Apply** button on the bottom of the **Backups** sett
 
 If you're enabling Automated Backup for the first time, Azure configures the SQL Server IaaS Agent in the background. During this time, the Azure portal might not show that Automated Backup is configured. Wait several minutes for the agent to be installed, configured. After that, the Azure portal will reflect the new settings.
 
+If you only see [Azure Backup](backup-restore.md#azbackup) as the backup type, then [Disable Azure Backup by deleting the associated Azure Vault](backup-restore.md#disable-azure-backup), and then choose **Automated Backup** to use Automated Backup instead.
+
 ## Configure with PowerShell
 
 You can use PowerShell to configure Automated Backup. Before you begin, you must:
 
-- [Download and install the latest Azure PowerShell](https://aka.ms/webpi-azps).
+- [Download and install the latest Azure PowerShell](/powershell/azure/install-azure-powershell).
 - Open Windows PowerShell and associate it with your account with the **Connect-AzAccount** command.
 
-[!INCLUDE [updated-for-az.md](../../includes/updated-for-az.md)]
-
 ### Install the SQL Server IaaS Extension
 
-If you provisioned a SQL Server virtual machine from the Azure portal, the SQL Server IaaS Extension should already be installed. You can determine whether it's installed for your VM by calling **Get-AzVM** command and examining the **Extensions** property.
+If you provisioned a SQL Server virtual machine from the Azure portal, the SQL Server IaaS Agent extension should already be installed. You can determine whether it's installed for your VM by calling **Get-AzVM** command and examining the **Extensions** property.
 
 ```powershell
 $vmname = "yourvmname"
@@ -170,7 +172,7 @@ $resourcegroupname = "yourresourcegroupname"
 
 If the SQL Server IaaS Agent extension is installed, you should see it listed as `SqlIaaSAgent` or `SQLIaaSExtension.` **ProvisioningState** for the extension should also show "Succeeded."
 
-If it isn't installed or it has failed to be provisioned, you can install it with the following command. In addition to the VM name and resource group, you must also specify the region (**$region**) that your VM is located in.
+If it isn't installed or provisioning failed, you can install it with the [Set-AzVMSqlServerExtension](/powershell/module/az.compute/set-azvmsqlserverextension) command. In addition to the VM name and resource group, you must also specify the region (**$region**) that your VM is located in.
 
 ```powershell
 $region = "EASTUS2"
@@ -425,6 +427,7 @@ The following table lists the possible solutions if you're having issues enablin
 | **Backup Multiple SQL instances using Automated Backup**   | Automated Backup currently only supports one SQL Server instance. If you have multiple named instances, and the default instance, Automated Backup works with the default instance. If you have multiple named instances and no default instance, turning on Automated Backup will fail. |
 | **Automated Backup can't be enabled due to account and permissions** | Check the following:  <br /> - The SQL Server Agent is running. <br /> - The  **NT Service\SqlIaaSExtensionQuery**  account has proper [permissions](sql-server-iaas-agent-extension-automate-management.md#permissions-models) for the Automated Backup feature both within SQL Server, and also for the [SQL virtual machines](manage-sql-vm-portal.md) resource in the Azure portal. <br /> - The **SA** account hasn't been renamed, though disabling the account is acceptable. |
 | **Automated Backup fails for SQL 2016 +**| **Allow Blob Public Access** is enabled on the storage Account. This solution provides a temporary workaround to a known issue. |
+|**The account being accessed does not have sufficient permissions to execute this operation** | This error occurs when the user lacks sufficient permissions to the storage account or container, or you select the default `$logs` container for backup storage. To resolve this issue, create a new container in your storage account and use that container for your backups instead of the default `$logs` container. |
 
 ### Common issues with Automated or Managed Backups
 

azure-sql/virtual-machines/windows/backup-restore.md

@@ -70,6 +70,24 @@ For more information on how to configure Automated Backup for SQL VMs, see one o
 
 This Azure Backup solution for SQL VMs is generally available. For more information, see [Back up SQL Server database to Azure](/azure/backup/backup-azure-sql-database).
 
+To use Azure backup, you must first make sure Automated backup is disabled.
+
+### Disable Azure Backup
+
+To disable Azure Backups, you have to delete the associated vault. To delete the vault, follow these steps: 
+
+1. Go to [Recovery Services vaults in the Azure portal](https://portal.azure.com/#browse/Microsoft.RecoveryServices%2Fvaults) and select the vault that contains your SQL Server Azure Backups. 
+1. Under **Protected items** select **Backup items**.
+1. On the **Backup items** page, select the **SQL Database in Azure VM** backup management type. 
+1. Select the ellipses (...) next to each database, and then select **Stop backup** to go to the **Stop backup** page.
+1. On the **Stop backup** page, select **Delete backup data** and then select **OK** to disable Azure Backup and delete the backup data for that database.
+1. Go back to the vault, and under **Manage**, select **Backup Infrastructure**.
+1. On the **Overview** blade of the **Backup Infrastructure** page, select **Workload in Azure VM**.
+1. On the **Protected Servers (Workload in Azure VM)** page, select the ellipses (...) next to the SQL Server VM, and then select **Unregister** to remove the SQL Server VM from Azure Backup protection.
+1. Go back to the vault, and then use **Delete** to delete the vault. 
+1. After the vault is deleted, Azure Backup is disabled for your [SQL virtual machine resource](manage-sql-vm-portal.md#backups)
+
+
 <a id="manual"></a>
 
 ## Manual backup

azure-sql/virtual-machines/windows/manage-sql-vm-portal.md

@@ -106,6 +106,8 @@ Use the **Backups** page of the SQL virtual machines resource to choose between
 
 Regardless of which backup solution you choose, you can use the **Backups** page to configure your backup settings, such as the retention period, backup storage location, encryption, whether or not to back up system databases, and a backup schedule.
 
+To use Azure backup, you must first make sure Automated backup is disabled.
+
 ## Modernization Advisor (preview)
 
 The [Modernization Advisor (Preview)](../modernization-advisor.md) assesses your SQL Server workload to identify cost-saving or performance optimizations you might gain by migrating to Azure SQL Managed Instance. This feature is currently in preview.

azure-sql/virtual-machines/windows/media/automated-backup/select-automated-backup.png

@@ -60,6 +60,10 @@ A common DNS suffix is necessary for a domain independent availability group's w
 1. On the System Properties dialog, select **Change** on the Computer Name tab.
 1. On the Computer Name/Domain Changes dialog, select **More**.
 1. On the DNS Suffix and NetBIOS Computer Name dialog, enter the common DNS suffix as the **Primary DNS** suffix.
+
+   > [!NOTE]
+   > Specify only the DNS suffix (for example, `CONTOSO.LAB`), not the full computer name. Do not include the hostname in the DNS suffix field.
+
 1. Select **OK** to close the DNS Suffix and NetBIOS Computer Name dialog.
 1. Select **OK** to close the Computer Name/Domain Changes dialog.
 1. You're prompted to restart the server for the changes to take effect. Select **OK** to close the Computer Name/Domain Changes dialog.