Deploy VS Code to managed devices
As an IT admin, use this guide to choose an installation method, prepare required services and controls, and validate a pilot before deploying Visual Studio Code broadly. Use your organization's software distribution and device management tools to carry out the rollout.
Define the rollout scope
Before choosing a package or policy:
- Check the system requirements and supported deployment environments, especially when planning virtual desktop or shared-machine deployments.
- Identify the operating systems, processor architectures, installation accounts, and developer accounts in the rollout.
- Choose a representative project and the development tasks that must work, such as installing an approved extension, building, debugging, or using an approved agent.
- Identify who owns software deployment, device policies, GitHub administration, and network access. Give pilot participants a support contact.
For AI work, include the clients and execution hosts your developers use. A policy on the connecting device does not establish runtime enforcement on a remote host or in a container.
Choose an installation method
Use the platform guide for package acquisition and installation steps:
| Platform | Deployment decision |
|---|---|
| Windows | Choose User setup for an individual account or System setup for a machine-wide installation. System setup requires administrator permissions. For automation, review unattended setup. |
| macOS | Choose a build for the target architecture and plan how your software distribution tool installs the application bundle. |
| Linux | Choose the package for the distribution. Decide whether to use the Microsoft package repository, Snap, or a package distributed through your own deployment process. Repository configuration and signing keys are part of installation. |
If you need a specific approved build, use the version-specific downloads. Record the version and installation type so the deployment team can reproduce the pilot.
A machine-wide installation does not replace extension configuration, device policies, or account-level AI controls.
Prepare network access and extensions
Confirm that the installation and the intended developer account can reach the services needed for approved work:
- Coordinate network access, proxy, and certificate requirements with your network team. Check installation and update services as well as the services developers use.
- Choose how developers obtain extensions. Use the public Marketplace or review the eligibility and deployment requirements for a private marketplace.
- Configure allowed extensions if your organization restricts installation or enablement.
- For a Windows image with preinstalled extension packages, follow Preinstall extensions and test first launch with a new user account.
An installed extension can still be disabled by policy or require additional tools. Include extension functionality in the pilot, not only installation.
Configure required controls
Choose controls based on organizational requirements rather than deploying every policy in a sample file.
- Editor settings: Follow the deployment steps for Windows Group Policy, macOS configuration profiles, or a Linux policy file.
- AI access and execution: Choose a management solution for each control. Check supported clients, harnesses, minimum versions, and precedence.
- Telemetry: Configure product telemetry and feedback. Review independent extension telemetry and agent monitoring separately.
- Servicing: Decide who manages application and extension updates. The application's update policy does not control package managers or an external installer.
Keep the configuration and the intended outcome for each control together. For example, distinguish setting a starting model from restricting which models developers can select.
Validate a pilot
Use a test group that covers the installation methods and development environments in the rollout.
-
Install the approved package and deploy the selected controls through your management tools. Wait for the target devices to receive the configuration.
-
Launch VS Code as the intended developer, not only as the account that installed it. Confirm the installed version.
-
Run Developer: Policy Diagnostics from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)). Compare effective values and sources with the intended configuration. See Verify policy enforcement.
-
Confirm the expected extensions and versions with
code --list-extensions --show-versionsunder the developer account. Check the Extensions view for enablement and policy restrictions, then exercise the extensions your test project needs. -
Complete the representative development tasks. For each important restriction, also test a harmless operation that the policy should block. A value in diagnostics alone does not prove that the restriction applies to that workflow.
-
For AI sessions, follow Verify an AI rollout on each approved client and execution host.
-
Verify that the chosen update mechanism behaves as intended. Check application, package-manager, and extension servicing separately.
If the pilot fails, pause the rollout and use administrator troubleshooting. Do not remove controls or bypass certificate checks as a general way to make the pilot pass.
Expand and maintain the deployment
After the pilot passes, expand deployment through your management tools. Keep the approved package, configuration, validation results, and responsible teams recorded in your deployment process.
- Tell developers which capabilities are available, how to request an exception, and where to report a problem.
- Schedule application and extension servicing, including security updates when the application's updater is off.
- Repeat relevant pilot checks when a client version, extension, policy, or AI harness changes.
- Define a recovery process with the deployment team. Before using an earlier build, check that it supports the controls your organization requires.