Updated command parameters with long-form formatting

Author: schaffererin

articles/aks/azure-blob-csi.md

@@ -47,13 +47,13 @@ Using the Azure CLI, you can enable the Blob storage CSI driver on a new or exis
 To enable the driver on a new cluster, include the `--enable-blob-driver` parameter with the `az aks create` command as shown in the following example:
 
 ```azurecli
-az aks create --enable-blob-driver -n myAKSCluster -g myResourceGroup
+az aks create --enable-blob-driver --name myAKSCluster --resource-group myResourceGroup
 ```
 
 To enable the driver on an existing cluster, include the `--enable-blob-driver` parameter with the `az aks update` command as shown in the following example:
 
 ```azurecli
-az aks update --enable-blob-driver -n myAKSCluster -g myResourceGroup
+az aks update --enable-blob-driver --name myAKSCluster --resource-group myResourceGroup
 ```
 
 You're prompted to confirm there isn't an open-source Blob CSI driver installed. After you confirm, it may take several minutes to complete this action. Once it's complete, you should see in the output the status of enabling the driver on your cluster. The following example resembles the section indicating the results of the previous command:
@@ -72,7 +72,7 @@ Using the Azure CLI, you can disable the Blob storage CSI driver on an existing
 To disable the driver on an existing cluster, include the `--disable-blob-driver` parameter with the `az aks update` command as shown in the following example:
 
 ```azurecli
-az aks update --disable-blob-driver -n myAKSCluster -g myResourceGroup
+az aks update --disable-blob-driver --name myAKSCluster --resource-group myResourceGroup
 ```
 
 ## Use a persistent volume with Azure Blob storage

articles/aks/azure-disk-customer-managed-keys.md

@@ -89,7 +89,7 @@ Either create a new resource group, or select an existing resource group hosting
 Run the following command to retrieve the DiskEncryptionSet value and set a variable:
 
 ```azurecli-interactive
-diskEncryptionSetId=$(az disk-encryption-set show --name mydiskEncryptionSetName --resource-gorup myResourceGroup --query "[id]" -o tsv)
+diskEncryptionSetId=$(az disk-encryption-set show --name mydiskEncryptionSetName --resource-group myResourceGroup --query "[id]" -o tsv)
 ```
 
 If you want to create a new resource group for the cluster, run the following command:

articles/aks/istio-meshconfig.md

@@ -23,7 +23,7 @@ This guide assumes you followed the [documentation][istio-deploy-addon] to enabl
 1. Find out which revision of Istio is deployed on the cluster:
 
     ```bash
-    az aks show -n $CLUSTER -g $RESOURCE_GROUP --query 'serviceMeshProfile'
+    az aks show --name $CLUSTER --resource-group $RESOURCE_GROUP --query 'serviceMeshProfile'
     ```
 
     Output:

articles/aks/keda-deploy-add-on-cli.md

@@ -74,7 +74,7 @@ To install the KEDA add-on, use `--enable-keda` when creating or updating a clus
 - Verify the KEDA add-on is installed on your cluster using the [`az aks show`][az-aks-show] command and set the `--query` parameter to `workloadAutoScalerProfile.keda.enabled`.
 
     ```azurecli-interactive
-    az aks show -g myResourceGroup --name myAKSCluster --query "workloadAutoScalerProfile.keda.enabled" 
+    az aks show --resource-group myResourceGroup --name myAKSCluster --query "workloadAutoScalerProfile.keda.enabled" 
     ```
 
     The following example output shows the KEDA add-on is installed on the cluster:

articles/aks/upgrade-aks-cluster.md

@@ -230,10 +230,10 @@ AKS accepts both integer values and a percentage value for max surge. An integer
 
     ```azurecli-interactive
     # Set max surge for a new node pool
-    az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 33%
+    az aks nodepool add --name mynodepool --resource-group MyResourceGroup --cluster-name MyManagedCluster --max-surge 33%
 
     # Update max surge for an existing node pool 
-    az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 5
+    az aks nodepool update --name mynodepool --resource-group MyResourceGroup --cluster-name MyManagedCluster --max-surge 5
     ```
 
 #### Set node drain timeout value
@@ -244,10 +244,10 @@ At times, you may have a long running workload on a certain pod and it can't be
 
     ```azurecli-interactive
     # Set drain timeout for a new node pool
-    az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster  --drain-timeout 100
+    az aks nodepool add --name mynodepool --resource-group MyResourceGroup --cluster-name MyManagedCluster  --drain-timeout 100
 
     # Update drain timeout for an existing node pool
-    az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --drain-timeout 45
+    az aks nodepool update --name mynodepool --resource-group MyResourceGroup --cluster-name MyManagedCluster --drain-timeout 45
     ```
 
 #### Set node soak time value
@@ -258,13 +258,13 @@ To allow for a duration of time to wait between draining a node and proceeding t
 
     ```azurecli-interactive
     # Set node soak time for a new node pool
-    az aks nodepool add -n MyNodePool -g MyResourceGroup --cluster-name MyManagedCluster --node-soak-duration 10
+    az aks nodepool add --name MyNodePool --resource-group MyResourceGroup --cluster-name MyManagedCluster --node-soak-duration 10
 
     # Update node soak time for an existing node pool
-    az aks nodepool update -n MyNodePool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 33% --node-soak-duration 5
+    az aks nodepool update --name MyNodePool --resource-group MyResourceGroup --cluster-name MyManagedCluster --max-surge 33% --node-soak-duration 5
 
     # Set node soak time when upgrading an existing node pool
-    az aks nodepool upgrade -n MyNodePool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 33% --node-soak-duration 20
+    az aks nodepool upgrade --name MyNodePool --resource-group MyResourceGroup --cluster-name MyManagedCluster --max-surge 33% --node-soak-duration 20
     ```
 
 ## View upgrade events

articles/aks/use-ultra-disks.md

@@ -29,7 +29,7 @@ This feature can only be set at cluster creation or when creating a node pool.
 Create an AKS cluster that is able to leverage Azure ultra Disks by using the following CLI commands. Use the `--enable-ultra-ssd` parameter to set the `EnableUltraSSD` feature.
 
 ```azurecli-interactive
-az aks create -g MyResourceGroup -n myAKSCluster -l westus2 --node-vm-size Standard_D2s_v3 --zones 1 2 --node-count 2 --enable-ultra-ssd
+az aks create --resource-group MyResourceGroup --name myAKSCluster --location westus2 --node-vm-size Standard_D2s_v3 --zones 1 2 --node-count 2 --enable-ultra-ssd
 ```
 
 If you want to create a cluster without ultra disk support, you can do so by omitting the `--enable-ultra-ssd` parameter.

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

@@ -101,16 +101,16 @@ Use the `-enable-azure-monitor-metrics` option `az aks create` or `az aks update
 
 ```azurecli
 ### Use default Azure Monitor workspace
-az aks create/update --enable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group>
+az aks create/update --enable-azure-monitor-metrics --name <cluster-name> --resource-group <cluster-resource-group>
 
 ### Use existing Azure Monitor workspace
-az aks create/update --enable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group> --azure-monitor-workspace-resource-id <workspace-name-resource-id>
+az aks create/update --enable-azure-monitor-metrics --name <cluster-name> --resource-group <cluster-resource-group> --azure-monitor-workspace-resource-id <workspace-name-resource-id>
 
 ### Use an existing Azure Monitor workspace and link with an existing Grafana workspace
-az aks create/update --enable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group> --azure-monitor-workspace-resource-id <azure-monitor-workspace-name-resource-id> --grafana-resource-id  <grafana-workspace-name-resource-id>
+az aks create/update --enable-azure-monitor-metrics --name <cluster-name> --resource-group <cluster-resource-group> --azure-monitor-workspace-resource-id <azure-monitor-workspace-name-resource-id> --grafana-resource-id  <grafana-workspace-name-resource-id>
 
 ### Use optional parameters
-az aks create/update --enable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group> --ksm-metric-labels-allow-list "namespaces=[k8s-label-1,k8s-label-n]" --ksm-metric-annotations-allow-list "pods=[k8s-annotation-1,k8s-annotation-n]"
+az aks create/update --enable-azure-monitor-metrics --name <cluster-name> --resource-group <cluster-resource-group> --ksm-metric-labels-allow-list "namespaces=[k8s-label-1,k8s-label-n]" --ksm-metric-annotations-allow-list "pods=[k8s-annotation-1,k8s-annotation-n]"
 ```
 
 #### Arc-enabled cluster
@@ -360,16 +360,16 @@ Use one of the following commands to enable monitoring of your AKS and Arc-enabl
 
 ```azurecli
 ### Use default Log Analytics workspace
-az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-name>
+az aks enable-addons --addon monitoring --name <cluster-name> --resource-group <cluster-resource-group-name>
 
 ### Use existing Log Analytics workspace
-az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-name> --workspace-resource-id <workspace-resource-id>
+az aks enable-addons --addon monitoring --name <cluster-name> --resource-group <cluster-resource-group-name> --workspace-resource-id <workspace-resource-id>
 ```
 
 **Example**
 
 ```azurecli
-az aks enable-addons -a monitoring -n "my-cluster" -g "my-resource-group" --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
+az aks enable-addons --addon monitoring --name "my-cluster" --resource-group "my-resource-group" --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
 ```
 
 
@@ -756,7 +756,7 @@ ama-logs-rs   1/1     1            1           24d
 Use the `aks show` command to find out whether the solution is enabled, the Log Analytics workspace resource ID, and summary information about the cluster.
 
 ```azurecli
-az aks show -g <resourceGroupofAKSCluster> -n <nameofAksCluster>
+az aks show --resource-group <resourceGroupofAKSCluster> --name <nameofAksCluster>
 ```
 
 The command will return JSON-formatted information about the solution. The `addonProfiles` section should include information on the `omsagent` as in the following example:

articles/backup/azure-kubernetes-service-cluster-manage-backups.md

@@ -33,7 +33,7 @@ To install Backup Extension, you need to register `Microsoft.KubernetesConfigura
 The registration may take up to *10 minutes*. To monitor the registration process, run the following command:
 
    ```azurecli-interactive
-   az provider show -n Microsoft.KubernetesConfiguration -o table
+   az provider show --name Microsoft.KubernetesConfiguration --output table
    ```
 
 ### Register the Trusted Access
@@ -130,10 +130,10 @@ To enable Trusted Access between Backup vault and AKS cluster, use the following
 
    ```azurecli-interactive
    az aks trustedaccess rolebinding create \
-   -g <aksclusterrg> \
+   --resource-group <aksclusterrg> \
    --cluster-name <aksclustername> \
-   -n <randomRoleBindingName> \
-   --source-resource-id $(az dataprotection backup-vault show -g <vaultrg> --vault <VaultName> --query id -o tsv) \
+   --name <randomRoleBindingName> \
+   --source-resource-id $(az dataprotection backup-vault show --resource-group <vaultrg> --vault <VaultName> --query id -o tsv) \
    --roles Microsoft.DataProtection/backupVaults/backup-operator   
    ```