add-policy

To add an enterprise configuration policy in VS Code, you register a configuration property with correct policy metadata, declare managed-settings keys, and ensure type alignment and localization for export compatibility.

You need managed settings and policy definitions in VS Code when a configuration property must be locked by organization policy, requiring canonical policy bag routing and preview-feature gating for enterprise enforcement.

Yes, you can reuse one enterprise policy across multiple VS Code settings using policyReference, which preserves type consistency and ensures policy-data export correctness across the codebase.

To lock Copilot or chat settings by organization policy, you declare managed-settings keys, route them through the canonical policy bag, apply preview-feature gating, and verify through export and test workflows.

VS Code configuration policy export breaks when policy metadata, managed-settings key definitions, localization, or type alignment are incorrect, requiring validation against policy-data export compatibility scenarios.

Yes, VS Code policy registration requires correct localization and type alignment to maintain enterprise policy export compatibility and ensure runtime behavior matches managed-settings wiring conventions.