惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
大猫的无限游戏
大猫的无限游戏
博客园 - 聂微东
Jina AI
Jina AI
The Cloudflare Blog
V
Visual Studio Blog
博客园_首页
量子位
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
博客园 - 司徒正美
阮一峰的网络日志
阮一峰的网络日志
Last Week in AI
Last Week in AI
V
V2EX
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 叶小钗
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
T
Tailwind CSS Blog
博客园 - Franky

Visual Studio Blog

Today I will... find hidden latency across a distributed .NET application - Visual Studio Blog Stop alt-tabbing into the wrong Visual Studio - Visual Studio Blog Today I will... review GitHub PRs - Visual Studio Blog VSLive! @ Microsoft HQ: Developer Takeaways and Must-Watch Sessions - Visual Studio Blog The Visual Studio Debugger Agentic Workflow Gets a Test-Driven Upgrade - Visual Studio Blog Visual Studio August Update — Work Smarter Across Models and Branches - Visual Studio Blog Today I will... Modernize a .NET application - Visual Studio Blog Today I will... manage Git Submodules without leaving the IDE - Visual Studio Blog Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit - Visual Studio Blog Tell your model when to think harder  - Visual Studio Blog Visual Studio July Update — Meet the New Agent, Powered by the GitHub Copilot SDK - Visual Studio Blog Visual Studio Administrator? Join our Private Marketplace Preview! - Visual Studio Blog Pick, manage, and get the most from your models - Visual Studio Blog Built-in Agent Skills Bring .NET and Azure Expertise into Visual Studio - Visual Studio Blog The Visual Studio Dev/Test Benefit: Freedom to Build, Test, and Experiment in Azure - Visual Studio Blog Visual Studio June Update - Track Your Usage, Trust Your Tools - Visual Studio Blog Automating your Visual Studio extension builds with GitHub Actions - Visual Studio Blog Make Visual Studio look the way you want - Visual Studio Blog Review pull requests without leaving Visual Studio What’s Coming Next in Visual Studio: Our Microsoft Build 2026 Announcements Visual Studio May Update – Plan, Review, Refine Plan Before You Build: Introducing the Plan agent in Visual Studio VSLive! Microsoft AI Hackathon 2026: Send Your Team Home With Working Code Agent Skills in Visual Studio: Teach Copilot How Your Team Works TypeScript 7 Beta Now Enabled by Default in Visual Studio 2026 18.6 Insiders 3 SDK-Style Support for Extension Projects Visual Studio April Update – Cloud Agent Integration - Visual Studio Blog From AI to .NET: 20 VS Live! Las Vegas Sessions You Can Watch Now - Visual Studio Blog Azure MCP tools now ship built into Visual Studio 2022 — no extension required Stop Hunting Bugs: Meet the New Visual Studio Debugger Agent Workflow
Unlocking the Power of AI for Every Developer in Visual S...
Tanmayee Kamath · 2026-08-25 · via Visual Studio Blog

The best AI in Visual Studio is the AI you can bring with you. Developers don’t work in a single-model world anymore. You might reach for one model for everyday coding, another for a domain-specific problem, and an approved model for work that must stay within your organization’s governance boundaries. So, the question we hear most often isn’t which model is best. It’s, can I use mine?

We’re bringing Bring Your Own Model (BYOM) in Preview to Visual Studio, making it available and enabled by default across Community, Professional, and Enterprise SKUs. This Preview focuses on the developer experience available today. Enterprise management capabilities, including admin controls to disable BYOM as well as centralized model configuration and management for Professional and Enterprise SKUs are coming soon.

From individual developers experimenting with new models to organizations standardizing approved deployments, BYOM gives you the flexibility to use AI in Visual Studio your way. With BYOM, you can connect to a Microsoft Foundry deployment, or use your own key from another supported provider, in Agent Mode, whether or not you’re signed in to GitHub.

This is an early Preview and we’d appreciate feedback on the developer experience. Before you dive in, watch the short demo below to see the capability in action. Then try it yourself by following the steps in the Getting started section below and let us know what’s working, what’s missing, and where you’d like us to invest next. Share your feedback in the Developer Community forum and/or fill out this short survey to help shape the future of BYOM in Visual Studio.

Getting Started

Important: The BYOM capability is evolving alongside Visual Studio’s new Agent (Preview), which is built on the new GitHub Copilot SDK-powered harness. As part of this transition, the previous BYOM experience available in the earlier Ask and Agent modes is no longer supported. To use BYOM, install the latest Visual Studio Insiders release and use the new Agent (Preview) experience. If you had previously added BYOM models, they will need to be re-added with this update. 

BYOM is available in Preview within the Visual Studio 18.10 Insiders Release.

To try it:

  1. Install Visual Studio 18.10 Insiders Release
  2. Within Chat, open the model picker and choose ‘Add a model’ or ‘Manage models’ option (this will work for both GitHub signed-in and signed-out flows)
  3. Connect to the provider of your choice, by clicking on ‘Add model provider’
  4. Start working in Agent (Preview) Mode

Supported providers for the Preview: Microsoft Foundry, OpenAI, Anthropic, Ollama with custom URL support for OpenAI & Ollama.

We also want to be candid about what Preview means. Not every model supports every Agent Mode capability today, and we’re not attempting to certify every model-and-provider combination in this release. Where a feature depends on a capability a model doesn’t offer, we aim to fail gracefully.

Why developers asked for BYOM

Over the past several months, we’ve spent a lot of time with enterprise developers, IT administrators, and security leads, the people who decide whether an AI coding tool gets approved, restricted, or blocked. One theme came through clearly: teams increasingly work in multi-model environments, and they want Visual Studio to meet them there.

A few motivations came up repeatedly as reflected in this suggestion ticket:

  • Organizations have already invested in approved models, often deployed behind private endpoints, and want developers to use them with Copilot in Visual Studio without sending code or prompts to another provider.
  • In regulated industries, including financial services, healthcare, the public sector, and defense, tools must meet organizational requirements for identity, data flow, and administrative control to be usable.
  • Cost and performance matter. Teams want the flexibility to choose models that meet their budget and latency requirements.

BYOM gives developers and organizations more choice in how they use AI in Visual Studio. Use GitHub Copilot models, access organization-approved deployments from Microsoft Foundry or connect your own provider. Developers stay in the same Visual Studio experience, while organizations retain the governance, security, and compliance controls they’ve already established. The result is more flexibility to use the models that best fit your workflow, budget, and organizational requirements.

What we’re working on next

This Preview is the first step toward Bring your Own Model in Visual Studio. Next, we’re focused on making BYOM easier to adopt and govern across organizations through an ADMX policy to disable it for Professional and Enterprise users that’s coming soon as part of the 18.10 GA release, centralized model configuration and management, more granular model controls such as configuring context size, tool calling, and model thinking effort, broader provider and model support, smarter compatibility detection and deeper Microsoft Foundry integration. These capabilities are not included in the current release, and your feedback will help us prioritize what comes next.

Try BYOM in Visual Studio 18.10 Insiders today and share what’s working, what’s missing, and what you’d like us to prioritize next through the Developer Community forum or our short survey. Your feedback will directly help shape the future of AI in Visual Studio. Happy Coding!