Merge pull request #36053 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-10 18:30 UTC

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

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

@@ -65,9 +65,9 @@ This section clarifies the monikers that refer to product versions. It also list
 
 ## Related links
 
-* ADO.NET 4.6 was released on July 20, 2015. A blog announcement from the .NET team is available [here](https://devblogs.microsoft.com/dotnet/announcing-net-framework-4-6/).
-* ADO.NET 4.5 was released on August 15, 2012. A blog announcement from the .NET team is available [here](https://devblogs.microsoft.com/dotnet/announcing-the-release-of-net-framework-4-5-rtm-product-and-source-code/).
-  * A blog post about ADO.NET 4.5.1 is available [here](https://devblogs.microsoft.com/dotnet/announcing-the-net-framework-4-5-1-preview/).
+* ADO.NET 4.6 was released on July 20, 2015. See the [.NET team blog announcement](https://devblogs.microsoft.com/dotnet/announcing-net-framework-4-6/).
+* ADO.NET 4.5 was released on August 15, 2012. See the [.NET team blog announcement](https://devblogs.microsoft.com/dotnet/announcing-the-release-of-net-framework-4-5-rtm-product-and-source-code/).
+  * See the [.NET team blog post about ADO.NET 4.5.1](https://devblogs.microsoft.com/dotnet/announcing-the-net-framework-4-5-1-preview/).
 
 * Microsoft ODBC Driver 17 for SQL Server
 https://aka.ms/downloadmsodbcsql

azure-sql/database/always-encrypted-enclaves-getting-started-sgx.md

@@ -61,7 +61,7 @@ In this step, you'll create a new Azure SQL Database logical server and a new da
    - **Server name**: Enter *mysqlserver*, and add some characters for uniqueness. We can't provide an exact server name to use because server names must be globally unique for all servers in Azure, not just unique within a subscription. So enter something like mysqlserver135, and the portal lets you know if it's available or not.
    - **Location**: Select a location from the dropdown list.
       > [!IMPORTANT]
-      > You need to select a location (an Azure region) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
+      > You need to select a location (an Azure region) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). See the [regional availability of Microsoft Azure Attestation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-attestation).
    - **Authentication method**: Select **Use SQL Authentication**
    - **Server admin login**: Enter an admin login name, for example: *azureuser*.
    - **Password**: Enter a password that meets requirements, and enter it again in the **Confirm password** field.
@@ -108,7 +108,7 @@ In this step, you'll create a new Azure SQL Database logical server and a new da
 1. Create a new resource group.
 
    > [!IMPORTANT]
-   > You need to create your resource group in a region (location) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
+   > You need to create your resource group in a region (location) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). See the [regional availability of Microsoft Azure Attestation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-attestation).
 
    ```powershell
    $resourceGroupName = "<your new resource group name>"

azure-sql/database/data-discovery-and-classification-overview.md

@@ -300,7 +300,7 @@ You can use the following SQL drivers to retrieve classification metadata:
 ## FAQ - Advanced classification capabilities
 
 **Question**: Will [Microsoft Purview](/azure/purview/overview) replace SQL Data Discovery & Classification or will SQL Data Discovery & Classification be retired soon?
-**Answer**: We continue to support SQL Data Discovery & Classification and encourage you to adopt [Microsoft Purview](/azure/purview/overview) which has richer capabilities to drive advanced classification capabilities and data governance. If we decide to retire any service, feature, API or SKU, you'll receive advance notice including a migration or transition path. Learn more about Microsoft Lifecycle policies [here](/lifecycle/index).
+**Answer**: We continue to support SQL Data Discovery & Classification and encourage you to adopt [Microsoft Purview](/azure/purview/overview) which has richer capabilities to drive advanced classification capabilities and data governance. If we decide to retire any service, feature, API or SKU, you'll receive advance notice including a migration or transition path. For more information, see the [Microsoft Lifecycle policies](/lifecycle/index).
 
 ## Next steps
 

azure-sql/database/elastic-scale-upgrade-client-library.md

@@ -36,13 +36,13 @@ Performing these steps in order ensures that old versions of the client library
 
 **2. Upgrade your scripts.** If you're using **PowerShell** scripts to manage shards, [download the new library version](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Client/) and copy it into the directory from which you execute scripts.
 
-**3. Upgrade your split-merge service.** If you use the elastic database split-merge tool to reorganize sharded data, [download and deploy the latest version of the tool](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Service.SplitMerge/). Detailed upgrade steps for the Service can be found [here](elastic-scale-overview-split-and-merge.md).
+**3. Upgrade your split-merge service.** If you use the elastic database split-merge tool to reorganize sharded data, [download and deploy the latest version of the tool](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Service.SplitMerge/). For detailed upgrade steps, see [Moving data between scaled-out cloud databases](elastic-scale-overview-split-and-merge.md).
 
 **4. Upgrade your Shard Map Manager databases**. Upgrade the metadata supporting your Shard Maps in Azure SQL Database.  There are two ways you can accomplish this, using PowerShell or C#. Both options are shown below.
 
 ***Option 1: Upgrade metadata using PowerShell***
 
-1. Download the latest command-line utility for NuGet from [here](https://nuget.org/nuget.exe) and save to a folder.
+1. Download the [latest command-line utility for NuGet](https://nuget.org/nuget.exe) and save to a folder.
 1. Open a Command Prompt, navigate to the same folder, and issue the command:
    `nuget install Microsoft.Azure.SqlDatabase.ElasticScale.Client`
 1. Navigate to the subfolder containing the new client DLL version you have downloaded, for example:

azure-sql/database/private-endpoint-overview.md

@@ -238,7 +238,7 @@ Consider [DNS configuration scenarios](/azure/private-link/private-endpoint-dns#
 
 ## Connect from Azure Synapse Analytics to Azure Storage using PolyBase and the COPY statement
 
-PolyBase and the COPY statement are commonly used to load data into Azure Synapse Analytics from Azure Storage accounts. If the Azure Storage account that you're loading data from limits access only to a set of virtual network subnets via Private Endpoints, Service Endpoints, or IP-based firewalls, the connectivity from PolyBase and the COPY statement to the account will break. For enabling both import and export scenarios with Azure Synapse Analytics connecting to Azure Storage that's secured to a virtual network, follow the steps provided [here](vnet-service-endpoint-rule-overview.md#impact-of-using-virtual-network-service-endpoints-with-azure-storage).
+PolyBase and the COPY statement are commonly used to load data into Azure Synapse Analytics from Azure Storage accounts. If the Azure Storage account that you're loading data from limits access only to a set of virtual network subnets via Private Endpoints, Service Endpoints, or IP-based firewalls, the connectivity from PolyBase and the COPY statement to the account will break. For enabling both import and export scenarios with Azure Synapse Analytics connecting to Azure Storage that's secured to a virtual network, see [Impact of using virtual network service endpoints with Azure Storage](vnet-service-endpoint-rule-overview.md#impact-of-using-virtual-network-service-endpoints-with-azure-storage).
 
 ## Data exfiltration prevention
 

azure-sql/database/transparent-data-encryption-byok-key-rotation.md

@@ -65,7 +65,7 @@ For installation, see [Install the Azure CLI](/cli/azure/install-azure-cli).
 Automatic rotation in a server, database, or managed instance can be used with automatic key rotation in Azure Key Vault to enable end-to-end zero touch rotation for TDE keys.
 
 > [!NOTE]
-> If the server or managed instance has geo-replication configured, prior to enabling automatic rotation, additional guidelines need to be followed as described [here](transparent-data-encryption-byok-overview.md#geo-replication-considerations-when-configuring-automated-rotation-of-the-tde-protector).  
+> If the server or managed instance has geo-replication configured, prior to enabling automatic rotation, see [Geo-replication considerations when configuring automated rotation of the TDE protector](transparent-data-encryption-byok-overview.md#geo-replication-considerations-when-configuring-automated-rotation-of-the-tde-protector).  
 
 # [Portal](#tab/azure-portal)
 

azure-sql/database/transparent-data-encryption-byok-overview.md

@@ -130,7 +130,7 @@ Auditors can use Azure Monitor to review managed HSM AuditEvent logs, if logging
 - If you're importing an existing key into key vault, ensure it's provided in one of the supported file formats: `.pfx`, `.byok`, or `.backup`. To import HSM-protected keys into Azure Managed HSM, see [Import HSM-protected keys to Managed HSM (BYOK)](/azure/key-vault/managed-hsm/hsm-protected-keys-byok).
 
 > [!NOTE]  
-> An issue with Thales CipherTrust Manager versions before v2.8.0 prevents keys newly imported into Azure Key Vault from being used with Azure SQL Database or Azure SQL Managed Instance for customer-managed TDE scenarios. More details about this issue can be found [here](https://thalesdocs.com/ctp/cm/2.6/release_notes/index.html#ciphertrust-cloud-key-manager_1). For such cases, wait 24 hours after importing the key into Azure Key Vault to begin using it as TDE protector for the server or managed instance. This issue is resolved in Thales CipherTrust Manager [v2.8.0](https://thalesdocs.com/ctp/cm/2.8/release_notes/index.html#resolved-issues).
+> An issue with Thales CipherTrust Manager versions before v2.8.0 prevents keys newly imported into Azure Key Vault from being used with Azure SQL Database or Azure SQL Managed Instance for customer-managed TDE scenarios. For more details about this issue, see [CipherTrust Cloud Key Manager release notes](https://thalesdocs.com/ctp/cm/2.6/release_notes/index.html#ciphertrust-cloud-key-manager_1). For such cases, wait 24 hours after importing the key into Azure Key Vault to begin using it as TDE protector for the server or managed instance. This issue is resolved in Thales CipherTrust Manager [v2.8.0](https://thalesdocs.com/ctp/cm/2.8/release_notes/index.html#resolved-issues).
 
 ## Recommendations when configuring customer-managed TDE
 

azure-sql/managed-instance/quickstart-content-reference-guide.md

@@ -74,7 +74,7 @@ Learn more about the [recommended migration process](../migration-guides/managed
 ## Related content
 
 - [Features comparison: Azure SQL Database and Azure SQL Managed Instance](../database/features-comparison.md)
-- [details and known issues here](transact-sql-tsql-differences-sql-server.md)
+- [T-SQL differences between SQL Server and Azure SQL Managed Instance](transact-sql-tsql-differences-sql-server.md)
 - [Technical characteristics of SQL Managed Instance](resource-limits.md#service-tier-characteristics)
 - [Azure SQL Managed Instance content reference](how-to-content-reference-guide.md)
 - [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio)

azure-sql/updates/ssl-root-certificate-expiring.md

@@ -68,7 +68,7 @@ No. Since the change is only on the client side to connect to the server, there'
 
 ### What if I can't get a scheduled downtime for this change?
 
-Since the clients used for connecting to the server needs to be updating the certificate information as described in the fix section [here](./ssl-root-certificate-expiring.md#what-do-i-need-to-do-to-maintain-connectivity), we don't need to a downtime for the server in this case.
+Since the clients used for connecting to the server needs to be updating the certificate information as described in the [fix section](ssl-root-certificate-expiring.md#what-do-i-need-to-do-to-maintain-connectivity), we don't need to a downtime for the server in this case.
 
 ### If I create a new server after November 30, 2020, will I be impacted?
 

azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md

@@ -422,7 +422,7 @@ You might encounter issues while setting up a Windows failover cluster or its co
 
 If you are on Windows Server 2019, and you don't see a Windows Cluster IP, you have configured [Distributed Network Name](failover-cluster-instance-distributed-network-name-dnn-configure.md), which is only supported on SQL Server 2019. If you have previous versions of SQL Server, you can remove and [Recreate the Cluster using Network Name](availability-group-manually-configure-tutorial.md#create-the-cluster).
 
-Review other Windows Failover [Clustering Events Errors and their Solutions here](/windows-server/failover-clustering/system-events)
+Review other Windows Failover [Failover Clustering system log events](/windows-server/failover-clustering/system-events) and their solutions.
 
 ## Next steps