Merge branch 'main' into broken-link-fix-David-Engel

Author: PhilKang0704

.github/workflows/signoff-review.yml

@@ -646,6 +646,8 @@ jobs:
                             # If so, always return success. If not, always keep at pending until approved.
                             if ($ApprovedLabelSet)
                             {
+                                $ActionableComment = $True
+                                
                                 Write-Host "Content team already approved. Returning success."
                                 $Status.state = "success"
                                 $Status.description = $ContentApprovalMessage

.openpublishing.redirection.json

@@ -67189,6 +67189,11 @@
       "source_path": "docs/relational-databases/data-tier-applications/validate-a-dac-package.md",
       "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/unpack-dacpac-file",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/sql-server-configuration-manager.md",
+      "redirect_url": "/sql/tools/configuration-manager/sql-server-configuration-manager",
+      "redirect_document_id": true
     }
   ]
 }

azure-sql/database/adonet-v12-develop-direct-route-ports.md

@@ -16,7 +16,7 @@ ms.custom: sqldbrb=1
 This topic describes the Azure SQL Database connection behavior for clients that use ADO.NET 4.5 or a later version.
 
 > [!IMPORTANT]
-> For information about connectivity architecture, see [Azure SQL Database connectivity architecture](connectivity-architecture.md).
+> For information about connectivity architecture, see [Connectivity architecture](connectivity-architecture.md).
 >
 
 ## Outside vs inside

azure-sql/database/automatic-tuning-overview.md

@@ -12,7 +12,7 @@ ms.topic: concept-article
 ms.custom:
   - sqldbrb=2
   - ignite-2024
-monikerRange: "=azuresql || =azuresql-db || =azuresql-mi || =fabric"
+monikerRange: "=azuresql || =azuresql-db || =azuresql-mi || =fabricsql"
 ---
 # Automatic database tuning
 

azure-sql/database/connectivity-architecture.md

@@ -1,40 +1,40 @@
 ---
-title: Connectivity settings for Azure SQL Database and Azure Synapse Analytics
-titleSuffix: Azure SQL Database and Azure Synapse Analytics
-description: This article explains the Transport Layer Security (TLS) version choice and the Proxy versus Redirect settings for Azure SQL Database and Azure Synapse Analytics.
+title: Connectivity settings
+titleSuffix: Azure SQL Database and SQL database in Fabric
+description: This article explains the Transport Layer Security (TLS) version choice and the Proxy versus Redirect settings for Azure SQL Database and SQL database in Microsoft Fabric.
 author: VanMSFT
 ms.author: vanto
-ms.reviewer: wiassaf, mathoma, vanto
+ms.reviewer: wiassaf, mathoma
 ms.service: azure-sql-database
-ms.date: 09/13/2024
+ms.date: 03/18/2025
 ms.subservice: connect
 ms.topic: how-to
 ms.custom:
   - devx-track-azurepowershell
   - devx-track-azurecli
 ms.devlang: azurecli
+monikerRange: "=azuresql || =azuresql-db || =fabricsql"
 ---
-# Connectivity settings for Azure SQL Database and Azure Synapse Analytics
-[!INCLUDE [appliesto-sqldb-asa](../includes/appliesto-sqldb-asa-formerly-sqldw.md)]
+# Connectivity settings
 
-This article introduces settings that control connectivity to the server for Azure SQL Database and [dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) in Azure Synapse Analytics.
+[!INCLUDE [appliesto-sqldb-fabricsqldb](../includes/appliesto-sqldb-fabricsqldb.md)]
+
+This article introduces settings that control connectivity to the server for Azure SQL Database and SQL database in Microsoft Fabric.
 
 - For more information on various components that direct network traffic and connection policies, see [connectivity architecture](connectivity-architecture.md).
 - This article does not apply to Azure SQL Managed Instance, instead see [Connect your application to Azure SQL Managed Instance](../managed-instance/connect-application-instance.md).
-- This article does not apply to dedicated SQL pools in Azure Synapse Analytics workspaces. See [Azure Synapse Analytics IP firewall rules](/azure/synapse-analytics/security/synapse-workspace-ip-firewall) for guidance on how to configure IP firewall rules for Azure Synapse Analytics with workspaces.
+- This article does *not* apply to Azure Synapse Analytics. 
+   - For settings that control connectivity to dedicated SQL pools in Azure Synapse Analytics, see [Azure Synapse Analytics connectivity settings](/azure/synapse-analytics/security/connectivity-settings).
+   - For connection strings to Azure Synapse Analytics pools, see [Connect to Synapse SQL](/azure/synapse-analytics/sql/connect-overview).
+   - See [Azure Synapse Analytics IP firewall rules](/azure/synapse-analytics/security/synapse-workspace-ip-firewall) for guidance on how to configure IP firewall rules for Azure Synapse Analytics with workspaces.
 
 ## Networking and connectivity
 
-You can change these settings in your [logical server](logical-servers.md). A logical SQL server can host both Azure SQL databases and standalone dedicated SQL pools not in an Azure Synapse Analytics workspace.
-
-> [!NOTE]
-> These settings apply to Azure SQL databases and dedicated SQL pools (formerly SQL DW) associated with the logical server. These instructions do not apply to dedicated SQL pools in an Azure Synapse analytics workspace. 
-
-:::image type="content" source="media/connectivity-settings/manage-connectivity-settings.png" alt-text="Screenshot of the Firewalls and virtual networks settings in Azure portal for SQL server.":::
+You can change these settings in your [logical server](logical-servers.md). 
 
 ## Change public network access
 
-It's possible to change the public network access for your Azure SQL Database or standalone dedicated SQL pool via the Azure portal, Azure PowerShell, and the Azure CLI.
+It's possible to change the public network access for your Azure SQL Database via the Azure portal, Azure PowerShell, and the Azure CLI.
 
 > [!NOTE]
 > These settings take effect immediately after they're applied. Your customers might experience connection loss if they don't meet the requirements for each setting.
@@ -43,6 +43,8 @@ It's possible to change the public network access for your Azure SQL Database or
 
 To enable public network access for the logical server hosting your databases:
 
+:::image type="content" source="media/connectivity-settings/manage-connectivity-settings.png" alt-text="Screenshot of the Firewalls and virtual networks settings in Azure portal for a logical SQL server.":::
+
 1. Go to the Azure portal, and go to the [logical server in Azure](logical-servers.md).
 1. Under **Security**, select the **Networking** page.
 1. Choose the **Public access** tab, and then set the **Public network access** to **Select networks**.
@@ -109,7 +111,7 @@ Unable to create or modify firewall rules when public network interface for the
 To manage server or database level firewall rules, please enable the public network interface.
 ```
 
-Ensure that **Public network access** is set to **Selected networks** to be able to add, remove, or edit any firewall rules for Azure SQL Database and Azure Synapse Analytics.
+Ensure that **Public network access** is set to **Selected networks** to be able to add, remove, or edit any firewall rules for Azure SQL Database.
 
 ## Minimum TLS version
 
@@ -121,7 +123,7 @@ Currently, Azure SQL Database supports TLS 1.0, 1.1, 1.2, and 1.3. Setting a min
 
 Azure has announced that support for older TLS versions (TLS 1.0, and 1.1) ends August 31, 2025. For more information, see [TLS 1.0 and 1.1 deprecation](https://azure.microsoft.com/updates/azure-support-tls-will-end-by-31-october-2024-2/).
 
-Starting November 2024, you will no longer be able to set the minimal TLS version for Azure SQL Database and Azure Synapse Analytics client connections below TLS 1.2. 
+Starting November 2024, you will no longer be able to set the minimal TLS version for Azure SQL Database client connections below TLS 1.2. 
 
 ### Configure minimum TLS version 
 
@@ -209,11 +211,11 @@ You can use the Azure portal and SQL audit logs to identify clients that are con
 
 In the Azure portal, go to **Metrics** under **Monitoring** for your database resource, and then filter by *Successful connections*, and *TLS versions* = `1.0` and `1.1`:
 
-:::image type="content" source="media/connectivity-settings/connections-in-portal.png" alt-text="Screenshot of the monitoring page for the database resource in the Azure portal with successful tls 1.0 and 1.1 connections filtered. "::: 
+:::image type="content" source="media/connectivity-settings/connections-in-portal.png" alt-text="Screenshot of the monitoring page for the database resource in the Azure portal with successful T L S 1.0 and 1.1 connections filtered. "::: 
 
-You can also query [sys.fn_get_audit_file](/sql/relational-databases/system-functions/sys-fn-get-audit-file-transact-sql) directly within your database to view the `client_tls_version_name` in the audit file: 
+You can also query [sys.fn_get_audit_file](/sql/relational-databases/system-functions/sys-fn-get-audit-file-transact-sql) directly within your database to view the `client_tls_version_name` in the audit file, looking for events named `audit_event`.
 
-:::image type="content" source="media/connectivity-settings/tls-entries-in-audit-file.png" alt-text="Screenshot of a query result of the audit file showing tls version connections. ":::
+:::image type="content" source="media/connectivity-settings/tls-entries-in-audit-file.png" alt-text="Screenshot of a query result of the audit file showing T L S version connections. ":::
 
 
 ## Change the connection policy
@@ -276,6 +278,8 @@ It's possible to change the connection policy for your logical server by using t
 
 ### Azure CLI in a Bash shell
 
+For information on how to change the Azure SQL Database connection policy for a server, see [conn-policy](/cli/azure/sql/server/conn-policy)
+
 The following CLI script shows how to change the connection policy in a Bash shell:
 
 ```azurecli-interactive
@@ -311,5 +315,4 @@ az resource update --ids %sqlserverid% --set properties.connectionType=Proxy
 
 ## Related content
 
-- [Azure SQL Database and Azure Synapse Analytics connectivity architecture](connectivity-architecture.md)
-- [conn-policy](/cli/azure/sql/server/conn-policy)
+- [Connectivity architecture](connectivity-architecture.md)

azure-sql/database/connectivity-settings.md

@@ -5,7 +5,7 @@ description: Learn about available connectivity libraries and best practices for
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: wiassaf, mathoma
-ms.date: 11/14/2019
+ms.date: 03/18/2025
 ms.service: azure-sql
 ms.subservice: development
 ms.topic: concept-article
@@ -15,6 +15,7 @@ ms.custom:
 monikerRange: "=azuresql || =azuresql-db || =azuresql-mi || =fabricsql"
 ---
 # Application development overview - Azure SQL Database & Azure SQL Managed Instance
+
 [!INCLUDE [appliesto-sqldb-sqlmi-fabricsqldb](../includes/appliesto-sqldb-sqlmi-fabricsqldb.md)]
 
 This article walks through the basic considerations that a developer should be aware of when writing code to connect to your database in Azure. This article applies to Azure SQL Database, and Azure SQL Managed Instance.
@@ -23,23 +24,22 @@ This article walks through the basic considerations that a developer should be a
 
 You can use various [programming languages and platforms](connect-query-content-reference-guide.md) to connect and query Azure SQL Database. You can find [sample applications](https://azure.microsoft.com/resources/samples/?service=sql-database&sort=0) that you can use to connect to the database.
 
-You can leverage open-source tools like [cheetah](https://github.com/wunderlist/cheetah), [sql-cli](https://www.npmjs.com/package/sql-cli), [VS Code](https://code.visualstudio.com/). Additionally, Azure SQL Database works with Microsoft tools like [Visual Studio](https://www.visualstudio.com/downloads/) and  [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms). You can also use the Azure portal, PowerShell, and REST APIs to help you gain additional productivity.
+You can use open-source tools like [cheetah](https://github.com/wunderlist/cheetah), [sql-cli](https://www.npmjs.com/package/sql-cli), [VS Code](https://code.visualstudio.com/). Additionally, Azure SQL Database works with Microsoft tools like [Visual Studio](https://visualstudio.microsoft.com/downloads) and  [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms). You can also use the Azure portal, PowerShell, and REST APIs to help you gain more productivity.
 
 ## Authentication
 
 Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database and SQL Managed Instance support users and logins for both SQL authentication and [authentication](authentication-aad-overview.md) with Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)). Microsoft Entra logins are generally available in SQL Managed Instance and are in Public Preview for Azure SQL Database.
 
-Learn more about [managing database access and login](logins-create-manage.md).
+Learn more about [managing database access and logins](logins-create-manage.md).
 
 ## Client connections
 
 In your client connection logic, override the default timeout to be 30 seconds. The default of 15 seconds is too short for connections that depend on the internet.
 
-If you are using a [connection pool](/dotnet/framework/data/adonet/sql-server-connection-pooling), be sure to close the connection the instant your program is not actively using it, and is not preparing to reuse it.
+If you're using a [connection pool](/dotnet/framework/data/adonet/sql-server-connection-pooling), be sure to close the connection the instant your program isn't actively using it, and isn't preparing to reuse it.
 
 Avoid long-running transactions because any infrastructure or connection failure might roll back the transaction. If possible, split the transaction in the multiple smaller transactions and use [batching to improve performance](../performance-improve-use-batching.md).
 
-
 It's possible to connect your application to your Azure SQL resource by using the following languages: 
 
 - [.NET with Visual Studio](connect-query-dotnet-visual-studio.md)
@@ -53,24 +53,23 @@ It's possible to connect your application to your Azure SQL resource by using th
 It's possible to configure Microsoft Entra authentication to your Azure SQL resource. Review the following articles for more information: 
 
 - [Connect to Azure SQL with Microsoft Entra authentication and SqlClient](/sql/connect/ado-net/sql/azure-active-directory-authentication)
-- [Use Managed Identities in Microsoft Entra ID for Azure SQL](authentication-azure-ad-user-assigned-managed-identity.md)
+- [Managed identities in Microsoft Entra for Azure SQL](authentication-azure-ad-user-assigned-managed-identity.md)
 - [Connect to SQL Database from .NET App Service without secrets using a managed identity](/azure/app-service/tutorial-connect-msi-sql-database)
 
-
 ## Resiliency
 
-Azure SQL Database is a cloud service where you might expect transient errors that happen in the underlying infrastructure or in the communication between cloud entities. Although Azure SQL Database is resilient on the transitive infrastructure failures, these failures might affect your connectivity. When a transient error occurs while connecting to SQL Database, your code should [retry the call](troubleshoot-common-connectivity-issues.md). We recommend that retry logic use backoff logic, so that it does not overwhelm the service with multiple clients retrying simultaneously. Retry logic depends on the [error messages for SQL Database client programs](troubleshoot-common-errors-issues.md).
+Azure SQL Database is a cloud service where you might expect transient errors that happen in the underlying infrastructure or in the communication between cloud entities. Although Azure SQL Database is resilient on the transitive infrastructure failures, these failures might affect your connectivity. When a transient error occurs while connecting to SQL Database, your code should [retry the call](troubleshoot-common-connectivity-issues.md). We recommend that retry logic use backoff logic, so that it doesn't overwhelm the service with multiple clients retrying simultaneously. Retry logic depends on the [error messages for SQL Database client programs](troubleshoot-common-errors-issues.md).
 
 For more information about how to prepare for planned maintenance events on your Azure SQL Database, see [planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md).
 
 ## Network considerations
 
-- On the computer that hosts your client program, ensure the firewall allows outgoing TCP communication on port 1433.  More information: [Configure an Azure SQL Database firewall](firewall-configure.md).
-- If your client program connects to SQL Database while your client runs on an Azure virtual machine (VM), you must open certain port ranges on the VM. More information: [Ports beyond 1433 for ADO.NET 4.5 and SQL Database](adonet-v12-develop-direct-route-ports.md).
-- Client connections to Azure SQL Database sometimes bypass the proxy and interact directly with the database. Ports other than 1433 become important. For more information, [Azure SQL Database connectivity architecture](connectivity-architecture.md) and [Ports beyond 1433 for ADO.NET 4.5 and SQL Database](adonet-v12-develop-direct-route-ports.md).
+- On the computer that hosts your client program, ensure the firewall allows outgoing TCP communication on port 1433. More information: [Azure SQL Database IP firewall rules](firewall-configure.md).
+- If your client program connects to SQL Database while your client runs on an Azure virtual machine (VM), you must open certain port ranges on the VM. More information: [Ports beyond 1433 for ADO.NET 4.5](adonet-v12-develop-direct-route-ports.md).
+- Client connections to Azure SQL Database sometimes bypass the proxy and interact directly with the database. Ports other than 1433 become important. For more information, [Connectivity architecture](connectivity-architecture.md) and [Ports beyond 1433 for ADO.NET 4.5](adonet-v12-develop-direct-route-ports.md).
 - For networking configuration for an instance of SQL Managed Instance, see [network configuration for SQL Managed Instance](../managed-instance/how-to-content-reference-guide.md#network-configuration).
 
-## Next steps
+## Related content
 
 Explore all the capabilities of [SQL Database](sql-database-paas-overview.md) and [SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md).
 

azure-sql/database/develop-overview.md

@@ -13,7 +13,7 @@ ms.custom:
   - azure-sql-split
   - sqldbrb=2
   - ignite-2024
-monikerRange: "=azuresql || =azuresql-db || =fabric"
+monikerRange: "=azuresql || =azuresql-db || =fabricsql"
 ---
 # Monitor performance using dynamic management views
 

azure-sql/database/monitoring-with-dmvs.md

@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 03/18/2025
+ms.service: azure-sql-database
+ms.topic: include
+---
+
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: [Azure SQL Database](/sql/sql-server/sql-docs-navigation-guide#applies-to) :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: [Azure Synapse Analytics (dedicated SQL pools only)](/sql/sql-server/sql-docs-navigation-guide#applies-to) :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: [SQL database in Fabric](/sql/sql-server/sql-docs-navigation-guide#applies-to)