This session shows how to get control of it using the Microsoft stack. We start with why the old model stops working. A human identity is created by HR and reviewed once a quarter. An agent identity is created from a blueprint in minutes, can clone itself, can call other agents, and makes access decisions in the middle of a conversation. Meanwhile, DLP still only looks at files and mail, not at prompts, inference, and tool calls. 6 We then name the four things that go wrong in practice: identity sprawl, data oversharing, tool misuse, and gaps in your compliance record, including agents left behind with no owner after their creator leaves the company.

The rest of the session covers Microsoft Agent 365 as a control plane rather than another admin console. It shows up inside the Microsoft 365 admin center, Entra, Purview, and Defender, and it works across Copilot Studio, Microsoft Foundry, AWS Bedrock, and Google Vertex AI. 758 We go through the three pillars in order.

See what you have. The central agent registry, sync across clouds, the agent map that shows how agents relate to each other, live adoption and health signals, and discovery of local agents running on real laptops.

Set the rules. The three building blocks in Entra Agent ID (blueprint, agent identity, agent user account), how an agent signs in with federated credentials over OAuth 2.0 and OIDC so no secret sits on the agent, Conditional Access for autonomous agents versus on-behalf-of agents, inherited permissions so new agents start narrow, and a five-stage lifecycle that includes what to do when a sponsor leaves.

Protect the data and catch the threats. Purview DSPM for AI, sensitivity labels that follow agent output, the unified audit log and eDiscovery for agent activity, insider risk policies for risky agents, then Defender for Cloud posture and AI bill of materials, Defender for Cloud Apps runtime protection for low-code agents, and the agent inventory and hunting table in Defender XDR for KQL investigation.

We finish with the parts most sessions leave out. Licensing explained SKU by SKU, including what the fleet math really means and where people get caught out. Power Platform environments as your actual security boundary. A maturity model so you can place yourself honestly.

1. Length. Built for 45 minutes plus 10 minutes of questions. Can run to 60 or 75 minutes with the Conditional Access and licensing sections expanded, or cut to 30 minutes for an executive audience.

2. Format. Slides plus live walkthroughs of the agent registry in the Microsoft 365 admin center, blueprint setup in Copilot Studio, and Defender XDR configuration. Recorded versions are ready if the venue network is unreliable.

3. Language. English or Norwegian. Full speaker notes exist in both.
Not a sales pitch. Technical content with sources listed. Coverage includes AWS Bedrock and Google Vertex AI, not only Microsoft platforms.

4. Kept current. Product status is checked before each delivery, and preview features are labelled as preview.