The use of Agents in Microsoft 365 is rapidly increasing. Agents create many opportunities and interesting business cases for organizations, but also raise practical questions about control, cost, and governance. Microsoft is here to help with the introduction of Agent 365
Agent 365
Agent 365 is positioned as the control plane for agents to observe, govern, and secure them.
In practice, that means organizations can use it to discover agents, manage access and lifecycle, and connect agent oversight to services like Microsoft Entra, Microsoft Purview, and Microsoft Defender. Sounds perfect, right?
As with most things in life, there is always more to the story. If you are evaluating Agent 365, you need to look beyond the license price to understand what you are actually getting, where extra costs may still arise, and what Microsoft does and does not solve for you today.
Agent 365 became generally available on the 1st of May 2026. This resulted in certain features being blocked. For example, on the Agent 365 overview page:
The all agents page:
Or the details of an agent: 
For your convenience, we have included an overview of all features (as of this writing) that now require an Agent 365 license. Note that this list is not exhaustive: additional capabilities across Microsoft Purview, Microsoft Entra, Microsoft Defender, and tools management for MCP servers are also part of the Agent 365 feature set.
|
Feature |
What it does |
|
Agents at risk / Risks |
Surfaces risk signals for every agent in the tenant, flagging agents that are behaving unexpectedly, accessing sensitive data, or violating policy. Without this, there is no way to identify which agents pose a threat before they cause damage. |
|
Agent run-time / Total sessions |
Shows how much each agent is actually being used - session counts, activity over time, and run-time data. Without this, you cannot tell whether agents are actively running, idle, or consuming credits with no business value. |
|
Agents with exceptions / Active users |
Highlights agents that have encountered errors, failed interactions, or configuration issues, and shows which users are actively interacting with them. Without this, operational problems go undetected until they escalate. |
|
Agent Map |
Visual map showing how agents connect to each other, what data sources they use, and how they perform over time. Think topology view for your agent ecosystem. |
|
Registry sync |
Connects agents built outside Microsoft 365 (third-party platforms, custom agents) into the central registry. Without this, only native M365 agents appear. |
|
Role-specific oversight |
Tailored dashboards for security leaders (risk view) and business leaders (ROI and business metrics). Without Agent 365 you only get the standard IT admin view. |
|
Lifecycle management automation |
Rules-based policies that automatically expire inactive agents, flag ownerless ones, or block risky agents. Without this, all lifecycle actions are manual. |
|
Integration management / least-privilege |
Controls exactly which users, data sources, MCP servers, and other agents each agent can access. Without this, there are no enforced guardrails on agent reach. |
|
Threat protection (Defender) |
Continuous monitoring for adversarial attacks, prompt injection, and malicious agent behavior via Microsoft Defender integration. |
|
Data security (Purview) |
Visibility into what sensitive data agents are accessing or creating, plus DLP enforcement and content safety controls for agent interactions. |
|
Audit and logging |
Full traceability of agent actions and interactions. Without Agent 365, logging is limited to what Purview and the standard audit log surface natively. |
|
Shadow agent discovery |
Detection of agents running locally on Windows devices via Intune that have not been formally registered - your unknown unknowns. |
Microsoft clearly scaled back the features available outside the Agent 365 license. Let’s move on and take a look at the pricing.
Pricing
Microsoft offers Agent 365 in two ways:
- Standalone: €12.86 ($15) per user per month
- Bundled in Microsoft 365 E7: €84.90 ($99) per user per month, alongside M365 E5 (€51.46 / $60), Microsoft 365 Copilot (€25.73 / $30), and Entra Suite (€10.29 / $12)
- Included and paid usage can exist at the same time: some employee-facing scenarios are included when the person using the agent has a Microsoft 365 Copilot license, but that does not mean all Copilot Studio usage is free across all scenarios, channels, or architectures
- Feature mix matters: Microsoft publishes different billing rates for classic answers, generative answers, agent actions, tenant graph grounding, AI tools, and voice, so the final cost depends on what the agent actually does
- Architecture matters: the same use case can become cheap or expensive depending on the channels, connectors, flows, retrieval choices, grounding, and actions behind it
- Budget predictability: A per-user license is easy to understand. Consumption-based billing is not. That means organizations often need additional reporting, internal guardrails, and ownership models before finance, IT, and the business are looking at the same reality.
- Visibility: Agent 365 provides centralized oversight and useful governance signals. That is a great first step. But many organizations will still want more detailed operational reporting, clearer cost attribution, and stronger lifecycle processes than the native experience delivers today.
- Agent sprawl: As more employees get access to agent-building tools, the number of agents can grow quickly. Without ownership standards, review processes, and cleanup routines, you end up with inactive, duplicate, or poorly governed agents that create noise, cost, and risk.
- Forecasting: Cost forecasting depends on interaction volume, orchestration design, connector usage, and channel choice. This is not easy for most organizations. You do not solve it with one nice dashboard. You solve it with a combination of governance, technical insight, and financial accountability.
- Manage and Secure AI Agents with Microsoft's Agent 365 and Purview
If you compare Microsoft’s published list prices, the E7 bundle saves about 15% compared to buying the listed products separately. That is a useful discount, especially for organizations that are already committed to the broader Microsoft stack.
This is where the pricing story gets more complicated. Microsoft presents Agent 365 as a per-user product, but the public guidance still leaves room for interpretation. Do you need it for every user in the tenant, every user who can create agents, or only the smaller group responsible for governance? That is not a small detail. It can completely change the cost model. So before you turn the list price into a business case, make sure you verify the licensing scope with Microsoft or your licensing partner.
The real billing picture: enter Copilot Studio
Agent 365 is a governance product. It helps you discover and manage agents, but it does not eliminate the need to consider how those agents are built, published, and billed. Once custom agent scenarios enter the picture, Copilot Studio usually becomes part of the conversation as well. One important nuance: employee-facing agents used by people with a Microsoft 365 Copilot license are included at no additional Copilot Studio credit cost, subject to fair usage limits. This covered usage applies when the agent operates using the licensed user’s identity. Beyond that threshold, or for external-facing scenarios, standard credit billing applies.
This is where the pricing story stops being a simple per-user discussion. Copilot Studio uses Copilot Credits as its billing unit, whether you buy prepaid capacity or use pay-as-you-go through Azure. In other words, the Agent 365 seat price may be visible, but it is not the full story once runtime usage scales.
Copilot Studio is not the only place where the cost story can become more complicated. Organizations that take a more Azure-first or code-first route can also end up in Azure AI Foundry (Foundry). And that brings a different kind of complexity. Instead of Copilot Credits, you are now dealing with Azure-style consumption across models, runtime, search, storage, tools, and other supporting services. Microsoft is quite open about that: Foundry does not even have one dedicated page in the Azure pricing calculator because it is made up of several optional Azure services. In other words, the pricing model changes, but the underlying challenge does not. The more flexible your agent architecture becomes, the harder it is to express the real cost in a single number.
Microsoft publicly lists Copilot Studio at €171.52 ($200) for 25,000 Copilot Credits, with a pay-as-you-go option through Azure at €0.0086 ($0.01) per credit. These numbers are clear. What matters more is that Microsoft also publishes feature-level billing rates and an agent usage estimator, which means the challenge is not a lack of guidance but that actual spend still depends heavily on design, usage volume, and the exact capabilities an agent invokes.
This is why cost estimates around custom agents should be handled with care. A simple internal FAQ agent is one thing. An agent with generative answers, actions, graph grounding, multiple connectors, or external-facing usage is something else entirely. The real challenge is not whether Copilot Studio can be affordable in specific situations. The real challenge is whether your organization can forecast, monitor, and explain the spend in a practical way.
Be aware: Microsoft distinguishes between creating and managing agents and simply using a published agent. To create and manage agents with Copilot Studio, organizations need both tenant capacity and user access for the people who build or administer them. But users of a published agent do not need a special Copilot Studio license just to interact with it.
The practical challenges for customers
This is where organizations start to feel the friction. Not because Microsoft published a new Agent 365 per-seat price, but because the price makes the story look a lot simpler than it really is. The following challenges apply:
- Budget predictability: A per-user license is easy to understand. Consumption-based billing is not. That means organizations often need additional reporting, internal guardrails, and ownership models before finance, IT, and the business are looking at the same reality.
- Visibility: Agent 365 provides centralized oversight and useful governance signals. That is a great first step. But many organizations will still want more detailed operational reporting, clearer cost attribution, and stronger lifecycle processes than the native experience delivers today.
- Agent sprawl: As more employees get access to agent-building tools, the number of agents can grow quickly. Without ownership standards, review processes, and cleanup routines, you end up with inactive, duplicate, or poorly governed agents that create noise, cost, and risk.
- Forecasting: Cost forecasting depends on interaction volume, orchestration design, connector usage, and channel choice. This is not easy for most organizations. You do not solve it with one nice dashboard. You solve it with a combination of governance, technical insight, and financial accountability.
Conclusion
Let’s be fair: Agent 365 adds real value. It gives organizations a stronger starting point for agent insights through a centralized overview, useful lifecycle controls, and tighter integration with Microsoft’s broader security and compliance services.
But this is only part of the story. The moment organizations start looking seriously at licensing scope, custom agents, Copilot Studio consumption, or more Azure-first routes like Azure AI Foundry, the conversation changes. What looks clear on paper quickly becomes more difficult in practice because the real question is no longer just what Agent 365 costs, but what it takes to govern agents properly as they scale.
That is where many organizations will still need more than the native baseline. They need clear ownership, lifecycle discipline, cost attribution, and compliance support that holds up under real operational pressure. So yes, Agent 365 matters. But the bigger story is not the list price. It is whether your governance model is ready for the way agents are actually being built, used, and billed.
Rencore's take
Rencore's AI and agent governance tool picks up where Agent 365 leaves off. While Agent 365 provides insights, Rencore Governance makes them actionable. Where Agent 365 shows you the status quo of agents in your tenant, Rencore Governance allows you to build and enforce policies, continuously monitor progress, and distribute governance tasks to both IT and end users.
This is what makes the difference in the fast-paced new reality of the AI-assisted modern workplace: responsible AI governance that scales because it is a true team effort.
Do you want to learn more about how Rencore Governance compares to Agent 365? Sign up for our upcoming webinar on July 24th, where our two experts, Matt Einig and Max Götz will, give you a clear picture of what Agent 365 can and cannot do. You'll walk away knowing what to prioritize, what risks to watch out for, and what smart organizations are already doing to stay ahead.
