20211005 bdc cu13 rotate changes, product name changes

Author: WilliamDAssafMSFT

docs/azdata/reference/reference-azdata-bdc-rotate.md

@@ -0,0 +1,46 @@
+---
+title: azdata bdc rotate reference
+titleSuffix: SQL Server Big Data Clusters
+description: Reference article for azdata bdc rotate commands.
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: cloudmelon
+ms.date: 10/05/2021
+ms.topic: reference
+ms.prod: sql
+ms.technology: big-data-cluster
+---
+
+# azdata bdc rotate
+
+Applies to [!INCLUDE [azure-data-cli-azdata](../../includes/azure-data-cli-azdata.md)]
+
+This command rotates the passwords of autogenerated AD accounts in a big data cluster. For more information, see [AD password rotation overview](..\..\big-data-cluster\active-directory-password-rotation.md). Autorotation of passwords for autogenerated AD objects was introduced with SQL Server Big Data Clusters CU13. 
+
+> [!NOTE]
+> The `azdata bdc rotate` command rotates passwords for autogenerated AD objects only. `azdata bdc rotate` does not rotate the password for the AD for big data cluster domain service account (DSA) created manually while performing a big data cluster AD-integrated deployment. For more information, see [big data cluster AD integrated deployment](..\..\big-data-cluster\active-directory-prerequisites.md).
+
+The following article provides reference for the **sql** commands in the **azdata** tool. For more information about other **azdata** commands, see [azdata reference](reference-azdata.md)
+
+## azdata bdc rotate 
+
+```bash
+azdata bdc rotate [--name -n] 
+```
+
+### Mandatory parameters
+
+#### `--name -n` 
+The name of your big data cluster.
+
+### Examples
+
+```bash
+   azdata bdc rotate -n mybdcclustername
+```
+
+## Next steps
+
+For more information about other **azdata** commands, see [azdata reference](reference-azdata.md). 
+
+For more information about how to install the **azdata** tool, see [Install azdata](..\install\deploy-install-azdata.md).

docs/azdata/reference/reference-azdata-bdc.md

@@ -2,9 +2,9 @@
 title: azdata bdc reference
 titleSuffix: SQL Server Big Data Clusters
 description: Reference article for azdata bdc commands.
-author: MikeRayMSFT
-ms.author: mikeray
-ms.reviewer: seanw
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: cloudmelon, seanw, danibunny
 ms.date: 10/05/2021
 ms.topic: reference
 ms.prod: sql
@@ -27,16 +27,18 @@ The following article provides reference for the **sql** commands in the **azdat
 [azdata bdc config](reference-azdata-bdc-config.md) | Configuration commands.
 [azdata bdc endpoint](reference-azdata-bdc-endpoint.md) | Endpoint commands.
 [azdata bdc debug](reference-azdata-bdc-debug.md) | Debug commands.
-[azdata bdc status](reference-azdata-bdc-status.md) | BDC status commands.
+[azdata bdc status](reference-azdata-bdc-status.md) | Big Data Clusters status commands.
 [azdata bdc control](reference-azdata-bdc-control.md) | Control service commands.
 [azdata bdc sql](reference-azdata-bdc-sql.md) | Sql service commands.
 [azdata bdc hdfs](reference-azdata-bdc-hdfs.md) | Hdfs service commands.
 [azdata bdc spark](reference-azdata-bdc-spark.md) | Spark service commands.
 [azdata bdc gateway](reference-azdata-bdc-gateway.md) | Gateway service commands.
 [azdata bdc app](reference-azdata-bdc-app.md) | App service commands.
 [azdata bdc hdfs](reference-azdata-bdc-hdfs.md) | The HDFS module provides commands to access an HDFS file system.
-[azdata bdc settings](reference-azdata-bdc-settings.md) | BDC settings commands.
+[azdata bdc settings](reference-azdata-bdc-settings.md) | Big Data Clusters settings commands.
 [azdata bdc spark](reference-azdata-bdc-spark.md) | The Spark commands allow the user to interact with the Spark system by creating and managing sessions, statements, and batches.
+[azdata bdc rotate](reference-azdata-bdc-rotate.md) | This command rotates the passwords of autogenerated AD accounts in a big data cluster. For more information, see [AD password rotation overview](..\..\big-data-cluster\active-directory-password-rotation.md).
+
 ## azdata bdc create
 Create a SQL Server Big Data Cluster - Kubernetes configuration is required on your system along with the following environment variables ['AZDATA_USERNAME', 'AZDATA_PASSWORD'].
 ```bash
@@ -50,19 +52,19 @@ azdata bdc create [--name -n]
 [--force -f]
 ```
 ### Examples
-Guided BDC deployment experience - you will receive prompts for needed values.
+Guided SQL Server Big Data Clusters deployment experience - you will receive prompts for needed values.
 ```bash
 azdata bdc create
 ```
-BDC deployment with arguments and custom config profile that was initialized via `azdata bdc config init`.
+Big Data Clusters deployment with arguments and custom config profile that was initialized via `azdata bdc config init`.
 ```bash
 azdata bdc create --accept-eula yes --config-profile ./path/to/config/profile
 ```
-BDC deployment with custom cluster name specified and a default config profile aks-dev-test.
+Big Data Clusters deployment with custom cluster name specified and a default config profile aks-dev-test.
 ```bash
 azdata bdc create --name <cluster_name> --accept-eula yes --config-profile aks-dev-test
 ```
-BDC deployment with arguments - no prompts will be given as the --force flag is used.
+Big Data Clusters deployment with arguments - no prompts will be given as the --force flag is used.
 ```bash
 azdata bdc create --accept-eula yes --config-profile aks-dev-test --force
 ```
@@ -95,7 +97,7 @@ azdata bdc delete --name -n
                   [--force -f]
 ```
 ### Examples
-BDC delete.
+Big Data Clusters delete.
 ```bash
 azdata bdc delete --name <cluster_name>
 ```
@@ -133,15 +135,15 @@ azdata bdc upgrade --name -n
 [--force -f]
 ```
 ### Examples
-BDC upgrade to a new image tag "cu2" from the same repository.
+Big Data Clusters upgrade to a new image tag "cu2" from the same repository.
 ```bash
 azdata bdc upgrade -t cu2
 ```
-BDC upgrade to a new images with tag "cu2" from a new repository "foo/bar/baz".
+Big Data Clusters upgrade to a new images with tag "cu2" from a new repository "foo/bar/baz".
 ```bash
 azdata bdc upgrade -t cu2 -r foo/bar/baz
 ```
-BDC upgrade to a new images with tag "cu2" from the same repository.The upgrade will wait 30 minutes for the controller to upgrade and 30 minutes for the controller db to upgrade. It will then wait for the controller and controller db to run for three minutes without crashing upgrading the rest of the cluster. Each subsequent phase of the upgrade will have forty minutes to complete.
+Big Data Clusters upgrade to a new images with tag "cu2" from the same repository.The upgrade will wait 30 minutes for the controller to upgrade and 30 minutes for the controller db to upgrade. It will then wait for the controller and controller db to run for three minutes without crashing upgrading the rest of the cluster. Each subsequent phase of the upgrade will have forty minutes to complete.
 ```bash
 azdata bdc upgrade -t cu2 --controller-timeout=30 --component-timeout=40 --stability-threshold=3
 ```

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

@@ -126,12 +126,12 @@ mode](manage-user-access.md).
 }
 ```
 
-- `security.activeDirectory.enableAES Optional parameter` **Optional parameter**: Boolean value indicating whether AES 128 and AES 256 should be enabled on the automatically generated AD accounts. Default value is false. When this parameter is set to true, the following flags ‘This account supports Kerberos AES 128 bit encryption’ and ‘This account supports Kerberos AES 256 bit encryption’ will be checked on the auto-generated AD objects during BDC deployment. 
+- `security.activeDirectory.enableAES Optional parameter` **Optional parameter**: Boolean value indicating whether AES 128 and AES 256 should be enabled on the automatically generated AD accounts. Default value is false. When this parameter is set to true, the following flags 'This account supports Kerberos AES 128 bit encryption' and 'This account supports Kerberos AES 256 bit encryption' will be checked on the auto-generated AD objects during big data cluster deployment. 
 
 > [!NOTE]
-> This feature is only available starting from SQL Server BDC CU13 release, please make sure your upgraded to at least CU13. If the big data cluster is a version prior to SQL BDC CU13, the following steps are required:
-> 1. Run the `azdata bdc rotate -n <your-cluster-name>` command, this command will rotate the keytabs in the cluster which is necessary to ensure that the AES entries in keytabs are correct. Besides that, the same command will also rotate the passwords of the AD objects that were auto-generated during the initial deployment in the OU that you specified.
-> 2. Set the the following flags ‘This account supports Kerberos AES 128 bit encryption’ and ‘This account supports Kerberos AES 256 bit encryption’ on each of auto-generated AD objects in the OU that you provided during the initial BDC deployment. This can be achieved by executing the following PowerShell script  `Get-ADUser -Filter * -SearchBase ‘<OU Path>’ | Set-ADUser -replace @{ ‘msDS-SupportedEncryptionTypes’ = ‘24’ }` on your domain controller which sets the AES fields on each account in the OU given in `<OU Path>` parameter.
+> This feature is only available starting from SQL Server Big Data Clusters CU13 release, please make sure your upgraded to at least CU13. If the big data cluster is a version prior to CU13, the following steps are required:
+> 1. Run the `azdata bdc rotate -n <your-cluster-name>` command, this command will rotate the keytabs in the cluster which is necessary to ensure that the AES entries in keytabs are correct. For more information, see [azdata bdc](/sql/azdata/reference/reference-azdata-bdc). Additionally, `azdata bdc rotate` will rotate the passwords of the AD objects that were auto-generated during the initial deployment in the specified OU.
+> 2. Set the the following flags 'This account supports Kerberos AES 128 bit encryption' and 'This account supports Kerberos AES 256 bit encryption' on each of auto-generated AD objects in the OU that you provided during the initial big data cluster deployment. This can be achieved by executing the following PowerShell script  `Get-ADUser -Filter * -SearchBase '<OU Path>' | Set-ADUser -replace @{ 'msDS-SupportedEncryptionTypes' = '24' }` on your domain controller which sets the AES fields on each account in the OU given in `<OU Path>` parameter.
 
   >[!IMPORTANT]
   >Create the groups provided for the settings below in AD before deployment begins. If the scope for any of these AD groups is domain local deployment fails.