Heidelberg AICurriculum

From the n8n canvas to Microsoft Teams with Microsoft Agent 365

n8n ·2026-05-19 ·2 min read

Summary written by us from the video's transcript. The video, and everything in it, is n8n's work.

Learn how to create a Microsoft 365 AI agent using n8n’s Agent 365 node, from CLI setup to configuring the trigger node in n8n.

Takeaways

  • The Agent 365 node lets n8n workflows call Microsoft 365 services securely through a webhook and Azure‑managed permissions.
  • All required tool access (Word, Excel, Teams, etc.) is granted via MCP server selection and inheritable permission commands in the CLI.
  • Publishing requires editing a manifest file to define agent metadata that appears in the Microsoft Agent Store.
  • After setup, n8n’s trigger node connects the blueprint’s endpoint with LLM, memory, and external tool nodes to create functional AI teammates.

Overview of the Agent 365 Integration

The session introduces the **Agent 365 node** in n8n, which bridges n8n workflows with Microsoft 365 tools via a webhook URL and secured credentials. It enables agents to access Outlook, Teams, Word, and other Microsoft services while remaining orchestrated by n8n.

The integration combines n8n’s rapid workflow building with Microsoft’s enterprise‑grade identity, permissions, governance, and monitoring (Entra, Defender, Purview).

Prerequisites

You need an active Microsoft Copilot license, a Teams license (often bundled in E5), an Agent 365 license (included in the new E7 tier), enrollment in the early‑access program, and either a global admin role or a less privileged role that can be elevated for certain steps.

On the n8n side you only need a running n8n instance; the rest of the setup is handled through Microsoft’s CLI tool.

Setting Up the Agent Blueprint with the CLI

Install or update the **Agent 365 CLI** and run `a365 setup requirements` to verify Azure CLI login and other prerequisites.

Create a working directory, then execute the single command that creates the blueprint, configures permissions, and generates a config file containing the blueprint ID, object IDs, service principal ID, and client secret.

Configuring Microsoft Tool Access

List available MCP servers (OneDrive, SharePoint, Teams, etc.) with the CLI and select the ones your agent needs (e.g., Word, Mail, Calendar, Planner, Excel).

Run the permission command to apply inheritable permissions for those tools; you can verify added permissions in Azure Portal under the blueprint’s application.

Publishing the Blueprint and Customizing the Manifest

Execute `a365 publish` to generate a manifest directory and zip file for upload to Microsoft Admin Center.

Edit **manifest.json** to set short name, full name, description, icons, version, developer info, privacy URL, and terms of use before final packaging.

Connecting n8n via the Agent 365 Trigger Node

In n8n, add the **Agent 365 trigger node**, paste the webhook endpoint from the blueprint, and configure credentials using the client secret obtained earlier.

Link the trigger node to an LLM chat model node, optional memory node, and any additional tool nodes (e.g., Salesforce, ServiceNow) to build your AI teammate workflow.

Running the Demo and Next Steps

The demo walks through each CLI command, manifest editing, and n8n node configuration, showing a complete end‑to‑end setup.

A step‑by‑step guide and video are provided for users to follow at their own pace; after deployment, agents can be instantiated from the Microsoft Agent Store within Teams.