Skip to content

THR980 Theater Wed 18 Nov 09:35 PST

Who Owns This Agent? Identity, Data, & Control across Microsoft Clouds

Martina Grom

Summary

From the recording

Martina Grom walked through a Foundry agent connected to Work IQ via MCP using delegated permissions, so users only see data they can already access. She said traces in Azure can also hold that data, and that routing sensitive content to a dedicated table via App Insights is still in preview. She described six agent objects, owner and sponsor roles, and Agent 365 discovery, disable and block controls. Caveat: the session was demo-led; the Agent 365 block option was called new without a date, and no licensing or availability dates were given.

Session description

Microsoft's catalogue description

Building an AI agent is easy. Governing it is the hard part. A Microsoft Foundry agent can access Microsoft 365, Microsoft IQ data, identities, and business content across multiple platforms. But who owns it, what can it access, and how do you retire it safely? Follow a real-world agent from deployment to decommissioning and learn the four governance controls every production agent needs: Ownership, Identity, Data Boundary, and Lifecycle.

Demo timestamps

Microsoft's player does not support links to a specific time, so open the recording and skip to the time shown.

  1. Skip to 2:21

    Customer briefing agent connected to Work IQ

    Demo setup of a customer briefing agent connected to Work IQ.

Watch on-demand (opens in a new tab)

← All sessions