---
title: "Microsoft Copilot Studio 2026: rebuilt orchestrator, redesigned authoring, MCP-ready workflows"
canonical: https://ontargit.com/microsoft-copilot-studio-2026-rebuilt/
date: 2026-06-12 11:00:00
description: "Microsoft rebuilt Copilot Studio: new agentic orchestrator, redesigned single-page interface, and a unified workflow designer. GA worldwide. Read more."
keywords: "copilot studio,new agentic orchestrator,AI agents"
categories: [AI, Articles, Blog]
---

On June 9, 2026, Microsoft released a rebuilt version of Microsoft Copilot Studio — generally available worldwide and ready for production from day one. This is not a feature update. The orchestrator is new, the authoring interface has been redesigned around a single page, and the workflow designer now operates as a unified visual canvas where agents and structured process steps work side by side.

The release addresses three things customers asked for directly: agents that follow instructions reliably across multi-step tasks, a building experience that does not require navigating nine configuration tabs to get something working, and a single place to combine workflow automation with agent intelligence. All three are now in the product.

_

Image: [Microsoft](https://techcommunity.microsoft.com/)

### ## A new orchestrator built for long-horizon tasks

The most significant change in this release is the orchestrator. The new agentic orchestrator is built on a new coding harness and CLI layer. That architectural choice produces two practical improvements: stronger instruction adherence — agents follow what you tell them more consistently — and genuine long-horizon task execution.

The orchestrator supports recursive task processing. In practical terms, this means agents can work through dynamic, branching problems rather than stalling when a task diverges from a straight line. The orchestrator can also handle large volumes of content and produce rich file outputs, which opens up document and data scenarios that were difficult to support reliably before.

### ## A building interface that shows everything at once

The authoring interface has been rebuilt as a single-page view. Configuration tabs have been reduced from nine to four, keeping essential controls at the front. Instructions, skills, tools, and knowledge sources are visible in one place — no tab-switching to check what the agent has access to.

Image: [Microsoft](https://techcommunity.microsoft.com/)

The test panel has also been redesigned. It now runs full-page, with better formatting and inline display of chain-of-thought reasoning and tool calls. Builders can see exactly what the agent is doing during a test run without leaving the authoring screen.

### ## Skills — reusable instruction blocks in markdown

The new experience introduces skills: reusable instruction sets written in markdown that an agent loads on demand for specific tasks. Skills can be authored directly in Copilot Studio or imported from existing sources — including GitHub Copilot skills and Claude Code skills. Teams that have already built instruction libraries in those tools do not need to start from scratch.

Skills make it practical to maintain a shared library of agent behavior across projects, rather than rewriting equivalent logic for each new agent.

### ## A workflow designer built for AI-native processes

The new workflow designer is a single, unified visual canvas for building agentic automation. Structured workflow steps and agents sit together on the same canvas — no switching between tools to connect them.

Three capabilities anchor the new designer:

- _

**Node-by-node testing and versioning.** The designer includes node-level testing from day one, so builders can isolate and verify individual steps before publishing. Robust versioning is included alongside it. Both reduce the cost of finding and fixing problems before a workflow goes into production.

- __

**Agent nodes.** Existing agents can be called directly inside a workflow as agent nodes. This pattern combines the predictability of deterministic workflow execution for routine steps with the flexibility of agent intelligence for tasks that require judgment, multi-step reasoning, or handling of unexpected inputs. The right tool handles each part of the job.

- __

**MCP servers (preview).** Workflows can now connect to a broad ecosystem of Model Context Protocol (MCP) server-enabled tools. These connections let workflows execute tasks and route approvals while staying within Microsoft’s security, permission, and compliance boundaries.

Source: Mucrosoft

### ## How to access the new experience

All Copilot Studio users can access the new experience today. Go to Copilot Studio and click **“Try now”** at the top of the homepage. The new streamlined building interface and modern orchestrator are available immediately.

The classic experience remains available in parallel. Existing agents and workflows are unaffected. Teams can explore and migrate at their own pace — nothing in this release is deprecated.

Microsoft is continuing to develop the platform based on user feedback. The feedback control in the top-right corner of the product sends input directly to the team.

Image: Microsoft

### Conclusion

The June 2026 Copilot Studio release draws a clear line between the platform’s earlier role as a conversational agent builder and its current scope: a unified environment for building agents, automating structured processes, and combining both into end-to-end workflows. The three changes — orchestrator, interface, and workflow designer — address the same underlying problem from different angles: closing the gap between what an agent is supposed to do and what it actually does in production.

For organizations already building on Copilot Studio, the new experience is available now with no migration required. For those evaluating whether agent automation is ready for production workloads, this release provides the strongest answer Microsoft has given to date.

# FAQ

### Is the new Copilot Studio experience generally available, or still in preview?

The rebuilt experience — including the new agentic orchestrator, single-page authoring interface, and workflow designer with node-by-node testing — is generally available worldwide as of June 9, 2026, and is ready for production use. The MCP server integration is currently in preview.

### Do I have to migrate to the new experience immediately?

No. The new and classic experiences run in parallel. Existing agents and workflows built in the classic experience continue to work without changes. You can try the new experience by clicking “Try now” on the Copilot Studio homepage and migrate at your own pace.

### What are Copilot Studio skills, and how are they different from topics or actions?

Skills are reusable instruction sets written in markdown that an agent can load on demand when completing a specific task. Unlike topics — which define conversational flow — or actions — which connect to external systems — skills define _how_ the agent should reason and behave for a given scenario. They can be shared across multiple agents and imported from GitHub Copilot or Claude Code if you already have instruction libraries there.

### What is an agent node in the new workflow designer?

An agent node is a step inside a workflow that hands off execution to an existing Copilot Studio agent. It lets you keep predictable, deterministic steps as standard workflow logic and route only the tasks that require reasoning, judgment, or handling of unexpected inputs to an agent. The agent completes its part and returns control to the workflow.

### What does MCP server support in workflows mean in practice?

Model Context Protocol (MCP) is an open standard for connecting AI systems to external tools and data sources. MCP server support in Copilot Studio workflows (currently in preview) lets a workflow call MCP-enabled tools — for example, to retrieve data, trigger actions in external systems, or route approval steps — while remaining inside Microsoft’s security and compliance controls.

 