Get-AzStorageAccount : Your Azure credentials have not been set up or have expired, please run Connect-AzAccount to set up your Azure credentials.

[justPaulo]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.

Summary

This error relates 100% with VS Code because the one-liner pwsh statement only generates errors when executed in VS Code. Executing it pwsh prompt or PowerShellISE works just great as expected.

PowerShell Version

Name                           Value                                                                                                                                      
----                           -----                                                                                                                                      
PSVersion                      5.1.18362.1801                                                                                                                             
PSEdition                      Desktop                                                                                                                                    
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                                                                    
BuildVersion                   10.0.18362.1801                                                                                                                            
CLRVersion                     4.0.30319.42000                                                                                                                            
WSManStackVersion              3.0                                                                                                                                        
PSRemotingProtocolVersion      2.3                                                                                                                                        
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.61.2
6cba118ac49a1b88332f312a8f67186f7f3c1643
x64

Extension Version

ms-vscode.powershell@2021.10.1

Steps to Reproduce

Screen.Recording.2021-10-26.at.19.58.40.mp4

Visuals

Screen.Recording.2021-10-26.at.19.58.40.mp4

Logs

1635329024-b39e1c8e-7939-492d-a531-aa7c87b6354c1635329022195.zip

[justPaulo]

In reference to microsoft/vscode#135847

[andyleejordan]

Similar to #3633, it looks like the Azure library's dependencies have some interference with the Editor Services library's dependencies. In Windows PowerShell, this is bound to happen. Can you please test this with the much more up to date PowerShell 7 and let us know if it continues to repro?

[andyleejordan]

Executing it pwsh prompt

Looks like you have already tested it in PowerShell 7, and it works! Great. Please change your Code's settings to use pwsh AKA PowerShell 7 instead of Windows PowerShell. While we do our best to support PowerShell 5.1, it has many of these issues that are difficult if not impossible to fix.

You can use the command "PowerShell: Show Session Menu" to choose PowerShell 7, and if that works, you can update the setting "PowerShell Default Version" so that it's used by default 😁

[justPaulo]

Similar to #3633, it looks like the Azure library's dependencies have some interference with the Editor Services library's dependencies. In Windows PowerShell, this is bound to happen. Can you please test this with the much more up to date PowerShell 7 and let us know if it continues to repro?

This is a managed machine, no possibility to test PowerShell 7.x

[andyleejordan]

The good news is that PowerShell 7 will soon be available via Windows Update and so should become available even on managed machines! PowerShell 5.1 is in maintenance mode, and this extension's compatibility with it is truly best-effort, as it doesn't support many features necessary for better support.

[andyleejordan]

@justPaulo I'm going to mark this as a duplicate because I'm pretty sure it's the same issue as #3633.