Welcome to the Cloud Wars Agent and Copilot Minute — your daily cloud news and commentary show. Each episode provides insights and perspectives around the “reimagination machine” that is the cloud.
In today’s Cloud Wars Agent and Copilot Minute, I analyze how Microsoft is addressing the limitations of pure AI autonomy in enterprise automation.
Highlights
00:09 — Microsoft has introduced new capabilities to Copilot Studio to enhance automated operations by combining AI agents and workflows. Currently, Copilot Studio users can choose between agents and workflows to create automations.
00:27 — While agents are inherently flexible when it comes to business use cases, Microsoft has recognized that, as they state, pure agent autonomy doesn’t always hold up to production requirements. On the other hand, workflows, which are more rigid and rule-based, can be inflexible and may have limitations in their capabilities.
00:58 — The first pattern involves workflows calling agents to make judgment calls on structured automations. To support this, Microsoft is introducing agent nodes. This allows users to call an existing agent from a workflow, send a message to the agent, retrieve the agent’s response, and use it in subsequent workflow steps if necessary.
01:31 — Now, the second pattern that Microsoft has identified is using workflows as tools. In this scenario, when an agent is working through a complex task, instead of trying to learn how to handle it independently, it can call an existing workflow to execute the subprocess and then continue its reasoning based on the results.
02:29 — Microsoft states that these two approaches combine agents and workflows to provide users with the flexibility to build automations that better address real-world needs—and that’s the key here: real-world applications.
Kieron Allen
Analyst
Cloud Wars, Agent and Copilot
Related Posts
