Closed msgerneu closed 6 years ago
@msgerneu Hey Gerrit, would you mind updating to the latest version of AzureRM
and seeing if you're able to reproduce this error? We made some changes to context persistence in the recent versions of AzureRM.Profile
that should fix the exception that you're seeing.
Closing for inactivity. @msgerneu Please reopen if you are able to follow the steps above and are still running into this issue.
Description
At a specific point of time, the command is not working anymore. After this, only working solution is:
Disabling Context Save with Disable-AzureRmContextAutoSave helps in making the time until it is happening again "longer". Without, it appears after one week, without it takes round about a month or more.
Script/Steps for Reproduction
This is a time based behaviour, no steps can be provided.
Set-AzureRMContext -Subscription just returns same Sub as before, like ignoring the input of Subscription
Module Version
Environment Data