Agent 365 licensing. Decoded for enterprise buyers.

Agent 365 is Microsoft's framework for governing AI agents inside the Microsoft 365 tenant. It runs across Copilot agents, custom Copilot Studio agents, third party Agent Store agents, and platform agents from Microsoft and ISV partners.

The licensing model uses three SKUs. Per user assignment for human centric agents. Per agent metered for autonomous and asynchronous agents. An Agent 365 plan that runs the governance layer at the tenant level.

This guide covers the SKU mix, the message metering math, the governance scope, and the right size playbook for enterprise estates.

Read this alongside the Microsoft knowledge hub, the Microsoft services page, the Microsoft EA Renewal Playbook, and the Microsoft 365 License Optimizer.

The three SKUs in the Agent 365 ladder

Microsoft splits Agent 365 into three layers. Each layer covers a defined agent population. Each is priced differently.

SKU one. Per user assignment

• Covers. Agents that run in the context of a single user, like the Copilot chat experience or a personal productivity agent.
• Metric. Per user per month.
• Price ladder. Stacks with M365 Copilot per user pricing at signing.

SKU two. Per agent metered

• Covers. Autonomous agents, asynchronous agents, scheduled agents, multi user agents.
• Metric. Per Copilot Message unit consumed.
• Price ladder. Sold in packs at a defined per message price.

SKU three. Agent 365 plan

• Covers. The governance layer across all agents in the tenant.
• Metric. Tenant level. Some elements scale per managed agent count.
• Price ladder. Annual tenant fee plus per agent add on.

Message metering, decoded

Message metering is the new commercial axis. Every autonomous or asynchronous agent action consumes a defined number of messages from a tenant pool.

Action type	Message cost	Notes
Simple LLM query	1 message	Single round trip, single agent.
Multi step reasoning	3 to 5 messages	Each reasoning step adds.
Tool use	1 message per tool call	Additional, on top of reasoning.
Agent to agent handoff	2 messages per handoff	Counts at each agent involved.
Scheduled run	Variable	Sum of the above across the run.
Long context retrieval	2 messages plus retrieval surcharge	Large context windows cost more.

The governance scope

Agent 365 plan covers the governance layer across all agents in the tenant. The scope is broader than most buyers assume.

What the governance layer covers

• Agent identity. Each agent registered as an entity in the Entra directory.
• Audit logging. Every agent action logged in the unified audit log.
• Lifecycle management. Version control, approval workflows, retirement.
• Sensitivity labels. Agents inherit and enforce the tenant sensitivity label scheme.
• DLP boundaries. Agents enforce the tenant data loss prevention policies.
• Data loss controls. Cross tenant data flow controls applied to agent calls.

What it does not cover

• Agent build tooling. Copilot Studio licensing is separate.
• Third party agent fees. ISV partner agents carry their own commercial terms.
• Underlying LLM compute. Inference cost flows through Microsoft 365 Copilot Messages.

The right size playbook

Most enterprise estates over license the per user SKU and under size the message pool. Run the right size as a four phase exercise.

Phase one. Agent inventory

1. List every agent in the tenant: Copilot, Copilot Studio, Agent Store, ISV.
2. Classify each agent as user centric or autonomous.
3. Tag every agent with the business owner and the consumption profile.

Phase two. Consumption baseline

1. Pull thirty day message consumption from the admin center.
2. Project annual consumption based on the rollout plan.
3. Identify the top three agents by message cost.

Phase three. SKU mapping

1. Map user centric agents to per user SKUs.
2. Map autonomous agents to the metered SKU.
3. Size the tenant level Agent 365 plan against the agent count.

Phase four. Negotiation

1. Lock the per message rate at signing with a cap on annual uplift.
2. Negotiate a message pool true up cadence (annual, not quarterly).
3. Pull the Agent 365 plan inside the M365 EA line for the discount stack.

Per user versus per agent metered

Dimension	Per user	Per agent metered
Primary metric	Per user per month	Per Copilot Message
Best for	Human centric agent use	Autonomous and scheduled agents
Predictability	High	Variable, depends on consumption
Right size driver	Active user count	Message efficiency per agent
Renewal lever	Per user discount stack	Per message rate cap

Security and compliance considerations

• Identity boundary. Every agent runs as a managed identity with documented permissions.
• Sensitivity inheritance. Agents inherit the sensitivity labels of the data they touch.
• DLP enforcement. Agents enforce the tenant DLP policies at the boundary.
• Audit retention. Agent actions retained per the tenant audit retention policy.
• Cross tenant flow. Cross tenant agent calls require explicit allow listing.

Where Agent 365 sits inside the Microsoft EA

Agent 365 SKUs land inside the M365 line of the Enterprise Agreement, not as a standalone product. That matters for the discount stack.

• Discount stack. The M365 EA discount applies to per user Agent 365 SKUs.
• Message pool placement. The Copilot Message pool sits inside the M365 EA, not the Azure commit.
• True up cadence. Aligned to the M365 EA true up.
• Renewal alignment. Agent 365 renewal aligns to the M365 EA anniversary.

Common anti patterns to avoid

• Buy the user SKU for autonomous agents. Autonomous agents bill on messages, not per user.
• Under size the message pool. The default Microsoft sizing under counts message consumption.
• Skip the governance plan. Without the plan the audit log is partial.
• Separate procurement from M365 EA. Procure Agent 365 inside the EA for the discount stack.
• No message efficiency target. Set a per agent message efficiency target at deployment.

What to do next

1. Inventory every agent in the Microsoft 365 tenant.
2. Classify each agent as user centric or autonomous.
3. Pull thirty day Copilot Message consumption from the admin center.
4. Project annual consumption based on the rollout plan.
5. Map agents to the three SKU layers.
6. Run the Microsoft 365 License Optimizer.
7. Engage Redress before the next Microsoft EA renewal window.

Frequently asked questions

How Redress engages on Agent 365

Redress runs Agent 365 advisory inside the Vendor Shield subscription. Every engagement is led by a former Microsoft commercial lead on the buyer side. Read the Microsoft services page, the Microsoft knowledge hub, and the Microsoft EA Renewal Playbook.