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

Corporate Extension Controls #203069

Closed
brakers87 opened this issue Jan 22, 2024 · 7 comments
Closed

Corporate Extension Controls #203069

brakers87 opened this issue Jan 22, 2024 · 7 comments
Assignees
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality
Milestone

Comments

@brakers87
Copy link

Our company uses Visual Studio Code and would like to create a process to review and approve extensions. We currently do this for browser extensions and would like to have the same control over extensions in Visual Studio Code. We manage browser extensions through group policy so if there was some way to control Visual Studio Code extensions, we'd be able to have a more secure environment.

@isidorn
Copy link
Contributor

isidorn commented Jan 24, 2024

Thanks for filling this feature request.
Would it work for you if there was a setting that is an allow list of extensions + version, and it is admin controlled through group policy https://code.visualstudio.com/docs/setup/enterprise

Can you share what industry your company is (just curious)?

@isidorn isidorn added feature-request Request for new features or functionality extensions Issues concerning extensions labels Jan 24, 2024
@isidorn isidorn added this to the Backlog milestone Jan 24, 2024
@brakers87
Copy link
Author

brakers87 commented Jan 25, 2024 via email

@isidorn
Copy link
Contributor

isidorn commented Jan 26, 2024

I suggest to reach out to me by email [email protected] and I can include the right folk from the Marketplace team so we start a discussion.

@davidwin
Copy link

I keep hearing the lack of control over extensions as a blocker for wider internal adoption of VS Code, and the workarounds are not pretty. For a feature like this to be useful, I think it is also important that it is more than a list of extensions+versions. It should be possible to allow/block based on attributes such as publisher and extension type, or allowed extensions would be perpetually out of date (and possibly unsecure because of that).

@dooleydo
Copy link

dooleydo commented Mar 21, 2024

Also interested in this. @isidorn I will reach out to you from my corp email. This is a tricky issue in regulated finance environments. For context I personally believe that control perhaps is an anti-developer pattern but better visibility at least would be a starting point.

Any method of control ideally would want to be delivered via CSP, not group policy as we would not expect modern managed devices to be in scope of GPO in 2024...

@markusrippl-dlr
Copy link

I would also be very interested in this feature. From a user/admin perspective, it could look like a list of permitted extension hashes similar to the GPO setting that MS Edge uses to allow or block extensions.

@isidorn
Copy link
Contributor

isidorn commented Dec 10, 2024

This is now shipped as part of #84756

@isidorn isidorn closed this as completed Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

6 participants