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

Azure Cloud Shell to connect to Sovereign Clouds #5026

New Issue
Open
opened 2026-01-31 00:03:20 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 00:03:20 +00:00
Owner
Copy Link

Originally created by @davemedvitz on GitHub (Nov 15, 2019).

The Azure Cloud Shell component needs to be able to connect to Azure Clouds other than the default Commercial cloud. Currently the relevant URL endpoints are hard coded to Commercial.

Originally created by @davemedvitz on GitHub (Nov 15, 2019). The Azure Cloud Shell component needs to be able to connect to Azure Clouds other than the default Commercial cloud. Currently the relevant URL endpoints are hard coded to Commercial.
claunia added the Issue-TaskProduct-TerminalArea-AzureShell labels 2026-01-31 00:03:20 +00:00
claunia commented 2026-01-31 00:03:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 15, 2019):

Yeah, fair point. Marking up for the backlog. 😄 Thanks

@DHowett-MSFT commented on GitHub (Nov 15, 2019): Yeah, fair point. Marking up for the backlog. :smile: Thanks
claunia commented 2026-01-31 00:03:21 +00:00
Author
Owner
Copy Link

@jmcarthurcorr commented on GitHub (Nov 18, 2019):

Giving a +1 to this issue. Logging in with portal.azure.us tenant gives the dreaded

AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: '245e1dee-74ef-4257-a8c8-8208296e1dfd'.

@jmcarthurcorr commented on GitHub (Nov 18, 2019): Giving a +1 to this issue. Logging in with portal.azure.us tenant gives the dreaded > AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: '245e1dee-74ef-4257-a8c8-8208296e1dfd'.
claunia commented 2026-01-31 00:03:21 +00:00
Author
Owner
Copy Link

@petkahl commented on GitHub (Jul 31, 2020):

I see from the duplicate issue that this is waiting on compliance as much as code. Is there anything those of us on the outside could do to help (write code and queue up a PR, etc?) or is it really just a matter of waiting for the compliance/legal part to be handled?

@petkahl commented on GitHub (Jul 31, 2020): I see from the duplicate issue that this is waiting on compliance as much as code. Is there anything those of us on the outside could do to help (write code and queue up a PR, etc?) or is it really just a matter of waiting for the compliance/legal part to be handled?
claunia commented 2026-01-31 00:03:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

This is all compliance stuff; the real work involved is in the MS first-party identity portal where we have to onboard to the sovereign clouds. That should be quick once we get signoff on security and accessibility for our service 😄

@DHowett commented on GitHub (Jul 31, 2020): This is all compliance stuff; the real work involved is in the MS first-party identity portal where we have to onboard to the sovereign clouds. That should be quick once we get signoff on security and accessibility for our service :smile:
claunia commented 2026-01-31 00:03:21 +00:00
Author
Owner
Copy Link

@davemedvitz commented on GitHub (Dec 8, 2020):

Do know if there is progress being made on the compliance pieces?

@davemedvitz commented on GitHub (Dec 8, 2020): Do know if there is progress being made on the compliance pieces?
claunia commented 2026-01-31 00:03:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 8, 2020):

Unfortunately, I don't have any news to share on that front.

@DHowett commented on GitHub (Dec 8, 2020): Unfortunately, I don't have any news to share on that front.
claunia commented 2026-01-31 00:03:22 +00:00
Author
Owner
Copy Link

@hphungnal commented on GitHub (Jun 7, 2021):

Hello, just checking in to see if there is any update on this issue? Would love for it to work with https://microsoft.com/deviceloginus
Thanks!

@hphungnal commented on GitHub (Jun 7, 2021): Hello, just checking in to see if there is any update on this issue? Would love for it to work with https://microsoft.com/deviceloginus Thanks!
claunia commented 2026-01-31 00:03:22 +00:00
Author
Owner
Copy Link

@benatsb commented on GitHub (Apr 25, 2022):

Hello, any updates on this capability?

@benatsb commented on GitHub (Apr 25, 2022): Hello, any updates on this capability?
claunia commented 2026-01-31 00:03:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 25, 2022):

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?
image
That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

@zadjii-msft commented on GitHub (Apr 25, 2022): Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️
claunia commented 2026-01-31 00:03:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 23, 2022):

The crazy idea from sync: Rather than onboarding the Terminal's AppID onto each cloud ourselves, we enable configuration options s.t. the user can specify their own AppID. That way, each entity could onboard and approve the Terminal themselves, synthesize their own appid for the cloud shell, and then users would just add that string to their settings file.

It's more burden on the users, for sure, but would allow each individual cloud the ability to control access to the azure cloud shell themselves.

@zadjii-msft commented on GitHub (May 23, 2022): The crazy idea from sync: Rather than onboarding the Terminal's AppID onto each cloud ourselves, we enable configuration options s.t. the user can specify their own AppID. That way, each entity could onboard and approve the Terminal themselves, synthesize their own appid for the cloud shell, and then users would just add that string to their settings file. It's more burden on the users, for sure, but would allow each individual cloud the ability to control access to the azure cloud shell themselves.
claunia commented 2026-01-31 00:03:23 +00:00
Author
Owner
Copy Link

@jamesseiwert commented on GitHub (Aug 30, 2023):

Is there any update on this? I was hoping with the cross cloud access now this would be resolved. I also like the idea from @zadjii-msft about enabling configuration options as a secondary idea. Most microsoft apps can auth can handle both commercial and goc clouds now

@jamesseiwert commented on GitHub (Aug 30, 2023): Is there any update on this? I was hoping with the cross cloud access now this would be resolved. I also like the idea from @zadjii-msft about enabling configuration options as a secondary idea. Most microsoft apps can auth can handle both commercial and goc clouds now
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
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#5026
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?