Edit

Manage Visual Studio in your organization

Use this guide to find Visual Studio administration tasks: deploy and maintain Visual Studio, govern extensions, and govern AI. Each section links to the detailed task and reference articles.

Start with the task that matches the machines you manage:

Your task Start here Completion checkpoint
Deploy Visual Studio to new developer machines Choose a golden path A pilot developer can build with the approved tools, permissions, and content sources.
Update installed instances through Intune or Configuration Manager Deploy and verify administrator updates The target version is verified on pilot clients before broad rollout.
Service installations from an internal or offline source Update layout-based clients or service fully offline machines Update content reaches the intended clients, and their versions and restart state are verified.
Configure organization-wide behavior Configure Visual Studio policies Effective policies are verified on the intended machines.

Use the task references in the following sections for an individual operation. Scenario selection and servicing choices are together in the golden-path overview.

Deploy and maintain Visual Studio

For a new deployment, prepare the content, configure permitted self-service, install each team's tools, and then establish servicing. Follow one golden path through the pilot instead of treating every linked reference as another required step.

Plan your deployment

Decide which edition, workloads, languages, update source, and installation permissions your organization needs before the first client installation.

System requirements

Check the Visual Studio system requirements ↗ for the target machines.

Check the Visual Studio 2022 system requirements ↗ for the target machines.

Deployment decisions

Visual Studio doesn't support application virtualization solutions such as Microsoft App-V, MSIX for Windows, or non-Microsoft application virtualization technologies. For an Azure virtual machine, start with Visual Studio images on Azure, not an application virtualization workaround.

Important

Initial installation by using the Visual Studio bootstrapper requires administrative privileges. Delegating updates or modification through the Visual Studio Installer UI with the AllowStandardUserControl policy doesn't grant permission to run the bootstrapper as a standard user.

Acquire and maintain layouts

A layout is a cache of installation content that you can use for initial deployment and subsequent updates. Choose this route when clients need an internal source or have limited internet access.

Configure permitted self-service

Before rollout, configure standard-user control if your organization permits manual Installer actions. Confirm the required Installer version and read/execute access to approved content. Keep write access restricted to administrators. Enabling administrator updates is a separate policy decision.

Deploy to developer machines

Manage updates

Plan who initiates updates and where each client gets its update content. Keep approved content up to date with security fixes. A deployment approval process isn't a reason to skip security updates.

Deploying an application through Intune and receiving Visual Studio administrator updates through Windows Update are different operations. Use the administrator-update guidance to check enrollment, policies, and access to update content.

Inventory and verify

Repair and troubleshoot

Govern extensions

Use the canonical article for the specific extension task:

The Private Marketplace is in preview and scoped to extension acquisition. It doesn't provide comprehensive extension governance: installation enforcement, provenance, inventory or audit, runtime loading or integrity, and status are separate concerns. Don't infer that Marketplace policies cover extensions installed through MSI or EXE packages, or sideloaded VSIX files. The existing private-gallery and Extension Manager articles describe specific sources and settings, not universal controls across those routes.

Govern AI

AI access and administration depend on the product and provider. GitHub Copilot, local models configured with a bring-your-own-key (BYOK) provider, and Microsoft 365 Copilot aren't interchangeable. Shared editor or chat experiences don't imply the same capabilities or policy controls.

This guide doesn't define Microsoft 365 Copilot administration or a shared policy surface across these AI paths. Use the canonical administration guidance for each product and verify feature status before describing planned controls as available.

Support or troubleshooting

Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.

Here are a few more support options:

  • Use the installation chat (English only) support option for installation-related issues.
  • Report product issues to us by using the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE. If you're an IT Administrator and don't have Visual Studio installed, you can submit IT Admin feedback.
  • Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

See also