This guide outlines the steps necessary to set up a Microsoft Agent 365 AI Teammate with n8n. AI teammates are invoked just like a human colleague, through at-mentions in Teams or within documents, as well as via email. With the help of a range of built-in Microsoft WorkIQ MCP tools, the AI teammate can handle a range of tasks out-of-the-box and be extended nearly endlessly via n8n.

📺 Watch a live walk-through of the setup

https://www.youtube.com/live/zjJUTP1nHH0?si=qMacr7QRkQIDUqHu&t=346

Documentation

Understanding Agent 365 Entra Objects

Agent 365 has three Entra objects: the Agent Identity Blueprint (a credential-holding template), the Agent Instance (the service principal that authenticates to Work IQ MCP servers at runtime), and the Agent User (a directory user object for OBO scenarios). See the Agent 365 Identity doc and the underlying Agent identity blueprints doc.

The entire setup uses the official a365 CLI:

1. a365 setup all --aiteammate creates the Blueprint and configures platform permissions (Step 3).
2. a365 develop add-mcp-servers populates the local ToolingManifest (Step 4).
3. a365 setup permissions mcp grants MCP server permissions via inheritable permissions (Step 5).
4. a365 publish packages the Teams manifest for upload (Step 6).

Prerequisites

Licensing and roles:

• Microsoft 365 Copilot license in your tenant — required by all Work IQ MCP servers.
• Microsoft Teams license — required because the Agent Instance communicates via Teams.
• Agent 365 (A365) license — e.g. included in the new E7 license. Note: Agent 365 is currently in preview via the Frontier preview program.