Transparent data encryption for SQL Database and Data Warehouse

Transparent data encryption (TDE) helps protect Azure SQL Database and Azure Data Warehouse against the threat of malicious activity. It performs real-time encryption and decryption of the database, associated backups, and transaction log files at rest without requiring changes to the application. By default, TDE is enabled for all newly deployed Azure SQL Databases. TDE cannot be used to encrypt the logical master database in SQL Database. The master database contains objects that are needed to perform the TDE operations on the user databases.

TDE will need to be manually enabled for older databases or Azure SQL Data Warehouse.

Transparent data encryption encrypts the storage of an entire database by using a symmetric key called the database encryption key. This database encryption key is protected by the transparent data encryption protector. The protector is either a service-managed certificate (service-managed transparent data encryption) or an asymmetric key stored in Azure Key Vault (Bring Your Own Key). You set the transparent data encryption protector at the server level.

On database startup, the encrypted database encryption key is decrypted and then used for decryption and re-encryption of the database files in the SQL Server Database Engine process. Transparent data encryption performs real-time I/O encryption and decryption of the data at the page level. Each page is decrypted when it's read into memory and then encrypted before being written to disk. For a general description of transparent data encryption, see Transparent data encryption.

SQL Server running on an Azure virtual machine also can use an asymmetric key from Key Vault. The configuration steps are different from using an asymmetric key in SQL Database. For more information, see Extensible key management by using Azure Key Vault (SQL Server).

Service-managed transparent data encryption

In Azure, the default setting for transparent data encryption is that the database encryption key is protected by a built-in server certificate. The built-in server certificate is unique for each server. If a database is in a geo-replication relationship, both the primary and geo-secondary database are protected by the primary database's parent server key. If two databases are connected to the same server, they share the same built-in certificate. Microsoft automatically rotates these certificates at least every 90 days.

Microsoft also seamlessly moves and manages the keys as needed for geo-replication and restores.

Important

All newly created SQL databases are encrypted by default by using service-managed transparent data encryption. Existing databases before May 2017 and databases created through restore, geo-replication, and database copy aren't encrypted by default.

Bring Your Own Key

With Bring Your Own Key support, you can take control over your transparent data encryption keys and control who can access them and when. Key Vault, which is the Azure cloud-based external key management system, is the first key management service that transparent data encryption has integrated with Bring Your Own Key support. With Bring Your Own Key support, the database encryption key is protected by an asymmetric key stored in Key Vault. The asymmetric key never leaves Key Vault. After the server has permissions to a key vault, the server sends basic key operation requests to it through Key Vault. You set the asymmetric key at the server level, and all databases under that server inherit it.

With Bring Your Own Key support, you now can control key management tasks such as key rotations and key vault permissions. You also can delete keys and enable auditing/reporting on all encryption keys. Key Vault provides central key management and uses tightly monitored hardware security modules. Key Vault promotes separation of management of keys and data to help meet regulatory compliance. To learn more about Key Vault, see the Key Vault documentation page.

To learn more about transparent data encryption with Bring Your Own Key support for SQL Database and Data Warehouse, see Transparent data encryption with Bring Your Own Key support.

To start using transparent data encryption with Bring Your Own Key support, see the how-to guide Turn on transparent data encryption by using your own key from Key Vault by using PowerShell.

Move a transparent data encryption-protected database

You don't need to decrypt databases for operations within Azure. The transparent data encryption settings on the source database or primary database are transparently inherited on the target. Operations that are included involve:

  • Geo-restore.
  • Self-service point-in-time restore.
  • Restoration of a deleted database.
  • Active geo-replication.
  • Creation of a database copy.

When you export a transparent data encryption-protected database, the exported content of the database isn't encrypted. This exported content is stored in unencrypted BACPAC files. Be sure to protect the BACPAC files appropriately and enable transparent data encryption after import of the new database is finished.

For example, if the BACPAC file is exported from an on-premises SQL Server instance, the imported content of the new database isn't automatically encrypted. Likewise, if the BACPAC file is exported to an on-premises SQL Server instance, the new database also isn't automatically encrypted.

The one exception is when you export to and from a SQL database. Transparent data encryption is enabled in the new database, but the BACPAC file itself still isn't encrypted.

Manage transparent data encryption in the Azure portal

To configure transparent data encryption through the Azure portal, you must be connected as the Azure Owner, Contributor, or SQL Security Manager.

You set transparent data encryption on the database level. To enable transparent data encryption on a database, go to the Azure portal and sign in with your Azure Administrator or Contributor account. Find the transparent data encryption settings under your user database. By default, service-managed transparent data encryption is used. A transparent data encryption certificate is automatically generated for the server that contains the database.

Service-managed transparent data encryption

You set the transparent data encryption master key, also known as the transparent data encryption protector, on the server level. To use transparent data encryption with Bring Your Own Key support and protect your databases with a key from Key Vault, see the transparent data encryption settings under your server.

Transparent data encryption with Bring Your Own Key support

Manage transparent data encryption by using PowerShell

To configure transparent data encryption through PowerShell, you must be connected as the Azure Owner, Contributor, or SQL Security Manager.

Cmdlet Description
Set-AzureRmSqlDatabaseTransparentDataEncryption Enables or disables transparent data encryption for a database
Get-Azure-Rm-Sql-Database-Transparent-Data-Encryption Gets the transparent data encryption state for a database
Get-Azure-Rm-Sql-Database-Transparent-Data-Encryption-Activity Checks the encryption progress for a database
Add-AzureRmSqlServerKeyVaultKey Adds a Key Vault key to a SQL Server instance
Get-AzureRmSqlServerKeyVaultKey Gets the Key Vault keys for a SQL server instance
Set-AzureRmSqlServerTransparentDataEncryptionProtector Sets the transparent data encryption protector for a SQL Server instance
Get-AzureRmSqlServerTransparentDataEncryptionProtector Gets the transparent data encryption protector
Remove-AzureRmSqlServerKeyVaultKey Removes a Key Vault key from a SQL Server instance

Manage transparent data encryption by using Transact-SQL

Connect to the database by using a login that is an administrator or member of the dbmanager role in the master database.

Command Description
ALTER DATABASE (Azure SQL Database) SET ENCRYPTION ON/OFF encrypts or decrypts a database
sys.dm_database_encryption_keys Returns information about the encryption state of a database and its associated database encryption keys
sys.dm_pdw_nodes_database_encryption_keys Returns information about the encryption state of each data warehouse node and its associated database encryption keys

You can't switch the transparent data encryption protector to a key from Key Vault by using Transact-SQL. Use PowerShell or the Azure portal.

Manage transparent data encryption by using the REST API

To configure transparent data encryption through the REST API, you must be connected as the Azure Owner, Contributor, or SQL Security Manager.

Command Description
Create Or Update Server Adds an Azure Active Directory identity to a SQL Server instance (used to grant access to Key Vault)
Create Or Update Server Key Adds a Key Vault key to a SQL Server instance
Delete Server Key Removes a Key Vault key from a SQL Server instance
Get Server Keys Gets a specific Key Vault key from a SQL Server instance
List Server Keys By Server Gets the Key Vault keys for a SQL Server instance
Create Or Update Encryption Protector Sets the transparent data encryption protector for a SQL Server instance
Get Encryption Protector Gets the transparent data encryption protector for a SQL Server instance
List Encryption Protectors By Server Gets the transparent data encryption protectors for a SQL Server instance
Create Or Update Transparent Data Encryption Configuration Enables or disables transparent data encryption for a database
Get Transparent Data Encryption Configuration Gets the transparent data encryption configuration for a database
List Transparent Data Encryption Configuration Results Gets the encryption result for a database

Next steps