Closed teto closed 1 year ago
Thank you for opening this issue, we will look into it.
Similar to https://github.com/Azure/azure-cli/issues/16498#issuecomment-836500907.
Judging by the call stack, the site-packages
is installed under /nix/store/680adxjlwzlc498mplx3pmc4kwljxfyn-python3.10-xxx
, so this is neither an official python, nor an official Azure CLI package.
You have azure-mgmt-authorization-3.0.0
installed, but azure-cli
2.53.0 requires
Please make sure the dependences of Azure CLI are satisfied.
For documentation on using Azure CLI with Service Principal, please see https://learn.microsoft.com/en-us/cli/azure/azure-cli-sp-tutorial-1.
I could not find how to create a service principal and give it contributor rights from the portal
You may create a support ticket for Azure Portal related problems at https://azure.microsoft.com/en-us/support/create-ticket.
Indeed, I've just checked and it works if I use azure-mgmt-authorization 4.0. I will see what I can on the nixpkgs side to prevent this wrong packaging sry for the noise and thanks for the fast answer.
Describe the bug
I could not find how to create a service principal and give it contributor rights from the portal so I resorted to the CLI but when trying to create a service principal with contributor role (because I want it to be able to create resource groups, via pulumi), the client fails.
Related command
az role assignment create --assignee APP_ID --role Contributor --scope /subscriptions/MY_SUBSCRIPTION --debug
Errors
Issue script & Debug output
Expected behavior
Success ?
Environment Summary
Additional context
I want to create credentials to be able to deploy new resource groups via pulumi. I am new to azure and I've got a hell of a time to achieve just that. The portal blinks with errors asking me to log again when I look at some "app registration" page and while everything recommands to use principals, the move to microsoft entra seems to have outdated even official docs and I can't find where to update the "service principal" credentials in the portal. So I resorted to the CLI with the previous problem.
Note that I tried an alternative command with the same result