After this year's Ignite there's no doubt left: Copilot and agents now sit at the center of Microsoft's plans. In the tenants I work in, I see it all the time. There are Copilot add-ins, autonomous agents built in Copilot Studio and homegrown plugins, and many of them run with hardly any central oversight. The Ignite 2025 Copilot announcements, above all Microsoft Agent 365 as a control plane for agents, suggest that this kind of agent sprawl won't last much longer. Still, it's worth sorting out what is real, what is preview and what matters for day-to-day admin work right now.

Microsoft Agent 365 acts as the control plane for every agent

Microsoft presented Agent 365 as the single registry and governance hub for AI agents of every kind, from Copilot extensions and Copilot Studio agents to Azure-based bots and third-party integrations. The idea is that every agent is registered, visualized, tracked and managed in one place. The part I find most interesting is Microsoft Entra Agent ID, a durable identity for each agent that is managed and governed as strictly as human or workload identities. In most organizations I support, agent identity has so far been a messy patchwork of service principals and app registrations, often with far too many permissions and no one clearly accountable.

Practical tip: Start an inventory now. Find out which agents and plugins run in your tenant, who owns them and which permissions they actually need. That work pays off once central agent governance arrives.

Agent ID and the registry are more than technical features. They come down to ownership, responsibility and compliance. If you want to see what will soon be expected, the official Microsoft Learn documentation on Entra Agent ID is already a good read. As of today (November 2025) the feature is still in preview, but the direction is obvious.

Ignite 2025 announced more for Copilot than tenants get today

Ignite always mixes production features with a lot of future vision, and this year was no different. Microsoft Agent 365 has been announced, and the registry portal is in closed preview. According to the roadmap, agents from Copilot Studio, Azure AI Foundry and third parties will be registered and managed there, with visualizations and centralized access management through Entra Agent ID. For now, hands-on agent management mostly covers agents built in Copilot Studio and published inside a tenant, and even there you can see the focus moving toward ownership and security. I covered that side in more detail in my security review of Copilot Studio agents.

The integration with Microsoft Defender XDR (agent posture and threat detection), Purview (audit and data governance) and the existing app governance tooling is still being worked out. The Ignite recap image for Microsoft Agent 365 shows the architecture, but a lot of it hasn't shipped yet. Watch the roadmap closely, and don't count on GA features appearing overnight.

Admins should start on agent governance now

You need agent governance today, no matter how fast Microsoft Agent 365 reaches GA. If you use Copilot, Copilot Studio agents, Azure AI Foundry or any custom or third-party agents, this is my short list of things to do:

  • Build and maintain a proper agent inventory (who runs what, where and for what purpose)
  • Clarify ownership and technical responsibility
  • Make agent identities visible (service principal, Entra Agent ID; see Managing Copilot agents in the admin center)
  • Review data access and permissions against least privilege
  • Write down the open licensing and cost questions

In larger tenants I recommend tracking agents in a Purview register, or at the very least in a SharePoint list. The biggest risk I see is agents with overly broad access to SharePoint or Exchange. Map your data access carefully, and go through your Purview and Copilot extensibility governance again with agents specifically in mind.

A diagram shows how registry, identity and governance fit together

Session after session at Ignite came back to the same point: registry, agent identity and security have to be connected. This flowchart sums up the architecture:

flowchart TD
  agent["Agent"] --> registry["Agent 365 Registry"]
  registry --> entraid["Entra Agent ID"]
  agent --> defender["Defender XDR"]
  agent --> purview["Purview"]
  entraid --> access["Access Control"]
  agent --> owner["Owner"]

Figure: How agent registration, identity, access and security connect.

The diagram makes one thing plain. If you don't know which agents you have, which identities they use and how they reach your data, you can't automate or govern any of it. Adjust your processes now, and you'll be ready for the registry model when it lands.

The Ignite hype still points to concrete next steps

Not everything Microsoft showed for Copilot at Ignite 2025 will be in your tenant tomorrow. The direction, though, is set. Agents are moving out of shadow IT and becoming governed entities in their own right, with proper identities, permissions and audit trails. If you build your agent inventory, settle ownership and get control of agent identity and data access, whether in Copilot, Copilot Studio or third-party tools, you'll be well prepared for Agent 365 and whatever follows it. The hype is only part of the picture. As agents become a core part of the Microsoft ecosystem, the organizations that get ownership, identity and access hygiene right will come out ahead. I'll keep following how the previews develop and when agent governance is truly ready for the enterprise.