Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an easy way to disable / remove Azure Cloud Shell from Terminal #17964

Closed
sboehle opened this issue Sep 26, 2024 · 1 comment · Fixed by #18009
Closed

Provide an easy way to disable / remove Azure Cloud Shell from Terminal #17964

sboehle opened this issue Sep 26, 2024 · 1 comment · Fixed by #18009
Assignees
Labels
Area-Settings Issues related to settings and customizability, for console or terminal In-PR This issue has a related PR Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal.

Comments

@sboehle
Copy link

sboehle commented Sep 26, 2024

Description of the new feature/enhancement

There are enterprise customers need to disable Azure Cloud Shell for their whole environment. At the moment the only known way is to use a json file. This is user specific and has to be created for each user in his profile. That is not a possible way for an enterprise environment. This feature request will be for an easy way to disable Azure Cloud Shell using a Regkey or a GPO.

Proposed technical implementation details (optional)

When a specific GPO or regkey is set, when you open terminal and choose the arrow down menu, there is no option to start an Azure Cloud Shell. Also the keyboard short cut should be disabled (ctrl+shift+3)

@sboehle sboehle added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 26, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 26, 2024
@lhecker lhecker added this to the Terminal v1.23 milestone Sep 26, 2024
@lhecker lhecker self-assigned this Sep 26, 2024
@DHowett
Copy link
Member

DHowett commented Sep 26, 2024

Thanks for the request! We definitely need better enterprise manageability for Terminal profiles (as well as sources, colors, themes, VT capabilities, ...).

In the meantime:

This is user specific

You can also install a machine-wide fragment extension that overrides the hidden property for the Azure Cloud Shell profile. That will affect removing it on all of your managed systems, and is not per-user.

@carlos-zamora carlos-zamora added Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. Needs-Discussion Something that requires a team discussion before we can proceed and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 2, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Oct 8, 2024
@lhecker lhecker removed the Needs-Discussion Something that requires a team discussion before we can proceed label Oct 14, 2024
DHowett pushed a commit that referenced this issue Oct 15, 2024
This adds a basic policy check for DisabledProfileSources, so that
organizations can easily disable certain profiles like the Azure one.

Closes #17964

## Validation Steps Performed
* Add a policy to disable Azure under HKCU. Disabled ✅
* Add a policy to disable nothing under HKLM. Enabled ✅
  (...because it overrides the HKCU setting.)
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Oct 15, 2024
DHowett pushed a commit that referenced this issue Oct 17, 2024
This adds a basic policy check for DisabledProfileSources, so that
organizations can easily disable certain profiles like the Azure one.

Closes #17964

* Add a policy to disable Azure under HKCU. Disabled ✅
* Add a policy to disable nothing under HKLM. Enabled ✅
  (...because it overrides the HKCU setting.)

(cherry picked from commit 3a06826)
Service-Card-Id: PVTI_lADOAF3p4s4AmhmszgT6i0Y
Service-Version: 1.21
DHowett pushed a commit that referenced this issue Oct 17, 2024
This adds a basic policy check for DisabledProfileSources, so that
organizations can easily disable certain profiles like the Azure one.

Closes #17964

## Validation Steps Performed
* Add a policy to disable Azure under HKCU. Disabled ✅
* Add a policy to disable nothing under HKLM. Enabled ✅
  (...because it overrides the HKCU setting.)

(cherry picked from commit 3a06826)
Service-Card-Id: PVTI_lADOAF3p4s4AmhmQzgT6i0c
Service-Version: 1.22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal In-PR This issue has a related PR Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants