What shipped, and when
Foundry Toolkit 1.6.18, released October 28, adds a redesigned hosted-agent sample gallery, preview Copilot harness support in Agent Builder, and model filters for task, capability, region, deployment option, SKU, and lifecycle. The toolkit changelog describes the harness item as a way to manage Foundry prompt agents with built-in tools and skills in Agent Builder. The release notes add that developers can edit local YAML definitions, deploy changes to Foundry, and run deployed agent versions.
The Azure Updates entry is dated later than the launch. Microsoft's Foundry blog says on October 28, we announced the Microsoft Copilot harness in Foundry Agent Service. The toolkit support landed the same day. The November 21 timestamp looks like a catalog entry, not a new release. The live Azure Updates page returned no detail for this ID when it was fetched, so the toolkit changelog and the Foundry blog are the sources that carry the substance.
What the harness is
The harness is not a model. Per the Foundry blog, it gives prompt agents a managed loop and sandbox for work that needs more than one model response. Examples are reading files, running code, using supported tools, and applying reusable skills. You still pick a supported model. The harness turns the model's next step into work within the tools and permissions you configure.
Other coverage adds background. The New Stack reports that it comes with built-in sandboxing, reusable skills, MCP integrations, and support for subagents. It also reports that the same harness now supports Copilot Code, Copilot Studio, GitHub Copilot, the CLI, and VS Code. That makes this a way for outside developers to use an execution layer Microsoft already ships in its own products.
The VS Code workflow
The toolkit gives you a local authoring loop with these steps:
- Open Agent Builder in the Foundry Toolkit extension.
- Work with a Foundry prompt agent that uses the harness, with its built-in tools and skills.
- Edit the local YAML definition.
- Deploy the changes to Foundry.
- Run the deployed agent version.
The release notes do not give menu labels, a minimum VS Code version, or a list of supported tools and skills for this integration. I won't invent them. Check the extension itself for those details.
Other routes exist too. Alphasignal reports that developers can also author agents in the Foundry portal, the Foundry Toolkit for Visual Studio Code, or the Microsoft Foundry plugin and Skill in the GitHub Copilot app. It adds that the preview Azure Developer CLI offers a direct deployment path. VS Code is one front door among several.
Limits to know before you build
- Preview only. Azure Updates defines "In preview" as available to Azure customers for non-production use and testing. The Foundry blog separates the managed harness, which is preview, from long-running hosted-agent resilience, which is generally available.
- Choose the harness at creation. The Foundry blog says to select the harness when creating the agent; switching an existing agent afterward is not supported yet. Existing agents are unchanged.
- Managed sandbox. Foundry controls the sandbox's CPU, memory, and idle settings.
- Not for custom runtimes. Microsoft advises keeping your existing implementation if custom execution or runtime requirements are essential.
- Configure tools and approvals. Microsoft tells developers to set the allowed tools and approval points for their workflow.
- Scope. This applies to Foundry prompt agents. It does not turn hosted agents into prompt agents.
Cost
Pricing is the part to watch. Several outlets report that the harness runtime is free during the preview and that billing starts December 1, 2026. FourWeekMBA attributes that date to Foundry's developer blog. TechTimes says the Copilot Harness is available in public preview at no charge through November 30, 2026. Alphasignal notes that model inference and separately billed tools incur their usual charges during the preview. I could not confirm the billing terms on a primary Microsoft page in the material reviewed. Check current Foundry pricing before budgeting.
Analysis
This is a small but useful tooling change. The harness is the story. The VS Code support means developers can author and deploy these agents without leaving the editor.
The trade-off is lock-in. The New Stack's headline frames the harness as easy until you want to switch. The fact that you can't change an agent's harness after creation fits that concern. For a team piloting agents in non-production, the risk is low. For anyone planning a migration of existing agents, treat it as a new-build option for now.
A sensible first test is a small prompt agent with a narrow tool list and human approval on anything that writes. Run it in a non-production Foundry project. Compare it with an equivalent plain prompt agent before the free period ends.
The preview label is the key point. Treat this as a testing workflow, not a production commitment.
References
- (In preview) Public Preview: Microsoft Copilot harness support in Foundry Toolkit for VS Code Azure Updates · 2026-11-21T00:43:13Z
- Microsoft Ships Copilot Harness to Run Multi-Step AI Agents Without Infrastructure alphasignal.ai
- Microsoft Copilot Harness Opens to Enterprise Developers: Model Flexibility, Platform Lock-In techtimes.com