Can't delete azure cloud shell #13352

Closed
opened 2026-01-31 03:40:25 +00:00 by claunia · 3 comments
Owner

Originally created by @matsmcp on GitHub (Apr 7, 2021).

Windows Terminal version (or Windows build number)

10.0.20303.1 1.7.210226002

Other Software

No response

Steps to reproduce

Try to delete the azure cloud shell

Expected Behavior

The Azure cloud shell configuration gets deleted

Actual Behavior

It cant be deleted since it's built in

For Customers that are legally prevented from using cloud services it's rather bad to have a mandatory config to a MS cloud service. Therefore it should be possible to delete it.

IT's also rather unpractical for AWS or Google users.

Originally created by @matsmcp on GitHub (Apr 7, 2021). ### Windows Terminal version (or Windows build number) 10.0.20303.1 1.7.210226002 ### Other Software _No response_ ### Steps to reproduce Try to delete the azure cloud shell ### Expected Behavior The Azure cloud shell configuration gets deleted ### Actual Behavior It cant be deleted since it's built in For Customers that are legally prevented from using cloud services it's rather bad to have a mandatory config to a MS cloud service. Therefore it should be possible to delete it. IT's also rather unpractical for AWS or Google users.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 03:40:26 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 7, 2021):

The Azure Cloud Shell is a "dynamic" profile, which can be hidden with

"hidden": true
@zadjii-msft commented on GitHub (Apr 7, 2021): The Azure Cloud Shell is a ["dynamic" profile](https://docs.microsoft.com/en-us/windows/terminal/dynamic-profiles#hide-a-profile), which can be hidden with ```json "hidden": true ```
Author
Owner

@matsmcp commented on GitHub (Apr 8, 2021):

@zadjii-msft
Hiding it doesn't prevent it from being in the config and so on so that didn't meet the need but you did solve it anyway by mentioning and linking dynamic profiles.

By using "disabledProfileSources": ["Windows.Terminal.Azure"] in the config file we can prevent it from being created so that will solve the issue :)

@matsmcp commented on GitHub (Apr 8, 2021): @zadjii-msft Hiding it doesn't prevent it from being in the config and so on so that didn't meet the need but you did solve it anyway by mentioning and linking dynamic profiles. By using "disabledProfileSources": ["Windows.Terminal.Azure"] in the config file we can prevent it from being created so that will solve the issue :)
Author
Owner

@LoganDark commented on GitHub (Apr 23, 2021):

On the newest version of Windows Terminal, it looks like your global settings are initialized with the defaults, and you can just completely delete the azure shell section and it disappears forever.

Edit: Nevermind, looks like that only affects the new tab menu.... disabledProfileSources is indeed the correct way to solve this.

@LoganDark commented on GitHub (Apr 23, 2021): ~~On the newest version of Windows Terminal, it looks like your global settings are initialized with the defaults, and you can just completely delete the azure shell section and it disappears forever.~~ Edit: Nevermind, looks like that only affects the new tab menu.... disabledProfileSources is indeed the correct way to solve this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13352