Merge pull request #186954 from dksimpson/azure-docs-pr-20220126-validation-2

Validation bulk update: Fix code tags for Azure CLI code blocks - batch 1

Author: ShannonLeavitt

articles/aks/api-server-authorized-ip-ranges.md

@@ -155,6 +155,9 @@ Add another IP address to the approved ranges with the following command.
 ```bash
 # Retrieve your IP address
 CURRENT_IP=$(dig +short "myip.opendns.com" "@resolver1.opendns.com")
+````
+
+```azurelci
 # Add to AKS approved list
 az aks update -g $RG -n $AKSNAME --api-server-authorized-ip-ranges $CURRENT_IP/32
 ```

articles/aks/certificate-rotation.md

@@ -41,12 +41,12 @@ curl https://{apiserver-fqdn} -k -v 2>&1 |grep expire
 ```
 
 * Check expiration date of certificate on VMAS agent node
-```console
+```azurecli
 az vm run-command invoke -g MC_rg_myAKSCluster_region -n vm-name --command-id RunShellScript --query 'value[0].message' -otsv --scripts "openssl x509 -in /etc/kubernetes/certs/apiserver.crt -noout -enddate"
 ```
 
 * Check expiration date of certificate on one VMSS agent node
-```console
+```azurecli
 az vmss run-command invoke -g MC_rg_myAKSCluster_region -n vmss-name --instance-id 0 --command-id RunShellScript --query 'value[0].message' -otsv --scripts "openssl x509 -in /etc/kubernetes/certs/apiserver.crt -noout -enddate"
 ```
 

articles/aks/ingress-tls.md

@@ -247,7 +247,7 @@ Note that this sample is for a Bash shell.
 
 ### [Azure CLI](#tab/azure-cli)
 
-```bash
+```azurecli
 # Public IP address of your ingress controller
 IP="MY_EXTERNAL_IP"
 

articles/aks/kubernetes-portal.md

@@ -74,13 +74,15 @@ For existing clusters, you may need to enable the Kubernetes resource view. To e
 
 > [!TIP]
 > The AKS feature for [**API server authorized IP ranges**](api-server-authorized-ip-ranges.md) can be added to limit API server access to only the firewall's public endpoint. Another option for such clusters is updating `--api-server-authorized-ip-ranges` to include access for a local client computer or IP address range (from which portal is being browsed). To allow this access, you need the computer's public IPv4 address. You can find this address with below command or by searching "what is my IP address" in an internet browser.
+
 ```bash
 # Retrieve your IP address
 CURRENT_IP=$(dig +short myip.opendns.com @resolver1.opendns.com)
+```
 
+```azurecli
 # Add to AKS approved list
 az aks update -g $RG -n $AKSNAME --api-server-authorized-ip-ranges $CURRENT_IP/32
-
 ```
 
 ## Next steps

articles/aks/limit-egress-traffic.md

@@ -365,7 +365,7 @@ az network firewall ip-config create -g $RG -f $FWNAME -n $FWIPCONFIG_NAME --pub
 
 When the previous command has succeeded, save the firewall frontend IP address for configuration later.
 
-```bash
+```azurecli
 # Capture Firewall IP Address for Later Use
 
 FWPUBLIC_IP=$(az network public-ip show -g $RG -n $FWPUBLICIP_NAME --query "ipAddress" -o tsv)

articles/aks/manage-azure-rbac.md

@@ -98,7 +98,7 @@ AKS provides the following four built-in roles:
 
 Roles assignments scoped to the **entire AKS cluster** can be done either on the Access Control (IAM) blade of the cluster resource on Azure portal or by using Azure CLI commands as shown below:
 
-```bash
+```azurecli
 # Get your AKS Resource ID
 AKS_ID=$(az aks show -g MyResourceGroup -n MyManagedCluster --query id -o tsv)
 ```

articles/aks/quickstart-event-grid.md

@@ -86,7 +86,6 @@ az eventgrid event-subscription list --source-resource-id $SOURCE_RESOURCE_ID
 The following example output shows you're subscribed to events from the *MyAKS* cluster and those events are delivered to the *MyEventGridHub* event hub:
 
 ```output
-$ az eventgrid event-subscription list --source-resource-id $SOURCE_RESOURCE_ID
 [
   {
     "deadLetterDestination": null,

articles/aks/use-multiple-node-pools.md

@@ -455,9 +455,11 @@ az aks nodepool add \
 
 The following example output from the [az aks nodepool list][az-aks-nodepool-list] command shows that *taintnp* is *Creating* nodes with the specified *nodeTaints*:
 
-```console
-$ az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+```azurecli
+az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+```
 
+```output
 [
   {
     ...
@@ -561,9 +563,10 @@ az aks nodepool add \
 
 The following example output from the [az aks nodepool list][az-aks-nodepool-list] command shows that *labelnp* is *Creating* nodes with the specified *nodeLabels*:
 
-```console
-$ az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+```azurecli
+az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
 
+```output
 [
   {
     ...

articles/app-service/configure-language-java.md

@@ -478,13 +478,13 @@ To enable via the Azure CLI, you will need to create an Application Insights res
 
 1. Enable the Applications Insights extension
 
-    ```bash
+    ```azurecli
     az extension add -n application-insights
     ```
 
 2. Create an Application Insights resource using the CLI command below. Replace the placeholders with your desired resource name and group.
 
-    ```bash
+    ```azurecli
     az monitor app-insights component create --app <resource-name> -g <resource-group> --location westus2  --kind web --application-type web
     ```
 
@@ -496,7 +496,7 @@ To enable via the Azure CLI, you will need to create an Application Insights res
     
 3. Set the instrumentation key, connection string, and monitoring agent version as app settings on the web app. Replace `<instrumentationKey>` and `<connectionString>` with the values from the previous step.
 
-    ```bash
+    ```azurecli
     az webapp config appsettings set -n <webapp-name> -g <resource-group> --settings "APPINSIGHTS_INSTRUMENTATIONKEY=<instrumentationKey>" "APPLICATIONINSIGHTS_CONNECTION_STRING=<connectionString>" "ApplicationInsightsAgent_EXTENSION_VERSION=~3" "XDT_MicrosoftApplicationInsights_Mode=default" "XDT_MicrosoftApplicationInsights_Java=1"
     ```
 
@@ -505,7 +505,7 @@ To enable via the Azure CLI, you will need to create an Application Insights res
     
 3. Set the instrumentation key, connection string, and monitoring agent version as app settings on the web app. Replace `<instrumentationKey>` and `<connectionString>` with the values from the previous step.
 
-    ```bash
+    ```azurecli
     az webapp config appsettings set -n <webapp-name> -g <resource-group> --settings "APPINSIGHTS_INSTRUMENTATIONKEY=<instrumentationKey>" "APPLICATIONINSIGHTS_CONNECTION_STRING=<connectionString>" "ApplicationInsightsAgent_EXTENSION_VERSION=~3" "XDT_MicrosoftApplicationInsights_Mode=default"
     ```
 
@@ -799,7 +799,7 @@ The platform also needs to know where your custom version of Tomcat is installed
 
 You can use the Azure CLI to change this setting:
 
-```powershell
+```azurecli
     az webapp config appsettings set -g $MyResourceGroup -n $MyUniqueApp --settings CATALINA_BASE="%LOCAL_EXPANDED%\tomcat"
 ```
 

articles/app-service/deploy-zip.md

@@ -173,19 +173,19 @@ The CLI command uses the [Kudu publish API](#kudu-publish-api-reference) to depl
 
 ### Deploy a startup script
 
-```bash
+```azurecli
 az webapp deploy --resource-group <group-name> --name <app-name> --src-path scripts/startup.sh --type=startup
 ```
 
 ### Deploy a library file
 
-```bash
+```azurecli
 az webapp deploy --resource-group <group-name> --name <app-name> --src-path driver.jar --type=lib
 ```
 
 ### Deploy a static file
 
-```bash
+```azurecli
 az webapp deploy --resource-group <group-name> --name <app-name> --src-path config.json --type=static
 ```