Microsoft Brings Its Copilot Harness to Foundry
Microsoft is turning agent orchestration into shared infrastructure inside Foundry.
On October 28, Microsoft introduced its Copilot harness in Foundry Agent Service in public preview. It packages the agent loop, working context, sandboxed execution, skills, and connected tools as a managed service. Teams bring their instructions, procedures, and supported model choice.
Tweet
For product teams, this puts a build-or-buy decision inside the agent stack. Owning execution infrastructure takes engineering time that could go into domain workflows and evaluating outcomes. A managed harness is worth testing where its controls fit the product.
The preview has limits: existing agents cannot switch to the harness after creation, and Foundry manages CPU, memory, and idle settings. Separately, long-running resilience for hosted agents is generally available. Recovery still depends on customer code saving progress and preventing duplicate actions when work restarts.
Run one representative workflow against your existing stack. Compare accepted outcomes, operator intervention, recovery, and total cost. Include model and tool charges; harness runtime billing starts December 1. Keep your own loop where you need execution behavior the managed service cannot provide.