Microsoft and Google push governance

AI agents are starting to look less like chatbots and more like employees with software access. That changes the problem. The hard part is no longer just getting a model to answer questions — it’s deciding what an agent is allowed to touch, what it can trigger, and how anyone proves what happened after the fact. That is why this week’s Microsoft and Google moves matter. They push AI-agent governance out of the lab and into ordinary enterprise IT. (computerworld.com) ### What changed this week? Microsoft moved Agent 365 into general availability on May 1, 2026, turning its agent control layer from preview into a product enterprises can actually buy and standardize on. Google used Cloud Next 2026 to pitch an “agentic enterprise” stack, including its Gemini Enterprise Agent Platform (computerworld.com)rise actors, not just clever assistants. (venturebeat.com) ### Why is governance suddenly the main event? Because agents do things. A chatbot that drafts text is one risk category. An agent that can read Slack, open Salesforce, call an API, update a ticket, and message a customer is another. Once software can act across systems, old questions come rushing back in a new form — identit(venturebeat.com) layer is becoming the bottleneck. (computerworld.com) ### What is Microsoft actually selling? Microsoft’s pitch is broad control across mixed environments. Its open-source Agent Governance Toolkit focuses on runtime policy enforcement for autonomous agents and says it covers all 10 OWASP agentic AI risks with deterministic controls. The bigger idea is familiar Microsoft p(computerworld.com)t. Basically, Microsoft wants agents to fit into the same control plane enterprises already use for people and devices. (opensource.microsoft.com) ### What is Google pushing instead? Google’s framing is narrower but still important. At Cloud Next 2026, it centered the “agentic enterprise” and launched tooling to build and manage agents on Google Cloud, with a lot of emphasis on Workspace, data, and operational oversight inside Google’s ecosystem(opensource.microsoft.com)ss-company automation. (cloud.google.com) ### Why is cross-platform control the hard part? Because the real enterprise stack is messy. Most large companies do not live inside one vendor’s clean diagram. They use Microsoft 365, Google Workspace, Salesforce, ServiceNow, Workday, custom apps, and old internal systems all at once. Governing an agent inside one suite is manageable. Governing an agent t(cloud.google.com)r supervision. That is where policy drift, over-permissioning, and audit gaps show up. (computerworld.com) ### What new work does this create for IT? A lot of unglamorous but valuable work. Someone has to define policies, write evals, map permissions, review logs, set escalation rules, and decide when an agent needs a human checkpoint. Analysts are already describing this as a shift from raw model access toward observabilit(computerworld.com) safely at scale.” (computerworld.com) ### Does regulation matter here? Yes — and the timing is not accidental. Microsoft’s own governance toolkit post points to the EU AI Act’s high-risk obligations taking effect in August 2026 and Colorado’s AI law becoming enforceable in June 2026. Even when these specific rules do not directly govern every agent, they push enterprises toward better records, controls, and accountability. Governance is becoming a compliance story as much as a product story. (opensource.microsoft.com) ### So what is the bottom line? The market is moving past “can we build agents?” and into “can we control them?” Microsoft and Google are both trying to own that answer. But the winner may be whoever makes cross-platform governance boring, legible, and auditable enough for a normal IT department to trust.