For years the separation was clean. Power Automate was the automation inside Microsoft 365: native, governed, no-code, woven into the tenant as if it had always been there. n8n was the automation from outside: powerful, flexible, with hundreds of connectors, but separate, living on the other side of the window while M365 happened inside.
In May 2026, n8n came through the front door. And it brought an Entra identity.
What always kept the two worlds apart
Power Automate has one advantage no external competitor can replicate from scratch: it is already there. You open the portal, use your work account, and flows see SharePoint, Teams, and Outlook because they all live in the same tenant. No app registrations in Entra, no OAuth2 credential management, no webhook configuration. Microsoft handled all of that.
In exchange, you accept the constraints. Conditional logic has limits. Complex loops get awkward. Flows with multiple AI branches require workarounds or Premium licenses. And every execution counts, and every premium connector costs.
n8n always offered the opposite: full control over logic, JavaScript when a node falls short, self-hosting with no per-execution billing, and connectivity to anything with an API, from HubSpot to Jira to Notion to Stripe. The catch was that "anything" did not include Microsoft 365 natively. Connecting to SharePoint meant registering an app in Entra, configuring OAuth2 by hand, and hoping the token did not expire at the wrong moment.
That changed.
The nodes nobody expected to see
n8n now has native nodes for Microsoft Outlook, Teams, OneDrive, and Excel, all through Microsoft Graph. Authentication works with delegated OAuth2 (the signed-in user) or with Service Principal, the mode for unattended flows with no user present, what Microsoft calls app-only.
The Microsoft Excel node actually shipped in two separate versions: one for workbooks stored in OneDrive and another specifically for workbooks in SharePoint document libraries, including files behind a Teams site. They are technically distinct because they use different Graph endpoints, and n8n recognized that difference.
For teams that always used n8n for external automation and Power Automate for everything inside M365, the border started to blur. A single n8n workflow can now receive a lead from HubSpot, create an opportunity in Salesforce, send a message in Teams, and open a folder in SharePoint, without switching tools.
The day n8n got a badge in Entra
What changed in May 2026 goes beyond integration nodes.
On May 1, 2026, Microsoft launched Microsoft Agent 365 in general availability, a platform for registering and governing AI agents inside a tenant. Four days later, n8n shipped the Microsoft Agent 365 Trigger, a cluster node that lets an n8n workflow serve as the backend for an agent with its own identity inside M365.
The detail that changes everything: the agent gets its own Entra ID identity, not a delegated copy of whoever mentioned it. When the tenant admin approves the agent, it appears in the company directory alongside human staff. It can be @mentioned in Teams (channels and direct messages), receive emails directly in Outlook, and be mentioned in SharePoint pages and comments.
Before May 2026, doing this required a manually registered webhook, token validation in a Code node, and hand-built message schema parsing, roughly two hours of fragile setup. The new trigger node handles all of that natively, and setup time drops to around twenty minutes.
The n8n workflow connected to the trigger can use any subnode: a language model, persistent memory (including Postgres), tools like HubSpot, Jira, Slack, GitHub, Salesforce. The agent that shows up in Teams can, behind the scenes, query a CRM, open a ticket, write to an external database, and reply to the employee, all under an identity the tenant admin governs, revokes, and audits like any other Entra application.
What this agent can do that Copilot Studio makes harder
Copilot Studio is Microsoft's answer for building agents in M365 without code. It is integrated, governed, and natively connected to Microsoft Graph and tenant policies. For organizations that need something a business analyst can maintain, it is the right choice.
n8n with the Agent 365 Trigger serves a different audience: complex branching logic, integrations with systems Copilot Studio does not cover natively (or covers via paid connectors), JavaScript when the standard node falls short, and full visibility into every step of the flow.
Copilot Studio delivers governance and speed. n8n delivers control and integration without boundaries.
They are not substitutes. They are for different profiles within the same organization.
Two lanes, one choice that is no longer obvious
| Criterion | Power Automate | n8n + Agent 365 |
|---|---|---|
| Initial setup | None (already in the tenant) | Entra app registration + Agent 365 CLI |
| Who builds it | Business analyst | Developer or technical admin |
| Complex logic | Limited, gets awkward | JavaScript, loops, conditions without limit |
| Cost per execution | Yes (freemium limits, Premium per connector) | No (self-hosted) or per cloud plan |
| External connectors | Hundreds, but many Premium | 400+, all included in the plan |
| Identity in the tenant | Native, flow runs as the signed-in user | Entra Service Principal or Agent 365 identity |
| Governance | Full (tenant policies, DLP, audit logs) | Partial (Entra governs the agent; n8n needs additional config) |
| AI and agents | Copilot Studio (separate product) | Native in the workflow, with any model |
| Self-hosting | No | Yes |
Power Automate is still the right answer for automations that business analysts need to build and maintain, that live entirely within the Microsoft ecosystem, and where tenant governance is non-negotiable from day one.
n8n with M365 nodes and the Agent 365 Trigger is the answer for technical teams that need complex logic, integrations with systems outside M365, control over execution costs, or agents that require memory and reasoning that Copilot Studio does not yet cover well.
The point
The Power Automate versus n8n comparison was always about ecosystem versus control. Teams that stayed inside M365 used one. Teams that needed to connect to the outside world used the other.
In May 2026, n8n got an Entra identity. The workflow that used to live outside the tenant can now appear in company Teams, reply to emails from the corporate Outlook, and be governed like any other registered application in the directory.
The border did not disappear. But it became a lot more permeable than it used to be.
If you want to stay ahead of what changes in the Microsoft 365 ecosystem, the Macareno newsletter covers exactly this kind of shift every week.
Sources
- Your First Teams-Native n8n Agent on Microsoft Agent 365 — Automation Labs / Medium
- Build Enterprise AI Agents with n8n + Microsoft Agent 365 — Noqta
- How to Deploy an n8n Agent Inside Microsoft 365 — Pondero
- Microsoft 365 in n8n: Outlook, Teams, SharePoint — Nordflux
- Microsoft Agent 365 Trigger — n8n Docs