Microsoft introduced:

• Microsoft 365 E7 — a new enterprise suite positioned above E5
• Agent 365 — a standalone licence for managing and governing AI agents

Alongside the product launch, Microsoft updated the wording of its multiplexing definition in the Product Terms.

The product launch is visible. The licensing detail requires a closer look.

Historically, multiplexing applied to scenarios where hardware or software acted as an intermediary to access Microsoft services.

In the May 2026 Product Terms, the wording now explicitly includes automation as a method of access.

What this means in practice

If an automated process interacts with a Microsoft service on behalf of a user or device, organisations should assess:

• who or what is being “served” by that automation
• whether the underlying users or devices are correctly licensed

This is particularly relevant for:

• AI agents
• RPA workflows
• attended and unattended bots
• integrations accessing Microsoft 365 services

The key point is not that every automation creates a licensing issue — but that automation-driven access now needs to be reviewed as part of standard SAM practice.

Microsoft 365 E7 is a new enterprise offering that builds on Microsoft 365 E5 and bundles additional capabilities, including:

• Microsoft 365 Copilot
• Agent 365
• Microsoft Entra Suite

At a list price of $99/user/month, E7 is positioned as a bundled option for organisations already investing in these components.

When it may be relevant

E7 may be worth evaluating if:

• you are already licensing or planning to license Copilot
• you expect broader AI adoption across teams
• you want consolidated governance across identity, security, and AI usage

For organisations earlier in their adoption journey, standalone licensing or partial rollout may still be more practical.

Agent 365 is Microsoft’s management and governance layer for AI agents.

It is designed to help organisations:

• discover which agents exist
• monitor their activity
• control access to data and systems
• govern both Microsoft-native and third-party agents

It is available as a standalone licence at $15/user/month, or included within E7.

The licence applies to individuals who manage agents or use them to perform work on their behalf.

AI adoption is moving faster than most SAM frameworks.

Many organisations already have:

• Copilot Studio workflows
• RPA automations
• integrations acting on behalf of users

The updated multiplexing wording means these scenarios should now be reviewed more explicitly from a licensing perspective.

At the same time, regulatory pressure is increasing. The EU AI Act begins applying key obligations from August 2026, including requirements around governance, transparency, and control for certain AI use cases.

Together, this creates a practical need to:

• understand where automation is used
• map it to users and data access
• ensure licensing and governance are aligned

1. Review automation and AI agent usage

Create a clear view of:

• which automations exist
• which systems they access
• which users or processes they support

This does not need to be perfect — but it needs to be visible.

2. Reassess your Microsoft licensing position

Focus on:

• indirect access scenarios
• shared or automated processes
• Copilot and AI-related usage patterns

The goal is to understand where current licensing assumptions may no longer fully reflect how systems are used.

3. Evaluate E7 based on actual usage

If you are considering E7:

• compare it against your current licensing mix
• validate how widely Copilot and agent-based workflows are used
• model different adoption scenarios

E7 creates value when the bundled components are actively used — not just available.

4. Treat AI agents as governed assets

From an ITAM/SAM perspective, AI agents are no longer just tooling — they are part of how work is executed.

That means:

• tracking them
• understanding their scope
• aligning them with licensing and governance processes

RixMind works with organisations to make their Microsoft licensing position clear and aligned with how systems are actually used.

This includes:

• mapping Microsoft entitlements against real usage
• identifying gaps related to automation and indirect access
• modelling E5 vs E7 scenarios based on your environment
• extending SAM practices to include AI-driven access

We do not resell licences. We help you understand what applies to your organisation — and where adjustments are needed.

Microsoft 365 E7 is the visible change.

The multiplexing update is the part that requires attention.

For organisations already using AI agents, bots, or automated workflows, this is a good moment to review how those scenarios interact with licensing — before it becomes a discussion driven by audit or compliance pressure.