Merge pull request #33875 from rwestMSFT/rw-0421-fix-links

Fix broken links

Author: prmerger-automator[bot]

docs/relational-databases/errors-events/includes/sql-server-2017-database-engine-events-and-errors-41400-49999.md

@@ -1,7 +1,8 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/10/2024
+ms.reviewer: maghan, mikeray
+ms.date: 04/10/2025
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -429,14 +430,14 @@ ms.topic: include
 | 45333 | 16 | No | The service request timed out. %ls. |
 | 45334 | 16 | No | Server edition '%ls' is invalid. |
 | 45335 | 16 | No | Server type '%ls' is invalid. |
-| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_01234567890123456789012345678901. |
+| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is `https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901`, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_01234567890123456789012345678901. |
 | 45337 | 16 | No | The planned failover operation has rolled back because database '%ls' could not be synchronized with its remote partner. This may be due to a service outage, or to a high volume of write traffic. Consider using forced failover. |
 | 45338 | 16 | No | The planned failover operation has rolled back because the remote server '%ls' could not be reached. This may be due to a service outage. Consider using forced failover. |
 | 45339 | 16 | No | The max size update on the geo-secondary database '%ls' on server '%ls' failed with reason '%ls'. |
 | 45340 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is '%ls'. |
 | 45341 | 16 | No | The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for '%ls' from server '%ls'. The encountered error message is '%ls'. |
 | 45342 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server '%ls' and key vault '%ls' belong to the same tenant. The error message from Active Directory Authentication library is '%ls'. |
-| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like 'https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
+| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like '`https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901`'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
 | 46501 | 15 | No | External table references '%S_MSG' that does not exist. |
 | 46502 | 15 | No | Type with name '%.\*ls' already exists. |
 | 46503 | 15 | No | Invalid format for option '%S_MSG'. |

docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-41400-49999.md

@@ -1,7 +1,8 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 11/20/2024
+ms.reviewer: maghan, mikeray
+ms.date: 04/10/2025
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -488,14 +489,14 @@ ms.topic: include
 | 45333 | 16 | No | The service request timed out. %ls. |
 | 45334 | 16 | No | Server edition '%ls' is invalid. |
 | 45335 | 16 | No | Server type '%ls' is invalid. |
-| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_YourKeyVersion. |
+| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is `https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion`, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_YourKeyVersion. |
 | 45337 | 16 | No | The planned failover operation has rolled back because database '%ls' could not be synchronized with its remote partner. This may be due to a service outage, or to a high volume of write traffic. Consider using forced failover. |
 | 45338 | 16 | No | The planned failover operation has rolled back because the remote server '%ls' could not be reached. This may be due to a service outage. Consider using forced failover. |
 | 45339 | 16 | No | The max size update on the geo-secondary database '%ls' on server '%ls' failed with reason '%ls'. |
 | 45340 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is '%ls'. |
 | 45341 | 16 | No | The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for '%ls' from server '%ls'. The encountered error message is '%ls'. |
 | 45342 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server '%ls' and key vault '%ls' belong to the same tenant. The error message from Active Directory Authentication library is '%ls'. |
-| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like 'https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
+| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like '`https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion`'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
 | 45344 | 16 | No | Catalog DB creation failed. |
 | 45345 | 16 | No | Cannot cancel database management operation '%ls' in the current state. |
 | 45346 | 16 | No | Subnet resource ID '%ls' is invalid. Please provide a correct resource Id for the target subnet. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-41400-49999.md

@@ -1,7 +1,8 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 01/16/2025
+ms.reviewer: maghan, mikeray
+ms.date: 04/10/2025
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -575,14 +576,14 @@ ms.topic: include
 | 45333 | 16 | No | The service request timed out. %ls. |
 | 45334 | 16 | No | Server edition '%ls' is invalid. |
 | 45335 | 16 | No | Server type '%ls' is invalid. |
-| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_YourKeyVersion. |
+| 45336 | 16 | No | The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For example, if the keyId is `https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion`, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_YourKeyVersion. |
 | 45337 | 16 | No | The planned failover operation has rolled back because database '%ls' could not be synchronized with its remote partner. This may be due to a service outage, or to a high volume of write traffic. Consider using forced failover. |
 | 45338 | 16 | No | The planned failover operation has rolled back because the remote server '%ls' could not be reached. This may be due to a service outage. Consider using forced failover. |
 | 45339 | 16 | No | The max size update on the geo-secondary database '%ls' on server '%ls' failed with reason '%ls'. |
 | 45340 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is '%ls'. |
 | 45341 | 16 | No | The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for '%ls' from server '%ls'. The encountered error message is '%ls'. |
 | 45342 | 16 | No | The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server '%ls' and key vault '%ls' belong to the same tenant. The error message from Active Directory Authentication library is '%ls'. |
-| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like 'https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
+| 45343 | 16 | No | The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like '`https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion`'. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at '%ls'. |
 | 45344 | 16 | No | Catalog DB creation failed. |
 | 45345 | 16 | No | Cannot cancel database management operation '%ls' in the current state. |
 | 45346 | 16 | No | Subnet resource ID '%ls' is invalid. Please provide a correct resource Id for the target subnet. |

docs/sql-server/azure-arc/manage-license-billing.md

@@ -130,7 +130,7 @@ The option of licensing SQL Server by physical cores with unlimited virtualizati
 - Your infrastructure and the selected payment method support the unlimited virtualization benefit.
 - Licensing your SQL Server instances by v-cores is more expensive than licensing the p-cores of the host.
 
-To use the unlimited virtualization benefit, you need to create a _SQLServerLicense_ resource that represents one or more physical hosts. The covered SQL Server instances must be connected to Azure Arc and configured to use the p-core license. For details about creating _SQLServerLicense_ resources, see [Create a SQL Server license](/sql/sql-server/azure-arc/manage-configuration).
+To use the unlimited virtualization benefit, you need to create a _SQLServerLicense_ resource that represents one or more physical hosts. The covered SQL Server instances must be connected to Azure Arc and configured to use the p-core license. For details about creating _SQLServerLicense_ resources, see [Create a SQL Server license](manage-configuration.md).
 
 > [!CAUTION]  
 > The unlimited virtualization benefit isn't available to VMs running on infrastructure from any of the [listed providers](https://aka.ms/listedproviders). These VMs can be licensed only by v-cores. If you create a *SQLServerLicense* resource with the intent of licensing these VMs by using unlimited virtualization, you'll be charged for the consumption of v-cores based on the SQL Server configuration of the host. Any existing p-core licenses don't apply to offset such charges.