Microsoft Agent 365 and n8n: giving an AI agent a real identity in Teams and Outlook

Since May 1, 2026, Microsoft Agent 365 has been generally available: an identity, governance, and security layer designed so that a company's AI agents are no longer anonymous scripts, but entities registered in Microsoft Entra Agent ID, listed in a registry alongside human accounts. n8n followed suit right away with a dedicated node, the Microsoft Agent 365 Trigger, which lets an n8n workflow become that agent — with its own name, its own identity, visible in Teams, Outlook, Word, and SharePoint. It's a step up from the classic Microsoft Teams bot many teams already know: this guide covers what the node actually does, how to configure it, what it costs, and where it genuinely changes a team's day-to-day work.

Microsoft Agent 365 in one sentence: an agent becomes a colleague in the directory

Two Microsoft building blocks are often conflated and worth separating:

• Microsoft Entra Agent ID is the identity foundation: it lets you create an "agent identity blueprint" — a distinct identity, with its own attributes and lifecycle — for an AI agent, exactly the way Entra ID already manages human identities and service accounts.
• Microsoft Agent 365 is the governance and security envelope built around that identity: a unified registry of agents (human or not, Microsoft or third-party), permissions, oversight, and security policies, all managed from the Microsoft 365 admin center.

In practice, an Agent 365 agent shows up in the company directory next to employees, can be @mentioned in a Teams channel, receive emails in a dedicated Outlook mailbox, or comment on a SharePoint document — without an admin having to hack together a generic service account to give it a presence in those apps.

What the Microsoft Agent 365 Trigger node changes in n8n

The node is a root trigger (like the AI Agent node), not a plain event listener: it receives a POST request sent by the Agent 365 runtime whenever a user addresses your agent, carrying the task context (user, channel — Teams or Outlook —, message). It then wires up exactly like a classic AI Agent:

• a Model sub-node (any chat model n8n already supports);
• a Memory sub-node to keep track of the conversation;
• Tool sub-nodes — native nodes, sub-workflows, or services connected through MCP, with a dedicated toggle to give the agent access to Microsoft 365 tools through that protocol.

The response the agent produces travels back through the same webhook, and Agent 365 delivers it into the originating app: a message in a Teams thread, a draft in Outlook, a comment on a SharePoint document. The n8n workflow itself doesn't change in nature — it's the same agent logic as anywhere else; only the identity and delivery envelope changes.

Setting up the Microsoft Agent 365 credential, step by step

Unlike a plain API key, the credential asks for three pieces that come from an application registration on the Microsoft side:

1. Tenant ID — found in Microsoft Entra ID, copied as-is into n8n.
2. Application (client) ID — obtained by registering a custom application through Microsoft's app registration portal, following the dedicated custom-client registration guide for Agent 365.
3. Client Secret — generated from that same application, copied immediately (it's shown only once) and pasted into the matching field of the n8n credential.

It's the same application-registration dance in Entra ID as for the classic Microsoft Teams Trigger or for setting up OAuth2 with Google: a mandatory step owned by the tenant administrator, one no no-code tool can shortcut.

Security: validating the Bot Framework token

An agent exposed inside Teams and Outlook receives requests from a Microsoft service — but also, in theory, from anyone who can guess the webhook URL. As of n8n versions 2.25.7 and 2.26.2, the node closes that door by default: every incoming request is checked before it reaches your business logic. The node verifies the Bot Framework token Microsoft attaches and confirms its Client ID matches the configured Microsoft Agent 365 credential; any request without a valid token, or with a mismatched Client ID, is rejected. The practical takeaway: stay current. Like any security mechanism shipped in a specific release, an instance stuck on a version older than 2.25.7 simply doesn't get it — our guide to updating n8n in Docker without breaking anything covers the process.

What it costs, and who pays for what

Two separate bills stack up:

• On the Microsoft side: Agent 365 is licensed per user, separately from your existing Microsoft 365 subscription (roughly $15 per user per month depending on the offer, or bundled into some E7 plans at the time of writing). It's an enterprise-governance cost, one you justify to IT leadership through the agent registry and traceability it provides, not through the workflow itself.
• On the n8n side: the Microsoft Agent 365 Trigger node is a standard app node, included in your existing n8n instance or plan — no extra node fee, whether you run self-hosted or on n8n Cloud.

Always check Microsoft's official pricing page before budgeting a team-wide rollout: these prices change, and the gap between license tiers can quickly dominate a project's total cost compared with the time spent building the workflow.

Where this node genuinely changes a team's daily work

Giving an agent its own identity isn't just a directory gimmick — it changes how humans delegate work to it. A large-scale study by Ju and Aral (MIT Sloan / Johns Hopkins Carey Business School, 2026), "Collaborating with AI Agents: Field Experiments on Teamwork, Productivity, and Performance" — see it, tracked more than 2,200 participants split into human-human and human-AI teams on a real ad-production task, later rated by human judges and tested in the field on X. The result: human-AI teams produced 50% more content per worker, with 17% more tasks delegated and 62% fewer manual edits — but also more homogeneous output between team members, a diversity-collapse signal worth watching rather than ignoring. Translated into n8n + Agent 365 usage: an agent that triages an Outlook inbox or answers in a Teams channel can absorb a real volume of repetitive work, provided a human keeps a check on the variety and quality of outputs, not just their volume.

That's exactly the balance our packs are built around: the Pack Inbox IA (€79) delivers AI-based sorting, urgency scoring, and Gmail reply drafts — a base directly adaptable to an Outlook agent wired through Microsoft Agent 365 — and the Pack Conformité & Audit (€149) provides the audit trail and summary report that give an agent's decisions traceability, a point that matters even more once that agent carries an official enterprise identity. The Complete FlowKit Bundle (€269 instead of €347) bundles all three packs on the same Supabase base.

An identity alone doesn't build trust

Making an agent visible in the directory answers an IT-governance question, not an adoption one. A multidisciplinary theoretical framework published by Ulfert, Georganta, et al. (European Journal of Work and Organizational Psychology, 2023), "Shaping a multidisciplinary understanding of team trust in human-AI teams" — see it, points out that trust in a human-AI team builds at multiple levels — between each human and the agent, but also at the whole-team level — and isn't decreed simply by the formal presence of an extra "member" on the org chart. In practice, that means a technically well-configured Agent 365 agent (identity, permissions, token security) still has to earn its place like any new colleague: reliable, traceable answers, and a team that knows what the agent does and doesn't do.

What this node doesn't solve

Two limits worth keeping in mind before rolling it out:

• It isn't a systematic replacement for the classic Microsoft Teams Trigger. For a simple internal bot with no need for enterprise governance or an Outlook/SharePoint presence, the native Microsoft Teams Trigger stays simpler to set up and doesn't require an Agent 365 license.
• Microsoft Graph permission governance doesn't go away. The node secures the authentication of the incoming request, not the downstream rights granted to the agent: least-privilege still applies to every tool and dataset you connect it to.

Summary

The Microsoft Agent 365 Trigger doesn't change how you build an agent in n8n — Model, Memory, Tool, the same architecture as anywhere else — but it radically changes how that agent exists for the rest of the company: an Entra identity, a registry, a native presence in Teams and Outlook. For a small team that just wants a bot in a channel, the classic Microsoft Teams Trigger stays faster to set up and free of license cost. For an organization that wants to govern its AI agents the way it governs its human accounts, Agent 365 is Microsoft's first building block designed for that — provided you keep, as the literature on trust in human-AI teams reminds us, real human oversight of what the agent does once its identity is created.