Microsoft 365 E7 and Agent 365 – making sense of the new licensing

On March 9, Microsoft dropped the biggest licensing shakeup since E5 landed back in 2015. A brand-new tier – Microsoft 365 E7, marketed as “The Frontier Suite” – plus a standalone product called Agent 365 that introduces governance for AI agents. I spent the last two weeks unpacking this with customers, and the reactions range from “finally, a single SKU” to “wait, another price increase?”

Both are valid. Let me walk through what actually changed, what it costs, and what it means for the people who have to make licensing decisions – or build on top of this stack.

E7: The Frontier Suite at $99 per user per month

Microsoft 365 E7 bundles four things into one SKU:

• Microsoft 365 E5 – the full productivity, security, and compliance suite
• Microsoft 365 Copilot – the AI assistant across Word, Excel, PowerPoint, Outlook, Teams, and more
• Microsoft Entra Suite – Private Access (VPN replacement), Internet Access (secure web gateway), identity governance with lifecycle workflows, and verified ID
• Agent 365 – the new control plane for governing AI agents across the organization

General availability is May 1, 2026.

If you were to buy all of these separately, you would be looking at roughly $117 per user per month (E5 at $57, Copilot at $30, Agent 365 at $15, plus Entra Suite). The E7 bundle saves you about 15-17% compared to a la carte pricing.

That is a real discount, especially at scale. But it is also $99 per user per month. For a 5,000-seat enterprise, you are committing to nearly $6 million per year. This is a decision that needs to be modeled carefully.

Why a new tier now

Microsoft has not introduced a new enterprise tier in over a decade. E5 launched in 2015 (originally as Office 365 E5, later folded into Microsoft 365 E5). E1 and E3 have been around even longer. So why now?

Two reasons, both fairly obvious.

First, the AI products have multiplied. Copilot alone was already a $30 add-on. Agent 365 adds another $15. Entra Suite capabilities have been growing. Stacking add-ons on top of E5 was becoming messy and hard to sell. A single SKU simplifies procurement conversations enormously.

Second – and this is the one Microsoft will not say out loud – Copilot adoption has been sluggish. As of Q2 FY2026, there are roughly 15 million paid M365 Copilot seats. That sounds impressive until you realize there are over 450 million Microsoft 365 users. That is about 3.3%. Most enterprise deployments are still pilots or phased rollouts, not wall-to-wall. Bundling Copilot into a premium tier where it comes “for free” with the security and governance tools that CISOs actually want? That is a smart way to get Copilot into more hands without asking budget owners to justify $30/user/month purely on productivity gains they struggle to measure.

Agent 365: the control plane for AI agents

Agent 365 is the piece of this announcement that I think gets underappreciated. It is available standalone at $15 per user per month (GA May 1), or included in E7.

Here is the problem it solves. Organizations are building and deploying AI agents – in Copilot Studio, with the Agents SDK, through third-party tools. These agents access data, take actions, and operate with varying levels of autonomy. But until now, there has been no unified way to see what agents exist, what they can access, and whether they comply with organizational policies.

Agent 365 gives you a registry – basically a central inventory of every agent in the organization, internal or third party. On top of that, it extends Entra conditional access and identity policies to agents with their own Agent IDs and lifecycle management. You get dashboards and telemetry across the entire agent fleet, plus an interoperability layer so agents work the same way regardless of where they were built. The security side ties into Microsoft Defender for threat detection and Microsoft Purview for compliance auditing.

Think of it as Entra plus Defender plus Purview, but for non-human identities that happen to be AI agents. If your organization is serious about deploying agents at scale, you need something like this. The question is whether $15/user/month is the right price point, or whether this should have been folded into E5.

Copilot Cowork: the Anthropic connection

Bundled within the Copilot experience (and therefore part of E7) is Copilot Cowork – the headline feature from the same March 9 announcement. Cowork is Microsoft’s move from conversational AI assistance to agentic AI execution, and it is built in partnership with Anthropic using Claude.

What makes Cowork interesting: it can take a task, break it into steps, execute across multiple M365 apps, and run in the background for minutes or hours. You describe the outcome you want, and Cowork plans and executes – with checkpoints where you can review, adjust, or pause.

It runs in a sandboxed cloud environment within your M365 tenant, meaning enterprise data protection, identity, and compliance policies apply by default. Cowork is currently in Research Preview with limited customers and will be more broadly available through the Frontier program in late March 2026.

For developers, the multi-model angle matters. Copilot in E7 now supports both OpenAI models and Anthropic’s Claude. Microsoft is clearly hedging its model strategy – and giving itself the ability to route tasks to whichever model performs best for a given scenario. If you are building agents or extensions that work with Copilot, expect the underlying model to become an implementation detail rather than a fixed constant.

The EU elephant in the room

There is a problem here that I have not seen enough people talk about. Anthropic’s Claude models are not covered by Microsoft’s EU Data Boundary. All Claude processing currently happens in the US – Anthropic has no EU data zones yet. That means your M365 data leaves the European boundary when Copilot routes a task to Claude.

For organizations operating under GDPR or with strict data residency requirements, this is a real blocker. Microsoft has added Anthropic as a subprocessor under their DPA, but that does not change the physical location of the processing. Some EU tenants have Anthropic models turned on by default since January 2026, which caught more than a few compliance teams off guard.

Microsoft clearly wants to move fast here – and I get it, the competitive pressure from Google and others is real. But as Europeans, we are stuck waiting for Anthropic to stand up EU-based infrastructure before any of this is actually compliant for many organizations. No timeline has been announced for that. If you are advising EU customers on E7, this needs to be part of the conversation right now, not after the contracts are signed.

What happens to E3 and E5 customers

Here is the part that affects everyone, not just E7 buyers. Effective July 1, 2026, list prices go up:

Microsoft is justifying the increases by adding Intune capabilities to both tiers. E3 gets Intune Remote Help, Advanced Analytics, and Plan 2. E5 additionally gets Intune Endpoint Privilege Management, Enterprise Application Management, Cloud PKI, and – notably – Security Copilot.

That last one is interesting. Security Copilot coming to all E5 customers (not just those who pay for the add-on) softens the blow of the $3 increase considerably. If you were already evaluating Security Copilot, the E5 price increase is essentially giving it to you for a fraction of what the standalone would cost.

But let us be honest: a $3/user/month increase across tens of thousands of seats adds up fast. For a 10,000-seat E5 customer, that is $360,000 per year in new spend. Budget conversations are happening right now.

The developer perspective

If you are a developer working in the M365 ecosystem, here is what E7 concretely unlocks.

Agent 365 means there will be Graph APIs and management surfaces for agent registration, identity, and lifecycle. If you are building agents, you will need to integrate with this. If you are building governance tooling, this is a new surface area to work with.

With Copilot now running both OpenAI and Claude models, your extensibility points may need to account for different model behaviors. Declarative agents and plugins should be model-agnostic in theory, but testing against multiple models becomes more important in practice.

As Cowork matures, there will be ways to build solutions that work alongside agentic execution – providing data, handling approvals, or extending what Cowork can do through custom actions. I am keeping an eye on this one.

And if you are building custom agents with the M365 Agents SDK, Entra Agent IDs and the associated access control model will become the standard pattern for agent authentication and authorization. Get familiar with it now.

The direction is pretty obvious: Microsoft wants governed, identity-aware agent infrastructure everywhere. If you already work in the M365 dev space, this is where the customer conversations are heading.

Licensing guidance: when E7 makes sense

Not every organization needs E7. Here is how I have been thinking about it in customer conversations.

E7 makes the most sense if you are already on E5 and paying for Copilot. If you also want Entra Suite capabilities and you are planning to deploy agents at scale, the bundle math works out. Simplifying procurement down to one SKU is a real selling point too – compliance teams love fewer line items.

If you only need Copilot for a subset of users, E5 plus add-ons is probably smarter. E7 is all-or-nothing per licensed user. Same goes if you are not ready for Agent 365 yet or your Entra needs are already covered by what ships in E5 (Entra ID Plan 2). Some customers just want to phase the AI investment instead of going all in.

E3 is still the right call for organizations where AI is not a near-term priority, where security is handled by third-party tools, or where the budget simply does not stretch.

One thing to watch: Microsoft has a history of making the premium tier incrementally more attractive over time by adding features exclusively there. E5 went through this cycle. E7 will almost certainly follow the same playbook. Features that are “E7 only” today will multiply, creating pressure to upgrade.

What comes next

The E7 announcement tells you where Microsoft thinks this is all going. Copilots everywhere, agents everywhere, and a governance layer bolted onto identity and security. That is the bet.

Whether customers actually follow at $99/user/month – I honestly do not know. But the licensing structure is in place, and the July 1 price increases are coming regardless. If you are advising customers on licensing strategy, now is the time to model the options before the new prices land.

Read more

• Microsoft Blog: Introducing Microsoft 365 E7 – The Frontier Suite – the official March 9 announcement with E7 pricing and bundle details
• Microsoft Blog: Introducing Copilot Cowork – deep dive on the Anthropic Claude-powered agentic execution feature
• Microsoft: Agent 365 overview – product page for the agent governance control plane
• Microsoft Blog: Microsoft 365 E3/E5 pricing update (December 2025) – the announcement of July 1 price increases and new Intune capabilities
• Windows Central: Microsoft 365 Copilot adoption lags behind expectations – the source for the 3.3% adoption stat (15M paid seats vs. 450M+ commercial users)
• Microsoft Learn: Anthropic as a subprocessor for Microsoft Online Services – official documentation on Anthropic’s role and EU Data Boundary exclusion
• Copilot at Work: What is preventing EU organizations from enabling Copilot Cowork? – detailed analysis of the EU data residency and GDPR challenges
• UC Today: Microsoft 365 Copilot to Enable Anthropic Models by Default – what compliance leads need to know about the January 2026 default-on change