CISO
Enterprise Architect
Compliance Officer
Industry relevance
Financial Services
Government
Retail
APRIL 30, 2026
The Agent 365 tooling gateway moves AI agent enforcement to pre-execution blocking. If yours isn’t configured, agents are acting before any control fires.
Microsoft published the inaugural In the Loop security update on April 30, 2026, authored by Alym Rayani, VP of Marketing for Microsoft Security. Highlights include: Microsoft Defender capabilities in preview in the Agent 365 tooling gateway enabling near-real-time detection, blocking, and investigation of anomalous AI agent behavior using webhooks before execution; Defender for Cloud integration with GitHub Advanced Security reaching GA for unified development lifecycle security visibility; and Microsoft Purview Data Security Investigations offering AI-powered deep content analysis for data security incidents.
GOVERNANCE IMPLICATION
The Agent 365 tooling gateway preview shifts the enforcement surface for agent actions from post-incident review to pre-execution prevention — a material change in what can be demonstrated to a regulator. Organizations that have deployed agents without configuring the tooling gateway are running agents that can execute actions before any detection fires. That is the Accountability Assumption in its most exposed form: the assumption that detection and logging is sufficient when the control point is actually pre-execution.
SCENARIO
An enterprise retailer has deployed 12 Copilot Studio agents for inventory, logistics, and customer service workflows. The security team learns the Agent 365 tooling gateway preview enables near-real-time pre-execution blocking of anomalous agent behavior. The CISO asks whether the gateway has been configured for the 12 deployed agents. IT confirms it has not. The CISO then asks what happens when an agent executes an anomalous action before the gateway is configured. The answer: the action executes, is logged, and is reviewed post-incident.
THE GOVERNANCE QUESTION
Have you configured the Agent 365 tooling gateway for your deployed agents — and if not, what is executing before your first detection fires?
CONTROL GAP
Organizations that have deployed agents without configuring the Agent 365 tooling gateway are operating with detection-only coverage — anomalous agent actions execute before any control fires. The shift to pre-execution blocking is available but requires deliberate configuration that most deployments have not completed.
REGULATORY RELEVANCE
SEC Cyber
FFIEC
DORA
OCC
PRIMARY SOURCE
What's new, updated, or recently released in Microsoft Security
Alym Rayani
April 30, 2026
Read the primary source →(opens in new tab)CONTINUE READING
MAY 11, 2026
AgentsMicrosoft Copilot Studio published April 2026 feature updates on May 11, 2026, authored by Nitasha Chopra, VP and COO of Copilot Studio. Key releases include the Analytics Viewer role reaching GA providing read-only access to agent analytics separated from configuration rights; agent nodes embeddable directly into workflows to delegate AI reasoning within deterministic automation; MCP server-enabled tools in preview for external system connectivity within workflows; and a centralized admin-controlled DLP-enforced environment for the Workflows Agent. The post also confirms Microsoft Agent 365 is now generally available as the centralized control plane for agents.
MAY 5, 2026
AgentsMicrosoft's 2026 Work Trend Index Annual Report, published May 5, 2026, includes the first WTI telemetry on AI agent volume. Active agents on Microsoft 365 grew 15x year-over-year across all customer segments, rising to 18x in large enterprises. This is the first time Microsoft has disclosed agent volume scale as part of its annual workforce research.
MAY 1, 2026
AgentsMicrosoft's May 1, 2026 What's New in Agent 365 announcement introduced registry sync, allowing organizations to connect the Agent 365 registry to external agent platforms. Initial preview connections include Amazon Web Services and Google Cloud, with additional partner platforms planned. When connected, agents built on those platforms appear in the Agent 365 unified registry with governance actions including agent deletion available directly from the registry interface. Without registry sync connections configured, Agent 365 shows only Microsoft-hosted agents.