Add interoperability include

Author: MikeRayMSFT

docs/big-data-cluster/deployment-high-availability.md

@@ -90,6 +90,8 @@ The following steps walk through an example on how to start from `aks-dev-test-h
 
 Depending on the type of workload you want to run against SQL Server master, you can connect either to the primary for read-write workloads or to the databases in the secondary replicas for read-only type of workloads. Here is an outline for each type of connection:
 
+[!INCLUDE [big-data-clusters-master-instance-ha-endpoint-requirement](../includes/big-data-clusters-master-instance-ha-endpoint-requirement.md)]
+
 ### Connect to databases on the primary replica
 
 For connections to the primary replica, use `sql-server-master` endpoint. This endpoint is also the listener for the AG. When using this endpoint, all connections are in the context of databases within the availability group. For example, a default connection using this endpoint will result in connecting to the `master` database within the availability group, not the SQL Server instance `master` database. Run this command to find the endpoint:

docs/includes/big-data-clusters-master-instance-ha-endpoint-requirement.md

@@ -0,0 +1,3 @@
+Certain operations, including configuring server (instance level) settings, or manually adding a database to an availability group, require a connection to the SQL Server Instance. Operations like `sp_configure`, `RESTORE DATABASE`, or any DDL command in a database belonging to an availability group require a connection to the SQL Server instance. By default, a big data cluster does not include an endpoint that enables a connection to the instance. You must expose this endpoint manually.
+
+For instructions, see [Connect to databases on the primary replica](../big-data-cluster/deployment-high-availability.md#connect-to-databases-on-the-primary-replica).

docs/relational-databases/system-stored-procedures/sp-configure-transact-sql.md

@@ -83,6 +83,10 @@ RECONFIGURE
 ## Remarks  
  Use **sp_configure** to display or change server-level settings. To change database-level settings, use ALTER DATABASE. To change settings that affect only the current user session, use the SET statement.  
 
+### [!INCLUDE [ssbigdataclusters-ss-nover](../../includes/ssbigdataclusters-ss-nover.md)]
+
+[!INCLUDE [big-data-clusters-master-instance-ha-endpoint-requirement](../../includes/big-data-clusters-master-instance-ha-endpoint-requirement.md)]
+
 ## Updating the Running Configuration Value  
  When you specify a new *value* for an *option*, the result set shows this value in the **config_value** column. This value initially differs from the value in the **run_value** column, which shows the currently running configuration value. To update the running configuration value in the **run_value** column, the system administrator must run either RECONFIGURE or RECONFIGURE WITH OVERRIDE.  
 

docs/t-sql/statements/restore-statements-transact-sql.md

@@ -373,6 +373,10 @@ The RESTORE statement also can be used to perform restores to alternate location
 > [!NOTE]
 > Full-text catalogs imported from [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] are still treated as database files. For these, the [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] procedure for backing up full-text catalogs remains applicable, except that pausing and resuming during the backup operation are no longer necessary. For more information, see [Backing Up and Restoring Full-Text Catalogs](https://go.microsoft.com/fwlink/?LinkId=107381).
 
+### [!INCLUDE [ssbigdataclusters-ss-nover](../../includes/ssbigdataclusters-ss-nover.md)]
+
+[!INCLUDE [big-data-clusters-master-instance-ha-endpoint-requirement](../../includes/big-data-clusters-master-instance-ha-endpoint-requirement.md)]
+
 ## Metadata
 
 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] includes backup and restore history tables that track the backup and restore activity for each server instance. When a restore is performed, the backup history tables are also modified. For information on these tables, see [Backup History and Header Information](../../relational-databases/backup-restore/backup-history-and-header-information-sql-server.md).