Back to Blog

    Strategy

    Copilot harness in Microsoft Foundry: what developers get and where it runs

    Since 28 October 2026 Microsoft offers the agent loop behind GitHub Copilot and Copilot Studio in Microsoft Foundry. We checked every capability for availability in Switzerland and say when the harness pays off.

    October 30, 20269 min read
    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    marcel.haas@cnext.ch
    In this article

    Since 28 October 2026 Microsoft Foundry runs agents on the same loop that powers GitHub Copilot and Copilot Studio. A development team describes instructions, skills and tools; Foundry plans the steps, works with files, runs commands in a sandbox and hands subtasks to subagents. The preview runs in nine Azure regions, none of them in Switzerland. We checked every capability for availability in Switzerland and say when we use the harness and when Copilot Studio or Microsoft Copilot is enough.

    What a development team gets from today

    Monday morning at a machine builder in Winterthur: purchasing has twelve quotes for a drive component, as PDF and Excel, each with different delivery times and discount tiers. An agent on the Copilot harness puts the files into its workspace, reads them, converts the prices to one quantity with a short script, checks them against the framework contracts in the ERP through an MCP tool and writes a comparison back as an Excel file. A person places the order.

    Microsoft calls the product "Microsoft Copilot harness" and describes the split like this: Microsoft runs the agent loop and the sandbox, the team brings knowledge, procedures and tools. In practice that means:

    • Tools in the harness: read and write files, run shell commands, fetch web pages and hand subtasks to subagents. All five are switched on for new agents and can be switched off one by one.
    • Skills: versioned procedures with instructions, scripts and material, stored as SKILL.md in the same Foundry project. Each agent version points to an immutable skill version, up to 50 per agent.
    • Connected tools: functions of your application, Foundry web search, MCP servers with approval per call and the tools of the Foundry toolbox, among them Azure AI Search, File Search, Fabric IQ and Work IQ for mail, calendar and SharePoint on behalf of the signed-in person.
    • Definition in the repository: the agent lives in an azure.yaml file and is rolled out with the Azure Developer CLI, or in the Foundry portal, with the Foundry Toolkit for Visual Studio Code or with the SDKs for Python, C#, TypeScript and Java.

    The agent remains a prompt agent in Foundry Agent Service and is called through the Responses API. Each conversation gets its own workspace; what should last, the agent stores in Foundry Files. Foundry Memory, that is memories across conversations, is not yet available with the harness, and neither is a custom model through Bring Your Own Model. You choose the harness when you create the agent; existing agents cannot be switched during the preview.

    How the harness relates to Copilot Studio, hosted agents and Microsoft Copilot

    According to the announcement by Tina Schuchman and Vladimir Fedorov, the same loop already powers Copilot Studio, the GitHub Copilot app, the command line and Visual Studio Code; GitHub built it, Microsoft adopted it company-wide. Whoever builds an agent in Copilot Studio today therefore uses the same technology, embedded in an interface for business teams, with publishing to Teams and Microsoft Copilot and billing through Copilot Credits.

    Foundry thus offers three routes. A prompt agent without the harness is enough when instructions and a few tools do the job. The harness fits when the agent works with files, scripts, skills and subagents over many steps and Microsoft should operate the runtime. A hosted agent is right when your team writes the loop itself, with Agent Framework, LangGraph or its own code in a container. For hosted agents Microsoft announces in the same post that long runs restart with the same input after a crash.

    Microsoft Copilot, the product for employees in Microsoft 365, is not mentioned in either announcement, and Microsoft names no change for Copilot licences.

    Availability in Switzerland

    As of 30 October 2026, checked against both announcements and the Microsoft Learn pages on limits, regions and models.

    CapabilityStatus according to MicrosoftIn Switzerland
    Copilot harness for prompt agents: loop, sandbox, file, shell, web and subagent tools, skillsPublic preview since 28 October 2026No. In Europe it runs in Germany West Central (Frankfurt), West Europe (Netherlands), Sweden Central and UK South; UK South is outside the EU
    Models for the harness: reasoning and tool calling, available in the project regionPreview, Bring Your Own Model not supportedIn the harness EU regions gpt-5.4, gpt-5.5 and the gpt-6 family as EU data zone, which does not include Switzerland; gpt-5.1 regionally in Sweden Central
    Network rules for outbound traffic of the sandbox, with audit and enforce modePreviewOnly in the harness regions
    Prompt agents without the harnessGenerally availableYes, Switzerland North and Switzerland West
    Hosted agents with their own loop in a container, their own Entra identity and publishing to TeamsAvailableYes, Switzerland North and Switzerland West
    Restart of long runs of hosted agents after a crashGenerally available this week according to the Foundry blog; the Learn page still lists it as previewExpected with hosted agents in both Swiss regions, Microsoft names no separate region list
    Own Entra identity per agent, visible in the Entra admin centerAvailable; access on behalf of the person in previewYes, the identity applies tenant-wide
    Regional models in Switzerland North: gpt-4.1, gpt-4o, gpt-5.1, embeddingsGenerally availableYes, for prompt agents without the harness and for hosted agents

    Foundry stores conversations, files and agent definitions in the region of the project. A harness agent in Frankfurt therefore keeps its data in Germany, and its model computes in the EU data zone or in Sweden. How we map data classes to deployment types is described in our guide to data boundaries.

    What it costs

    Until 30 November 2026 the harness runtime is free. From 1 December 2026 Microsoft bills the sandbox at USD 0.0994 per vCPU hour and USD 0.0118 per GiB hour, with variations by region and agreement. Model calls, web search, Code Interpreter and connected services are added as before. Prompt agents without the harness cost nothing extra in Agent Service.

    Foundry allocates CPU and memory to the sandbox itself; you cannot set them. A forecast therefore needs a test run with real files. How the other cost items of an agent in Foundry add up, we calculate in the article What an agent in Microsoft Foundry really costs.

    When we recommend which route

    The work happens in mail, documents and Teams, and a person checks every result. Microsoft Copilot is enough. An agent on the harness adds little here, because Copilot already knows the data in Microsoft 365 and the licence covers the use.

    A business team wants an agent in Teams, connected to two or three systems. Copilot Studio fits. The loop is the same, the interface is built for business experts, and publishing, approvals and billing run through Microsoft 365.

    The agent works with files, calculates, writes reports and should be versioned in the Git repository. Then we build on the harness in Microsoft Foundry, with skills for the recurring procedures and MCP tools with approval for everything that writes into other systems. Precondition during the preview: the data may be processed in the EU, and your data protection officer has recorded that. The quotes of the machine builder in Winterthur are a typical case.

    Personal data or professional secrets must stay in Switzerland. Then the agent runs as a hosted agent or as a prompt agent without the harness in Switzerland North, with the models available there regionally. For payroll, patient data or client files this is the route today. As soon as Microsoft brings the harness to a Swiss region, we review the move.

    How we build and run such agents in Foundry is described on our Microsoft Foundry page.

    What it means for governance

    Every new agent in Foundry receives its own agent identity in Microsoft Entra ID. It appears in the Entra admin center next to the agents from Copilot Studio, starts without permissions and can be governed with Conditional Access, sign-in logs and audit logs. For a harness agent to return files, its identity needs the Foundry User role on the project, nothing more.

    The shell is the broadest tool in the harness. Microsoft itself writes that switching off the file tools draws no boundary as long as the shell is on. We switch it on only when the procedure needs scripts, and then set network rules: first in audit mode to see the destinations needed, then as an allow list of hosts in enforce mode.

    We treat skills like code. They live in the repository, go through a review and are bound to the agent as a fixed version. Writing MCP tools require approval per call, so that a person always sees an order, a booking or a dispatch.

    Limits

    The harness is a preview without a service level agreement, and Microsoft advises against production workloads. Microsoft names no date for Swiss regions. The documentation says nothing about evaluating harness agents; the Foundry portal shows traces of every response. Whether a harness agent can be published to Teams or Microsoft Copilot, Microsoft so far describes only for hosted agents. The statements on restarting long runs differ between blog and documentation; we will update the table once Microsoft aligns them.

    Next step

    Which of your procedures suit an agent, and where may it compute? Send us two or three candidates with their data class. You get our recommendation per procedure for Microsoft Copilot, Copilot Studio or Microsoft Foundry, with the state of availability in Switzerland. I look forward to the conversation.

    Marcel Haas, CEO CNEXT

    Sources: Jeff Hollan, Viswajeeet Balaji and Anthony Chu, "Introducing the Microsoft Copilot harness in Foundry Agent Service", Microsoft Foundry Blog, 28 October 2026. Tina Schuchman and Vladimir Fedorov, "Introducing the Microsoft Copilot harness", Microsoft, 28 October 2026. Microsoft Learn, Use the Microsoft Copilot harness with prompt agents and Quotas, limits and regions for Foundry Agent Service, both as of 29 October 2026; Hosted agents, as of 19 October 2026; Resilience for long-running hosted agents, as of 30 July 2026; Agent identity concepts, as of 28 October 2026; Create and manage a toolbox, as of 26 October 2026; Region availability for Foundry Models, updated 19 October 2026. All facts checked on 30 October 2026.

    Agentic AIGovernanceSchweizGitHub Copilot
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    6x Microsoft Applied Skills

    Classify procedures for agents

    We map your procedures to Microsoft Copilot, Copilot Studio or Microsoft Foundry and record what of it runs in Switzerland today.