Connect-AzAccount does not work in PowerShell Integrated Console

[markr-rpc]

Note, the solution is posted in the Azure PowerShell module. They have a temporary engineering built of the Az.Accounts module, with version 2.6.2 with instructions on how to install. The link is here:
Azure/azure-powershell#16340

---

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 have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.

Summary

I have setup VS Code on 2 new computers and they are both having the same issue. I have the Integrated PowerShell Console set to load Windows PowerShell 5.1.
When I run a script, the PowerShell Integrated Console (PIC) gives the error shown below. Even if I type the Connect-AzAccount manually in the PIC I get the same error. However, if I switch the terminal to Windows PowerShell (not Integrated), the command works fine (it loads the login prompt in an external PowerShell window). But when I run any script it automatically switches back to the PIC. Note that PowerShell Core works fine, it loads the login prompt in a browser window.

I have one older computer running Windows 10 that has had VS Code configured for years that is not showing the problem. I tried copying all the settings in the %appdata%, but it did not solve the problem.

Error:
WARNING: Unable to acquire token for tenant 'organizations' with error 'Method 'GetTokenAsync' in type 'Azure.Identity.InteractiveBrowserCredential' from assembly 'Azure.Identity, Version=1.4.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8' does not have an implementation.'
Connect-AzAccount : Method 'GetTokenAsync' in type 'Azure.Identity.InteractiveBrowserCredential' from assembly 'Azure.Identity, Version=1.4.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8' does not have an
implementation.
At line:1 char:1

• Connect-AzAccount

•   + CategoryInfo          : CloseError: (:) [Connect-AzAccount], TypeLoadException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.ConnectAzureRmAccountCommand
  
  

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22000.282
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.282
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

Install VS Code
Install PowerShell Az modules (Install-Module -Name Az)
Set the default console to be Windows PowerShell 5.1 so that the PowerShell Integrated Console runs with Windows PowerShell.
Type the command in the PowerShell Integrated Console window or put the command in a script and run: Connect-AzAccount

Visuals

Logs

logs.zip

[andyleejordan]

Does this reproduce with PowerShell 7? If not, it's likely a GAC-dependency issue like several others where the error is "method not found" and unfortunately may not be resolvable within the constraints of PowerShell 5.1.

[markr-rpc]

It does work with PowerShell 7. Unfortunately, I have some Windows forms built into the PowerShell scripts so I can't use PowerShell 7. It is working on 2 other Windows 10 computers that I had installed VS Code back in 2019, which is running VS Code version 1.61.1.
I can't figure out why the old ones work and the new installs don't work. I tried new installs on both Windows 10 and Windows 11, with current version of VS Code and version 1.60.x, everything fails. It only fails in the Integrated console, not the regular console.
Is there any settings somewhere other than in $AppData%\Code?

[andyleejordan]

Are your old installations using an old version of the extension? My guess is dependencies were updated and now we have a dependency which conflicts with that module. Unfortunately in Windows PowerShell the GAC prevents us from isolating those dependencies (which we successfully do in PowerShell Core).

[andyleejordan]

Unfortunately, I have some Windows forms built into the PowerShell scripts so I can't use PowerShell 7.

The good news is that Windows Forms do work in PowerShell 7, and we even have a regression test about running code in the integrated console that utilizes Forms.

My recommendation would be to open a separate powershell.exe console in Code that is not the integrated console, which will isolate you away from any interference caused by the editor services being loaded in that instance.

[markr-rpc]

The old machines are running PowerShell extension v2021.10.1 and VS Code 1.16.1. They are working fine with the integrated console.
I am not sure what you mean by "open a powershell.exe console in Code that is not the integrated console". When I debug, I have VS Code start a new temporary console in order to reload my classes. It always starts the PowerShell Integrated Console. Even if I turn that off, if I am in the PowerShell terminal that works, as soon as I run my script it switches to the integrated console to run.

Good news about PowerShell Core 7 that I didn't know, I thought it was a generic shell and would only support things that run on all platforms (linux, mac, windows). I also found an extension for Visual Studio 2019 that will run my scripts in PowerShell 5.1. I like the interface for VS Code better though, I use color schemes for various messages in my scripts and VS2019 doesn't show colors when debugging.

[andyleejordan]

Debugging in VS Code will always use the integrated console, there's no way around that, as the editor services are required for debugging (that library is what hooks up the VS Code Debugger to the PowerShell debugger). Can you run your script in PowerShell Core, or is Windows PowerShell a hard requirement for you?