New-AzAksCluster cluster fails to use the Service principal provided as input using the credentials parameter
The credentials being used as input are distinct than the user that execute the cmdlet, but both have the right permissions over the subscription. The credential permissions were verified by creating the cluster using the arm template approach.
WARNING: Upcoming breaking changes in the cmdlet 'New-AzAksCluster' :
The cmdlet 'New-AzAksCluster' is replacing this cmdlet.
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
VERBOSE: Cluster does not exist.
VERBOSE: Cluster is new.
VERBOSE: Performing the operation "Creating a managed Kubernetes cluster." on target "foobar in aksdemo01".
VERBOSE: Preparing for deployment of your managed Kubernetes cluster.
VERBOSE: Using location eastus2 from the resource group aksdemo01.
VERBOSE: Using DNS name prefix patit20b9.
VERBOSE: Fetching SSH public key from file C:\Users\auser\.ssh\id_rsa.pub
VERBOSE: No Service Principal found in C:\Users\auser\.azure\acsServicePrincipal.json for this subscription. Creating a new Service Principal.
New-AzAksCluster: Operation returned an invalid status code 'Forbidden'
Description
New-AzAksCluster cluster fails to use the Service principal provided as input using the credentials parameter
The credentials being used as input are distinct than the user that execute the cmdlet, but both have the right permissions over the subscription. The credential permissions were verified by creating the cluster using the arm template approach.
Steps to reproduce
Environment data
Module versions
Debug output
Error output