Copilot Studio’s new agentic workflow is evolving fast, and it now makes it easy to combine automated flow orchestration with M365 Copilot agent execution. If you have used Microsoft Foundry Workflow, the interface will feel familiar: a visual designer with triggers, actions, inline testing, flow notes, and governance hooks. What’s new in Copilot Studio agentic workflows Version control with built-in version comparison Action-level testing without running the full flow One action to initialize multiple variables Create and invoke agents directly from the workflow designer Flow-level sticky notes for context and documentation Built-in classification, human review, prompt orchestration, and M365 Copilot integration Flexible layout switching between horizontal and vertical A Tidy button to reorganize the designer automatically Easier disconnect/reconnect support for actions and connections Invoking an M365 Copilot Declarative Agent In this post I demonstrate how to invoke an M365 Copilot agent (a DeclarativeAgent) from a Copilot Studio workflow.

Introduction When building agents in Microsoft Copilot Studio, you’re faced with a fundamental choice: Classic Orchestration or Generative AI Orchestration. Understanding the differences between these approaches is crucial for making the right architectural decision for your chatbot project. Enabling Generative AI unlocks dynamic capabilities where responses are intelligently crafted using available tools and knowledge sources as needed. In contrast, Classic Orchestration restricts responses to only the predefined content and behaviors explicitly configured in your agent’s topics.

Develop in the cloud with Microsoft Dev Box by Dona Sarkar I attended the session Develop in the cloud with Microsoft Dev Box at MS Build AI Day by Dona Sarkar on the 19th Oct 2023. Dona started the session to gauge the audience how long it takes to set up a dev environment before a Dev can submit their first PR. It takes between 1-5 days for Dev environment set up.