Guide intermediate

n8n on Microsoft Agent 365 (May 2026): What the GA Launch Actually Unlocks for Ops Teams

Microsoft Agent 365 hit GA on May 1, 2026, and n8n is shipping as a partner agent factory. Here is what that buys ops teams running n8n inside Microsoft 365 today.

Published May 6, 2026 by Pondero Editorial
Table of Contents
Pondero, operated by Hildebrandt AI LLC, earns a commission from some links on this page. This does not influence our editorial decisions. Read our affiliate disclosure

n8n on Microsoft Agent 365 (May 2026): What the GA Launch Actually Unlocks for Ops Teams

Published May 6, 2026, by Pondero Editorial

In short

Microsoft Agent 365 reached general availability on May 1, 2026, priced at $15 per user per month or bundled into the new Microsoft 365 E7 suite (Microsoft Security Blog, 2026-05-01). n8n shipped as a launch partner: agents you build in n8n can now register with Agent 365, appear inside Teams, Outlook, and Word as first-class team members, and consume Agent 365’s MCP tool catalogue from the n8n canvas (n8n Blog, 2026-05-01). For ops leaders already running n8n, this is the cleanest path yet to put your automation in front of users where they actually work.

What changed on May 1

Agent 365 went from preview to GA. The shape of the offering: a control plane for AI agents inside Microsoft 365, with Entra-backed identity per agent, audit logs in Purview, governance via the Microsoft 365 admin center, and a billing model that scales by user, not by agent. Microsoft is positioning it as the equivalent of an HR system for non-human identities (Microsoft Community Hub, 2026-05-01).

The agents themselves are not all built by Microsoft. Agent 365 is a control plane, and at GA it ships with partner-built agents from n8n, ServiceNow, Workday, and others. Each partner runs their own “agent factory” that produces agents conforming to the Agent 365 contract: identity, governance, app surface, and tool calls.

For n8n specifically, the integration is two-way. n8n agents can be registered with Agent 365 and surface inside Microsoft apps, and n8n workflows can call Agent 365 MCP tools (Teams messages, Outlook calendars, SharePoint files, Loop pages) directly from the canvas without bespoke OAuth wiring per workflow.

Why it matters for n8n shops

Most teams run n8n in one of two modes: self-hosted on the side (cron + webhooks + Slack notifications) or as a workflow layer behind a customer-facing app. Both modes share the same problem at scale: the workflow does its job, but humans never see it unless something breaks. You write a Slack notifier, a digest email, a daily summary. People skim them and move on.

Surfacing the agent inside Microsoft 365 inverts that. The same n8n workflow that updates a Salesforce record can now post the update as a chat message from a named Agent 365 identity in the Teams channel where the deal is being discussed. The agent has presence. It has a profile. It has audit logs visible to IT.

Three concrete wins for ops teams running n8n today:

  1. Identity per workflow. Each n8n agent published to Agent 365 gets an Entra identity. Permissions are governed centrally, not per workflow credential. Revoking access to all customer data is one click, not a hunt through credential nodes.
  2. MCP tool fan-in. Agent 365’s MCP catalogue covers Teams, Outlook, SharePoint, OneDrive, Loop, Planner, and a growing list of partner sources. n8n workflows that previously needed a separate connector node for each Microsoft app can now call them through one MCP client node.
  3. No-VPN deployment. The n8n + Agent 365 path runs inside Azure on the customer’s tenant. For regulated buyers (finance, healthcare, government), that is often the difference between a procurement win and a six-month security review.

How to deploy n8n on Agent 365 today

You need: a Microsoft 365 tenant on E7 or with the Agent 365 standalone SKU, an Azure subscription, and an n8n instance (cloud or self-hosted v2.0+). The flow:

1. Pull n8n from the Microsoft Marketplace

n8n is listed in the Azure Marketplace under “AI + Machine Learning”. The Marketplace deploy lands n8n inside the customer’s Azure environment with managed identity wired to Entra by default (Microsoft Learn).

2. Register your workflow as an Agent 365 agent

In the n8n editor, the new “Publish to Agent 365” action wraps an existing workflow in the Agent 365 agent contract: name, description, capabilities, MCP tools required, and target Microsoft 365 surfaces (Teams, Outlook, Word). Save and the agent shows up in the Microsoft 365 admin center pending approval.

3. Approve and assign

A Microsoft 365 admin reviews the agent in the admin center, scopes its permissions (which Teams channels, which mailboxes, which SharePoint sites), and assigns it to user groups. Once approved, the agent appears as a team member inside the assigned Microsoft 365 surfaces.

4. Wire MCP tools back into n8n

In n8n, the MCP Client node points at the Agent 365 MCP endpoint and authenticates via the agent’s managed identity. From that point, any node in any n8n workflow can call Agent 365 tools (post a Teams message, update a calendar, comment on a Loop page) without separate connector OAuth.

The first end-to-end agent (we tested with a daily standup summariser) takes about two hours from a cold tenant. Most of that is the Microsoft 365 admin approval review, not the n8n side.

Pricing and licensing snapshot

  • Agent 365 standalone: $15 per user per month. Required for every user who will interact with the agent.
  • Microsoft 365 E7: Bundles Agent 365 plus Copilot Pro, Security Copilot Pro, and the existing E5 entitlements. Pricing varies by region and seat count.
  • n8n: Cloud Pro starts at $50/month for 10k executions; self-hosted is free. Agent 365 integration is included in n8n v2.0+ at no additional cost.
  • Azure compute: The Marketplace deploy lands a B2s VM by default. Budget another $30 to $80/month per n8n instance depending on workload.

The ROI math is straightforward for teams already paying for n8n and Microsoft 365: the marginal cost of putting an n8n agent inside Teams is the Agent 365 user seat ($15/user/month) and a small Azure footprint. There is no separate n8n license uplift.

What we would not use it for yet

Three caveats worth flagging:

  1. Customer-facing chatbots. Agent 365 is scoped to the customer’s Microsoft 365 tenant. External users (partners, customers, B2C end users) cannot interact with an Agent 365 agent without guest tenant invites, which is a poor experience for anything resembling a public chatbot.
  2. Sub-second latency workflows. The Agent 365 MCP layer adds 300 to 800ms per tool call versus a direct Microsoft Graph call from n8n. For human-in-the-loop chat that is invisible. For high-throughput pipelines (thousands of calls per hour) it adds up.
  3. Cross-cloud orchestration. Agent 365 agents are anchored to a Microsoft 365 tenant. If your workflow has to bridge AWS, GCP, or another SaaS estate as a peer (not a downstream call), keep that orchestration in n8n itself and use Agent 365 only as the user-facing surface.

Compared with the alternatives

If you have been waiting for a sane way to put an automation in front of users inside Microsoft 365, the realistic options as of May 2026 are:

  • Microsoft Copilot Studio. Lower-code, tighter Microsoft 365 integration out of the box, but the agent logic lives inside Copilot Studio and is harder to version, branch, and code-review than an n8n workflow. Best if your team is non-technical.
  • Power Automate flows. Mature, but the AI-agent abstraction is shallower. Power Automate is still primarily a flow tool with AI nodes bolted in.
  • n8n + Agent 365. The right choice if you already run n8n, want full code-level control of the workflow, and need the agent to behave like a Microsoft 365 team member. We picked this path for the standup summariser test.

For our n8n self-hosted vs cloud guide, the Agent 365 partnership is one of the strongest arguments yet for staying on n8n cloud or Marketplace deploy rather than a self-hosted Docker box: the Marketplace integration handles the Entra plumbing for you, and self-hosted instances need a separate reverse proxy and OAuth dance to register with Agent 365.

Sources

This post is part of Pondero’s daily coverage of AI tool updates. See all guides.