-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Import-AzContext - Previously create Json file won't connect to Azure. #7554
Comments
Hum!! I was polishing some demos when I came up with this issue. Thinking more... What about if the issue more with the Save-AzContext? As it's the file was newly created with that cmdlet. :) |
The issue is here: #7456 We will fix it, but out of curiosity, whey are you uaing save/import context rather than the context autosave feature. If you just turn on context autosave, your contexts are automatically saved and are available every time you open a new session |
Closing as duplicate of #7456 |
Hi @markcowl, Hum!! Autosave! I'll try that one. Thanks, |
Hi @markcowl, The AutoSave works! Thanks, |
Description
I use the Import-AzContext to streamline my azure connection by using the Json file I create after using the Connect-AzAccount cmdlet.
Now, I've created a new Json file using the Save-AzContext, then realized that is not accepting the credential stored in the file
Script/Steps for Reproduction
Here's the steps reproduce:
Module Version
Environment Data
Debug Output
Below is the information:
Observation
Just an FYI
I'm saying that's the issue is with the Import-AzContext because I can use the "Connect-AzAccount" to connect to Azure and the continue working without any issues.
The text was updated successfully, but these errors were encountered: