Merge pull request #112279 from SubhashVasarapu-MSFT/patch-44

(AzureCXP) fixes MicrosoftDocs/azure-docs#52794

Author: PRMerger17

articles/application-gateway/ingress-controller-install-existing.md

@@ -126,7 +126,7 @@ It is also possible to provide AGIC access to ARM via a Kubernetes secret.
 blob to be saved to Kubernetes.
 
 ```azurecli
-az ad sp create-for-rbac --subscription <subscription-uuid> --sdk-auth | base64 -w0
+az ad sp create-for-rbac --sdk-auth | base64 -w0
 ```
 
 2. Add the base64 encoded JSON blob to the `helm-config.yaml` file. More information on `helm-config.yaml` is in the
@@ -194,7 +194,7 @@ In the first few steps, we install Helm's Tiller on your Kubernetes cluster. Use
     ## Alternatively you can use Service Principal credentials
     # armAuth:
     #    type: servicePrincipal
-    #    secretJSON: <<Generate this value with: "az ad sp create-for-rbac --subscription <subscription-uuid> --sdk-auth | base64 -w0" >>
+    #    secretJSON: <<Generate this value with: "az ad sp create-for-rbac --sdk-auth | base64 -w0" >>
     
     ################################################################################
     # Specify if the cluster is RBAC enabled or not
@@ -231,7 +231,7 @@ In the first few steps, we install Helm's Tiller on your Kubernetes cluster. Use
          --set appgw.subscriptionId=subscription-uuid \
          --set appgw.shared=false \
          --set armAuth.type=servicePrincipal \
-         --set armAuth.secretJSON=$(az ad sp create-for-rbac --subscription <subscription-uuid> --sdk-auth | base64 -w0) \
+         --set armAuth.secretJSON=$(az ad sp create-for-rbac --sdk-auth | base64 -w0) \
          --set rbac.enabled=true \
          --set verbosityLevel=3 \
          --set kubernetes.watchNamespace=default \