AI agents: access granted. Trust not included | THR877

Leandro Iwase and Ehud Itshaki present an intermediate-level Microsoft Ignite 2026 session on securing AI agent access with Microsoft Entra Agent ID. They cover identity architecture, agent discovery, risk signals, and access controls, followed by demonstrations of policy enforcement.

Separate identities for AI agents

AI agents need access to applications, data, and resources, but inheriting a user’s permissions can give them more access than they should have. The session explains the need for separate agent identities rather than treating user access as a blank check for an agent.

The architecture discussion spans Microsoft and third-party agents, including agents running in the cloud and locally. Microsoft Entra Agent ID provides the focus for securing agent connections and limiting risky permissions.

Discover, manage, govern, and protect agents

The presenters organize agent security around four activities:

The discovery segment covers Microsoft Defender and Global Secure Access, with a later demonstration showing discovery, risk scoring, and visibility into local AI agents. Network controls are also part of the session’s approach to reducing risk.

Dynamic risk and Conditional Access

The session covers unified, dynamic agent risk signals across Microsoft Entra, Microsoft Defender, and Microsoft Purview. It then examines how Conditional Access can use dynamic controls to restrict or block risky agents.

The announcement segment addresses previews for Entra Agent ID, dynamic agent risk, and Conditional Access. The demonstrations show how these controls respond to agent activity, including:

Session chapters

Resources