starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Azure Shell Reports Unknown Id Instead of Tenant ID #21755

New Issue
Open
opened 2026-01-31 07:53:56 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:53:56 +00:00
Owner
Copy Link

Originally created by @CheetahChrome on GitHub (May 23, 2024).

Originally assigned to: @PankajBhojwani on GitHub.

Windows Terminal version

1.20.11271.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

  1. Open Azure Cloud Shell in Terminal
  2. Follow steps for reported authentication.
  3. Select one of the provided tenants
  4. Inspect the error message and note that the id reported is not tenant id of the tenants listed.

Expected Behavior

I expect that the error message should report the actual tenant id of the target tenant being logged into. Or that the id being reported, if different from any in the list, tells a user what the origination or name of that id is being reported along with the id. This unknown Id, Account(?) is unclear.

Actual Behavior

I run the Azure Cloud Shell (1) and follow the authentication steps outside the shell (2). Once the outside steps are successfully completed, I am presented with the tenants I want to log into for that session (3). Upon picking a tenant, I am presented with an MFA error and an Id for reference. The Id given is not either of the tenant ids I am attempting to log into. What is this Id?

See the reported Id staring with 797....

image

Here are the actual tenant ids and none of them are in the 797... realm.

image

Note that I can login in a PowerShell shell using

image

Note the actual failure is also an issue and appears to have been reported

Azure Cloud Shell Fails to connect when you have multiple tenants and 1 of them requires MFA · Issue #12458 · microsoft/terminal · GitHub

Originally created by @CheetahChrome on GitHub (May 23, 2024). Originally assigned to: @PankajBhojwani on GitHub. ### Windows Terminal version 1.20.11271.0 ### Windows build number 10.0.22621.0 ### Other Software _No response_ ### Steps to reproduce 1. Open `Azure Cloud Shell` in Terminal 2. Follow steps for reported authentication. 3. Select one of the provided tenants 4. Inspect the error message and note that the id reported is not tenant id of the tenants listed. ### Expected Behavior I expect that the error message should report the *actual* tenant id of the target tenant being logged into. Or that the id being reported, if different from any in the list, tells a user **what the origination or name** of that id is being reported along with the id. This unknown Id, Account(?) is unclear. ### Actual Behavior I run the Azure Cloud Shell (1) and follow the authentication steps outside the shell (2). Once the outside steps are successfully completed, I am presented with the tenants I want to log into for that session (3). Upon picking a tenant, I am presented with an MFA error and an `Id` for reference. The `Id` given is not either of the tenant ids I am attempting to log into. What is this `Id`? See the reported Id staring with `797...`. ![image](https://github.com/microsoft/terminal/assets/1110966/eaae4a04-74e8-4fec-8bc2-e7e56fe9f91b) Here are the actual tenant ids and none of them are in the `797...` realm. ![image](https://github.com/microsoft/terminal/assets/1110966/c8101e61-1e11-4c4d-b68d-6c99fe6d5352) Note that I can login in a PowerShell shell using ![image](https://github.com/microsoft/terminal/assets/1110966/203d90eb-4956-4958-b180-6f795cbd2357) Note the actual failure is also an issue and appears to have been reported [Azure Cloud Shell Fails to connect when you have multiple tenants and 1 of them requires MFA · Issue #12458 · microsoft/terminal · GitHub](https://github.com/microsoft/terminal/issues/12458)
claunia added the Issue-BugProduct-TerminalArea-AzureShell labels 2026-01-31 07:53:57 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-AzureShell Issue-Bug Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21755
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?