Visual Studio & Tooling

Bring Your Own Model General Availability Lands in Visual Studio

Visual Studio 18.12 introduces general availability for the Bring Your Own Model feature, enabling developers to integrate internal, local, or third-party AI models directly into their IDE workflow without requiring a GitHub login.

What changed From the source

The Bring Your Own Model feature has reached general availability in Visual Studio 18.12. This release incorporates user feedback from the August Preview, introducing support for multiple configurations per provider, a dedicated custom endpoint experience, enhanced proxy handling, and granular API compatibility controls.

Developers can utilize local models or internally hosted models within air-gapped environments, provided the endpoint is reachable and authentication requirements are fulfilled. No GitHub sign-in is necessary to use the feature.

Users can maintain multiple configurations for a single provider, assigning custom names to distinguish between setups like work and personal. The Custom Endpoint provider caters to OpenAI-compatible services such as OpenRouter, allowing developers to supply an endpoint URL and API key. Additionally, users can connect to local models served by LM Studio using OpenAI-compatible URLs.

The release allows selection of specific API formats, including OpenAI-compatible Completions or Responses, and Anthropic-compatible Messages. Developers can further fine-tune context size, maximum output, tool calling, and vision support. For enterprise environments, proxy support has been improved to ensure connections and Agent Mode honor Visual Studio's resolved proxy configuration, and administrators retain the ability to toggle BYOM access through organizational policies.

  • Install Visual Studio 18.12 GA to access the feature.
  • Navigate to Chat, open the model picker, and select Manage models.
  • Choose Add model provider to select Microsoft Foundry, OpenAI, Anthropic, Ollama, or Custom Endpoint.
  • Configure the connection, assign a name, add desired models, and select them for Agent Mode.

At a glance · Visual Studio & Tooling

What changedWhy it mattersWho should careUpgrade and migration considerations

Why it matters Analysis

The general availability of Bring Your Own Model provides development teams with the flexibility to leverage proprietary, custom, or locally hosted AI infrastructure without switching tools. By removing the strict dependency on a single vendor or GitHub authentication, the feature accommodates specialized security postures and offline network constraints.

The ability to define multiple named configurations for the same provider reduces friction for developers who frequently switch between enterprise resource pools and personal accounts. Furthermore, explicit control over API formats, context windows, and tool calling ensures that diverse model architectures integrate smoothly into Visual Studio workflows.

  • Enables utilization of air-gapped and self-hosted inference servers.
  • Improves multi-account management through named provider configurations.
  • Enhances compatibility with custom gateway services and local engines like LM Studio.

Who should care Analysis

Enterprise developers operating under strict security compliance or air-gapped environments will find the local model and proxy improvements particularly beneficial. Teams utilizing internal AI gateways or alternative model providers outside of standard public defaults can now streamline their daily tooling.

IT administrators also gain control over developer environments through centralized policy enforcement, allowing them to explicitly permit or restrict BYOM access according to corporate governance standards.

  • Enterprise development teams with internal or restricted network policies.
  • Developers experimenting with local inference servers or multi-provider setups.
  • IT administrators managing Visual Studio deployment policies.

Upgrade and migration considerations Analysis

Organizations moving to Visual Studio 18.12 should verify whether enterprise policies restrict bring-your-own-model access, as administrators have the authority to disable the feature. Developers upgrading from preview builds should review their existing provider configurations to take advantage of the new named multi-configuration support and dedicated custom endpoint options.

  • Verify that Visual Studio 18.12 GA is installed across development workstations.
  • Check organizational policies if the Add model provider option is not visible.
  • Review and update custom model definitions to match the appropriate API format and context settings.

Sources and further reading

Original: “Bring Your Own Model is now generally available in Visual Studio”, Visual Studio Blog, published 11 Nov 2026, retrieved 12 Nov 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.