Microsoft’s Copilot harness comes to Foundry for managed agent execution

Microsoft is making the Copilot harness available through Microsoft Foundry, according to its October 28 announcement. The offering gives developers a managed route to the system around a model: instructions, context, an execution environment and controls for agents doing work with tools. The announcement also links a downloadable Copilot SDK.

The useful distinction is between choosing a model and choosing how an agent operates. A model can contribute reasoning or propose a next step. The surrounding application still needs to provide the relevant information, run permitted tools and manage the ongoing task. Microsoft describes the harness as that orchestration layer, rather than a newly announced consumer assistant.

Microsoft says the cloud route is managed by Foundry: Microsoft runs the agent loop and sandbox, while the developer brings instructions, skills, tools and model choice. That divides the work differently from assembling and maintaining the whole runtime independently. Source: Microsoft

The SDK and managed cloud routes are therefore separate implementation choices. The release says the SDK is available to download, but it is not an installation guide and does not establish every environment’s configuration requirements. No SDK code was downloaded or executed for this report.

For a platform team, a useful evaluation follows the task beyond its first model response: where does tool execution occur, which context reaches it, and which controls govern the next action? A managed runtime addresses who operates the loop; it does not make the application’s instructions, tool selection or data‑access decisions disappear.

The announcement describes support for open standards such as MCP and agent skills, alongside plugins. It also says Microsoft’s platforms remain open to other harnesses and frameworks. Those are descriptions of the platform’s design, rather than proof that any existing plugin or skill works unchanged in a particular deployment. Source: announcement

For the skills concept, OpenTools’ Agent Skills Specification reference explains a concrete packaging pattern: a folder centered on a SKILL.md file, with metadata and instructions, plus optional scripts, references and assets. This provides background on organizing a reusable procedure; it is not a Foundry configuration guide or a compatibility test.

A procedure describes how work should be done. The execution environment and its access controls determine where its actions can run. Keeping those concerns distinct helps a team avoid treating a portable instruction package as a substitute for deciding what an agent may access or change.

Microsoft says the harness already powers multiple Copilot developer surfaces and supports work across model families. The current announcement brings that surrounding system to Foundry; it does not mean that using a Copilot application automatically configures an enterprise agent or grants it access to the same tools and data. [Source: Microsoft](https://blogs.microsoft.com/blog/2026/10/28/introducing‑the‑microsoft‑copilot‑harness‑unlocking‑the‑potential‑of‑truly‑multi‑model‑agentic‑work/) A practical pilot would identify the task, its required context, the permitted tools and the execution boundary before choosing the model route. That gives a team specific behavior to check: whether the agent receives only the intended context, runs the intended operations and handles the task’s control requirements. Those are evaluation questions, not tests performed here. The release does not provide a complete model‑by‑model, price or regional‑availability matrix. Its performance and cost descriptions also are not independently verified results in this report. The supported product change is access to a managed harness and an SDK route, with the application builder still supplying the task‑specific ingredients. AI‑generated conceptual illustration of a model as one part of surrounding instructions, tools and controlled execution. The workbench and apparatus are metaphors, not Microsoft software, its architecture or an actual agent output. Original artwork by OpenTools Team, based on [Microsoft’s announcement](https://blogs.microsoft.com/blog/2026/10/28/introducing‑the‑microsoft‑copilot‑harness‑unlocking‑the‑potential‑of‑truly‑multi‑model‑agentic‑work/).