Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error building AzureRM Client: Error populating Client ID from the Azure CLI: No Authorization Tokens were found #3191

Closed
aswinraaj opened this issue Apr 5, 2019 · 2 comments

Comments

@aswinraaj
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

0.11.13

Affected Resource(s)

  • provider.azurerm

Terraform Configuration Files

Debug Output

Panic Output

Expected Behavior

terraform plan should work as expected

Actual Behavior

terraform plan fails with the following error : * provider.azurerm: Error building AzureRM Client: Error populating Client ID from the Azure CLI: No Authorization Tokens were found - please re-authenticate using az login.

Steps to Reproduce

  1. terraform plan

Important Factoids

References

  • #0000
@tombuildsstuff
Copy link
Contributor

hi @aswinraaj

Thanks for opening this issue :)

The error you're seeing above is because you're attempting to use a Service Principal via the Azure CLI which we don't support. Instead we support using either the Azure CLI with a user account, or by using a Service Principal specified either via Environment Variables or inline (more details can be found here). Would you be able to take a look and see if that works for you?

Since this is a question about Terraform Configuration rather than a bug in Terraform I'm going to close this issue for the moment - however please let us know if that doesn't work for you and we'll take another look.

Thanks!

@ghost
Copy link

ghost commented May 6, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators May 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants