Skip to content

Support macOS Configuration Profiles as a policy backend #148942

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

Closed
2 tasks done
Tracked by #147756
joaomoreno opened this issue May 6, 2022 · 5 comments
Closed
2 tasks done
Tracked by #147756

Support macOS Configuration Profiles as a policy backend #148942

joaomoreno opened this issue May 6, 2022 · 5 comments
Assignees
Labels
config VS Code configuration, set up issues feature-request Request for new features or functionality macos Issues with VS Code on MAC/OS X on-testplan
Milestone

Comments

@joaomoreno
Copy link
Member

joaomoreno commented May 6, 2022

@joaomoreno joaomoreno added feature-request Request for new features or functionality macos Issues with VS Code on MAC/OS X config VS Code configuration, set up issues labels May 6, 2022
@joaomoreno joaomoreno added this to the Backlog milestone May 6, 2022
@joaomoreno joaomoreno self-assigned this May 6, 2022
@joaomoreno joaomoreno changed the title Generate macOS Configuration Profiles definition files from static analysis Support macOS Configuration Profiles as a policy backend May 6, 2022
@rossgrady
Copy link

If the only purpose of this feature request is to use it as a placeholder when closing other duplicate requests, then . . .

Can we get an update re: whether this is ever going to be moved off the backlog? Especially now that:

  • Enterprise Extension management has GAed
  • Copilot Free is a thing

It is increasingly critical that enterprises be given management tooling for VSCode which isn't Windows-only.

Yes, I recognize that it's a free offering. It's also the world's most popular code editor/IDE.

@joaomoreno joaomoreno modified the milestones: Backlog, January 2025 Jan 7, 2025
@joaomoreno
Copy link
Member Author

@rossgrady Moving it out now. 👍

@hlwndon

This comment has been minimized.

@sandstrom
Copy link

Somewhat related, it would be neat if there was not only allow/disallow, but also something in the middle.

E.g. where we could have a whitelist of allowed extensions, but also permit manual override (i.e. adding non-whitelisted extensions) behind some large warning or semi-complicated override-step.

That way, power-users would still be able to install anything, but junior people would get a clear warning and hopefully not install non-whitelisted extensions.

@joshspicer
Copy link
Member

joshspicer commented Mar 17, 2025

👋 All the pieces are available and ready for testing in the latest Insiders. For interested folks, please feel free to give things a try and let me know your feedback

Instructions to get started can be found here: microsoft/vscode-docs#8159

Known issues:

@Ayukjhay
Copy link

Ayukjhay commented Mar 17, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config VS Code configuration, set up issues feature-request Request for new features or functionality macos Issues with VS Code on MAC/OS X on-testplan
Projects
None yet
Development

No branches or pull requests

7 participants