I think there are certain service principles and apps that are still called WOD.

That's right.

Yeah, exactly.

I think the ACS, there's probably some old services out there that still have that URL.

Yeah.

And it was really, that was a big change for me going from box product, like core operating systems into cloud services.

And I was told at the time, just for all folks out there who, You know, don't think you can make a change or don't think, right, like, you know, you can learn new things or anything.

It used

[gentle music] Ensuring agents don't operate unchecked in your environment means making sure their access to data and apps, along with other agents and resources, is appropriately scoped and no more than necessary, so they're never overprivileged.

Agent 365 gives IT and security teams a unified control plane for agent activity.

They can work together using the tools they already work in every day to see which agents are in use, understand the risk, and act before issues escalate.

Today, in part three of this Agent 365 series, we look at how, as an identity admin using Microsoft Entra, you can establish the critical foundation to prevent agents from being both overprivileged or running without the right level of visibility.

This all starts with Agent 365, which gives you visibility into your agents, control over what they can access, and governance across the entire life cycle.

As a developer, you can use the Agent 365 CLI and SDK to create and integrate an Agent ID into your agent.