Microsoft Defender XDR
General

Ai Agent Detection Protection

In brief

The documentation now states that unpublished Foundry agents, including playground-only agents, aren't supported for threat detection and links to publishing guidance. It also updates terminology and metadata.

What Defender admins need to know

Only published Foundry agents are covered, so review publishing status when assessing AI agent detection coverage.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

  • Ensure that your AI agent emits observability data to Microsoft 365:
    • Agents built with Microsoft Copilot Studio, Microsoft Foundry, and declarative agents built with the Microsoft 365 Copilot Agent Builder send observability data to Microsoft 365 by default.
    • For AI agents built on other platforms, enable observability using the Microsoft Agent 365 SDK, as described in the Agent 365 development lifecycle documentation.

Detect AI agent threats in near-real-time

Microsoft Defender continuously monitors AI agent activity and detects suspicious and malicious behavior for all Agent 365‑365-managed agents. Defender analyzes agent telemetry, tool usage, and execution patterns to identify threats such as jailbreak attempts, XPIAindirect prompt injection (XPIA) attempts, malicious content propagation, secretssecret and credentials leakcredential leakage, evasion techniques, suspicious user accesslarge language model (LLM) reconnaissance, and more.suspicious user or IP access.

Microsoft Defender surfaces detections as near‑real‑time alerts in the Defender portal and enables security teams to investigate them using familiar security operations workflows, including alert triage, incident correlation, and Advanced Hunting.