Licensing is easy to treat as a purchasing detail, but with Microsoft Agent 365 it is also an architecture decision. The edition you choose decides whether you get a useful registry with basic controls or a fuller control plane with policy templates, observability, tenant-wide tool restrictions, and programming access. If you understand that line before rollout, you can plan governance, security, and budget with fewer surprises.

Start with the simple facts

Microsoft Agent 365 became generally available for commercial customers on May 1, 2026. General availability means the service is released for production use by eligible customers, not merely preview or test use.

Agent 365 is licensed per user. In practical terms, you buy licenses for people, not for each individual agent. The planning question is therefore not “How many agents might we create?” but “Whose work will these agents support, and which users need the governed experience?”

Microsoft sells Agent 365 in two ways. It can be bought as a standalone add-on to an eligible Microsoft 365 subscription, or it can be included as part of Microsoft 365 E7, also referred to as Microsoft Enterprise 7. At least one user in the tenant, meaning the organization’s dedicated cloud service instance, must hold a qualifying Agent 365 license before the service can be used.

📌
The unit is the user. Agent 365 licensing is counted by people, so plan around the users whose work agents support rather than the number of agents in the registry.

Why the edition matters

Some products use licensing mostly to count seats. Agent 365 does more than that: the license tier changes the capabilities available to administrators and security teams.

The basic Microsoft 365 experience gives you meaningful visibility and control. You can see agents in the Agent Registry and perform core governance actions. That is enough to reduce unmanaged agent sprawl, identify owners, and stop agents that should not run.

The higher tier, delivered through Microsoft 365 E7 or Agent 365, adds the deeper controls that make the service feel like a security control plane. This is where policy templates, observability, tenant-wide tool governance, Microsoft Graph application programming interface access, and Microsoft Entra access packages appear.

The base experience gives visibility and core governance; the premium tier adds the deeper controls of a security control plane. Base vs Premium Tier Base Premium Registry visibility Core governance Stop unmanaged sprawl Policy templates Observability Tenant-wide tool control
The base experience gives visibility and core governance; the premium tier adds the deeper controls of a security control plane.

Prerequisites are about the security foundation

Agent 365 does not operate in isolation. It builds on Microsoft identity, security, compliance, and device-management services, including Microsoft Entra, Microsoft Purview, Microsoft Defender, and Microsoft Intune.

Microsoft 365 E5 is the recommended prerequisite. The reason is straightforward: E5 already includes advanced security, compliance, and identity capabilities that Agent 365 can extend to agents. If E5 is already deployed, adopting Agent 365 is closer to an incremental governance step. If the organization is on a lower Microsoft 365 edition, the missing E5-class foundation may become part of the rollout plan.

The second prerequisite is activation through licensing. Before Agent 365 can be used in a tenant, at least one user must have a qualifying Agent 365 license.

  • Recommended base: Microsoft 365 E5.
  • Required to start: at least one qualifying Agent 365 license in the tenant.
  • Best fit: organizations that already rely on Microsoft Entra, Purview, Defender, and Intune for enterprise governance.
Agent 365 builds on E5-class identity, security, and compliance services, activated by at least one qualifying license. The Security Foundation Microsoft 365 E5recommended base Security servicesEntra, Purview, Defender, Intune Agent 365 licenseactivates the service
Agent 365 builds on E5-class identity, security, and compliance services, activated by at least one qualifying license.

What ordinary Microsoft 365 plans include

The base capabilities are not cosmetic. They give administrators an inventory of agents in the Agent Registry and the basic actions needed to govern their lifecycle.

Those actions include publishing, deploying, blocking, deleting, approving, assigning agents to users or groups, reassigning ownership, and pinning agents. These are the controls that let an organization move from “we think people are using agents” to “we can see them, assign responsibility, and take action.”

Base plans also include automation of lifecycle actions through conditions-based rules. They also allow synchronization of agent metadata from external platforms into the registry, so the control plane is not limited only to agents created inside Microsoft tools.

✅
The base tier is useful. Even without premium features, the registry and lifecycle controls can reduce agent sprawl and clarify ownership.
Base plans move an organization from guessing about agents to seeing them, assigning responsibility, and taking action. Base Governance Actions Publish & deploymake agents available Block & deletestop risky agents Assign ownersaccountability Sync metadataexternal platforms
Base plans move an organization from guessing about agents to seeing them, assigning responsibility, and taking action.

What requires Microsoft 365 E7 or Agent 365

The premium capabilities are the ones most closely associated with operating agents as a governed enterprise estate. They do not merely show that agents exist; they help administrators define how agents behave, what they can reach, and how their activity is monitored.

Policy templates let teams apply customized controls to agents. Observability and monitoring provide visualization and telemetry for agent activity. Tenant-wide tool control lets administrators decide which tools and connectors agents may use, including Microsoft Model Context Protocol servers. Model Context Protocol, often shortened to MCP, is a way for agents to connect to tools and data sources through governed servers.

The premium tier also includes Microsoft Graph application programming interface, or API, access to the registry, metadata, and governance actions. That matters for teams that want to integrate Agent 365 into their own portals, workflows, reporting systems, or security automation. Microsoft Entra access packages are also premium; they help define the scope of an agent’s permissions.

  • Policy templates for customized agent controls.
  • Observability and monitoring of agent activity through visualization and telemetry.
  • Tenant-wide control over which tools and connectors agents may use.
  • Microsoft Graph API access to registry data, metadata, and governance actions.
  • Microsoft Entra access packages to define an agent’s permission scope.
⚠️
Do not assume monitoring is included. The richer observability, policy, tool-control, and API features require Microsoft 365 E7 or Agent 365.

The decision leaders and practitioners actually face

The practical choice is not simply “Do we buy Agent 365?” It is “How much control do we need, and where must that control operate?” A team that only needs to discover agents, clean up ownership, and block obvious risks may get significant value from the broadly available base capabilities.

A security or platform team with a larger mandate will usually need the premium tier. If the goal is to monitor agent behavior, enforce reusable policies, restrict tools across the tenant, or automate governance through the Microsoft Graph API, the base tier will not be enough.

This is also a coverage decision. Because licensing is per user, leaders should map licenses to the people whose business processes agents support. Practitioners should map the required capabilities to operating requirements: inventory, lifecycle governance, monitoring, policy enforcement, tool restriction, and automation.

If the goal is to monitor behavior, enforce policy, or restrict tools tenant-wide, the base tier is not enough. Which Tier Do You Need? Need monitoringor policy? Premium tierE7 or Agent 365 Base capabilitiesbroadly available Yes No
If the goal is to monitor behavior, enforce policy, or restrict tools tenant-wide, the base tier is not enough.

Plan with today’s facts, but verify before purchase

Licensing pages, plan names, prices, and bundle contents can change. The durable pattern to remember is the split between broadly available inventory and basic governance on one side, and premium monitoring, policy, tool control, API access, and permission scoping on the other.

At launch, Microsoft also made a set of pre-integrated partner agents deployable from the Microsoft 365 admin center, giving organizations a way to begin governing real third-party agents immediately. That does not remove the need to confirm licensing; it makes early clarity more important.

Before committing budget, confirm the current plan comparison details in Microsoft’s official documentation. Then match the edition to the operating model you intend to run, not to a vague expectation that all governance features will be available everywhere.

📌
Capabilities first. Treat the price sheet as the last check, not the design tool; first decide which governance capabilities the organization truly needs.

Key takeaways

  • Agent 365 became generally available for commercial customers on May 1, 2026.
  • It is licensed per user and sold either as a standalone add-on or as part of Microsoft 365 E7.
  • Microsoft 365 E5 is the recommended prerequisite, and at least one qualifying license is needed in the tenant before use.
  • Ordinary Microsoft 365 plans include the Agent Registry, basic lifecycle actions, conditions-based automation, and external metadata synchronization.
  • Microsoft 365 E7 or Agent 365 is required for policy templates, observability, tenant-wide tool control, Microsoft Graph API access, and Microsoft Entra access packages.
  • The right licensing choice depends on whether the organization needs basic visibility or a monitored, policy-driven agent control plane.

Glossary

Agent 365
Microsoft’s service for registering, governing, monitoring, and controlling agents across an organization.
Per-user license
A licensing model in which the service is bought for people rather than for each individual agent.
Tenant
An organization’s dedicated instance of a cloud service, with its own users, policies, data, and administrative settings.
Microsoft 365 E5
An enterprise Microsoft 365 edition that includes advanced identity, security, compliance, and management capabilities and is the recommended base for Agent 365.
Microsoft 365 E7
An enterprise Microsoft 365 edition that includes Agent 365 and unlocks its premium governance capabilities.
Agent Registry
The inventory in Agent 365 where agents and their metadata are listed so administrators can see and manage them.
Microsoft Graph application programming interface
A Microsoft programming interface that lets software read Microsoft 365 data and perform supported actions, including premium Agent 365 registry and governance operations.
Model Context Protocol server
A governed server that exposes tools or data sources for agents to call through the Model Context Protocol.
Microsoft Entra access package
A defined bundle of access used in Microsoft Entra to scope what a user, workload, or agent is allowed to reach.