Microsoft rebuilds Copilot Studio for multi-step agent workflows
Microsoft's rebuilt Copilot Studio introduces a new agent experience for complex, multi-step work. The preview highlights orchestration, testing and governance.
A new authoring and orchestration experience
Microsoft announced a rebuilt Copilot Studio preview on 9 June 2026 for creating agents that handle more complex, multi-step work. Its updated experience uses natural-language-first authoring and a new orchestration runtime rather than requiring every path to be assembled as a fixed conversation flow.
Microsoft's documentation organizes the lifecycle into building, previewing, evaluating, publishing and monitoring an agent. It also separates knowledge, tools, reusable skills, models and connected specialist agents in the authoring surface.
The practical opportunity for Microsoft 365 businesses
A business already operating in Microsoft 365 may be able to ground an agent in organizational information and connect it to approved tools without introducing a completely separate user interface. Potential workflows include preparing meeting context, organizing requests, updating records and producing reviewable summaries.
The platform choice should still follow the workflow. Copilot Studio is most relevant when Microsoft data, identity and governance are central requirements; another platform may be simpler for a lightweight public website or messaging workflow.
Preview status requires careful evaluation
Microsoft states that the new and classic agent experiences use different architectures and currently have no migration path between them. Existing classic agents can continue operating, while new projects can evaluate whether the new orchestration model fits their requirements.
Teams should validate feature availability, regional support, licensing, connector behavior and governance before committing a production workflow to a preview architecture.
- Choose the authoring experience before building a large workflow.
- Test with real Microsoft 365 permissions and representative data.
- Use the evaluation surface to track regressions before publishing.
- Confirm licensing and preview limitations in the current documentation.
Sources and further reading
Primary references used to prepare this guide.

