Microsoft Agent 365 Supports n8n Agents in Microsoft 365 With Governance
Microsoft Agent 365 lists n8n as a partner for third-party agents, bringing n8n-built agents into Microsoft 365 with identity, governance and observability controls.
Microsoft Agent 365 supports third-party agents built with n8n, creating a route for n8n automations to operate inside Microsoft 365 applications with their own Entra ID. The integration matters because it connects an automation platform to the identity, governance and observability layer Microsoft is building around workplace agents. For teams already using Microsoft 365, it offers a more structured path to bringing task-oriented agents into familiar tools such as Teams, Word and Outlook.
Microsoft lists n8n among the supported partners on its official Agent 365 third-party agents documentation. The documentation describes connecting an n8n environment to Agent 365 through the Microsoft 365 admin center. This is a confirmed ecosystem integration, not simply a conference concept.
The development was discussed in the context of In The Loop, n8n's Berlin event scheduled for October 13 and 14, 2026. The event context is useful, but the more significant news is the product connection itself: n8n can serve as the runtime for agents that are surfaced and managed through Microsoft Agent 365.
How the Agent 365 and n8n integration works
The two platforms have distinct roles. n8n is the environment where teams build and run workflow-based agents, while Microsoft Agent 365 provides the Microsoft 365-facing identity and management layer for supported partner agents. Rather than treating an agent as an isolated automation, this model associates it with an identity and places it within the tools where employees already work.
| Area | n8n's role | Microsoft Agent 365's role |
|---|---|---|
| Agent operation | Builds and runs agents | Supports third-party n8n agents in its ecosystem |
| Identity | Agents can be provisioned for the integration | Agents run with their own Entra ID |
| Microsoft 365 presence | Provides the agent runtime | Enables use in apps including Teams, Word and Outlook |
| Management | Connects an n8n environment | Provides governance and observability tooling |
This separation is important in practice. Workflow teams can use n8n to design the operational logic, while Microsoft 365 administrators have a documented route to connect that environment and manage the resulting agents through Agent 365. The integration therefore addresses more than where an agent runs. It also addresses how the agent is identified and observed once it is introduced into a company's Microsoft environment.
Identity, permissions and reusable automation patterns
The core operational issue for agentic automation is not only whether a workflow can complete a task. It is whether the agent has an appropriate identity and is used within a repeatable setup. Agent 365's support for n8n agents with their own Entra ID is the relevant confirmed capability here.
For businesses, that can make a difference when moving from a one-off workflow to agents that employees encounter in everyday applications. A repeatable integration pattern can reduce the need to treat each new automation as a separate, disconnected deployment. It does not remove the need to decide what an agent should do, what access it requires or how people should use it. Instead, it provides a supported framework for connecting those agents to Microsoft 365.
The immediate use cases will depend on the workflows a team builds in n8n. The verified material does not promise specific prebuilt business processes or outcomes. What it does establish is the ability to deploy n8n agents inside Microsoft applications including Teams, Outlook, Word and SharePoint, with Agent 365 governance and observability as part of the model.
Rollout status, licensing and what remains open
The integration has developed over several published updates. n8n announced its Microsoft Agent 365 integration in a November 2025 blog post, and a May 2026 n8n update described the continuing work to deploy n8n agents inside Microsoft applications. Microsoft documentation now identifies n8n as an Agent 365 ecosystem partner and explains the connection process from the Microsoft 365 admin center.
There are still important limits to keep in view:
- Agent 365 credentials are in preview through the Frontier program, according to n8n documentation.
- n8n documentation points to an MCP-driven agent runtime as part of the current product direction.
- The supplied sources do not provide public pricing details for Agent 365 credentials, n8n provisioning or the integration.
- The available material confirms governance and observability support, but it does not specify every control, permission configuration or rollout condition.
That means decision-makers should treat the integration as an active platform capability with preview elements, rather than assume a fully specified pricing and deployment model. Before planning a production use case, teams should confirm licensing, preview eligibility and the precise access requirements for their intended workflows.
For companies using Microsoft 365, the practical opportunity is to place n8n-built agents closer to the work where requests, documents and communications already happen. The practical constraint is equally clear: successful adoption depends on designing a useful workflow and connecting it with appropriate identity and access choices, not merely switching on an agent.
Running agents across Microsoft 365 can reduce manual handoffs, but reliable value comes from workflows that map to real operational work. Scalevise's n8n setup service helps businesses design, connect and productionize n8n automations around the systems their teams already use. That can turn an experimental agent into a maintained workflow with clear triggers, integrations and error handling. Discuss an n8n implementation with Scalevise.
Frequently Asked Questions
What is the Microsoft Agent 365 and n8n integration?
Microsoft Agent 365 supports n8n as a third-party agent partner. It enables agents built in n8n to connect to Agent 365 and operate in Microsoft 365 applications with their own Entra ID.
Which Microsoft apps can n8n agents appear in?
The verified n8n material identifies Teams, Outlook, Word and SharePoint as Microsoft applications where n8n agents can be deployed.
Does Agent 365 provide governance for n8n agents?
Yes. The verified research states that n8n agents can be governed with Microsoft Agent 365 governance and observability tooling.
Are Microsoft Agent 365 credentials generally available?
n8n documentation describes Agent 365 credentials as being in preview through the Frontier program. The supplied research does not provide a general availability date.
What does the integration cost?
The supplied research does not provide public pricing for Agent 365 credentials, n8n provisioning or the integration. Teams should confirm applicable licensing and preview eligibility with the relevant providers.
Conclusion
Microsoft's support for n8n in Agent 365 makes agentic automation more concrete for Microsoft 365 users: n8n supplies the agent runtime, while Agent 365 brings identity, governance and observability into the picture. The integration is confirmed, but credentials remain in preview and public pricing details are not established in the supplied materials. Its value will depend on whether businesses can apply the model to focused, well-designed workflows.