Replace product name with include

Author: MikeRayMSFT

docs/big-data-cluster/active-directory-connect.md

@@ -52,7 +52,7 @@ From Azure Data Studio:
 
 ### Connect to controller with AD authentication from Linux/Mac
 
-There are two options for connecting to the controller endpoint using Azure Data CLI and AD authentication. You can use the *--endpoint/-e* parameter:
+There are two options for connecting to the controller endpoint using [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] and AD authentication. You can use the *--endpoint/-e* parameter:
 
 ```bash
 kinit <username>@<domain name>

docs/big-data-cluster/active-directory-deploy.md

@@ -115,7 +115,7 @@ mode](manage-user-access.md).
 
 Below table show the authorization model for application management:
 
-|   Authorized roles   |   Azure Data CLI command   |
+|   Authorized roles   |   [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] command   |
 |----------------------|--------------------|
 |   appOwner           | azdata app create  |
 |   appOwner           | azdata app update  |
@@ -130,7 +130,7 @@ Below table show the authorization model for application management:
   >The value passed through the subdomain setting is not a new AD domain but only a DNS domain used by the BDC cluster internally.
 
   >[!IMPORTANT]
-  >You need to install or upgrade latest version of **Azure Data CLI** as of SQL Server 2019 CU5 release to leverage these new capabilities and deploy multiple big data clusters in the same domain.
+  >You need to install or upgrade latest version of **[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]** as of SQL Server 2019 CU5 release to leverage these new capabilities and deploy multiple big data clusters in the same domain.
 
   See [Concept: deploy [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)] in Active Directory mode](active-directory-deployment-background.md) for more details regarding deploying multiple big data clusters in the same Active Directory domain.
 
@@ -147,7 +147,7 @@ If you have not already initialized the deployment configuration file, you can r
 azdata bdc config init --source kubeadm-prod  --target custom-prod-kubeadm
 ```
 
-To set the above parameters in the `control.json` file, use the following Azure Data CLI commands. The commands replace the config and provide your own values before deployment.
+To set the above parameters in the `control.json` file, use the following [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] commands. The commands replace the config and provide your own values before deployment.
 
 > [!IMPORTANT]
 > In the SQL Server 2019 CU2 release, the structure of the security configuration section in the deployment profile changed sightly and all the Active Directory related settings are in the new `activeDirectory` in the json tree under `security` in the `control.json` file.
@@ -209,15 +209,15 @@ azdata bdc config replace -c custom-prod-kubeadm/control.json -j "$.spec.endpoin
 You can find an example script here for [deploying a SQL Server big data cluster on single node Kubernetes cluster (kubeadm) with AD integration](https://github.com/microsoft/sql-server-samples/tree/master/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu-single-node-vm-ad).
 
 > [!Note]
-> There might be scenarios where you can't accommodate the newly introduced `subdomain` parameter. For example, you must deploy an a pre-CU5 release and you already upgraded **Azure Data CLI**. This is highly unlikely, but if you need to revert to the pre-CU5 behavior, you can set `useSubdomain` parameter to `false` in the active directory section of `control.json`.  Here is the command to do so:
+> There might be scenarios where you can't accommodate the newly introduced `subdomain` parameter. For example, you must deploy an a pre-CU5 release and you already upgraded **[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]**. This is highly unlikely, but if you need to revert to the pre-CU5 behavior, you can set `useSubdomain` parameter to `false` in the active directory section of `control.json`.  Here is the command to do so:
 
 ```bash
 azdata bdc config replace -c custom-prod-kubeadm/control.json -j "$.security.activeDirectory.useSubdomain=false"
 ```
 
 You should now have set all the required parameters for a deployment of BDC with Active Directory integration.
 
-You can now deploy the BDC cluster integrated with Active Directory using the Azure Data CLI command and the kubeadm-prod deployment profile. For full documentation of how to deploy [!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)], please visit the [How to deploy SQL Server Big Data Clusters on Kubernetes](deployment-guidance.md).
+You can now deploy the BDC cluster integrated with Active Directory using the [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] command and the kubeadm-prod deployment profile. For full documentation of how to deploy [!INCLUDE[big-data-clusters](../includes/ssbigdataclusters-nover.md)], please visit the [How to deploy SQL Server Big Data Clusters on Kubernetes](deployment-guidance.md).
 
 ## Verify reverse DNS entry for domain controller
 

docs/big-data-cluster/active-directory-deployment-background.md

@@ -135,7 +135,7 @@ It is not required, but is recommended. Providing separate OUs for separate clus
 
 ### How to revert back to the pre-CU5 behavior?
 
-There might be scenarios where you can't accommodate the newly introduced `subdomain` parameter. For example you must deploy a pre-CU5 release and you already upgraded Azure Data CLI. This is highly unlikely, but if you need to revert to the pre-CU5 behavior you can set `useSubdomain` parameter to `false` in the active directory section of `control.json`.
+There might be scenarios where you can't accommodate the newly introduced `subdomain` parameter. For example you must deploy a pre-CU5 release and you already upgraded [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]. This is highly unlikely, but if you need to revert to the pre-CU5 behavior you can set `useSubdomain` parameter to `false` in the active directory section of `control.json`.
 
 The following example sets `useSubdomain` to `false` for this scenario.
 

docs/big-data-cluster/app-consume.md

@@ -21,7 +21,7 @@ This article describes how to consume an app deployed on a SQL Server big data c
 ## Prerequisites
 
 - [SQL Server big data cluster](deployment-guidance.md)
-- [Azure Data CLI](../azdata/install/deploy-install-azdata.md)
+- [[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]](../azdata/install/deploy-install-azdata.md)
 - An app deployed using either [azdata](app-create.md) or the [App Deploy extension](app-deployment-extension.md)
 
 > [!NOTE]

docs/big-data-cluster/app-create.md

@@ -27,7 +27,7 @@ This article describes how to deploy and manage R and Python script as an applic
 - Support hosting additional application types - SQL Server Integration Services (SSIS) and MLeap.
 - [Visual Studio Code Extension](app-deployment-extension.md) to manage application deployment.
 
-Applications are deployed and managed using Azure Data CLI command-line utility. This article provides examples of how to deploy apps from the command line. To learn how to use this in Visual Studio Code refer to [Visual Studio Code Extension](app-deployment-extension.md).
+Applications are deployed and managed using [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] command-line utility. This article provides examples of how to deploy apps from the command line. To learn how to use this in Visual Studio Code refer to [Visual Studio Code Extension](app-deployment-extension.md).
 
 The following types of apps are supported:
 
@@ -39,7 +39,7 @@ The following types of apps are supported:
 ## Prerequisites
 
 - [SQL Server 2019 big data cluster](deployment-guidance.md)
-- [Azure Data CLI](../azdata/install/deploy-install-azdata.md)
+- [[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]](../azdata/install/deploy-install-azdata.md)
 
 ## Capabilities
 
@@ -109,7 +109,7 @@ spec.yaml
 
 ## Create an app
 
-To create an application, you use Azure Data CLI with the `app create` command. These files reside locally on the machine that you're creating the app from.
+To create an application, you use [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] with the `app create` command. These files reside locally on the machine that you're creating the app from.
 
 Use the following syntax to create a new app in big data cluster:
 

docs/big-data-cluster/app-monitor.md

@@ -21,7 +21,7 @@ This article describes how to monitor an application inside a SQL Server Big Dat
 ## Prerequisites
 
 - [SQL Server 2019 big data cluster](deployment-guidance.md)
-- [Azure Data CLI](../azdata/install/deploy-install-azdata.md)
+- [[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]](../azdata/install/deploy-install-azdata.md)
 
 ## Capabilities
 

docs/big-data-cluster/app-run.md

@@ -19,7 +19,7 @@ This article describes how to run an application inside a SQL Server Big Data Cl
 ## Prerequisites
 
 - [SQL Server 2019 big data cluster](deployment-guidance.md)
-- [Azure Data CLI](../azdata/install/deploy-install-azdata.md)
+- [[!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]](../azdata/install/deploy-install-azdata.md)
 
 ## Capabilities
 

docs/big-data-cluster/concept-application-deployment.md

@@ -73,7 +73,7 @@ allowedCapabilities:
 ## How to work with Application Deployment
 
 The two main interfaces for application deployment are: 
-- [Command line interface Azure Data CLI](app-create.md)
+- [Command line interface [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]](app-create.md)
 - [Visual Studio Code and Azure Data Studio extension](app-deployment-extension.md)
 
 It is also possible for an application to be executed using a RESTful web service. For more information, see [Consume applications on big data clusters](app-consume.md).

docs/big-data-cluster/concept-security.md

@@ -32,7 +32,7 @@ The external cluster endpoints support AD authentication. Use your AD identity t
 
 There are five entry points to the big data cluster
 
-* Master Instance - TDS endpoint for accessing SQL Server Master Instance in the cluster, using database tools and applications like SSMS or Azure Data Studio. When using HDFS or SQL Server commands from Azure Data CLI (`azdata`), the tool will connect to the other endpoints, depending on the operation.
+* Master Instance - TDS endpoint for accessing SQL Server Master Instance in the cluster, using database tools and applications like SSMS or Azure Data Studio. When using HDFS or SQL Server commands from [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)], the tool will connect to the other endpoints, depending on the operation.
 
 * Gateway to access HDFS files, Spark (Knox) - HTTPS endpoint for accessing services like webHDFS and Spark.
 

docs/big-data-cluster/concept-storage-pool.md

@@ -52,7 +52,7 @@ The main methods for accessing the data in the storage pool are:
 You can also interact with HDFS using:
 
 - Azure Data Studio.
-- Azure Data CLI.
+- [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)].
 - kubectl to issue commands to the Hadoop container.
 - HDFS http gateway.