Merge pull request #34260 from markingmyname/sqlvalid

[Build Validation] Edit warnings and broken links

Author: ttorble

azure-sql/database/connectivity-settings.md

@@ -115,7 +115,7 @@ Ensure that **Public network access** is set to **Selected networks** to be able
 
 ## Minimum TLS version
 
-The minimum [Transport Layer Security (TLS)](https://support.microsoft.com/help/3135244/tls-1-2-support-for-microsoft-sql-server) version setting allows customers to choose which version of TLS their SQL database uses. It's possible to change the minimum TLS version by using the Azure portal, Azure PowerShell, and the Azure CLI.
+The minimum [Transport Layer Security (TLS)](/troubleshoot/sql/database-engine/connect/tls-1-2-support-microsoft-sql-server) version setting allows customers to choose which version of TLS their SQL database uses. It's possible to change the minimum TLS version by using the Azure portal, Azure PowerShell, and the Azure CLI.
 
 Currently, Azure SQL Database supports TLS 1.0, 1.1, 1.2, and 1.3. Setting a minimum TLS version ensures that newer TLS versions are supported. For example, choosing a TLS version 1.1 means only connections with TLS 1.1 and 1.2 are accepted, and connections with TLS 1.0 are rejected. After you test to confirm that your applications support it, we recommend setting the minimal TLS version to 1.3. This version includes fixes for vulnerabilities in previous versions and is the highest version of TLS that's supported in Azure SQL Database.
 

azure-sql/database/develop-cplusplus-simple.md

@@ -30,7 +30,7 @@ There are currently two ways to connect to Azure SQL Database: ODBC (Open Databa
 
 ## Create your Azure SQL Database
 
-See the [getting started page](single-database-create-quickstart.md) to learn how to create a sample database.  Alternatively, you can follow this [short two-minute video](https://azure.microsoft.com/documentation/videos/azure-sql-database-create-dbs-in-seconds/) to create an Azure SQL Database using the Azure portal.
+See the [getting started page](single-database-create-quickstart.md) to learn how to create a sample database.
 
 ## Get connection string
 

azure-sql/database/security-overview.md

@@ -195,14 +195,29 @@
     },
     "dest": "azure-sql",
     "rules": {
+      "sensitive-language-ma": {
+        "exclude": [
+          "database-engine/install-windows/**/*.md"
+        ]
+      },
       "sensitive-language-sl": {
         "exclude": [
+          "includes/bias-sensitive-term-t.md",
           "virtual-machines/linux/rhel-high-availability-fencing-tutorial.md",
           "virtual-machines/linux/sles-high-availability-fencing-tutorial.md",
           "virtual-machines/linux/ubuntu-high-availability-fencing-tutorial.md",
           "virtual-machines/linux/high-availability-listener-tutorial.md"
         ]
-      }
-    }
-  }
-}
+      },
+      "sensitive-language-wl": {
+        "exclude": [
+          "big-data-cluster/reference-config-spark-hadoop.md",
+          "relational-databases/errors-events/**/*.md"
+        ]
+      },
+      "sensitive-language-bl": {
+        "exclude": []
+       }
+     }
+   }
+  }

azure-sql/docfx.json

@@ -0,0 +1,11 @@
+---
+author: MikeRayMSFT
+ms.author: mikeray
+ms.reviewer: maghan
+ms.date: 05/29/2025
+ms.service: sql
+ms.topic: include
+---
+
+> [!NOTE]
+> This article contains references to the term slave, a term that Microsoft no longer uses. When the term is removed from the software, we remove it from this article.

azure-sql/includes/bias-sensitive-term-t.md

@@ -5,7 +5,7 @@ ms.date: 03/29/2023
 ms.service: virtual-machines
 ms.topic: include
 ---
-SQL Server features and capabilities provide methods of securing data at the database level that can be combined with security features at the infrastructure level. Together, these features provide [defense-in-depth](https://azure.microsoft.com/resources/videos/defense-in-depth-security-in-azure/) at the infrastructure level for cloud-based and hybrid solutions. In addition, with Azure security measures, it's possible to encrypt your sensitive data, protect virtual machines from viruses and malware, secure network traffic, identify and detect threats, meet compliance requirements, and provides a single method for administration and reporting for any security need in the hybrid cloud.
+SQL Server features and capabilities provide methods of securing data at the database level that can be combined with security features at the infrastructure level. Together, these features provide defense-in-depth at the infrastructure level for cloud-based and hybrid solutions. In addition, with Azure security measures, it's possible to encrypt your sensitive data, protect virtual machines from viruses and malware, secure network traffic, identify and detect threats, meet compliance requirements, and provides a single method for administration and reporting for any security need in the hybrid cloud.
 
 - Use [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction) to evaluate and take action to improve the security posture of your data environment. Capabilities such as [Azure Advanced Threat Protection (ATP)](../database/threat-detection-overview.md) can be used across your hybrid workloads to improve security evaluation and give the ability to react to risks. Registering your SQL Server VM with the [SQL IaaS Agent extension](../virtual-machines/windows/sql-agent-extension-manually-register-single-vm.md) surfaces Microsoft Defender for Cloud assessments within the [SQL virtual machine resource](../virtual-machines/windows/manage-sql-vm-portal.md) of the Azure portal.
 - Use [Microsoft Defender for SQL](/azure/defender-for-cloud/defender-for-sql-introduction) to discover and mitigate potential database vulnerabilities, as well as detect anomalous activities that could indicate a threat to your SQL Server instance and database layer.

azure-sql/includes/virtual-machines-best-practices-security.md

@@ -146,7 +146,7 @@ The following constraints on virtual network features and traffic are in effect:
 - **Virtual network peering – configuration**: When establishing virtual network peering between virtual networks that contain subnets with SQL Managed Instances, such subnets must use different route tables and network security groups (NSG). Reusing the route table and NSG in two or more subnets participating in virtual network peering will cause connectivity issues in all subnets using those route tables or NSG, and cause SQL Managed Instance's management operations to fail.
 - **NAT gateway**: Using [Azure Virtual Network NAT](/azure/virtual-network/nat-gateway/nat-overview) to control outbound connectivity with a specific public IP address renders SQL Managed Instance unavailable. The SQL Managed Instance service is currently limited to use the basic load balancer, which doesn't provide coexistence of inbound and outbound flows with Azure Virtual Network NAT.
 - **IPv6 for Azure Virtual Network**: Deploying SQL Managed Instance to [dual stack IPv4/IPv6 virtual networks](/azure/virtual-network/ip-services/ipv6-overview) is expected to fail. Associating a network security group or a route table with user-defined routes (UDRs) that contains IPv6 address prefixes to a SQL Managed Instance subnet renders SQL Managed Instance unavailable. Also, adding IPv6 address prefixes to a network security group or UDR that's already associated with a managed instance subnet renders SQL Managed Instance unavailable. SQL Managed Instance deployments to a subnet with a network security group and UDR that already have IPv6 prefixes are expected to fail.
-- **TLS 1.2 is enforced on outbound connections**: Beginning in January 2020, Microsoft enforces TLS 1.2 for intra-service traffic in all Azure services. For SQL Managed Instance, this resulted in TLS 1.2 being enforced on outbound connections that are used for replication and on linked server connections to SQL Server. If you use a version of SQL Server that's earlier than 2016 with SQL Managed Instance, make sure that you apply [TLS 1.2-specific updates](https://support.microsoft.com/help/3135244/tls-1-2-support-for-microsoft-sql-server).
+- **TLS 1.2 is enforced on outbound connections**: Beginning in January 2020, Microsoft enforces TLS 1.2 for intra-service traffic in all Azure services. For SQL Managed Instance, this resulted in TLS 1.2 being enforced on outbound connections that are used for replication and on linked server connections to SQL Server. If you use a version of SQL Server that's earlier than 2016 with SQL Managed Instance, make sure that you apply [TLS 1.2-specific updates](/troubleshoot/sql/database-engine/connect/tls-1-2-support-microsoft-sql-server).
 - **Internal fallback to Azure DNS**: Managed instances depend on functioning DNS resolution in their virtual networks. If a managed instance's virtual network is configured to use [custom DNS server(s)](/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#name-resolution-that-uses-your-own-dns-server) and a DNS request issued to custom DNS server(s) fails to complete within a certain interval (1-2 seconds), managed instance will repeat the request against [Azure DNS](/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#azure-provided-name-resolution) in that virtual network.
 
 

azure-sql/managed-instance/connectivity-architecture-overview.md

@@ -18,7 +18,7 @@ ms.devlang: azurecli
 > 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 Managed Instance client connections below TLS 1.2. 
 
-The Minimal [Transport Layer Security (TLS)](https://support.microsoft.com/help/3135244/tls-1-2-support-for-microsoft-sql-server) Version setting allows customers to control the version of TLS used by their Azure SQL Managed Instance.
+The Minimal [Transport Layer Security (TLS)](/troubleshoot/sql/database-engine/connect/tls-1-2-support-microsoft-sql-server) Version setting allows customers to control the version of TLS used by their Azure SQL Managed Instance.
 
 At present we support TLS 1.0, 1.1 and 1.2. Setting a Minimal TLS Version ensures that subsequent, newer TLS versions are supported. For example,  e.g.,  choosing  a TLS version greater than 1.1. means only connections with TLS 1.1 and 1.2 are accepted and TLS 1.0 is rejected. After testing to confirm your applications supports it, we recommend setting minimal TLS version to 1.2 since it includes fixes for vulnerabilities found in previous versions and is the highest version of TLS supported in Azure SQL Managed Instance.
 
@@ -58,7 +58,7 @@ Set-AzSqlInstance -Name sql-instance-name -ResourceGroupName resource-group -Min
 ## Set Minimal TLS Version via Azure CLI
 
 > [!IMPORTANT]
-> All scripts in this section requires [Azure CLI](/cli/azure/install-azure-cli).
+> All scripts in this section require [Azure CLI](/cli/azure/install-azure-cli).
 
 ### Azure CLI in a bash shell
 

azure-sql/managed-instance/minimal-tls-version-configure.md

@@ -175,6 +175,4 @@ The Data SQL Engineering team developed these resources. This team's core charte
 
 - For other migration guides, see [Azure Database Migration Guide](/data-migration/).
 
-- For migration videos, see [Overview of the migration journey and recommended migration and assessment tools and services](https://azure.microsoft.com/resources/videos/overview-of-migration-and-recommended-tools-services/).
-
 - For more [cloud migration resources](https://azure.microsoft.com/migration/resources/), see [cloud migration solutions](https://azure.microsoft.com/migration).

azure-sql/migration-guides/database/mysql-to-sql-database-guide.md

@@ -288,4 +288,4 @@ The Data SQL Engineering team developed these resources. This team's core charte
 - [Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso-migration-scale)
 - [Best practices for costing and sizing workloads for migration to Azure](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs)
 - [Cloud Migration Resources](https://azure.microsoft.com/migration/resources)
-- [Overview of the migration journey and the tools and services recommended for performing assessment and migration](https://azure.microsoft.com/resources/videos/overview-of-migration-and-recommended-tools-services/)
+