Moving Beyond the Visio: Practical Governance for Agentic Workflows in Multi-Cloud Environments
Last month, I was pulled into a post-mortem for a 'small automation pilot' that went sideways. A developer had deployed a Python-based agent designed to 'optimize' cloud spend by scanning resources across AWS and Azure and shutting down underutilized instances. Sounds great on paper. In reality, the agent hit a rate limit on the Azure Resource Manager API, misinterpreted the error code, and started a recursive loop that tried to re-authenticate every 50 milliseconds. It didn't just crash the local service; it triggered a security alert that locked out the entire automation service principal across three production subscriptions. This is the reality of moving from static scripts to what everyone is calling 'Agentic Workflows.' We aren't just dealing with a cron job anymore. We are dealing with autonomous code that makes decisions—deciding which API to call, which data to move, and how to respond to errors. As Enterprise Architects, our job is shifting. ...