Microsoft 365 E7 and Agent 365: AI Agent Governance Becomes a Licensing Line

Available since 1 May 2026, Microsoft 365 E7, which Microsoft presents as the "Frontier Suite", bundles Microsoft 365 E5, Microsoft Copilot, the full Microsoft Entra Suite and Agent 365 into a single SKU. It is a strict superset of E5: the licence adds capabilities and removes none. In practice, Copilot is no longer an add-on to buy separately, the Entra Suite is no longer limited to Entra ID P2, and an entirely new component appears, dedicated to agents.

This is the most structural piece, and the one that existed nowhere else. Agent 365 treats agents as manageable objects, in the same way as users or devices. It brings centralised visibility and governance over the organisation's agents, an agent identity with conditional access and identity protection, lifecycle management from provisioning through to expiry, governance rules that can be applied in bulk, agent security posture management, detection of suspicious activity with alerting and blocking, and unified observability logs for hunting a threat inside an agent.

The other half of the story is less visible but just as decisive. In E7, the guardrails you already know stop stopping at the agent boundary. DLP policies extend to agent interactions, sensitivity labels flow their context into AI agents, eDiscovery lets you discover and manage agent interaction data for a legal matter or an internal investigation, and auditing gains traceability over agent actions. On the identity side, the full Entra Suite adds Entra Internet Access, Entra Private Access, Entra ID Governance and access packages that apply to agents.

Before settling a licence, you need to answer a simple question, and most organisations we meet cannot yet: how many agents are running in your tenant, and which ones? A SharePoint agent created by a business team, a declarative agent built in Copilot Studio, a connector left active after a pilot are all objects reaching into company data. Until that list exists, no licence will fix the problem, because you cannot govern what you cannot see. This inventory is achievable with E5 tooling, and it is where to start.

Not necessarily, and product announcements say little about this. E7 sits well above E5, and its list price should be checked against your own CSP price list before any decision. More importantly, Agent 365 and the Entra Suite are also available as standalone add-ons: a company already on E5 that only wants to govern its agents can add the relevant component without moving its entire licence base. The calculation therefore compares three paths, E5 as it stands, E5 plus the add-ons that are genuinely useful, and E7, over the population of users actually concerned, which is almost never the full headcount.

This subject meets the EU AI Act. Transparency obligations have applied since August 2026, the team-awareness obligation since February 2025, and all of it presupposes knowing which AI uses exist in the company. Audit logs and an agent inventory are therefore not just operational tools: they are the evidence you will produce if a customer, an insurer or an authority asks how your agents access data. Documented governance costs far less than reconstructing it after the fact.