n8n Agents Integrate into Microsoft 365 Workflows
Microsoft has released Microsoft Agent 365 for general use. This lets n8n users create AI agents that appear within Microsoft 365 apps where work occurs. People can now mention these agents with an @ in Microsoft Teams, include them in Outlook emails, or tag them in Word documents to involve them in tasks.
Each agent gets its own Entra ID through Microsoft Agent 365. Employees grant it permissions to Microsoft 365 services, such as SharePoint and Teams channels, just like any coworker. Microsoft manages identity, access rules, and compliance via Purview and Defender. Agent 365 also covers agent lifecycle tasks, rules, policies, and analytics in the Microsoft 365 Admin Center. This setup provides control over agents using standard tools. In n8n, the canvas serves as the place to define the agent's functions: its system prompt, links to external tools, connecting logic, and specific actions. When a user messages the agent in Teams, n8n coordinates tasks across required systems and sends results back into the chat.
Benefits for Daily Work and Developers
Microsoft 365 hosts much of everyday work. Agent 365 enables n8n users to develop agents that join this work directly, not just run in the background. For developers familiar with Microsoft, n8n offers a visual builder plus more than a thousand native integrations to link agents to other parts of the technology stack.
Microsoft 365 is where so much of daily work happens. With Agent 365, n8n users can build agents that don't just automate in the background, they participate directly in that work. And for Microsoft developers, n8n gives them a visual builder and over a thousand native integrations to connect agents to the rest of their tech stack.
, Ben Kiziltug, Vice President, n8n
This feature extends a partnership revealed at Ignite in November 2025. Agent 365's general availability opens full features to any group with a Microsoft 365 tenant and n8n. Teams can find n8n in the Microsoft Marketplace for deployment in their Azure setup. This provides controlled access to Agent 365's MCP tools from the n8n canvas and lets agents appear as team members in Microsoft applications.
We're happy to welcome n8n to the Agent 365 ecosystem. With Agent 365, partners like n8n can bring agents directly into the flow of work across Microsoft 365. It gives developers a secure, governed way to build agents that show up where people already collaborate, communicate, and create.
, Srini Raghavan, Corporate Vice President, CoPilot directory & Agents Ecosystem at Microsoft Corp.
Practical Example: customer support automation
Imagine a customer support manager who begins each day by reviewing Zendesk for overnight issues, fetching account details from Salesforce, checking PagerDuty for ongoing infrastructure problems that impact customers, and then posting a summary in Teams while emailing the account team. An n8n agent powered by Agent 365 changes this. The manager mentions the agent in a Teams channel, and it takes over. The agent retrieves tickets, matches them with account information, scans for incidents across the three systems, posts a message in chat, and prepares an email with action items and assignments.
Connecting services happens easily on the n8n canvas by attaching them as tools to the Microsoft Agent 365 node. Zendesk links via a drag-and-drop node with credentials set once for reuse in workflows. Salesforce and PagerDuty connect similarly. The agent selects tools based on the chat context and its system prompt. Actions in Microsoft services, such as emailing or posting in Teams, route through Agent 365's MCP servers and activate via a setting in the node.
Stay ahead of the AI curve
The most important updates, news, and content — delivered weekly.
No spam. Unsubscribe anytime.
Advanced Capabilities with Workflows and Tools
Current n8n workflows and third-party MCP tools add more power. For instance, if the support manager has an n8n workflow that updates customer records by drawing from Salesforce, verifying contract status, and assessing account health, that workflow packages as a sub-workflow to serve as an agent tool. No need to recreate the logic. Just link it. If the team monitors with Datadog, its MCP server connects via the MCP Client node, allowing the agent real-time service insights during issue triage.
Visual Design, Coding Flexibility, and Governance
n8n supports visual design with code where required. Beyond built-in nodes, users add JavaScript or Python for custom data changes, business rules, or HTTP calls to internal services. Code fits where needed, visual nodes handle the rest, all in one workflow.
Governance operates on two levels. Agent 365 manages Microsoft-side elements: Entra ID, conditional access, data protection via Purview, threat detection with Defender, plus agent registry, analytics, and policies in the Microsoft 365 Admin Center. n8n governs workflows with role-based access control, credential handling for services, input validation, safety checks like PII detection, and error workflows. These layers combine to oversee agents from identity to execution. For data residency or compliance needs, self-host n8n on your infrastructure for control over data location and processing.
Teams gain visibility into agent operations. Each run logs details of outputs, behaviors, decisions, tools used, and data returned. The full sequence stays visible, testable, and adjustable.
Steps to Deploy Agents
Existing n8n workflows with Microsoft nodes continue to function. Agent 365 offers a fresh option for agents that appear in Microsoft apps and act like team members.
Setup starts with Microsoft tasks: register the app in Entra ID, create an agent blueprint using the Agent 365 CLI, and secure admin approval in the tenant. In n8n, add the Agent 365 Trigger node and attach tools. Native nodes, MCP services, and sub-workflows all serve as callable tools. After approval, the agent appears in Teams, Outlook, SharePoint, and Word for mentions and use.
The Microsoft Agent 365 Trigger node exists now in n8n.
Related on Neura Market