Microsoft brings its Copilot orchestration layer to Foundry

The platform, built by GitHub’s engineering team and already adopted company-wide at Microsoft, currently drives Copilot Code, Copilot Studio, the GitHub Copilot app, its CLI, and VS Code. Tina Schuchman, CVP of Foundry, and Vladimir Fedorov, CTO of GitHub, framed the move as a response to how fast the model landscape shifts: a frontier model that leads today can fall behind tomorrow, and building a custom orchestration layer — what the post calls a “harness” — to keep pace is slow and difficult work most companies would rather not repeat themselves. Opening the platform through Foundry means developers get a fully managed way to build agents that reason, call tools, and complete long, complex tasks without switching their platform or the rest of their stack.

Microsoft describes an orchestration layer as everything that surrounds the model itself: it supplies an agent’s instructions, context, execution environment, and controls, and a credible platform needs open standards like MCP and Agent Skills alongside agent plugins. The company says it recently ported the platform’s runtime to Rust, which it credits with industry-leading performance and lower session overhead and time-to-first-token, and argues the platform’s experience running at the scale of Microsoft’s own millions of users and hundreds of real use cases gives outside developers a foundation already proven in production. The platform supports more than 20 frontier models plus the option to bring a custom API key, letting developers route each task to whichever model fits it rather than tracking and evaluating new models themselves.

Developers can download the SDK or run the orchestration platform in the cloud, fully managed through Foundry, and Microsoft says its platforms remain open and interoperable enough to plug in any other framework a team already uses. With the Copilot orchestration platform, Microsoft runs the agent loop and the sandbox, with governance and optimization built in from day one, while developers supply the instructions, skills, tools, and model choice.

Why it matters

By offering the same orchestration layer it runs internally, Microsoft is betting that developers will pay for managed infrastructure around model choice rather than building and maintaining their own switching logic as frontier models keep changing hands at the top of the leaderboard.