Merge pull request #78807 from oslake/patch-16

Update sql-database-serverless.md

Author: PRMerger17

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

@@ -11,7 +11,7 @@ author: oslake
 ms.author: moslake
 ms.reviewer: sstein, carlrab
 manager: craigg
-ms.date: 06/04/2019
+ms.date: 06/05/2019
 ---
 # SQL Database serverless (preview)
 
@@ -103,6 +103,14 @@ Autopausing is triggered if all of the following conditions are true for the dur
 
 An option is provided to disable autopausing if desired.
 
+The following features do not support autopausing.  That is, if any of the following features are used, then the database remains online regardless of the duration of database inactivity:
+
+- Geo-replication (active geo-replication and auto-failover groups).
+- Long-term backup retention (LTR).
+- The sync database used in SQL data sync.
+
+Autopausing is temporarily prevented during the deployment of some service updates which require the database be online to apply the update.  In such cases, autopausing becomes allowed again once the service update completes.
+
 ### Autoresume
 
 Autoresuming is triggered if any of the following conditions are true at any time:
@@ -122,7 +130,7 @@ Autoresuming is triggered if any of the following conditions are true at any tim
 |Modifying certain database metadata|Adding new database tags.<br>Changing max vCores, min vCores, or autopause delay.|
 |SQL Server Management Studio (SSMS)|Using SSMS version 18 and opening a new query window for any database in the server will resume any auto-paused database in the same server. This behavior does not occur if using SSMS version 17.9.1 with IntelliSense turned-off.|
 
-Autoresuming is also triggered during service updates.
+Autoresuming is also triggered during the deployment of some service updates which require the database be online to apply the update.
 
 ### Connectivity
 
@@ -132,14 +140,6 @@ 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.
 
-### Feature support
-
-The following features do not support autopausing and autoresuming. That is, if any of the following features are used, then the database remains online regardless of duration of database inactivity:
-
-- Geo-replication (active geo-replication and auto failover groups).
-- Long-term backup retention (LTR).
-- The sync database used in SQL data sync.
-
 ## 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: