Configure allowed extensions - GPO format and examples

Open
#8,211 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
vscode
Domain
documentation

Research direction

Start with the linked Configure allowed extensions documentation and review its existing GPO and update-setting guidance. Add registry-entry formatting and concrete Reg Add or PowerShell examples for manual GPO and Intune setup; done means administrators can configure allowed or denied extensions and updates without guessing the value format.

Written by the indexing model from the issue text.

Description

doc-enhancement feature-request

https://code.visualstudio.com/docs/setup/enterprise#_configure-allowed-extensions

Intune is currently unable to import GPO correctly due to a microsoft limitation

Looking at the documentation there is not much about how to configure the registry entry to allow or deny extensions, nor is there much on same for update.

There are no example registry entries and no hints as to the formatting to use for registry entries.

Theres a lot about how to configure the JSON settings for individual install but nothing on how to add to Intune via script or to configure the GPO manually

Ideally the format of what needs to get into something like a Reg Add command such as;

reg add "HKLM\SOFTWARE\Policies\Microsoft\VSCode" /v AllowedExtensions /t REG_SZ /d {"ms-vscode.powershell":true,"microsoft":true}

or a Powershell equivalent

Dominant language
Markdown
Stars
6.7k
Forks
5.8k
Avg merge
1d 7h
Merged PRs (30d)
138

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-docs

All issues in microsoft/vscode-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.