M365 AgentInstall

Summary

Send a Teams O365 Connector Card message. The card content is supplied as a JSON object conforming to the O365 Connector Card schema (title, text, themeColor, summary, sections, potentialAction).

Inputs

• cardContent (required) — Full O365ConnectorCard object defining the card layout and content.
• authKind (required) — Authentication method: classicBot (Azure Bot Service + Entra App Registration) or agent365 (Entra Agent Identity).
• conversationSource — Source of conversation routing information. 'From Envelope' uses the conversationReference from the current item (automatic for replies/updates/deletes). 'Specify Manually' requires serviceUrl and conversationId to be provided.
• serviceUrl — Bot Connector service URL for the target channel. Required when conversationSource is 'manual'.
• conversationId — Conversation identifier (e.g., 19:xxx@thread.tacv2 for Teams). Required when conversationSource is 'manual'.
• channelId — Azure Bot Service channel the conversation belongs to (directline, emulator, msteamscopilot, msteams, webchat). Defaults to 'msteams'.
• activityId — Required only for Reply/Update/Delete operations against a specific activity. Leave empty for proactive sends.
• identityMode — Applicable when authKind is agent365. 'autonomous' acts as the Blueprint app identity; 'agentUser' acts as the agent's own M365 user (requires sidecar transport and additional licenses).
• userSelectorMode — Applicable when authKind is agent365 and identityMode is agentUser. 'byUpn' selects by user principal name; 'byObjectId' selects by Azure AD object ID.
• agentUsername — UPN of the agentic user. Defaults to the credential's Default Agent Username. Required when authKind is agent365, identityMode is agentUser, and userSelectorMode is byUpn.
• agentUserId — Azure AD object ID of the agentic user. Required when authKind is agent365, identityMode is agentUser, and userSelectorMode is byObjectId.
• options — Optional collection. 'fallbackText' provides fallback text for the card. 'rawActivityOverride' replaces the constructed Activity body with raw JSON (for protocol fields not exposed in the UI, must parse to a JSON object).

Output shape

The operation returns the sent activity/connector response as provided by the bot connector, but the exact return shape is not detailed in the available properties or source.

When conversationSource is 'manual', serviceUrl and conversationId must be supplied. When authKind is agent365 with identityMode agentUser, additionally configure userSelectorMode, agentUsername (or agentUserId), and ensure the agentic user has appropriate M365 licenses.

Examples

Example 1: Proactive send with classic bot

Set authKind to classicBot, conversationSource to manual, provide serviceUrl and conversationId, and supply cardContent with the connector card JSON.

Example 2: Reply via envelope

Set conversationSource to envelope (default) and supply cardContent. The node will use the conversationReference from the incoming item.

Links

• n8n community nodes installation guide