Merge pull request #104129 from danimir/patch-1

Important updates to new Azure defaults

Author: PRMerger9

articles/sql-database/sql-database-automatic-tuning.md

@@ -73,6 +73,13 @@ In case you are applying tuning recommendations through T-SQL, the automatic per
 
 Automatic tuning options can be independently enabled or disabled per database, or they can be configured on SQL Database servers and applied on every database that inherits settings from the server. SQL Database servers can inherit Azure defaults for Automatic tuning settings. Azure defaults at this time are set to FORCE_LAST_GOOD_PLAN is enabled, CREATE_INDEX is enabled, and DROP_INDEX is disabled.
 
+> [!IMPORTANT]
+> As of March, 2020 changes to Azure defaults for automatic tuning will take effect as follows:
+> - New Azure defaults will be FORCE_LAST_GOOD_PLAN = enabled, CREATE_INDEX = disabled, and DROP_INDEX = disabled.
+> - Existing servers with no automatic tuning preferences configured will be automatically configured with the new Azure defaults. This applies to all customers currently having automatic tuning in an undefined state.
+> - New servers created will automatically be configured with the new Azure defaults (unlike earlier when automatic tuning configuration was in an undefined state upon new server creation).
+>
+
 Configuring Automatic tuning options on a server and inheriting settings for databases belonging to the parent server is a recommended method for configuring automatic tuning as it simplifies management of automatic tuning options for a large number of databases.
 
 ## Next steps