Merge pull request #178393 from jdmartinez36/clirolefix2

1876839: Add CLI contributor role to code blocks #2

Author: laurabren

articles/application-gateway/ingress-controller-multiple-namespace-support.md

@@ -174,7 +174,7 @@ options:
     ## 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 --subscription <subscription-uuid> --role Contributor --sdk-auth | base64 -w0" >>
     
     ################################################################################
     # Specify if the cluster is Kubernetes RBAC enabled or not

articles/application-gateway/ingress-controller-troubleshoot.md

@@ -313,7 +313,7 @@ armAuth:
 ## 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 --subscription <subscription-uuid> --role Contributor --sdk-auth | base64 -w0" >>
 
 ################################################################################
 # Specify if the cluster is Kubernetes RBAC enabled or not

articles/azure-app-configuration/use-key-vault-references-spring-boot.md

@@ -93,7 +93,7 @@ To add a secret to the vault, you need to take just a few additional steps. In t
 1. In this tutorial, you use a service principal for authentication to Key Vault. To create this service principal, use the Azure CLI [az ad sp create-for-rbac](/cli/azure/ad/sp#az_ad_sp_create_for_rbac) command:
 
     ```azurecli
-    az ad sp create-for-rbac -n "http://mySP" --sdk-auth
+    az ad sp create-for-rbac -n "http://mySP" --role Contributor --sdk-auth
     ```
 
     This operation returns a series of key/value pairs:

articles/azure-arc/kubernetes/create-onboarding-service-principal.md

@@ -21,8 +21,8 @@ Walk through the following steps to learn how to use service principals for conn
 
 Create a new service principal with an informative name that is unique for your Azure Active Directory tenant.
 
-```console
-az ad sp create-for-RBAC --skip-assignment --name "https://azure-arc-for-k8s-onboarding"
+```azurecli
+az ad sp create-for-RBAC --name "https://azure-arc-for-k8s-onboarding"
 ```
 
 **Output:**
@@ -50,7 +50,7 @@ You can limit permissions further by passing in the appropriate `--scope` argume
 | Subscription | `--scope /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333` | Service principal can register cluster in  any resource group under that subscription. |
 | Resource Group | `--scope /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333/resourceGroups/myGroup`  | Service principal can __only__ register clusters in the resource group `myGroup`. |
 
-```console
+```azurecli
 az role assignment create \
     --role 34e09817-6cbe-4d01-b1a2-e0eac5743d41 \      # this is the id for the built-in role
     --assignee 22cc2695-54b9-49c1-9a73-2269592103d8 \  # use the appId from the new SP

articles/azure-netapp-files/azacsnap-installation.md

@@ -109,7 +109,7 @@ Create RBAC Service Principal
 1. Create a service principal using Azure CLI per the following example
 
     ```azurecli-interactive
-    az ad sp create-for-rbac --sdk-auth
+    az ad sp create-for-rbac --role Contributor --sdk-auth
     ```
 
     1. This should generate an output like the following example:

articles/azure-netapp-files/azure-netapp-files-develop-with-rest-api.md

@@ -43,7 +43,7 @@ The REST API specification for Azure NetApp Files is published through [GitHub](
    2. Enter the following command in the Azure CLI: 
 
         ```azurecli
-        az ad sp create-for-rbac --name $YOURSPNAMEGOESHERE
+        az ad sp create-for-rbac --name $YOURSPNAMEGOESHERE --role Contributor
         ```
 
       The command output is similar to the following example:  

articles/azure-netapp-files/develop-rest-api-powershell.md

@@ -36,7 +36,7 @@ The REST API specification for Azure NetApp Files is published through [GitHub](
    2. Enter the following command in the Azure CLI:  
 
       ```azurecli
-      $RBAC_SP = az ad sp create-for-rbac --name <YOURSPNAMEGOESHERE> | ConvertFrom-Json         
+      $RBAC_SP = az ad sp create-for-rbac --name <YOURSPNAMEGOESHERE> --role Contributor | ConvertFrom-Json         
       ```
 
       To display the service principal information, type `$RBAC_SP` and press Enter.

articles/cognitive-services/Computer-vision/spatial-analysis-logging.md

@@ -83,7 +83,7 @@ After setting up Azure Monitor, you will need to create credentials that enable
 > [!NOTE] 
 > This command requires you to have Owner privileges on the subscription. 
 
-```bash
+```azurecli
 # Find your Azure IoT Hub resource ID by running this command. The resource ID  should start with something like 
 # "/subscriptions/b60d6458-1234-4be4-9885-c7e73af9ced8/resourceGroups/..."
 az iot hub list
@@ -430,7 +430,7 @@ Create a new support ticket at the [New support request](https://ms.portal.azure
 
 1. Set **Issue Type** to be `Technical`.
 2. Select the subscription that you are utilizing to deploy the Spatial Analysis container.
-3. Select `My services` and select `Cognitive Services` as the the service.
+3. Select `My services` and select `Cognitive Services` as the service.
 4. Select the resource that you are utilizing to deploy the Spatial Analysis container.
 5. Write a brief description detailing the problem you are facing. 
 6. Select `Spatial Analysis` as your problem type.

articles/cognitive-services/Custom-Vision-Service/logo-detector-mobile.md

@@ -113,7 +113,7 @@ az account set --subscription "<subscription name or subscription id>"
 Then create your service principal. (This process might take some time to finish.)
 
 ```azurecli
-az ad sp create-for-rbac --name <servicePrincipalName> --password <yourSPStrongPassword>
+az ad sp create-for-rbac --name <servicePrincipalName> --role Contributor --password <yourSPStrongPassword>
 ```
 
 Upon successful completion, you should see the following JSON output, including the necessary credentials.