You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO: Scanning...
Do you want to run software from this untrusted publisher?
File C:\Users\user\Documents\PowerShell\Modules\Az.Accounts\2.12.5\Accounts.format.ps1xml is published by CN=Microsoft Corporation,
O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted on your system. Only run scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is "D"):
Do you want to run software from this untrusted publisher?
File C:\Users\user\Documents\PowerShell\Modules\Az.Accounts\2.12.5\Accounts.generated.format.ps1xml is published by CN=Microsoft
Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted on your system. Only run scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is "D"):
Failed to perform Auto-login: PSContextCredentialInvalid output while retrving token.
Have you found a mitigation/solution?
Running the shell using pwsh -ExecutionPolicy Bypass, but that's not a great option.
Note that the module works fine when using it directly (e.g. calling Get-AzAccessToken).
The text was updated successfully, but these errors were encountered:
@nakulkar-msft I'm pretty sure this error is because of #2491. On my machine the modules are only installed for PowerShell 7 and azcopy tried to launch PowerShell 5. Please prefer using pwsh over powershell even on Windows, or try to detect the current shell.
Which version of the AzCopy was used?
10.22.0
Which platform are you using?
Windows
What command did you run?
What problem was encountered?
Have you found a mitigation/solution?
Running the shell using
pwsh -ExecutionPolicy Bypass
, but that's not a great option.Note that the module works fine when using it directly (e.g. calling
Get-AzAccessToken
).The text was updated successfully, but these errors were encountered: