Skip to content

Correct Windows enterprise policy Step 2 guidance to ADMX/GPO workflow #9867

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.

Sign up for GitHub

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

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
+12 −68
Draft

Correct Windows enterprise policy Step 2 guidance to ADMX/GPO workflow #9867

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62a9343
Initial plan
Copilot Jun 1, 2026
0727ad5
Fix Windows policy Step 2 to use GPO/MDM guidance
Copilot Jun 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 6 additions & 34 deletions docs/enterprise/policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,42 +38,14 @@ You can get the ADMX and ADML files from either an existing installation or by d

### Step 2: Configure policy values

Edit the policy values according to your requirements:
After installing the ADMX and ADML files, configure policy values through your management tool:

**String policies** - policies that accept text values or JSON strings:
- For Active Directory environments, use the Group Policy Editor (`gpedit.msc`) and navigate to **Computer Configuration** > **Administrative Templates** > **Visual Studio Code**.
- For cloud-managed devices, use your MDM solution (for example, Microsoft Intune) to configure the imported VS Code administrative template policies.
- Open each policy, set it to **Enabled** or **Disabled**, and provide any required value in the policy UI.
- Leave policies in the **Not Configured** state if you don't want to enforce them.

```xml
<!-- Example: Allow extensions from specific publishers -->
<key>AllowedExtensions</key>
<string>{"microsoft": true, "github": true}</string>

<!-- Example: Set update mode to a specific value -->
<key>UpdateMode</key>
<string>start</string>
```

> [!IMPORTANT]
> If there's a syntax error in the policy value, the setting will not be applied. You can check the Window log in VS Code for errors (press `kb(workbench.action.showCommands)` and enter **Show Window Log**).

**Boolean policies** - policies that accept true/false values:

```xml
<!-- Example: Enable user feedback -->
<key>EnableFeedback</key>
<true/>

<!-- Example: Disable telemetry -->
<key>EnableTelemetry</key>
<false/>
```

**Remove unwanted policies** - delete both the key and value for any policy you don't want to enforce:

```xml
<!-- To not enforce an update mode policy, remove these lines: -->
<key>UpdateMode</key>
<string>start</string>
```
Configured policy values are written to the registry under `Software\Policies\Microsoft\VSCode`.

Refer to the [policy reference](#vs-code-enterprise-policy-reference) below for details on each policy's accepted values and behavior.

Expand Down
40 changes: 6 additions & 34 deletions docs/enterprise/policies.template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,42 +38,14 @@ You can get the ADMX and ADML files from either an existing installation or by d

### Step 2: Configure policy values

Edit the policy values according to your requirements:
After installing the ADMX and ADML files, configure policy values through your management tool:

**String policies** - policies that accept text values or JSON strings:
- For Active Directory environments, use the Group Policy Editor (`gpedit.msc`) and navigate to **Computer Configuration** > **Administrative Templates** > **Visual Studio Code**.
- For cloud-managed devices, use your MDM solution (for example, Microsoft Intune) to configure the imported VS Code administrative template policies.
- Open each policy, set it to **Enabled** or **Disabled**, and provide any required value in the policy UI.
- Leave policies in the **Not Configured** state if you don't want to enforce them.

```xml
<!-- Example: Allow extensions from specific publishers -->
<key>AllowedExtensions</key>
<string>{"microsoft": true, "github": true}</string>

<!-- Example: Set update mode to a specific value -->
<key>UpdateMode</key>
<string>start</string>
```

> [!IMPORTANT]
> If there's a syntax error in the policy value, the setting will not be applied. You can check the Window log in VS Code for errors (press `kb(workbench.action.showCommands)` and enter **Show Window Log**).

**Boolean policies** - policies that accept true/false values:

```xml
<!-- Example: Enable user feedback -->
<key>EnableFeedback</key>
<true/>

<!-- Example: Disable telemetry -->
<key>EnableTelemetry</key>
<false/>
```

**Remove unwanted policies** - delete both the key and value for any policy you don't want to enforce:

```xml
<!-- To not enforce an update mode policy, remove these lines: -->
<key>UpdateMode</key>
<string>start</string>
```
Configured policy values are written to the registry under `Software\Policies\Microsoft\VSCode`.

Refer to the [policy reference](#vs-code-enterprise-policy-reference) below for details on each policy's accepted values and behavior.

Expand Down