You only get the error when you specify -AsSecureString, otherwise it works fine and has been using a secure string by default for a while now. The warning is stupid and misleading.
Comments
Log in with your Bluesky account to leave a comment
Not anymore. Remember that the warning was that they would be changing things and we should add the -AsSecureString. They've made the update now, and even without it I get the token error.
Comments