SQL Server Transparent Data Encryption encrypts database files and backups. Extensible Key Management changes where the key that protects the database encryption key is managed. The SQL Server provider bridges the engine to a cloud key service, software key manager or hardware security module. The provider, SQL Server edition and operating system need to be supported together.

A cloud key service can fit an estate that already uses that identity and control plane. A self-managed key manager or HSM can fit different custody and network requirements. The key service also becomes part of database recovery. Each choice needs operational coverage for restoring an older backup, starting a replica and reaching the required key after credentials or infrastructure change.

SQL Server EKM providers for TDE at a glance

Use the integration model to estimate which components must be available to each SQL Server instance. Verify the exact SQL edition, platform and provider release before the trial.

Eight SQL Server EKM approaches and their restore checks
ProviderKey service or deviceSQL integrationRestore dependency to verify
SQL Server Connector for Azure Key VaultAzure Key Vault according to connector prerequisitesMicrosoft SQL Server Connector EKM providerDatabase protector, vault identity and reachability from recovery host
Thales CipherTrust CAKMCipherTrust Manager and supported key backingThales CAKM for SQL Server EKMProvider settings, client registration and old active key access
Fortanix Data Security ManagerFortanix DSM security object and groupFortanix SQL Server EKM providerTarget app identity, group permissions and replicated key availability
Entrust nShield SQL EKM ProvidernShield HSM and Security World configurationEntrust EKM integrationTarget hardware and continued access to correct key material
HashiCorp Vault EKM ProviderVault-backed key workflow with supported deploymentVault SQL Server EKM providerRequired Vault licensing, target identity and key version access
Utimaco SQL Server EKM Provideru.trust GP HSM per the integration guideUtimaco EKM providerTarget partition, device reachability and expected key identity
Futurex KMES Series 3 with Futurex EKMFuturex enterprise key-management systemFuturex EKM integrationRecovery KMES path, key policy and compatible provider configuration
Eviden Key Management System with Cosmian EKMEviden KMS SQL Server integrationCosmian EKM module in documented deploymentModule support, client credential and access to existing protector

SQL Server Connector for Azure Key Vault

The SQL Server Connector for Azure Key Vault lets supported SQL Server deployments protect a database encryption key with an asymmetric key in Azure Key Vault. It is useful when an organization already manages key access and auditing in Azure and wants SQL Server to use the same key service.

Its strength is the Microsoft-documented integration across eligible Windows and Linux scenarios. Authentication and setup differ by SQL Server build and deployment, especially for managed identity. Restores and failover targets need a working provider configuration and access to the key version that protected the database.

Prepare a separate SQL Server recovery host with the supported connector and the approved vault identity. Ensure the old key can still be opened and used from the recovery host. Record the key version and the principal's effective rights.

For a rotated protector, choose a backup made before rotation and another made after it. Rehearse restoring both according to the applicable Microsoft connector instructions, and check that the recovery identity accesses only the intended keys.

SQL Server Connector for Microsoft Azure Key Vault installation wizard.
Microsoft’s Windows installation wizard for the SQL Server Connector to Azure Key Vault. Publisher example
Compatibility
Supported SQL Server and Azure Key Vault EKM combination. Linux and managed identity have specific version and deployment requirements.
License and trial
Microsoft connector. Azure Key Vault usage and SQL Server licensing apply.

Thales CipherTrust CAKM for Microsoft SQL Server EKM

Thales CipherTrust CAKM for Microsoft SQL Server EKM connects the SQL Server provider to CipherTrust-managed keys. It is a candidate where an organization already uses CipherTrust Manager to govern key access and needs SQL Server TDE to operate under that model.

Its main value is integrating database TDE with an existing key management service. The provider release, supported SQL Server host and server authentication must agree. The design also needs a durable path to the same key from restored databases and other SQL Server nodes.

Record the CipherTrust Manager configuration and CAKM provider version alongside the SQL Server build. Set up the documented provider registration on both the source and target before you try an encrypted restore.

Check recovery access from a clean target and compare available versions with the thumbprint recorded for the backup. Rehearse a temporary lab dependency outage to see what a fresh recovery operation actually requires.

Thales CAKM for Microsoft SQL Server EKM installer showing the Server Protocol selection.
The CipherTrust CAKM installation wizard asks for the server protocol. Publisher example
Compatibility
Supported CipherTrust Manager, CAKM provider and SQL Server version and host combination.
License and trial
Commercial Thales licensing.

Fortanix Data Security Manager

Fortanix Data Security Manager provides an EKM provider and documents SQL Server TDE for standalone servers and backup and restore. It is useful when a team wants a centralized key service with an explicit walkthrough for making the protected database available on another instance.

The benefit is managing key access and the provider’s identity in DSM. A restore target needs the compatible provider and the appropriate key access. Comparing standalone operation, replication and recovery separately helps identify where more than one SQL Server installation must be configured.

Use a Fortanix app or identity authorized for the test security object. Check that the source and target use compatible provider versions and can reach the correct DSM service or cluster.

The standalone guide describes one topology. For an availability-group deployment, validate the relevant replica instructions and failover requirements separately. Preserve the older test key for a restore of a pre-rotation backup.

SQL Server Management Studio restore error 33111 with the asymmetric key thumbprint.
Fortanix’s restore guide shows SQL Server error 33111 when the restore instance cannot find the external asymmetric key. Publisher example
Compatibility
Supported Fortanix DSM and SQL Server EKM provider and Windows SQL Server setup.
License and trial
Commercial DSM and provider entitlement.

Entrust nShield SQL EKM Provider

Entrust nShield’s SQL EKM integration lets supported SQL Server use an asymmetric key protected by an nShield HSM. It is useful where cryptographic key custody needs to fit an existing hardware-backed Security World and SQL Server will participate in that environment.

The useful distinction is putting key protection under the HSM’s operating and authorization model. The SQL Server provider depends on the configured nShield software and HSM access. A recovered server or replica needs compatible enrollment and access to the required key material.

Confirm the target can use its planned nShield hardware and Security World configuration during a recovery. Record how the administrative team restores approved key access if the source SQL host is lost.

Test restore from a separately built SQL Server instance that uses the intended EKM/provider credentials. Keep the recovery permissions and hardware prerequisites with the resulting evidence.

SQL Server Management Studio query and object tree showing the Entrust nShield EKM provider.
Entrust’s integration guide shows the nShield provider registered in SQL Server Management Studio. Publisher example
Compatibility
Supported nShield HSM and software, Entrust SQL EKM provider and SQL Server configuration.
License and trial
Commercial Entrust software, hardware and support terms.

HashiCorp Vault EKM Provider

HashiCorp’s Vault EKM provider connects SQL Server TDE to asymmetric keys managed through Vault Transit. It is useful when a company already operates Vault and wants to extend that key service to SQL Server database encryption. This is a separate integration from Vault’s database credential engine.

Its strength is central key policy around a service already managed by the organization. The provider is an Enterprise feature and relies on the supported client, Vault authentication and availability. A recovery design needs to preserve both the Vault keys and a reliable way for the target to use them.

Verify the exact Vault EKM provider and Vault licensing and platform support for the proposed deployment. The database secrets engine addresses SQL credentials and has a different scope from the SQL Server encryption integration.

Check authentication and key access from the designated recovery host and record the provider's supported procedures for key rotation. Restore a test backup that predates rotation with the older required key still available.

Vault documentation showing the EKM provider installation and its listed prerequisites.
HashiCorp’s Windows installation guide shows the Vault EKM provider prerequisites. Documentation screenshot
Compatibility
Supported Vault EKM provider deployment with Vault Enterprise and the required Key Management module.
License and trial
Commercial Vault Enterprise with the applicable Advanced Data Protection module.

Utimaco SQL Server EKM Provider with u.trust GP HSM

Utimaco’s SQL Server EKM provider works with the u.trust GP HSM to protect a SQL Server TDE key. Its guides cover transparent encryption and a documented SQL Server clustering integration. It is useful when an organization has chosen the Utimaco HSM platform and needs supported database encryption.

The hardware integration is the main reason to consider it. Node software, HSM connectivity and provider access have to work from each applicable SQL Server node. The clustering guide is relevant because installing and testing one provider on one host only proves one path to the key.

Validate the SQL Server EKM provider version with the documented u.trust GP HSM deployment. Capture the device or partition configuration that the authorized SQL Server service relies on at startup and restore.

Restore a small protected lab database on a second host. Note what key access is required, how device reachability is monitored and what the runbook says when the initially preferred device is unavailable.

Utimaco transparent data encryption documentation showing its asymmetric key example.
Utimaco documents the asymmetric key setup used with its SQL Server EKM provider. Documentation screenshot
Compatibility
Supported Utimaco HSM, provider and documented SQL Server deployment.
License and trial
Commercial provider, hardware and support terms.

Futurex KMES Series 3 with Futurex EKM

Futurex documents a SQL Server integration using its EKM provider with the KMES Series 3 key management platform. It is useful for organizations that already centralize hardware-backed key operations through Futurex and need those operations available to SQL Server TDE.

The fit depends on the documented SQL host and KMES setup. Provider enrollment, service identity and reachability determine whether SQL Server can use the key. Database migration and disaster recovery also require the target to connect to the appropriate key service and access the original protector.

Ask for the exact Futurex EKM and KMES release combination and document which service or device supplies the key in each environment. Verify supported methods for recovery host registration using the version supplied.

Keep timing and error evidence from an authorized restore using the planned redundant key service. Compare access to current and prior protectors when the recovery site is deliberately isolated from the source SQL host.

Futurex KMES Series 3 Network Options with System/Host API and User Certificates settings.
The Futurex KMES Series 3 integration guide shows the System/Host API certificate settings. Publisher example
Compatibility
Compatible Futurex KMES deployment, EKM provider and SQL Server version.
License and trial
Commercial Futurex hardware, software and support terms.

Eviden Key Management System with Cosmian EKM

Eviden KMS documents a Windows EKM provider DLL that sends key operations to the service over mutual TLS. SQL Server can use it as a TDE provider in the documented configuration. It is useful when an organization wants its SQL Server keys managed through the Eviden and Cosmian integration.

The design fits an estate that can install the provider and manage mutual TLS identities on SQL Server nodes. Provider and service compatibility, certificate renewal and access to historical keys affect recovery. The operating team needs to maintain those dependencies together.

Verify the documented SQL Server and operating system versions for the deployed Cosmian EKM module and Eviden KMS. Record client certificate and credential ownership along with the expected external key identity.

Test on a cold SQL Server recovery target using the supported module and an independently configured credential. Confirm restore, completed encryption state and access to the protected data after recovery.

Eviden documentation showing the CREATE CRYPTOGRAPHIC PROVIDER example for Cosmian EKM.
Eviden’s integration guide shows how the signed Cosmian provider is registered in SQL Server. Documentation screenshot
Compatibility
Windows SQL Server with the documented EKM DLL, Eviden KMS and mutual TLS setup.
License and trial
Commercial or applicable platform terms depend on the deployment.

Shortlist by the key service and the recovery topology

What you needTools to shortlistWhat to verify
Use Azure Key Vault from SQL ServerMatch operating system, SQL build, identity model and connector path. Test vault access from the restore instance as well as the source.
Use an external key manager with a SQL Server providerConfirm supported edition and operating system, software version, old key access, endpoint and credential setup on every instance.
Use a supported appliance or HSM pathConfirm the exact appliance, client, provider version and authentication model. Test key use from a clean restore host and check the recovery copy of the key.
Protect a database in an Availability GroupUse the publisher’s setup for your SQL topology. Verify provider, credential and key bindings for each replica and perform a planned failover in the lab.

Identify which external key dependency must survive a recovery

The SQL database encryption key is protected by a certificate or asymmetric key. With an EKM integration, the SQL Server provider connects to an external key service or device for the configured protector. Record the protector and service identity as part of the backup recovery plan.

Check SQL Server edition and platform first. Confirm supported plugin and service versions, supported SQL hosts and whether each replica can open the required key. Plan recovery access for prior protectors required by retained backup media.

What must remain available if the source server is gone?
  • A managed vault already owns the SQL key lifecycle

    Verify connector identity and previous key versions

    Rebuild the connector and establish key access from the recovery path.

  • Policy requires a supported HSM or protected key manager

    Trial the SQL provider and secondary device or service

    Prove a clean recovery host can reach and use the same required key.

  • Availability-group replicas need to take over

    Prepare each replica's key access

    Rehearse failover and backup restore as separate recovery cases.

Restore a protected backup on a separate SQL Server host

Use a disposable pair of instances, the provider's supported procedure and one encrypted synthetic database. Record the source protector thumbprint and key version at the time of the backup. Prepare the target provider and an approved key identity. Keep the required older test protector if you exercise rotation.

Treat restore completion and a recovered marker row as separate checks. If you also check missing-key handling, use an isolated test host or identity with intentionally missing test permission. Restore access before repeating the test. Avoid disabling, deleting or purging actual keys used by recoverable data.

Proof to keep for the EKM recovery pilot
StageRecordExpected evidence
Source backupBackup ID, instance build, protector version and SQL thumbprintBackup and original protection state are attributable
Recovery target preparationProvider version, credential scope and approved key service pathThe configured target can access the required protector
Restored databaseKey state, protector thumbprint and marker readDatabase is online, encrypted and accessible under the intended role
Backup predating a key changePrior protector availability and restore resultRetained backups have a verified restore path

How to compare these tools

Connect the exact provider and SQL Server build on an isolated instance. Verify key access on every replica and a restore host. Record what happens when access to the key service is interrupted. Sources checked .

Restore an EKM-protected TDE backup on a separate instance

Use a synthetic table dbo.TdeRecoveryTrialRows with RowId and Marker columns in TdeRecoveryTrial. Record the following values on the lab source, then run the same read-only check on a restored database with the same name on an independent target. Use an authorized identity with the SQL Server release's documented encryption-state DMV permission.

SQL

Read TDE protection state and the recovered marker

T-SQL · 14 lines

SET NOCOUNT ON;IF DB_NAME() <> N'TdeRecoveryTrial'    THROW 51000, 'Use the disposable TdeRecoveryTrial database.', 1; SELECT SYSUTCDATETIME() AS ObservedUtc,       CONVERT(nvarchar(128), SERVERPROPERTY('ServerName')) AS SqlInstance,       d.name AS DatabaseName, d.state_desc AS DatabaseState,       k.encryption_state AS EncryptionState, k.encryptor_type AS EncryptorType,       CONVERT(varchar(66), k.encryptor_thumbprint, 1) AS ProtectorThumbprintFROM sys.databases AS dLEFT JOIN sys.dm_database_encryption_keys AS k ON k.database_id = d.database_idWHERE d.database_id = DB_ID(); SELECT RowId, Marker FROM dbo.TdeRecoveryTrialRows WHERE RowId = 1;
Review before runningT-SQLUTF-814 lines
  1. Record the source protection state. Wait for encryption to complete before taking the lab backup. Save which protector and external key version were needed for that specific backup.
  2. Prepare the independent SQL Server target per vendor instructions and restore the test backup. Use the read-only checks to confirm the online database, expected encryption state and marker row.
  3. Repeat with a backup from before a controlled test key change if key rotation is in scope. Record whether recovery needs older key access and how the approved recovery identity obtains it.

Conclusion

Shortlist the providers that support the SQL Server releases and hosts you run. Give each one the same recovery test. A separate instance should restore the backup and read a known row, including after a planned key change. Record the key identifier, registration steps and restore time in the runbook before the provider protects a production database.

Frequently asked questions

What does an EKM provider do for SQL Server TDE?

It lets SQL Server use an external asymmetric key to protect the database encryption key. SQL Server still encrypts and decrypts the database pages. The provider handles access to the external key and the supported key operations.

Can I restore a SQL Server TDE backup on another instance?

Yes, if the target has the required protector. For an EKM-protected database, configure the compatible provider and credential on the target and make the original external key available. Test with a separate restore instance.

How long should I retain an old EKM key after rotation?

Keep every protector needed for a backup you still intend to restore. Test at least one backup from before the change and one after it. Apply the retention decision to the original key and any required versions or access policies.

Does EKM support follow SQL Server TDE support?

Check both capabilities in the Microsoft matrix for your SQL Server release. Then check the vendor’s own matrix for provider, operating system and connector support. A supported SQL edition can still have additional publisher requirements.

What is the difference between SQL Server EKM and a managed database key setting?

SQL Server instance-level EKM registers a cryptographic provider. Services such as Azure SQL Database expose a separate managed TDE protector configuration. Use the documentation for the deployment you run.

Does an encrypted SQL Server database prove that a backup will restore?

Use a restore to verify the backup and its protector access together. Prepare a separate SQL Server instance, restore with the intended provider and confirm the recovered data and encryption state.

Can I remove an older external TDE key after rotation?

Check the required protectors for retained backups and replicas first. Preserve keys required for recovery and verify a backup from before rotation while the older key is available.

Related guides

Guide~13 min readUpdated 16 Nov 2026
LinkedInXEmail