`AIAgentsInfo` → `AgentsInfo`: A Technical Migration Guide Before the July 1, 2026 Cutoff

6 min readJun 16, 2026

Deadline: July 1, 2026. The AIAgentsInfo Advanced Hunting table is being deprecated and replaced by the new, unified AgentsInfo table, powered by Microsoft Agent 365 as the single source of authority for AI agent inventory. Saved queries, custom detections, workbooks, and automation that still reference AIAgentsInfo will return empty result sets or errors after this date.

First things first …

This is not a table rename. Column names and types changed, the primary key changed, and the data source changed. A find-and-replace of AIAgentsInfo → AgentsInfo will result in errors if the column (e.g.UserAuthenticationType) is not present.

Disclaimer many specific security Copilot Studio queries cannot be migrated to the new AgentsInfo table (e.g. No Authentication, Maker-credentials, etc.)

Microsoft does auto-migrate queries saved inside the Defender portal, including those backing custom detection rules. But because the migration has to map a Copilot Studio–shaped schema onto a unified one where columns were renamed, split, and retyped, treat every “auto-migrated” query as suspect and re-validate it, many (I repeat many) queries may still need validation or cannot be migrated at all.

I tested all community queries and none of them worked with the new AgentsInfo table due to nonexistent columns.

Why the change?

AIAgentsInfo was introduced during the preview of Microsoft's AI agent security features and was built for Copilot Studio. Many of its columns were platform-specific (UserAuthenticationType, IsGenerativeOrchestrationEnabled, AgentTopicsDetails), and its Platform column effectively only ever returned Copilot Studio.

It was populated through the Defender for Cloud Apps AI Agents inventory connector.

As Microsoft Agent 365 matures into the central governance plane for all AI agents, a unified table was required.

The new AgentsInfo table is established through Security for AI in the Defender portal and provides one schema for Copilot Studio, Microsoft Foundry, Microsoft 365 Copilot, third-party agents, and endpoint-discovered agents.

To query it: Investigation & response → Hunting → Advanced hunting → query the AgentsInfo table.

⚠️Column inconsistency

At the time of writing there’s a column inconsistency in the Microsoft Docs versus the AgentsInfo Schema, see Name as example.

What’s new in `AgentsInfo`

The schema expands into four areas that matter for security posture:

🔹 Identity & origin

AgentId, SourceAgentId (platform-native ID), EntraAgentId (the agent's enterprise-application object ID in Entra), EntraBlueprintId (the identity blueprint the agent was minted from) and Platform.
ToolsAuthenticationType — structured summary of the agent's identity/auth/authz model.
Permissions — requested vs. granted permissions, approval state, and consent enumeration.

🔹 Lifecycle & deployment

PublishedStatus (Draft / Published) and LifecycleStatus (Active / Blocked / Uninstalled / Deleted) — together these replace the old single AgentStatus column and the boolean IsBlocked.
Availability, CreatedDateTime, LastPublishedDateTime, LastUpdatedDateTime, Owners, SharedWith.

🔹 Configuration & runtime surface (the real hunting value)

Instructions (system prompt), Model, Channels, Capabilities, DeclaredDataSources, DeclaredTools.
McpServers — connected Model Context Protocol servers, including server URLs and credential configuration (now a first-class column, not buried in a tools blob).
Skills, ConnectedAgents, Memory, Triggers, Guardrails, Endpoints (with transport type and an external-connectivity flag), ObservabilityId.

And a future-proofing column: RawAgentInfo, now dynamic JSON (it was string in the old table), carrying additional provider data so the schema can evolve without data loss.

Column mapping: `AIAgentsInfo` → `AgentsInfo`

⚠️ Microsoft has not published an explicit field-by-field crosswalk. The mappings below are derived by comparing the two published schemas , verify against your own queries.

**Microsoft Docs [**⚠️ **AgentName is Name in the Schema]**

Because RawAgentInfo is now dynamic, replace parse_json(RawAgentInfo).x with direct access RawAgentInfo.x. And note that fields you used to dig out of the JSON blob , modelNameHint, publishedStatus , are now first-class columns (Model, PublishedStatus), so you often won't need RawAgentInfo at all.

Query migration & examples

1️⃣ Inventory of all agents

// ⛔ OLD — breaks after July 1, 2026
AIAgentsInfo
| summarize arg_max(Timestamp, *) by AIAgentId
| where AgentStatus != "Deleted"
| project AIAgentName, Platform, AIModel, EntraObjectId, IsBlocked

// ✅ NEW — AgentsInfo, powered by Agent 365
AgentsInfo
| summarize arg_max(Timestamp, *) by AgentId          // AgentId, not AIAgentId
| where LifecycleStatus != "Deleted"
| project Name, Platform, Model, AgentId, LifecycleStatus, PublishedStatus

2️⃣ Published agents missing a system prompt [prompt-injection risk]

// ✅ NEW
AgentsInfo
| summarize arg_max(Timestamp, *) by AgentId
| where PublishedStatus == "Published"
| where LifecycleStatus != "Blocked"        // there is no IsBlocked column anymore
| where isempty(Instructions) or Instructions == "N/A"
| project AgentId, Name, LifecycleStatus, PublishedStatus, Model, Platform

3️⃣ Which models are in use across the estate [Compliance]

// Model is now a first-class column; RawAgentInfo (dynamic) is only a fallback
AgentsInfo
| summarize arg_max(Timestamp, *) by AgentId
| where LifecycleStatus != "Deleted"
| extend modelHint = coalesce(tostring(Model), tostring(RawAgentInfo.modelNameHint))
| where isnotempty(modelHint)
| summarize AgentCount = count() by modelHint, Platform
| sort by AgentCount desc

4️⃣ Agents with MCP servers configured [attack-surface review]

// McpServers is a first-class dynamic column — no parse_json, no AgentToolsDetails
AgentsInfo
| summarize arg_max(Timestamp, *) by AgentId
| where LifecycleStatus != "Deleted"
| where array_length(McpServers) > 0
| mv-expand server = McpServers
| project AgentId, Name, Platform, Server = server
// Inspect one row to confirm subfields (e.g. server.url) before projecting them

Recommended “Top Risk” Copilot Studio query

AgentsInfo
| summarize arg_max(Timestamp, *) by AgentId
| where Platform == "Copilot Studio"
| where PublishedStatus == "Published"
| project
    Name,
    Owners,
    SharedWith,
    ToolsAuthenticationType,
    Permissions,
    DeclaredTools,
    McpServers

Again many specific security Copilot Studio queries cannot be migrated to the new AgentsInfo table (e.g. No Authentication, Maker-credentials, etc.)

Licensing & prerequisites

The AgentsInfo table is exclusively powered by Microsoft Agent 365. Without an eligible license, queries return no results. Effective July 1, 2026, AI agent security capabilities for Copilot Studio and Foundry agents require a Microsoft Agent 365 license.

Prerequisites to validate:

Agent 365 eligible (e.g. Microsoft 365 E7) license assigned.
Preview features ON: Settings → Microsoft Defender XDR → Preview features.
Security for AI toggle ON, post-cutover this is the tenant-wide master switch; when off, AgentsInfo queries are disabled.

Agent 365 migration guidance

The table swap is one part of agent security moving into Agent 365.

🔹Block mode enforcement ends
Existing real-time protection rules stop actively blocking: source

🔹Detection data moves
AI security events move to the new BehaviorInfo table: source

🔹Policies must be recreated
Existing block rules need to be reconfigured in the new Security for AI policy engine: source

🔹Licensing enforcement begins
Agent 365 licensing becomes required for certain AI security capabilities.

Always verify the latest Microsoft guidance, as preview timelines and licensing requirements may change.

I hope this blogs helps with the transition to the new Agent 365 Security framework🙏

AIAgentsInfo → AgentsInfo: A Technical Migration Guide Before the July 1, 2026 Cutoff