Merge pull request #107325 from oslake/patch-30

Update sql-database-serverless.md

Author: PRMerger20

articles/sql-database/sql-database-serverless.md

@@ -10,7 +10,7 @@ ms.topic: conceptual
 author: oslake
 ms.author: moslake
 ms.reviewer: sstein, carlrab
-ms.date: 12/03/2019
+ms.date: 3/11/2020
 ---
 # Azure SQL Database serverless
 
@@ -143,6 +143,10 @@ If a serverless database is paused, then the first login will resume the databas
 
 The latency to autoresume and autopause a serverless database is generally order of 1 minute to autoresume and 1-10 minutes to autopause.
 
+### Customer managed transparent data encryption (BYOK)
+
+If using [customer managed transparent data encryption](transparent-data-encryption-byok-azure-sql.md) (BYOK) and the serverless database is auto-paused when key deletion or revocation occurs, then the database remains in the auto-paused state.  In this case, when resuming is next attempted, the database remains paused until its status transitions to inaccessible after approximately 10 minutes or less.  Once the database becomes inaccessible, the recovery process is the same as for provisioned compute databases.  If the serverless database is online when key deletion or revocation occurs, then the database also becomes inaccessible after approximately 10 minutes or less in the same way as with provisioned compute databases.
+
 ## Onboarding into serverless compute tier
 
 Creating a new database or moving an existing database into a serverless compute tier follows the same pattern as creating a new database in provisioned compute tier and involves the following two steps.