Key insight

Agent 365 became generally available for commercial customers on May 1, 2026, licensed per user, sold either standalone or included with Microsoft 365 E7, and it works best with Microsoft 365 E5 in place. Crucially, capabilities are tiered: every Microsoft 365 plan gets the agent inventory and basic governance, but the deeper powers — observability, policy templates, tenant-wide tool control, and the Graph API — require E7 or Agent 365.

It is tempting to skip licensing as procurement’s problem. Resist that here, because with Agent 365 the license tier is the feature set: the difference between “we can list our agents” and “we can watch, police, and lock down every tool call” is a licensing line. Knowing the tiers up front stops the common disappointment of expecting a capability that turns out to sit one edition higher.

1 · Why licensing is worth understanding first

Most products put nearly all their features in the box and let licensing decide only how many people can use them. Agent 365 is different: it deliberately gates which capabilities you get by tier. The base inventory-and-governance is broad and available widely, but the capabilities that turn Agent 365 into a genuine security control plane — deep observability, custom policy, tenant-wide tool control — are reserved for the higher editions. So a plan built on the wrong assumption (“we’ll just turn on monitoring”) can stall. Understanding the map now avoids that.

2 · How Agent 365 is sold: standalone, E7, and per-user

Three facts define how you acquire it:

Standalone

A subscription you add on top of an eligible Microsoft 365 subscription, for organisations not on the all-in-one edition.

add-on

Included with E7

Microsoft 365 E7, one of the enterprise editions, includes Agent 365 — no separate purchase.

bundled

Per user

Licensed for people, not for agents directly. You license the users whose work the agents support.

per-user

And the timing: Agent 365 reached general availability (GA — full production release for all eligible customers) for the Commercial segment on May 1, 2026. At launch, a set of pre-integrated partner agents can be deployed directly from the Microsoft 365 admin center, so an organisation can start governing real third-party agents from day one.

3 · Prerequisites: E5, and at least one qualifying license

Agent 365 does not stand entirely alone; it leans on a security foundation of Entra, Purview, Defender, and Intune. Two prerequisites matter:

The practical reading: if an organisation is already on E5, adopting Agent 365 is an incremental step; if it is on a lower edition, expect the E5-class security foundation to be part of the conversation.

4 · What every plan gets versus what needs E7 or Agent 365

This is the heart of the article. Microsoft’s published feature-availability table draws a clear line. Read it as two tiers: a base that comes with ordinary Microsoft 365 plans, and a premium set that requires Microsoft E7 or Agent 365.

CapabilityMicrosoft 365 plansMicrosoft E7 / Agent 365
Inventory of agents in the Agent RegistryYesYes
Basic governance actions (publish, deploy, block, delete, approve; assign to users/groups; reassign owner; pin)YesYes
Automate lifecycle actions with conditions-based rulesYesYes
Synchronise agents & metadata from external platforms into the registryYesYes
Policy templates for customised controlsNoYes
Observability & monitoring of agent activity (Visualization & telemetry)NoYes
Control which tools (incl. Microsoft MCP servers) agents may access tenant-wideNoYes
Graph API access to the registry, metadata, and governance actionsNoYes
Access packages in Microsoft Entra to define an agent’s permission scopeNoYes

The pattern is consistent: seeing and basically governing agents is broadly available; the deep observability, fine-grained policy, and tool control that make Agent 365 a true control plane require the top tiers. If your goal is inventory and cleanup of sprawl, the base tier already helps enormously. If your goal is a policed, monitored agent estate, budget for E7 or Agent 365.

5 · Planning who to license

Because Agent 365 is per user, a natural planning question is “who exactly needs a license?” The general principle is to license the people whose work the agents support — the users on whose behalf agents act — and to confirm the E5-class security foundation is present. Microsoft’s FastTrack program offers remote guidance for adopting Agent 365’s premium capabilities, which is a useful signal that rollout is expected to be a planned exercise, not a single switch. Rollout planning is a deeper subject on its own; here the takeaway is only that tier and coverage should be matched to the depth of governance you actually intend to operate.

Prices and packaging change — capabilities are the point

Exact plan names, prices, and inclusions evolve. The durable lesson from this article is the shape: a broadly available base of inventory and basic governance, with observability, policy, and tool control gated to the higher tiers. Always confirm the current specifics against Microsoft Learn and the plan comparison documents before committing a budget.

6 · Glossary — every short-form term, spelled out

License (per user)
A right to use a service, here counted per person rather than per agent; you license the users the agents support.
Standalone subscription
Agent 365 bought as an add-on on top of an eligible Microsoft 365 subscription.
Microsoft 365 E5
An enterprise Microsoft 365 edition carrying advanced Entra, Purview, and Defender capabilities; the recommended prerequisite for Agent 365.
Microsoft 365 E7 / Microsoft Enterprise 7
The enterprise edition that includes Agent 365 and unlocks its premium capabilities.
General availability (GA)
The point at which a product is fully released for production use by all eligible customers; Agent 365 reached this for Commercial on May 1, 2026.
Feature availability
Which capabilities are included at each licensing tier; for Agent 365 this varies significantly by tier.
Policy template
A reusable set of customised controls applied to agents; a premium (E7 / Agent 365) capability.
Observability
The ability to monitor agent activity through visualization and telemetry; a premium capability.
MCP server (Model Context Protocol server)
A governed source of tools and data an agent can call; premium tiers let admins control which ones agents may use tenant-wide.
Graph API
A programming interface for reaching Microsoft 365 data and actions in code; premium tiers expose the agent registry through it.
Access package (Entra)
A defined bundle of permissions in Microsoft Entra used to scope what an agent may reach; a premium capability.
FastTrack
Microsoft’s program offering remote deployment guidance, including for Agent 365 premium capabilities.
Tenant
An organisation’s own dedicated instance of a cloud service; Agent 365 activates once at least one user in it holds a qualifying license.
Key takeaways

Agent 365 became generally available for commercial customers on May 1, 2026, licensed per user.
It is sold standalone as an add-on, and included with Microsoft 365 E7.
It works best with Microsoft 365 E5 in place, and at least one user must hold a qualifying license to activate it.
Every Microsoft 365 plan gets the base: the agent inventory, basic governance actions, conditions-based automation, and external-platform sync.
Policy templates, observability, tenant-wide tool control, Graph API access, and Entra access packages require Microsoft E7 or Agent 365.
License the people the agents support, confirm the E5-class foundation, and match the tier to the depth of governance you actually intend to run.

References

  1. Microsoft 365 service descriptions, Microsoft Agent 365 — Feature availability — the per-tier capability table. learn.microsoft.com
  2. Microsoft Learn, Overview of Microsoft Agent 365 — general availability, per-user licensing, and the E5 prerequisite. learn.microsoft.com
  3. Microsoft Learn, FastTrack for Microsoft Agent 365 — adoption guidance for premium capabilities. learn.microsoft.com