Merge pull request #115789 from MashaMSFT/includes2

added more includes

Author: tfosmark

articles/azure-sql/database/aad-authentication-overview.md

@@ -12,7 +12,8 @@ ms.author: mireks
 ms.reviewer: vanto, carlrab
 ms.date: 04/23/2020
 ---
-# Use Azure Active Directory Authentication for authentication with Azure SQL
+# Use Azure Active Directory Authentication
+[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa.md)]
 
 Azure Active Directory authentication is a mechanism of connecting to [Azure SQL Database](sql-database-paas-overview.md), [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) by using identities in Azure Active Directory (Azure AD).
 

articles/azure-sql/database/active-geo-replication-configure-portal.md

@@ -15,6 +15,7 @@ ms.date: 02/13/2019
 # Tutorial: Configure active geo-replication & fail over in portal (Azure SQL Database)
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
+
 This article shows you how to configure [active geo-replication for Azure SQL Database](active-geo-replication-overview.md#active-geo-replication-terminology-and-capabilities) using the [Azure portal](https://portal.azure.com) and to initiate failover.
 
 For best practices using auto-failover groups, see [Best practices for Azure SQL Database](auto-failover-group-overview.md#best-practices-for-sql-database) and [Best practices for Azure SQL Managed Instance](auto-failover-group-overview.md#best-practices-for-sql-managed-instance). 

articles/azure-sql/database/advanced-data-security.md

@@ -14,6 +14,7 @@ ms.reviewer: vanto
 ms.date: 04/23/2020
 ---
 # Advanced data security
+[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa.md)]
 
 
 Advanced data security (ADS) is a unified package for advanced SQL security capabilities. ADS is available for for Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse. It includes functionality for discovering and classifying sensitive data, surfacing and mitigating potential database vulnerabilities, and detecting anomalous activities that could indicate a threat to your database. It provides a single go-to location for enabling and managing these capabilities.

articles/azure-sql/database/alerts-insights-configure-portal.md

@@ -13,6 +13,7 @@ ms.reviewer: jrasnik, carlrab
 ms.date: 05/04/2020
 ---
 # Create alerts for Azure SQL Database and Azure Synapse using Azure portal
+[!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
 
 
 ## Overview

articles/azure-sql/database/arm-templates-content-guide.md

@@ -14,8 +14,8 @@ ms.reviewer: sstein
 ms.date: 02/04/2019
 ---
 
-# Azure Resource Manager templates for Azure SQL Database & Azure SQL Managed Instance 
-
+# Azure Resource Manager templates for Azure SQL Database & SQL Managed Instance
+[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 Azure Resource Manager templates enable you to define your infrastructure as code and deploy your solutions to Azure cloud for your Azure SQL Database and Azure SQL Managed Instance.
 

articles/azure-sql/database/audit-log-format.md

@@ -12,6 +12,8 @@ ms.custom: sqldbrb=1
 ms.date: 04/28/2020
 ---
 # SQL Database Audit Log Format
+[!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
+
 
 [Azure SQL Database auditing](auditing-overview.md) tracks database events and writes them to an audit log in your Azure storage account, or sends them to Event Hub or Log Analytics for downstream processing and analysis.
 

articles/azure-sql/database/audit-write-storage-account-behind-vnet-firewall.md

@@ -12,6 +12,8 @@ ms.date: 03/19/2020
 ms.custom: azure-synapse
 ---
 # Write audit to a storage account behind VNet and firewall
+[!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
+
 
 Auditing for [Azure SQL Database](sql-database-paas-overview.md) and [Azure Synapse Analytics](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) supports writing database events to an [Azure Storage account](../../storage/common/storage-account-overview.md) behind a virtual network and firewall.
 

articles/azure-sql/database/auditing-overview.md

@@ -12,6 +12,8 @@ ms.date: 04/28/2020
 ms.custom: azure-synapse, sqldbrb=1
 ---
 # Azure SQL Auditing
+[!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
+
 
 Auditing for [Azure SQL Database](sql-database-paas-overview.md) and [Azure Synapse Analytics](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs.
 

articles/azure-sql/database/auto-failover-group-configure.md

@@ -14,7 +14,7 @@ ms.reviewer: sstein, carlrab
 ms.date: 08/14/2019
 ---
 # Configure a failover group for Azure SQL Database
-[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
+[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 This topic teaches you how to configure an [auto-failover group](auto-failover-group-overview.md) for Azure SQL Database and Azure SQL Managed Instance.
 

articles/azure-sql/database/auto-failover-group-overview.md

@@ -15,6 +15,7 @@ ms.date: 2/10/2020
 ---
 
 # Use auto-failover groups to enable transparent and coordinated failover of multiple databases
+[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 Auto-failover groups allow you to manage replication and failover of a group of databases on a server or all databases in a managed instance to another region. It is a declarative abstraction on top of the existing [active geo-replication](active-geo-replication-overview.md) feature, designed to simplify deployment and management of geo-replicated databases at scale. You can initiate failover manually or you can delegate it to the Azure service based on a user-defined policy. The latter option allows you to automatically recover multiple related databases in a secondary region after a catastrophic failure or other unplanned event that results in full or partial loss of the SQL Database or SQL Managed Instance service availability in the primary region. A failover group can include one or multiple databases, typically used by the same application. Additionally, you can use the readable secondary databases to offload read-only query workloads. Because auto-failover groups involve multiple databases, these databases must be configured on the primary server. Auto-failover groups support replication of all databases in the group to only one secondary server or instance in a different region.