I debugged Power Automate flows this week without opening the Power Automate designer once.
Claude Code, connected to the Power Automate MCP server.
The workflow: I describe the failure symptom. Claude pulls the flow definition, walks the run history, finds the failed action, reads the inputs and outputs on either side of it, and tells me what actually broke — not what the error message claims broke.
Anyone who has debugged a flow through the designer knows the ritual. Open the run. Expand the action. Expand the next action. Squint at a JSON blob in a box four lines tall. Repeat for forty actions. The designer is a fine authoring surface and a miserable debugging surface.
An agent with MCP access doesn’t squint. It reads the run history as data, diffs the failing run against the last successful one, and comes back with the actual cause: a connector started returning a different schema last Tuesday, and here’s the expression that stopped resolving.
Doing this for real rather than as a demo has taught me two things. The agent is only as good as its access — scope the connection to the environments you want it reading, because least privilege matters more with agents, not less. And it’s fastest on exactly the failures humans are slowest at: schema drift, expression evaluation, pagination weirdness. The unglamorous 80% of what actually breaks.
Step back and notice what this is. A Claude agent debugging Microsoft’s automation layer through an open protocol. Cross-platform agentic work isn’t a slide anymore. It’s just work now.
The platform you author in and the platform you operate from are decoupling. Architects should be watching that seam.