Merge pull request #21127 from TimShererWithAquent/us1907184c

Validation Code tag cleanup sql

Author: PRMerger4

docs/big-data-cluster/active-directory-deployment-aks-tutorial.md

@@ -39,7 +39,7 @@ Before deploying a SQL Server big data cluster, you need to:
 
 1. Create the AKS subnet
 
-   ```console
+   ```azurecli
    SUBNET_ID=$(az network vnet subnet show \
     --resource-group $RESOURCE_GROUP \
     --vnet-name $VNet_NAME \

docs/big-data-cluster/cluster-troubleshooting-commands.md

@@ -201,7 +201,7 @@ You can launch the Kubernetes dashboard for additional information about the clu
 
 To launch the Kubernetes dashboard run:
 
-```bash
+```azurecli
 az aks browse --resource-group <azure_resource_group> --name <aks_cluster_name>
 ```
 

docs/big-data-cluster/private-deploy.md

@@ -33,7 +33,7 @@ This section shows you deploy a big data cluster in Azure Kubernetes Service (AK
 
 ## Create a private AKS cluster with advanced networking
 
-```bash
+```azurecli
 
 export REGION_NAME=<your Azure region >
 export RESOURCE_GROUP=< your resource group name >
@@ -67,7 +67,7 @@ echo $SUBNET_ID
 
 To be able to get to next step, you need to provision an AKS cluster with Standard Load Balancer with private cluster feature enabled. Your command will look like as follows: 
 
-```bash
+```azurecli
 az aks create \
     --resource-group $RESOURCE_GROUP \
     --name $AKS_NAME \

docs/big-data-cluster/private-restrict-egress-traffic.md

@@ -90,7 +90,7 @@ The following steps provide details.
 
 1. Define a set of environment variables for creating resources.
 
-   ```console
+   ```azurecli
    export FWNAME=bdcaksazfw
    export FWPUBIP=$FWNAME-ip
    export FWIPCONFIG_NAME=$FWNAME-config

docs/connect/odbc/linux-mac/connecting-with-bcp.md

@@ -99,7 +99,7 @@ Specifies the password for the login ID. When used with the -G option without -U
 
 Access tokens can be obtained via various methods. It's important to ensure the access token is correct byte-for-byte, as it will be sent as-is. Below is an example command that obtains an access token. The command uses the Azure CLI and Linux commands and saves it to a file in the proper format. If your system or terminal's default encoding isn't ASCII or UTF-8, you may need to adjust the `iconv` options. Be sure to carefully secure the resulting file and delete it when it's no longer required.
 
-```bash
+```azurecli
 az account get-access-token --resource https://database.windows.net --output tsv | cut -f 1 | tr -d '\n' | iconv -f ascii -t UTF-16LE > /tmp/tokenFile
 ```
 

docs/connect/odbc/linux-mac/connecting-with-sqlcmd.md

@@ -115,7 +115,7 @@ Specify a user password. When used with the -G option without -U, specifies a fi
 
 Access tokens can be obtained via various methods. It's important to ensure the access token is correct byte-for-byte, as it will be sent as-is. Below is an example command that obtains an access token. The command uses the Azure CLI and Linux commands and saves it to a file in the proper format. If your system or terminal's default encoding isn't ASCII or UTF-8, you may need to adjust the `iconv` options. Be sure to carefully secure the resulting file and delete it when it's no longer required.
 
-```bash
+```azurecli
 az account get-access-token --resource https://database.windows.net --output tsv | cut -f 1 | tr -d '\n' | iconv -f ascii -t UTF-16LE > /tmp/tokenFile
 ```
 

docs/linux/tutorial-sql-server-containers-kubernetes-dh2i.md

@@ -106,7 +106,7 @@ $docker push <registry-name>.azurecr.io/sqlimage:latest
 
 This ensures that the custom image has been pushed to Azure Container Registry (ACR) and that you can now integrate your Azure Kubernetes Service (AKS) with ACR by running the following command. For more information, see this [Integrate ACR with an AKS cluster](/azure/aks/cluster-container-registry-integration).
 
-```bash
+```azurecli
 az aks update -n myAKSCluster -g <myResourceGroup> --attach-acr <registry-name>
 ```
 

docs/sql-server/azure-arc/connect.md

@@ -185,21 +185,21 @@ If you disconnected your SQL Server instance by mistake, you can restore its __S
 
 1. If you also uninstalled the SQL Server extension by mistake, reinstall it.
 
-```console
+```azurecli
    az connectedmachine extension create --machine-name "{your machine name}" --location {"azure region"} --name "WindowsAgent.SqlServer" --resource-group "{your resource group name}" --type "WindowsAgent.SqlServer" --publisher "Microsoft.AzureData" --settings '{\"SqlManagement\":{\"IsEnabled\":true},  \"excludedSqlInstances\":[]}'
 ```
  > [!NOTE]
    > The location property must match the location of the **Server - Azure Arc** resource for the server specified by the *--machine-name* parameter.
 
 2. Check to make sure your instance is in the exclusion list (see the value of the _excludedSqlInstances_ property).
 
-```console
+```azurecli
     az connectedmachine extension show --machine-name "{your machine name}" --resource-group "{your resource group name}" -n WindowsAgent.SqlServer
 ```
 
 3. Make sure to remove your instance from the exclusion list and update the extension settings.
 
-```console
+```azurecli
     az connectedmachine extension create --machine-name "{your machine name}" --location {"azure region"} --name "WindowsAgent.SqlServer" --resource-group "{your resource group name}" --type "WindowsAgent.SqlServer" --publisher "Microsoft.AzureData" --settings '{\"SqlManagement\":{\"IsEnabled\":true},  \"excludedSqlInstances\":[\"{named instance 1}\",\"{named instance 3}}\"]}'
 ```
 The instance will be restored after the next sync with the agent. For information on how to manage vm extensions using Portal or PowerShell, see [virtual machine extension management](/azure/azure-arc/servers/manage-vm-extensions).