Skip to content

Commit 3e25dd6

Browse files
committed
TDE on by default for new MI databases
1 parent 6f53fa2 commit 3e25dd6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
author: aliceku
1111
ms.author: aliceku
1212
ms.reviewer: vanto
13-
ms.date: 04/19/2019
13+
ms.date: 08/12/2019
1414
---
1515
# Transparent data encryption for SQL Database and Data Warehouse
1616

@@ -31,7 +31,7 @@ In Azure, the default setting for transparent data encryption is that the databa
3131
Microsoft also seamlessly moves and manages the keys as needed for geo-replication and restores.
3232

3333
> [!IMPORTANT]
34-
> All newly created SQL databases are encrypted by default by using service-managed transparent data encryption. Azure SQL Managed Instance databases, existing SQL databases created before May 2017 and SQL databases created through restore, geo-replication, and database copy are not encrypted by default.
34+
> All newly created SQL databases and Managed Instance databases are encrypted by default by using service-managed transparent data encryption. Existing SQL databases created before May 2017 and SQL databases created through restore, geo-replication, and database copy are not encrypted by default. Existing Managed Instance databases created before February 2019 are not encrypted by default. Managed Instance databases created through restore inherit encryption status from the source.
3535
3636
## Customer-managed transparent data encryption - Bring Your Own Key
3737

0 commit comments

Comments
 (0)