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

Feature Request: Specific Azure Tenant per Cloud Shell profile #8306

New Issue
Closed
opened 2026-01-31 01:26:07 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:26:07 +00:00
Owner
Copy Link

Originally created by @yaakov-h on GitHub (May 20, 2020).

I belong to multiple Azure tenancies / Azure ADs, and when I open a Cloud Shell profile it asks every time which one I want to log in to, like so:

Tenant 0: First Tenant (tenant1.com.au)
Tenant 1: Second Tenant (tenant2.com.au)
Please enter the desired tenant number.
Enter n to login with a new account
Enter r to remove the above saved connection settings.
>

I think it would be great if I could specify the tenant in the profile (as defined in settings.json) so that I can open a Cloud Shell directly using wt or the new-tab UI and have it connect automatically to the Azure tenant that I want.

I would expect to be able to do something like this to skip the tenancy selection dialog:

{
    "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
    "hidden": false,
    "name": "Azure Cloud Shell (Tenant1)",
    "source": "Windows.Terminal.Azure",
    "tenant": "{my-first-azure-ad-tenant-guid-here}"
},
{
    "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
    "hidden": false,
    "name": "Azure Cloud Shell (Tenant2)",
    "source": "Windows.Terminal.Azure",
    "tenant": "{my-second-azure-ad-tenant-guid-here}"
}

(probably with different profile GUIDs though, I guess)

Originally created by @yaakov-h on GitHub (May 20, 2020). I belong to multiple Azure tenancies / Azure ADs, and when I open a Cloud Shell profile it asks every time which one I want to log in to, like so: > Tenant 0: First Tenant (tenant1.com.au) Tenant 1: Second Tenant (tenant2.com.au) Please enter the desired tenant number. Enter n to login with a new account Enter r to remove the above saved connection settings. \> I think it would be great if I could specify the tenant in the profile (as defined in settings.json) so that I can open a Cloud Shell directly using `wt` or the new-tab UI and have it connect automatically to the Azure tenant that I want. I would expect to be able to do something like this to skip the tenancy selection dialog: ``` { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell (Tenant1)", "source": "Windows.Terminal.Azure", "tenant": "{my-first-azure-ad-tenant-guid-here}" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell (Tenant2)", "source": "Windows.Terminal.Azure", "tenant": "{my-second-azure-ad-tenant-guid-here}" } ``` (probably with different profile GUIDs though, I guess)
claunia added the Issue-TaskResolution-DuplicateProduct-TerminalArea-AzureShell labels 2026-01-31 01:26:07 +00:00
claunia commented 2026-01-31 01:26:08 +00:00
Author
Owner
Copy Link

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

This sounds like a great idea. I'd think that this is sorta related to #5311, but probably different enough. We should probably get a spec going for outlining some improvements to the ACS connection.

@zadjii-msft commented on GitHub (May 20, 2020): This sounds like a great idea. I'd think that this is sorta related to #5311, but probably different enough. We should probably get a spec going for outlining some improvements to the ACS connection.
claunia commented 2026-01-31 01:26:08 +00:00
Author
Owner
Copy Link

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

Thanks for the request! I think this is a /dupe of #5311, though with more information. I'm going to move your comment over there.

@DHowett commented on GitHub (May 21, 2020): Thanks for the request! I think this is a /dupe of #5311, though with more information. I'm going to move your comment over there.
claunia commented 2026-01-31 01:26:08 +00:00
Author
Owner
Copy Link

@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.
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-Task Product-Terminal Resolution-Duplicate
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#8306
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?