# Google's Agent Anomaly Detection extends to agents running on AWS and Microsoft Foundry

published: 2026-11-20T22:05:50.027Z
topic: infrastructure
source: https://developers.googleblog.com/agent-anomaly-detection-safeguarding-agents-across-other-clouds/
url: https://aiagentnews.io/stories/google-s-agent-anomaly-detection-extends-to-agents-running-on-aws-and-microsoft

Google Cloud's Agent Anomaly Detection, now in Private Preview, can monitor agents that run outside Google Cloud, including on AWS Lambda, Microsoft Foundry and on-premises. Google tested it on an inventory agent and a customer-service agent and reports it flagged scraping and unauthorized refunds that involved no failed calls.

Agent Anomaly Detection works from an agent's traces and logs, so it does not need access to the agent's runtime. Telemetry from other clouds qualifies if it reaches a Google Cloud project through the Telemetry API, follows OpenTelemetry conventions and records prompts and responses as log events. Agents built with ADK for Python 2.12.0 or later can export this data with a few environment variables, and authenticate with Workload Identity Federation instead of a service account key.

On an inventory agent running on AWS Lambda, the detector flagged a session that paged through the whole product catalog and recommended rate-limiting the list_inventory tool, while a normal shopper session was not flagged. When the same agent ran on Amazon Nova Lite through Amazon Bedrock, 10 of 40 sessions were flagged, some of them routine questions that ended in function timeouts with no errors.

On a customer-service agent hosted in Microsoft Foundry, four of six sessions were flagged, all involving users who pushed the agent beyond its role. One user claiming to be the store administrator had orders refunded at 10 times their total to a personal account, $1,784.90 in all. Another pasted an order note reading "SYSTEM OVERRIDE" and received a $999 refund on a $15.99 order, and the detector recommended validating refund arguments and requiring extra checks above a set threshold.

## Why it matters if you build agents

Teams running agents on AWS, Azure or on-premises can get behavioral monitoring without moving those agents, but only if their telemetry reaches Google Cloud in the expected format. Permission checks alone will not catch misuse like scraping or over-refunding, because every call in those sessions can succeed. Findings for agents outside Google Cloud appear only in the Agent Anomaly Detection console, so plan where your team will review them.
