Microsoft Agent 365 Goes GA May 1: Day-One Review
Microsoft Agent 365 Goes GA May 1: Day-One Review
Microsoft Agent 365 hit general availability on May 1, 2026 at $15 per user per month. It’s the productized result of two years of Microsoft’s “AI for work” strategy — and the first real attempt at a unified enterprise control plane for agentic AI. Here’s what actually shipped, what didn’t, and how it stacks up against Salesforce Agentforce 360 and the rest of the agent landscape on day one.
Last verified: May 2, 2026
What launched yesterday
Microsoft’s official Agent 365 GA blog confirmed three things shipped at GA:
- Agent 365 control plane — agent identity, lifecycle, and assignment management.
- Entra integration — agents get Entra IDs, conditional access, and identity governance.
- Initial prebuilt agents — Sales Agent, Finance Agent, Service Agent, plus Copilot Cowork as the user-facing surface.
Microsoft also confirmed three things are still preview, not GA:
- Context mapping through Defender — public preview in June 2026.
- Policy-based agent controls in Intune — public preview in June 2026.
- Runtime blocking and alerts — public preview in June 2026.
That gap between “Agent 365 is GA” and “Agent 365’s security controls are GA” matters. It means day-one deployments are operating with identity governance but not full runtime policy enforcement until June.
Pricing recap
| Path | Cost | What you get |
|---|---|---|
| Agent 365 standalone | $15/user/mo | Control plane + Copilot Cowork + prebuilt agents |
| Microsoft 365 E7 | $99/user/mo | E5 + Copilot + Agent 365 + Entra Suite + advanced governance |
| Microsoft 365 E5 + Copilot + Agent 365 add-ons | ~$102+/user/mo | Same components, separately licensed |
E7 is roughly cost-neutral vs assembling the components separately, with the added benefit of single-SKU procurement. Microsoft’s pitch is that E7 is the cheaper path for any enterprise that wanted E5-level security plus agents anyway. If you only want agents, the $15 standalone is the play.
What’s actually new vs March announcement
Microsoft announced Agent 365 on March 9, 2026 at the Microsoft 365 Conference. The GA release on May 1 added:
- Multi-model orchestration shipped. Copilot Wave 3 confirmed Claude (Anthropic) and next-gen OpenAI models route alongside Microsoft’s own models depending on task type.
- Excel Python integration paired with cross-workbook analysis. Excel agents can now reason across multiple workbooks in one task.
- Copilot Cowork. The collaborative surface where humans and agents work side-by-side inside Word, Excel, Outlook, and Teams went GA.
- Agent identity in Entra. Agents get conditional access, identity governance, and audit logs the same way users do.
What’s missing at GA but expected through 2026:
- Runtime policy enforcement (June 2026 preview).
- Third-party agent marketplace (timeline not committed).
- Agent-to-agent protocols beyond Microsoft’s stack (limited at GA).
How it compares on day one
| Capability | Agent 365 | Salesforce Agentforce 360 | ServiceNow AI Agents |
|---|---|---|---|
| Identity for agents | Entra (mature) | Salesforce IDM | ServiceNow IAM |
| Surface | Word, Excel, Outlook, Teams | CRM, Service Cloud | ITSM, HRSD, CSM |
| Pricing model | Per-user $15/mo | Usage-capped, settable | Per-conversation / per-action |
| Multi-model | Yes (Claude + OpenAI + MS) | Atlas + customer models | Now LLM + bring-your-own |
| Best for | M365 shops, knowledge work | CRM/sales/service workflows | IT, HR, customer service flows |
| Day-one maturity | High (M365 ecosystem) | High (CRM ecosystem) | High (ITSM ecosystem) |
The honest read: each platform wins in its native ecosystem. Agent 365 dominates anywhere knowledge work happens in Microsoft 365. Agentforce dominates anywhere a CRM is the system of record. ServiceNow AI Agents dominate ITSM and adjacent enterprise workflows.
Day-one strengths
Identity governance is the standout. Giving agents Entra IDs with conditional access policies is more mature than what most agent platforms ship. It’s the answer to the “who’s accountable when an agent does something it shouldn’t” question, and Microsoft has the most mature identity stack to lean on.
Excel + Python + agents is genuinely new. The combination of Excel Python execution, cross-workbook analysis, and agent reasoning is something no other platform offers natively for the spreadsheet-as-system-of-record use case (which is most of finance and analytics work in mid-market and enterprise).
Multi-model routing reduces vendor lock-in. Copilot Wave 3’s confirmation that Claude and OpenAI models route alongside Microsoft’s own is a meaningful concession. It signals Microsoft is no longer trying to win on “best Microsoft model” but on “best orchestration of multiple models.”
Day-one weaknesses
Runtime policy enforcement is in preview, not GA. This is the single biggest gap. Identity governance handles “who is the agent.” Runtime enforcement handles “what is the agent allowed to do at this moment.” That second piece is in Defender/Intune public preview through June 2026, which means many enterprise deployments will wait to scale up until those land.
Prebuilt agent library is small at GA. Sales Agent, Finance Agent, Service Agent, plus Copilot Cowork. That’s a starting set, not a marketplace. Compared to Agentforce 360’s deeper agent library or ServiceNow’s broader workflow library, Agent 365’s prebuilt agents are limited at launch.
Pricing surprises at scale. $15/user/mo is fine for hundreds of seats. At thousands of seats, the difference between standalone and E7 pricing — and the unbundled add-ons (Excel Python compute, Defender for Agents, etc.) — can compound. Several analyst firms flagged this through April; expect organizations to hit pricing math earlier than they expect.
Who should adopt at GA vs wait
Adopt at GA:
- Microsoft 365 E5 customers wanting agent capabilities now.
- Organizations with mature Entra deployments that want agent identity governance.
- Finance and analytics teams that benefit from Excel Python + cross-workbook analysis.
- Sales orgs looking for an alternative to Agentforce that lives in their existing M365 tooling.
Wait until June 2026 preview / late 2026 GA:
- Security-sensitive deployments needing runtime policy enforcement at scale.
- Highly regulated industries (financial services, healthcare) waiting for Defender/Intune preview features to mature.
- Organizations wanting a richer prebuilt agent library before committing.
Bottom line
Microsoft Agent 365’s GA on May 1, 2026 is real and meaningful, but the security control plane is preview-only until June. The identity governance story, multi-model orchestration, and Excel + Python + agent combo are genuinely differentiated. The runtime enforcement gap and small prebuilt agent library are the day-one weaknesses. Most M365 shops should start a pilot now and plan to scale once the June 2026 preview features land. Salesforce-first or ServiceNow-first organizations should test Agent 365 in adjacent knowledge-work scenarios but keep their CRM and ITSM agent investments where they are.
Built with 🤖 by AI, for AI.