Microsoft Agent 365 Is Here: What Enterprise .NET Developers Actually Need to Know

Published: March 14, 2026

TL;DR

Microsoft announced general availability of Agent 365 and Microsoft 365 E7 on March 9, 2026, both landing May 1, 2026. For .NET and Azure developers, this isn’t just a licensing story — it’s a new identity, governance, and SDK surface for enterprise AI agents. Your agents are about to get their own Entra IDs, mailboxes, and audit trails. Time to plan accordingly.

The Big Picture: Agents Are Getting Employee Badges

Microsoft announced the general availability of Agent 365 and Microsoft 365 Enterprise 7, two products designed to bring security and governance to the rapidly growing population of AI agents operating inside the world’s largest organizations — both becoming available on May 1st, alongside Wave 3 of Microsoft 365 Copilot. In short: Microsoft wants your agents to behave like (accountable) employees, not like rogue scripts running in the dark. And honestly, given the state of most enterprise AI rollouts, that’s not the worst idea. According to Microsoft’s Cyber Pulse report, more than 80 percent of Fortune 500 companies are actively using AI agents built with low-code and no-code tools, and IDC projects 1.3 billion agents in circulation by 2028. That’s a lot of autonomous processes with no audit trail. Agent 365 is Microsoft’s answer to that problem.

What Is Agent 365, Exactly?

Agent 365, priced at $15 per user per month, serves as what Microsoft calls the “control plane for agents” — a centralized system for IT, security, and business teams to observe, govern, and secure AI agents across an enterprise. Microsoft 365 Enterprise 7, dubbed the “Frontier Worker Suite,” bundles Agent 365 with Microsoft 365 Copilot and the company’s most advanced security stack into a single $99-per-user-per-month license. At $99 per user, E7 costs less than purchasing the components individually — E5 currently runs $57 per month (rising to $60 in July), Copilot adds $30, and Agent 365 adds $15 — offering modest savings while pulling customers deeper into Microsoft’s ecosystem. Whether that’s a bargain or a bundle tax depends on your current licensing stack. Either way, it’s the pricing reality your finance team will be asking you about soon.

The Developer Story: Identity, Observability, MCP

This is where it gets genuinely interesting for engineers. Agent 365 isn’t just an admin console — it ships with an SDK and CLI that change how you register, deploy, and govern agents.

Agents Get Their Own Identity

Each agent gains its own unique, persistent enterprise identity, separate from human users or generic application registrations. This identity equips the agent with privileges, authentication, roles, and compliance capabilities similar to a human employee. Agentic users function as full members of your Microsoft 365 organization — they can be assigned licenses, have their own mailbox and OneDrive storage, and appear in the organizational chart and people cards. Yes, your agent will have a profile photo slot. We’re in the future now.

The Agent 365 SDK & CLI

The Agent 365 SDK is a software development kit that can be used to extend agents built using any agent SDK or platform, with enterprise‑grade identity, observability, notifications, security, and governed access to Microsoft 365 data. The Agent 365 CLI is the command-line backbone for Agent 365 throughout the agent development lifecycle — automating setup, identity, configuration, MCP integration, publishing, and Azure deployment for enterprise-ready agents. Here’s the typical workflow to bootstrap an agent using the CLI:

# Install the Agent 365 CLI (preview)
npm install -g @microsoft/agent365-cli

# Create a new agent blueprint
agent365 blueprint create --name "InvoiceAgent" --language dotnet

# Register agent identity in Entra
agent365 identity register --blueprint InvoiceAgent

# Deploy agent code to Azure
agent365 deploy --target azure-functions

# Publish to your M365 admin center
agent365 publish --catalog org

⚠️ Note: You currently need to be part of the Frontier preview program to get early access. Frontier connects you directly with Microsoft’s latest AI innovations, but previews are subject to the existing preview terms of your customer agreements.

Full Observability via OpenTelemetry

Agents gain full observability via Open Telemetry, enabling audited, traceable agent interactions, inference events, and tool usage. For .NET developers, this slots neatly into existing System.Diagnostics.ActivitySource patterns and your existing Azure Monitor / Application Insights setup. No new observability stack required — just wire up the Agent 365 SDK and your traces start flowing.

MCP Is the Integration Bus

Agents invoke governed Model Context Protocol (MCP) servers to access Microsoft 365 workloads — such as Mail, Calendar, SharePoint, and Teams — under admin control, and function within an IT‑approved blueprint system, ensuring each agent instance inherits compliance, governance, and security policies. Agent 365’s agentic tools expose consistent MCP interfaces and SDKs. Developers can use agentic tools for Outlook, Teams, and SharePoint — accelerating delivery while inheriting enterprise-grade security and compliance. If you’ve been following the MCP wave, this is its enterprise landing zone. The pattern: your .NET agent calls an MCP server → MCP server calls M365 APIs → all of it is admin-governed and Purview-audited.

Multi-SDK, Multi-Cloud (Seriously)

Agent 365 works with agents built on any agent SDK or platform, including low-code platforms like Copilot Studio and Azure AI Foundry, as well as pro-code options such as Microsoft Agent Framework, Microsoft Agents SDK, OpenAI Agents SDK, Claude Code SDK, and LangChain SDK. Agent 365 also works with agent code hosted on any endpoint — Azure, AWS, GCP, or any other cloud provider. That last sentence is worth re-reading. This is a governance layer, not a compute lock-in play. Your Fargate-hosted LangChain agent can still be enrolled. Microsoft is betting on being the control plane, not the only runtime.

What About Model Diversity?

Microsoft 365 Copilot is model diverse by design. Rather than betting on a single model, Microsoft built a system that makes every model useful at work, giving customers choice, performance, and flexibility in an open, heterogeneous environment. Claude is now available in mainline chat in Copilot via the Frontier program, alongside the latest generation of OpenAI models. From a developer perspective: your agents can now target Anthropic’s Claude or OpenAI models within the same governance envelope. This is meaningful if your organization has model-specific compliance requirements or cost-optimization strategies across workload types.

Practical Takeaways for .NET/Azure Engineers

| Area | What to Do Now | |—|—| | Identity | Plan for agents as first-class Entra principals. Update your IAM designs. | | Observability | Instrument your agents with OpenTelemetry today — it’s the native telemetry surface for Agent 365. | | MCP | Evaluate Azure Functions MCP (now GA) as your tool-hosting layer. It already integrates with Agent 365. | | SDK | Join the Frontier preview and start testing the Agent 365 CLI against a non-production tenant. | | Cost | Budget the $15/user/month for Agent 365 or factor into the E7 bundle conversation with your licensing team. | | Governance | Work with your security/compliance teams now — the tools to build agents are freely available and require no security expertise, but the tools to govern them require budget approval, implementation cycles, and organizational alignment across IT, security, and business teams. |

The Honest Caveat

Agent 365 and E7 reach general availability on May 1st, but several capabilities — including Defender and Purview risk signals and security posture management for Foundry and Copilot Studio agents — will remain in public preview at launch. Don’t plan a production rollout on day one for the security features specifically. Let the dust settle through Q2.