Merge pull request #183436 from shohamMSFT/patch-17

Update transparent-data-encryption-byok-configure.md

Author: Court72

articles/azure-sql/database/transparent-data-encryption-byok-configure.md

@@ -20,7 +20,7 @@ ms.date: 06/23/2021
 This article walks through how to use a key from Azure Key Vault for Transparent Data Encryption (TDE) on Azure SQL Database or Azure Synapse Analytics. To learn more about the TDE with Azure Key Vault integration - Bring Your Own Key (BYOK) Support, visit [TDE with customer-managed keys in Azure Key Vault](transparent-data-encryption-byok-overview.md). 
 
 > [!NOTE] 
-> Azure SQL now supports using a RSA key stored in a Managed HSM as TDE Protector. This feature is in **public preview**. Azure Key Vault Managed HSM is a fully managed, highly available, single-tenant, standards-compliant cloud service that enables you to safeguard cryptographic keys for your cloud applications, using FIPS 140-2 Level 3 validated HSMs. Learn more about [Managed HSMs](../../key-vault/managed-hsm/index.yml).
+> Azure SQL now supports using a RSA key stored in a Managed HSM as TDE Protector. Azure Key Vault Managed HSM is a fully managed, highly available, single-tenant, standards-compliant cloud service that enables you to safeguard cryptographic keys for your cloud applications, using FIPS 140-2 Level 3 validated HSMs. Learn more about [Managed HSMs](../../key-vault/managed-hsm/index.yml).
 
 > [!NOTE]
 > This article applies to Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics (dedicated SQL pools (formerly SQL DW)). For documentation on Transparent Data Encryption for dedicated SQL pools inside Synapse workspaces, see [Azure Synapse Analytics encryption](../../synapse-analytics/security/workspaces-encryption.md).
@@ -38,7 +38,7 @@ This article walks through how to use a key from Azure Key Vault for Transparent
   - No expiration date
   - Not disabled
   - Able to perform *get*, *wrap key*, *unwrap key* operations
-- **(In Preview)** To use a Managed HSM key, follow instructions to [create and activate a Managed HSM using Azure CLI](../../key-vault/managed-hsm/quick-create-cli.md)
+- To use a Managed HSM key, follow instructions to [create and activate a Managed HSM using Azure CLI](../../key-vault/managed-hsm/quick-create-cli.md)
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -83,7 +83,7 @@ For adding permissions to your server on a Managed HSM, add the 'Managed HSM Cry
 - Use the [Get-AzSqlServerTransparentDataEncryptionProtector](/powershell/module/az.sql/get-azsqlservertransparentdataencryptionprotector) cmdlet to confirm that the TDE protector was configured as intended.
 
 > [!NOTE]
-> **(In Preview)** For Managed HSM keys, use Az.Sql 2.11.1 version of PowerShell.
+> For Managed HSM keys, use Az.Sql 2.11.1 version of PowerShell.
 
 > [!NOTE]
 > The combined length for the key vault name and key name cannot exceed 94 characters.