1. What Agent 365 Actually Is
Microsoft is positioning Agent 365 as a framework for building, managing, and licensing autonomous AI agents that can operate across Microsoft 365 applications, SharePoint, Copilot Studio, and third-party systems. These agents are not Copilot for M365 (which requires a human user licence). These are autonomous, non-human identities that act on behalf of your organisation.
An agent might be a bot that processes expense reports, generates compliance reports, monitors security logs, or orchestrates multi-step workflows. Each agent requires its own Entra ID identity and, by extension, its own licence.
2. Agent 365 Is Not Included in M365 E3 or E5
This is Microsoft's intentional new revenue lever. Your existing M365 subscriptions cover human users with Copilot access. Agents are separate. You cannot repurpose an E3 or E5 licence for an autonomous agent. You must purchase an A365 SKU for each agent.
The licensing model is deliberately different from traditional Microsoft licensing, where SKU bundles cover multiple features. For agents, each autonomous identity = one licence requirement.
3. The A365 Licence SKU
Microsoft has announced an A365 licence tier, but as of March 2026, general availability pricing is not public. The A365 is positioned as a per-agent subscription, with expected pricing in the range of $10 to $50 per agent per month (industry estimates pending public pricing announcement). This is subject to change and will likely be set during EA negotiations.
In your next EA negotiation, A365 pricing will be a key battleground. You should demand:
- Commitment pricing (lower than list price for high-volume agent deployments)
- Clarity on what "per agent" means (does one agent = one identity in Entra ID?)
- Cost controls: are agents metered by API calls, or is it a fixed per-identity cost?
- Flexibility: can you grow or shrink agent counts without penalty?
4. Agentic Users in Entra ID
Every agent must have an Entra ID identity. This is not a feature licence; it is a standalone user object that counts separately from your human user count. You will see new user types in Entra ID management:
- Human users: Traditional M365 licences (E3, E5, etc.)
- Agentic users: Autonomous identities licensed under A365
- Guest identities: Existing external user model
For audit and compliance, this separation is critical. You must be able to report on human vs. agentic user counts separately. Failure to do so creates audit exposure.
5. Consumption-Based Billing and Cost Exposure
The second revenue lever is consumption. In addition to the per-agent A365 licence, Microsoft is embedding consumption-based billing through Copilot Credits and API usage charges. An agent that frequently invokes Copilot features or calls expensive APIs (Power Platform, Cognitive Services) can rack up significant overage charges.
Key risks:
- Unbounded cost: A single agent deploying at scale with high API call volume can exceed your annual budget in a month.
- Lack of visibility: Many organisations will not have cost monitoring in place for agentic activity, creating budget surprises.
- Consumption-based pricing: Unlike fixed user licence costs, consumption costs escalate with demand. More agents = more calls = exponential cost growth.
When negotiating Agent 365 in your next EA, demand a consumption cap and a monthly cost alert framework.
6. Five Essential EA Renewal Provisions
Before July 2026 (when many EA renewals occur), you should demand that your renewal agreement includes these five provisions:
- Agent 365 pricing lock-in: Negotiate a per-agent unit price (either per identity or per month) that is fixed for the three-year term. Do not accept open-ended consumption pricing.
- Consumption ceiling: Cap total agent consumption costs at a defined monthly or annual maximum. Overages are not permitted without prior written approval.
- Agentic user count flexibility: You must be able to add or remove agents without penalty. Do not accept minimum agent commitments.
- Reporting and metering transparency: Demand that Microsoft provides real-time visibility into: (a) number of agentic identities provisioned, (b) API call volume, (c) consumption costs accrued, and (d) monthly cost projections. Without this, you cannot govern spending.
- Future-proofing clause: Explicitly negotiate that future agent-based services (agents for Copilot Studio, agents for Power Platform, agents for Dynamics) are covered under the same pricing and governance terms.
Agent 365 licensing will reshape Microsoft EA negotiations in 2026.
Microsoft Licensing Strategy & Agent 365 Updates
Get monthly guidance on Agent 365 licensing, Microsoft EA negotiation tactics, and how to manage consumption-based costs—delivered to your inbox.
Frequently Asked Questions
No. M365 E5 covers Copilot access for human users. Agent 365 is a separate licence tier for autonomous agents. You must purchase A365 licences separately for each agent identity.
If you are building autonomous workflows in Copilot Studio, Power Automate, or other Microsoft platforms that require an Entra ID identity independent of human users, you need A365. If you are using Copilot as a productivity assistant for human employees only, you do not need A365.
General availability pricing has not been publicly announced as of March 2026. Industry estimates suggest $10 to $50 per agent per month, but this is subject to change. In your EA negotiation, demand a commitment price that is significantly below list price.
Copilot Studio is the authoring platform. Agents built in Copilot Studio require A365 licences when deployed. The licensing is separate from the platform.
This is unclear and must be negotiated. Some consumption (basic API calls) may be included in the A365 licence fee. Consumption above a certain threshold will likely be billed separately. Demand clarity during EA negotiation.
Start now: (1) Identify your current and planned agent workloads. (2) Estimate agent counts for the next three years. (3) Understand the consumption patterns of your agents. (4) Engage an independent adviser to negotiate Agent 365 provisions into your EA. (5) Demand fixed unit pricing and consumption caps, not open-ended consumption billing.
Unlikely. Most EAs signed before 2026 do not contain Agent 365 provisions. You will need to wait for your renewal or amend the agreement with Microsoft (which is difficult without renewal leverage). Start planning now for your next EA negotiation.
Need help preparing for Agent 365 in your EA renewal?