Merge pull request #179437 from jdmartinez36/cliskipassign

1876839: Remove deprecated --skip-assignment parameter

Author: laurabren

articles/aks/configure-kubenet.md

@@ -121,7 +121,7 @@ az network vnet create \
 To allow an AKS cluster to interact with other Azure resources, an Azure Active Directory service principal is used. The service principal needs to have permissions to manage the virtual network and subnet that the AKS nodes use. To create a service principal, use the [az ad sp create-for-rbac][az-ad-sp-create-for-rbac] command:
 
 ```azurecli-interactive
-az ad sp create-for-rbac --skip-assignment
+az ad sp create-for-rbac
 ```
 
 The following example output shows the application ID and password for your service principal. These values are used in additional steps to assign a role to the service principal and then create the AKS cluster:

articles/aks/kubernetes-service-principal.md

@@ -61,10 +61,10 @@ New-AzAksCluster -Name myAKSCluster -ResourceGroupName myResourceGroup
 
 ### [Azure CLI](#tab/azure-cli)
 
-To manually create a service principal with the Azure CLI, use the [az ad sp create-for-rbac][az-ad-sp-create] command. In the following example, the `--skip-assignment` parameter prevents any additional default assignments being assigned:
+To manually create a service principal with the Azure CLI, use the [az ad sp create-for-rbac][az-ad-sp-create] command.
 
 ```azurecli-interactive
-az ad sp create-for-rbac --skip-assignment --name myAKSClusterServicePrincipal
+az ad sp create-for-rbac --name myAKSClusterServicePrincipal
 ```
 
 The output is similar to the following example. Make a note of your own `appId` and `password`. These values are used when you create an AKS cluster in the next section.

articles/aks/limit-egress-traffic.md

@@ -423,7 +423,7 @@ A cluster identity (managed identity or service principal) is used by AKS to cre
 ```azurecli
 # Create SP and Assign Permission to Virtual Network
 
-az ad sp create-for-rbac -n "${PREFIX}sp" --skip-assignment
+az ad sp create-for-rbac -n "${PREFIX}sp"
 ```
 
 Now replace the `APPID` and `PASSWORD` below with the service principal appid and service principal password autogenerated by the previous command output. We'll reference the VNET resource ID to grant the permissions to the service principal so AKS can deploy resources into it.

articles/aks/update-credentials.md

@@ -64,10 +64,10 @@ Now continue on to [update AKS cluster with new service principal credentials](#
 
 If you chose to update the existing service principal credentials in the previous section, skip this step. Continue to [update AKS cluster with new service principal credentials](#update-aks-cluster-with-new-service-principal-credentials).
 
-To create a service principal and then update the AKS cluster to use these new credentials, use the [az ad sp create-for-rbac][az-ad-sp-create] command. In the following example, the `--skip-assignment` parameter prevents any additional default assignments being assigned:
+To create a service principal and then update the AKS cluster to use these new credentials, use the [az ad sp create-for-rbac][az-ad-sp-create] command.
 
 ```azurecli-interactive
-az ad sp create-for-rbac --skip-assignment
+az ad sp create-for-rbac
 ```
 
 The output is similar to the following example. Make a note of your own `appId` and `password`. These values are used in the next step.

articles/aks/virtual-nodes-cli.md

@@ -83,10 +83,10 @@ az network vnet subnet create \
 
 To allow an AKS cluster to interact with other Azure resources, a cluster identity is used. This cluster identity can be automatically created by the Azure CLI or portal, or you can pre-create one and assign additional permissions. By default, this cluster identity is a managed identity. For more information, see [Use managed identities](use-managed-identity.md). You can also use a service principal as your cluster identity. The following steps show you how to manually create and assign the service principal to your cluster.
 
-Create a service principal using the [az ad sp create-for-rbac][az-ad-sp-create-for-rbac] command. The `--skip-assignment` parameter limits any additional permissions from being assigned.
+Create a service principal using the [az ad sp create-for-rbac][az-ad-sp-create-for-rbac] command.
 
 ```azurecli-interactive
-az ad sp create-for-rbac --skip-assignment
+az ad sp create-for-rbac
 ```
 
 The output is similar to the following example:

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

@@ -39,7 +39,7 @@ Follow the steps below to create an Azure Active Directory (AAD) [service princi
 
 1. Create AD service principal ([Read more about Azure RBAC](../role-based-access-control/overview.md)):
     ```azurecli
-    az ad sp create-for-rbac --skip-assignment -o json > auth.json
+    az ad sp create-for-rbac -o json > auth.json
     appId=$(jq -r ".appId" auth.json)
     password=$(jq -r ".password" auth.json)
     ```

articles/cognitive-services/containers/azure-kubernetes-recipe.md

@@ -173,7 +173,7 @@ The following steps are needed to get the required information to connect your c
 1. Create service principal.
 
     ```azurecli-interactive
-    az ad sp create-for-rbac --skip-assignment
+    az ad sp create-for-rbac
     ```
 
     Save the results `appId` value for the assignee parameter in step 3, `<appId>`. Save the `password` for the next section's client-secret parameter `<client-secret>`.

articles/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md

@@ -84,14 +84,14 @@ You can also register resource providers via the `az cli`. For more information,
 
 1. To create a service principal, use the following command via the `az cli`.
 
-    `az ad sp create-for-rbac --skip-assignment --name "<Informative name for service principal>"`  
+    `az ad sp create-for-rbac --name "<Informative name for service principal>"`  
 
     For information on how to log into the `az cli`, [Start Cloud Shell in Azure portal](../cloud-shell/quickstart-powershell.md#start-cloud-shell)
 
     Here is an example. 
 
     ```azurecli
-    PS /home/user> az ad sp create-for-rbac --skip-assignment --name "https://azure-arc-for-ase-k8s"
+    PS /home/user> az ad sp create-for-rbac --name "https://azure-arc-for-ase-k8s"
     {
       "appId": "aa8a082e-0fa1-4a82-b51c-e8b2a9fdaa8b",
       "displayName": "azure-arc-for-ase-k8s",

articles/key-vault/general/manage-with-cli2.md

@@ -195,7 +195,7 @@ For detailed steps on registering an application with Azure Active Directory you
 To register an application in Azure Active Directory:
 
 ```azurecli
-az ad sp create-for-rbac -n "MyApp" --password "hVFkk965BuUv" --skip-assignment
+az ad sp create-for-rbac -n "MyApp" --password "hVFkk965BuUv"
 # If you don't specify a password, one will be created for you.
 ```
 

articles/sentinel/sap-solution-deploy-snc.md

@@ -50,7 +50,7 @@ spname=<sp-name>
 kvname=<keyvaultname>
 # Optional when Azure MI not enabled - Create sp user for AZ cli connection, save details for env.list file
 
-az ad sp create-for-rbac –name $spname
+az ad sp create-for-rbac –name $spname --role Contributor
 
 SpID=$(az ad sp list –display-name $spname –query “[].appId” --output tsv