Merge pull request #104276 from TimShererWithAquent/us1669724a

[Azure CLI code blocks]

Author: PRMerger20

articles/azure-monitor/insights/container-insights-azure-redhat-setup.md

@@ -108,7 +108,7 @@ The Log Analytics workspace has to be created before you enable monitoring using
 
     The output resembles the following:
 
-    ```azurecli
+    ```output
     provisioningState       : Succeeded
     ```
 
@@ -192,7 +192,7 @@ The Log Analytics workspace has to be created before you enable monitoring using
 
     The output resembles the following:
 
-    ```azurecli
+    ```output
     provisioningState       : Succeeded
     ```
 

articles/azure-monitor/insights/container-insights-enable-existing-clusters.md

@@ -31,7 +31,7 @@ az aks enable-addons -a monitoring -n MyExistingManagedCluster -g MyExistingMana
 
 The output will resemble the following:
 
-```azurecli
+```output
 provisioningState       : Succeeded
 ```
 
@@ -47,7 +47,7 @@ If you would rather integrate with an existing workspace, perform the following
 
     The output will resemble the following:
 
-    ```azurecli
+    ```output
     Name                                  CloudName    SubscriptionId                        State    IsDefault
     ------------------------------------  -----------  ------------------------------------  -------  -----------
     Microsoft Azure                       AzureCloud   68627f8c-91fO-4905-z48q-b032a81f8vy0  Enabled  True
@@ -63,7 +63,7 @@ If you would rather integrate with an existing workspace, perform the following
 
 3. The following example displays the list of workspaces in your subscriptions in the default JSON format.
 
-    ```
+    ```azurecli
     az resource list --resource-type Microsoft.OperationalInsights/workspaces -o json
     ```
 
@@ -77,7 +77,7 @@ If you would rather integrate with an existing workspace, perform the following
 
     The output will resemble the following:
 
-    ```azurecli
+    ```output
     provisioningState       : Succeeded
     ```
 
@@ -268,7 +268,7 @@ If you choose to use the Azure CLI, you first need to install and use the CLI lo
 
        The configuration change can take a few minutes to complete. When it's completed, a message is displayed that's similar to the following and includes the result:
 
-       ```powershell
+       ```output
        provisioningState       : Succeeded
        ```
 
@@ -282,7 +282,7 @@ If you choose to use the Azure CLI, you first need to install and use the CLI lo
 
        The configuration change can take a few minutes to complete. When it's completed, a message is displayed that's similar to the following and includes the result:
 
-       ```azurecli
+       ```output
        provisioningState       : Succeeded
        ```
 
@@ -302,7 +302,7 @@ kubectl get ds omsagent --namespace=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:
 
-```
+```output
 User@aksuser:~$ kubectl get ds omsagent --namespace=kube-system
 NAME       DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
 omsagent   2         2         2         2            2           beta.kubernetes.io/os=linux   1d
@@ -316,7 +316,7 @@ kubectl get deployment omsagent-rs -n=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:
 
-```
+```output
 User@aksuser:~$ kubectl get deployment omsagent-rs -n=kube-system
 NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE    AGE
 omsagent   1         1         1            1            3h
@@ -332,7 +332,7 @@ kubectl get ds omsagent --namespace=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:  
 
-```
+```output
 User@aksuser:~$ kubectl get ds omsagent --namespace=kube-system
 NAME       DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
 omsagent   2         2         2         2            2           beta.kubernetes.io/os=linux   1d
@@ -348,7 +348,7 @@ az aks show -g <resourceGroupofAKSCluster> -n <nameofAksCluster>
 
 After a few minutes, the command completes and returns JSON-formatted information about solution.  The results of the command should show the monitoring add-on profile and resembles the following example output:
 
-```
+```output
 "addonProfiles": {
     "omsagent": {
       "config": {

articles/azure-monitor/insights/container-insights-optout-openshift.md

@@ -100,7 +100,7 @@ az group deployment create --resource-group <ResourceGroupName> --template-file
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```azurecli
+```output
 ProvisioningState       : Succeeded
 ```
 
@@ -118,7 +118,7 @@ New-AzResourceGroupDeployment -Name opt-out -ResourceGroupName <ResourceGroupNam
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```powershell
+```output
 ProvisioningState       : Succeeded
 ```
 

articles/azure-monitor/insights/container-insights-optout.md

@@ -135,7 +135,7 @@ az group deployment create --resource-group <ResourceGroupName> --template-file
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```azurecli
+```output
 ProvisioningState       : Succeeded
 ```
 
@@ -153,7 +153,7 @@ New-AzResourceGroupDeployment -Name opt-out -ResourceGroupName <ResourceGroupNam
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```powershell
+```output
 ProvisioningState       : Succeeded
 ```
 

articles/container-instances/container-instances-volume-gitrepo.md

@@ -77,13 +77,13 @@ To mount a gitRepo volume for a private Git repository, specify credentials in t
 
 For example, the Azure CLI `--gitrepo-url` parameter for a private GitHub repository would appear similar to the following (where "gituser" is the GitHub user name, and "abcdef1234fdsa4321abcdef" is the user's personal access token):
 
-```azurecli
+```console
 --gitrepo-url https://gituser:[email protected]/GitUser/some-private-repository
 ```
 
 For an Azure Repos Git repository, specify any user name (you can use "azurereposuser" as in the following example) in combination with a valid PAT:
 
-```azurecli
+```console
 --gitrepo-url https://azurereposuser:[email protected]/your-org/_git/some-private-repository
 ```
 

articles/container-registry/container-registry-faq.md

@@ -110,13 +110,13 @@ ACR supports Docker Registry HTTP API V2. The APIs can be accessed at
 
 If you are on bash:
 
-```bash
+```azurecli
 az acr repository show-manifests -n myRegistry --repository myRepository --query "[?tags[0]==null].digest" -o tsv  | xargs -I% az acr repository delete -n myRegistry -t myRepository@%
 ```
 
 For Powershell:
 
-```powershell
+```azurecli
 az acr repository show-manifests -n myRegistry --repository myRepository --query "[?tags[0]==null].digest" -o tsv | %{ az acr repository delete -n myRegistry -t myRepository@$_ }
 ```
 
@@ -147,13 +147,13 @@ docker push myregistry.azurecr.io/1gb:latest
 
 You should be able to see that the storage usage has increased in the Azure portal, or you can query usage using the CLI.
 
-```bash
+```azurecli
 az acr show-usage -n myregistry
 ```
 
 Delete the image using the Azure CLI or portal and check the updated usage in a few minutes.
 
-```bash
+```azurecli
 az acr repository delete -n myregistry --image 1gb
 ```
 
@@ -212,12 +212,12 @@ ACR supports [custom roles](container-registry-roles.md) that provide different
   Then you can assign the `AcrPull` or `AcrPush` role to a user (the following example uses `AcrPull`):
 
   ```azurecli
-    az role assignment create --scope resource_id --role AcrPull --assignee [email protected]
-    ```
+  az role assignment create --scope resource_id --role AcrPull --assignee [email protected]
+  ```
 
   Or, assign the role to a service principle identified by its application ID:
 
-  ```
+  ```azurecli
   az role assignment create --scope resource_id --role AcrPull --assignee 00000000-0000-0000-0000-000000000000
   ```
 
@@ -235,9 +235,9 @@ The assignee is then able to authenticate and access images in the registry.
   az acr repository list -n myRegistry
   ```
 
- To pull an image:
-    
-  ```azurecli
+* To pull an image:
+
+  ```console
   docker pull myregistry.azurecr.io/hello-world
   ```
 
@@ -271,9 +271,10 @@ To troubleshoot common environment and registry issues, see [Check the health of
  - If `docker pull` fails continuously, then there could be a problem with the Docker daemon. The problem can generally be mitigated by restarting the Docker daemon. 
  - If you continue to see this issue after restarting Docker daemon, then the problem could be some network connectivity issues with the machine. To check if general network on the machine is healthy, run the following command to test endpoint connectivity. The minimum `az acr` version that contains this connectivity check command is 2.2.9. Upgrade your Azure CLI if you are using an older version.
 
-   ```azurecli
-    az acr check-health -n myRegistry
-    ```
+  ```azurecli
+  az acr check-health -n myRegistry
+  ```
+
  - You should always have a retry mechanism on all Docker client operations.
 
 ### Docker pull is slow

articles/logic-apps/logic-apps-enterprise-integration-create-integration-account.md

@@ -135,13 +135,13 @@ To make this change, you can use either the Azure portal by following the steps
 
 1. At the command prompt, enter the [**az resource** command](https://docs.microsoft.com/cli/azure/resource?view=azure-cli-latest#az-resource-update), and set `skuName` to the higher tier that you want.
 
-   ```Azure CLI
+   ```azurecli
    az resource update --resource-group {ResourceGroupName} --resource-type Microsoft.Logic/integrationAccounts --name {IntegrationAccountName} --subscription {AzureSubscriptionID} --set sku.name={SkuName}
    ```
 
    For example, if you have the Basic tier, you can set `skuName` to `Standard`:
 
-   ```Azure CLI
+   ```azurecli
    az resource update --resource-group FabrikamIntegration-RG --resource-type Microsoft.Logic/integrationAccounts --name Fabrikam-Integration --subscription XXXXXXXXXXXXXXXXX --set sku.name=Standard
    ```
 
@@ -159,13 +159,13 @@ To make this change, use the [Azure CLI](https://docs.microsoft.com/cli/azure/ge
 
 1. At the command prompt, enter the [**az resource** command](https://docs.microsoft.com/cli/azure/resource?view=azure-cli-latest#az-resource-update) and set `skuName` to the lower tier that you want.
 
-   ```Azure CLI
+   ```azurecli
    az resource update --resource-group <resourceGroupName> --resource-type Microsoft.Logic/integrationAccounts --name <integrationAccountName> --subscription <AzureSubscriptionID> --set sku.name=<skuName>
    ```
 
    For example, if you have the Standard tier, you can set `skuName` to `Basic`:
 
-   ```Azure CLI
+   ```azurecli
    az resource update --resource-group FabrikamIntegration-RG --resource-type Microsoft.Logic/integrationAccounts --name Fabrikam-Integration --subscription XXXXXXXXXXXXXXXXX --set sku.name=Basic
    ```