Authentication failed to Azure for Azure Cloud Shell #8341

Closed
opened 2026-01-31 01:26:54 +00:00 by claunia · 4 comments
Owner

Originally created by @sakaldeepyadav on GitHub (May 20, 2020).

Authentication failed to Azure Cloud Shell on Windows Terminal. I have tried different accounts. I am able to authenticate using the same credentials on normal PowerShell but it fails on here as below.
image

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

Originally created by @sakaldeepyadav on GitHub (May 20, 2020). Authentication failed to Azure Cloud Shell on Windows Terminal. I have tried different accounts. I am able to authenticate using the same credentials on normal PowerShell but it fails on here as below. ![image](https://user-images.githubusercontent.com/34697487/82455639-1162e380-9aab-11ea-8b1b-ba86dac60659.png) <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 01:26:54 +00:00
Author
Owner

@johnem-msft commented on GitHub (May 20, 2020):

I'm seeing this too ... but when I perform a task like: az account list I get output making think that it is really connected .... (or is this just cach'd info?)

Does choosing n instead of 0 and authenticating again have any effect?

@johnem-msft commented on GitHub (May 20, 2020): I'm seeing this too ... but when I perform a task like: az account list I get output making think that it is really connected .... (or is this just cach'd info?) Does choosing **n** instead of **0** and authenticating again have any effect?
Author
Owner

@sakaldeepyadav commented on GitHub (May 20, 2020):

az account list does give output but if you run az vm list then you won't get anything so it giving cached info.

Tried authenticating many time but no luck.

@sakaldeepyadav commented on GitHub (May 20, 2020): az account list does give output but if you run az vm list then you won't get anything so it giving cached info. Tried authenticating many time but no luck.
Author
Owner

@DHowett commented on GitHub (May 21, 2020):

Thanks for reporting this! It looks like this has the same root cause as #2371 (we're not handling one of the azure shell messages properly), so I'm going to close it as a duplicate.

/dup #2371.

@DHowett commented on GitHub (May 21, 2020): Thanks for reporting this! It looks like this has the same root cause as #2371 (we're not handling one of the azure shell messages properly), so I'm going to close it as a duplicate. /dup #2371.
Author
Owner

@ghost commented on GitHub (May 21, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 21, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8341