n8n agents can now join Microsoft 365 workflows

n8n users can now deploy AI agents that appear inside Microsoft 365 apps as if they were part of the team, thanks to Microsoft Agent 365’s general availability. The companies said the integration lets users @mention agents in Microsoft Teams, add them to Outlook emails, and tag them in Word so the agents can take part in everyday work instead of running only in the background.

Microsoft Agent 365 gives each agent its own Entra ID, which means the agent can be granted access to Microsoft 365 services such as SharePoint and Teams channels the same way an employee would be. Microsoft said it handles identity, access policies, compliance through Purview, and threat protection through Defender. It also provides agent lifecycle management, rules, policies, and analytics in the Microsoft 365 Admin Center.

n8n provides the workflow layer. On the n8n canvas, developers define what the agent does: its system prompt, the tools it can use, and the logic connecting those tools. When someone messages the agent in Teams, n8n runs the workflow across the required systems and returns the result back into the conversation.

The setup is aimed at teams that already work inside Microsoft 365. Ben Kiziltug, vice president at n8n, said Microsoft 365 is where much of daily work happens, and that Agent 365 lets n8n users build agents that participate directly in that work. He said n8n’s visual builder and more than 1,000 native integrations help connect those agents to the rest of a company’s stack.

The announcement builds on a collaboration first disclosed at Ignite in November 2025. n8n said that with Agent 365 now generally available, the full set of capabilities is available to any organization with a Microsoft 365 tenant and n8n. The company is also available in the Microsoft Marketplace for teams that want to deploy within their Azure environment.

A support example shows how the integration is intended to work. A support lead who normally checks Zendesk, Salesforce, and PagerDuty in the morning could instead @mention an n8n-powered Agent 365 agent in Teams. The agent would gather ticket details, account context, and incident status across those systems, then post a summary in chat and draft a follow-up email with next steps and owner assignments.

n8n said its drag-and-drop nodes make those services easy to attach as tools. Zendesk, Salesforce, and PagerDuty can each be connected once with their own credentials and reused across workflows. Microsoft services such as Teams and Outlook are exposed through Agent 365’s MCP servers, with support enabled through a toggle in the Microsoft Agent 365 node configuration.

Existing workflows can also be reused. n8n said a workflow that enriches a customer record, checks contract status, and scores account health can be packaged as a sub-workflow and connected as a tool, rather than rebuilt inside the agent. Third-party MCP tools can be connected too; the company cited Datadog as an example for observability data during customer issue triage.

The company also said users can mix visual nodes with code where needed. n8n supports JavaScript and Python inside workflows, along with HTTP request nodes for internal services.

Governance is split between Microsoft and n8n. Microsoft handles Entra ID, conditional access, Purview, Defender, agent registry, analytics, and policies at the platform level. n8n handles workflow-level controls, including role-based access control, credential management, guardrails such as input validation and PII detection, and error-handling workflows.

n8n said its self-hosting option can help teams with data residency or compliance requirements, since the platform can run on a company’s own infrastructure. The company also said each execution leaves a detailed record showing the agent’s output, every decision it made, each tool it called, and the data returned from those tools.

To get started, organizations need to set up the Microsoft side first by registering the app in Entra ID, creating an agent blueprint through the Agent 365 CLI, and getting admin approval inside the tenant. On the n8n side, users add the Agent 365 Trigger node and connect the tools they want the agent to use. Once approved, the agent appears in Teams, Outlook, SharePoint, and Word, ready to be @mentioned by the team.