Updated command parameters with long-form formatting

Author: schaffererin

articles/aks/azure-cni-overlay.md

@@ -127,7 +127,7 @@ subscriptionId=$(az account show --query id -o tsv)
 vnetName="yourVnetName"
 subnetName="yourNewSubnetName"
 subnetResourceId="/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.Network/virtualNetworks/$vnetName/subnets/$subnetName"
-az aks nodepool add  -g $resourceGroup --cluster-name $clusterName \
+az aks nodepool add --resource-group $resourceGroup --cluster-name $clusterName \
   --name $nodepoolName --node-count 1 \
   --mode system --vnet-subnet-id $subnetResourceId
 ```
@@ -233,13 +233,13 @@ The following attributes are provided to support dual-stack clusters:
 1. Create an Azure resource group for the cluster using the [`az group create`][az-group-create] command.
 
     ```azurecli-interactive
-    az group create -l <region> -n <resourceGroupName>
+    az group create --location <region> --name <resourceGroupName>
     ```
 
 2. Create a dual-stack AKS cluster using the [`az aks create`][az-aks-create] command with the `--ip-families` parameter set to `ipv4,ipv6`.
 
     ```azurecli-interactive
-    az aks create -l <region> -g <resourceGroupName> -n <clusterName> \
+    az aks create --location <region> --resource-group <resourceGroupName> --name <clusterName> \
       --network-plugin azure \
       --network-plugin-mode overlay \
       --ip-families ipv4,ipv6

articles/aks/azure-cni-powered-by-cilium.md

@@ -73,7 +73,7 @@ Azure CNI powered by Cilium currently has the following limitations:
 Use the following commands to create a cluster with an overlay network and Cilium. Replace the values for `<clusterName>`, `<resourceGroupName>`, and `<location>`:
 
 ```azurecli-interactive
-az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
+az aks create --name <clusterName> --resource-group <resourceGroupName> --loctaion <location> \
   --network-plugin azure \
   --network-plugin-mode overlay \
   --pod-cidr 192.168.0.0/16 \
@@ -94,15 +94,15 @@ az group create --name <resourceGroupName> --location <location>
 
 ```azurecli-interactive
 # Create a virtual network with a subnet for nodes and a subnet for pods
-az network vnet create -g <resourceGroupName> --location <location> --name <vnetName> --address-prefixes <address prefix, example: 10.0.0.0/8> -o none 
-az network vnet subnet create -g <resourceGroupName> --vnet-name <vnetName> --name nodesubnet --address-prefixes <address prefix, example: 10.240.0.0/16> -o none 
-az network vnet subnet create -g <resourceGroupName> --vnet-name <vnetName> --name podsubnet --address-prefixes <address prefix, example: 10.241.0.0/16> -o none 
+az network vnet create --resource-group <resourceGroupName> --location <location> --name <vnetName> --address-prefixes <address prefix, example: 10.0.0.0/8> -o none 
+az network vnet subnet create --resource-group <resourceGroupName> --vnet-name <vnetName> --name nodesubnet --address-prefixes <address prefix, example: 10.240.0.0/16> -o none 
+az network vnet subnet create --resource-group<resourceGroupName> --vnet-name <vnetName> --name podsubnet --address-prefixes <address prefix, example: 10.241.0.0/16> -o none 
 ```
 
 Create the cluster using `--network-dataplane cilium`:
 
 ```azurecli-interactive
-az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
+az aks create --name <clusterName> --resource-group <resourceGroupName> --location <location> \
   --max-pods 250 \
   --network-plugin azure \
   --vnet-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/nodesubnet \
@@ -131,7 +131,7 @@ To perform the upgrade, you will need Azure CLI version 2.52.0 or later. Run `az
 Use the following command to upgrade an existing cluster to Azure CNI Powered by Cilium. Replace the values for `<clusterName>` and `<resourceGroupName>`:
 
 ```azurecli-interactive
-az aks update -n <clusterName> -g <resourceGroupName> \
+az aks update --name <clusterName> --resource-group <resourceGroupName> \
   --network-dataplane cilium
 ```
 

articles/aks/configure-kubenet-dual-stack.md

@@ -71,19 +71,19 @@ The following attributes are provided to support dual-stack clusters:
 1. Create an Azure resource group for the cluster using the [`az group create`][az-group-create] command.
 
     ```azurecli-interactive
-    az group create -l <region> -n <resourceGroupName>
+    az group create --location <region> --name <resourceGroupName>
     ```
 
 2. Create a dual-stack AKS cluster using the [`az aks create`][az-aks-create] command with the `--ip-families` parameter set to `ipv4,ipv6`.
 
     ```azurecli-interactive
-    az aks create -l <region> -g <resourceGroupName> -n <clusterName> --ip-families ipv4,ipv6
+    az aks create --location <region> --resource-group <resourceGroupName> --name <clusterName> --ip-families ipv4,ipv6
     ```
 
 3. Once the cluster is created, get the cluster admin credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
     ```azurecli-interactive
-    az aks get-credentials -g <resourceGroupName> -n <clusterName>
+    az aks get-credentials --resource-group <resourceGroupName> --name <clusterName>
     ```
 
 # [Azure Resource Manager](#tab/azure-resource-manager)
@@ -151,7 +151,7 @@ The following attributes are provided to support dual-stack clusters:
 2. Once the cluster is created, get the cluster admin credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
     ```azurecli-interactive
-    az aks get-credentials -g <resourceGroupName> -n <clusterName>
+    az aks get-credentials --resource-group <resourceGroupName> --name <clusterName>
     ```
 
 > [!NOTE]
@@ -198,7 +198,7 @@ The following attributes are provided to support dual-stack clusters:
 2. Once the cluster is created, get the cluster admin credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
     ```azurecli-interactive
-    az aks get-credentials -g <resourceGroupName> -n <clusterName>
+    az aks get-credentials --resource-group <resourceGroupName> --name <clusterName>
     ```
 
 > [!NOTE]

articles/aks/csi-secrets-store-configuration-options.md

@@ -34,23 +34,23 @@ Follow the steps in [Use the Azure Key Vault provider for Secrets Store CSI Driv
 * Enable auto-rotation of secrets on a new cluster using the [`az aks create`][az-aks-create] command and enable the `enable-secret-rotation` add-on.
 
     ```azurecli-interactive
-    az aks create -n myAKSCluster2 -g myResourceGroup --enable-addons azure-keyvault-secrets-provider --enable-secret-rotation
+    az aks create --name myAKSCluster2 --resource-group myResourceGroup --enable-addons azure-keyvault-secrets-provider --enable-secret-rotation
     ```
 
 #### Enable auto-rotation on an existing AKS cluster
 
 * Update an existing cluster to enable auto-rotation of secrets using the [`az aks addon update`][az-aks-addon-update] command and the `enable-secret-rotation` parameter.
 
     ```azurecli-interactive
-    az aks addon update -g myResourceGroup -n myAKSCluster2 -a azure-keyvault-secrets-provider --enable-secret-rotation
+    az aks addon update --resource-group myResourceGroup --name myAKSCluster2 --addon azure-keyvault-secrets-provider --enable-secret-rotation
     ```
 
 #### Specify a custom rotation interval
 
 * Specify a custom rotation interval using the [`az aks addon update`][az-aks-addon-update] command with the `rotation-poll-interval` parameter.
 
     ```azurecli-interactive
-    az aks addon update -g myResourceGroup -n myAKSCluster2 -a azure-keyvault-secrets-provider --enable-secret-rotation --rotation-poll-interval 5m
+    az aks addon update --resource-group myResourceGroup --name myAKSCluster2 --addon azure-keyvault-secrets-provider --enable-secret-rotation --rotation-poll-interval 5m
     ```
 
 #### Disable auto-rotation
@@ -60,13 +60,13 @@ To disable auto-rotation, you first need to disable the add-on. Then, you can re
 1. Disable the secrets provider add-on using the [`az aks addon disable`][az-aks-addon-disable] command.
 
     ```azurecli-interactive
-    az aks addon disable -g myResourceGroup -n myAKSCluster2 -a azure-keyvault-secrets-provider
+    az aks addon disable --resource-group myResourceGroup --name myAKSCluster2 --addon azure-keyvault-secrets-provider
     ```
 
 2. Re-enable the secrets provider add-on without the `enable-secret-rotation` parameter using the [`az aks addon enable`][az-aks-addon-enable] command.
 
     ```azurecli-interactive
-    az aks addon enable -g myResourceGroup -n myAKSCluster2 -a azure-keyvault-secrets-provider
+    az aks addon enable --resource-group myResourceGroup --name myAKSCluster2 --addon azure-keyvault-secrets-provider
     ```
 
 If you are already using a `SecretProviderClass`, you can update the add-on without disabling it first by using `az aks addon enable` without specifying the `enable-secret-rotation` parameter.

articles/aks/csi-secrets-store-identity-access.md

@@ -54,7 +54,7 @@ In this security model, the AKS cluster acts as token issuer. Microsoft Entra ID
     ```azurecli-interactive
     az identity create --name $UAMI --resource-group $RESOURCE_GROUP
 
-    export USER_ASSIGNED_CLIENT_ID="$(az identity show -g $RESOURCE_GROUP --name $UAMI --query 'clientId' -o tsv)"
+    export USER_ASSIGNED_CLIENT_ID="$(az identity show --resource-group $RESOURCE_GROUP --name $UAMI --query 'clientId' -o tsv)"
     export IDENTITY_TENANT=$(az aks show --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP --query identity.tenantId -o tsv)
     ```
 
@@ -194,18 +194,18 @@ In this security model, you can grant access to your cluster's resources to team
 1. Access your key vault using the [`az aks show`][az-aks-show] command and the user-assigned managed identity created by the add-on. You should also retrieve the identity's `clientId`, which you'll use in later steps when creating a `SecretProviderClass`.
 
     ```azurecli-interactive
-    az aks show -g <resource-group> -n <cluster-name> --query addonProfiles.azureKeyvaultSecretsProvider.identity.objectId -o tsv
-    az aks show -g <resource-group> -n <cluster-name> --query addonProfiles.azureKeyvaultSecretsProvider.identity.clientId -o tsv
+    az aks show --resource-group <resource-group> --name <cluster-name> --query addonProfiles.azureKeyvaultSecretsProvider.identity.objectId -o tsv
+    az aks show --resource-group <resource-group> --name <cluster-name> --query addonProfiles.azureKeyvaultSecretsProvider.identity.clientId -o tsv
     ```
 
     Alternatively, you can create a new managed identity and assign it to your virtual machine (VM) scale set or to each VM instance in your availability set using the following commands.
 
     ```azurecli-interactive
-    az identity create -g <resource-group> -n <identity-name>
-    az vmss identity assign -g <resource-group> -n <agent-pool-vmss> --identities <identity-resource-id>
-    az vm identity assign -g <resource-group> -n <agent-pool-vm> --identities <identity-resource-id>
+    az identity create -resource-group <resource-group> --name <identity-name>
+    az vmss identity assign --resource-group <resource-group> --name <agent-pool-vmss> --identities <identity-resource-id>
+    az vm identity assign --resource-group <resource-group> --name <agent-pool-vm> --identities <identity-resource-id>
 
-    az identity show -g <resource-group> --name <identity-name> --query 'clientId' -o tsv
+    az identity show --resource-group <resource-group> --name <identity-name> --query 'clientId' -o tsv
     ```
 
 2. Create a role assignment that grants the identity permission to access the key vault secrets, access keys, and certificates using the [`az role assignment create`][az-role-assignment-create] command.
@@ -221,7 +221,7 @@ In this security model, you can grant access to your cluster's resources to team
     > ```
 
     ```azurecli-interactive
-    export IDENTITY_OBJECT_ID="$(az identity show -g <resource-group> --name <identity-name> --query 'principalId' -o tsv)"
+    export IDENTITY_OBJECT_ID="$(az identity show --resource-group <resource-group> --name <identity-name> --query 'principalId' -o tsv)"
     export KEYVAULT_SCOPE=$(az keyvault show --name <key-vault-name> --query id -o tsv)
 
     # Example command for key vault with RBAC enabled using `key` type
@@ -339,7 +339,7 @@ A key vault certificate also contains public x509 certificate metadata. The key
 - Disable the Azure Key Vault provider for Secrets Store CSI Driver capability in an existing cluster using the [`az aks disable-addons`][az-aks-disable-addons] command with the `azure-keyvault-secrets-provider` add-on.
 
     ```azurecli-interactive
-    az aks disable-addons --addons azure-keyvault-secrets-provider -g myResourceGroup -n myAKSCluster
+    az aks disable-addons --addons azure-keyvault-secrets-provider --resource-group myResourceGroup --name myAKSCluster
     ```
 
 > [!NOTE]

articles/aks/csi-secrets-store-nginx-tls.md

@@ -50,7 +50,7 @@ You can import the ingress TLS certificate to the cluster using one of the follo
 2. Import the certificate using the [`az keyvault certificate import`][az-key-vault-certificate-import] command.
 
     ```azurecli-interactive
-    az keyvault certificate import --vault-name $AKV_NAME -n $CERT_NAME -f $CERT_NAME.pfx
+    az keyvault certificate import --vault-name $AKV_NAME --name $CERT_NAME --file $CERT_NAME.pfx
     ```
 
 ## Deploy a SecretProviderClass

articles/aks/egress-outboundtype.md

@@ -107,13 +107,13 @@ Migration is only supported between `loadBalancer`, `managedNATGateway` (if usin
 ### Update cluster from loadbalancer to managedNATGateway  
 
 ```azurecli-interactive
-az aks update -g <resourceGroup> -n <clusterName> --outbound-type managedNATGateway --nat-gateway-managed-outbound-ip-count <number of managed outbound ip>
+az aks update --resource-group <resourceGroup> --name <clusterName> --outbound-type managedNATGateway --nat-gateway-managed-outbound-ip-count <number of managed outbound ip>
 ```
 
 ### Update cluster from managedNATGateway to loadbalancer
 
 ```azurecli-interactive
-az aks update -g <resourceGroup> -n <clusterName> \
+az aks update --resource-group <resourceGroup> --name <clusterName> \
 --outbound-type loadBalancer \
 <--load-balancer-managed-outbound-ip-count <number of managed outbound ip>| --load-balancer-outbound-ips <outbound ip ids> | --load-balancer-outbound-ip-prefixes <outbound ip prefix ids> >
 ```
@@ -126,15 +126,15 @@ az aks update -g <resourceGroup> -n <clusterName> \
 - Add route `0.0.0.0/0` to default route table. Please refer to [Customize cluster egress with a user-defined routing table in Azure Kubernetes Service (AKS)](egress-udr.md)
 
 ```azurecli-interactive
-az aks update -g <resourceGroup> -n <clusterName> --outbound-type userDefinedRouting
+az aks update --resource-group <resourceGroup> --name <clusterName> --outbound-type userDefinedRouting
 ```
 
 ### Update cluster from loadbalancer to userAssignedNATGateway in BYO vnet scenario
 
 - Associate nat gateway with subnet where the workload is associated with. Refer to [Create a managed or user-assigned NAT gateway](nat-gateway.md)
 
 ```azurecli-interactive
-az aks update -g <resourceGroup> -n <clusterName> --outbound-type userAssignedNATGateway
+az aks update --resource-group <resourceGroup> --name <clusterName> --outbound-type userAssignedNATGateway
 ```
 
 ## Next steps