The Windows "Step 2: Configure policy values" section in docs/enterprise/policies.md shows macOS plist-style XML (<key>/<string>/<true/>) as the format for configuring Windows policies. This is incorrect — Windows ADMX-based policies are configured through the Group Policy Editor UI or MDM, not by hand-editing plist XML.
Current (incorrect — this is macOS plist syntax):
<key>AllowedExtensions</key>
<string>{"microsoft": true, "github": true}</string>
<key>EnableFeedback</key>
<true/>What should be there: Guidance on using the Group Policy Editor (gpedit.msc) or Intune to configure the policies after installing the ADMX/ADML templates. The Step 2 should not show raw XML for administrators to edit — on Windows, policy values are set through the GPO UI which writes to the registry under Software\Policies\Microsoft\VSCode.
The detailed Step 3 expand sections already describe the correct GPO Editor workflow, so Step 2's XML examples are both misleading and inconsistent with the rest of the section.
Source confirmation: VS Code generates standard ADMX templates with registry-backed policy elements, not plist key/value pairs.
The Windows "Step 2: Configure policy values" section in
docs/enterprise/policies.mdshows macOS plist-style XML (<key>/<string>/<true/>) as the format for configuring Windows policies. This is incorrect — Windows ADMX-based policies are configured through the Group Policy Editor UI or MDM, not by hand-editing plist XML.Current (incorrect — this is macOS plist syntax):
What should be there: Guidance on using the Group Policy Editor (gpedit.msc) or Intune to configure the policies after installing the ADMX/ADML templates. The Step 2 should not show raw XML for administrators to edit — on Windows, policy values are set through the GPO UI which writes to the registry under
Software\Policies\Microsoft\VSCode.The detailed Step 3 expand sections already describe the correct GPO Editor workflow, so Step 2's XML examples are both misleading and inconsistent with the rest of the section.
Source confirmation: VS Code generates standard ADMX templates with registry-backed policy elements, not plist key/value pairs.