M365 AgentInstall

Summary

Update a Teams connector card in an existing O365/M365 Agent conversation.

Inputs

• cardContent (required) — Teams-specific connector card object. Full O365ConnectorCard object — title, text, themeColor, summary, sections, potentialAction.
• conversationSource (required) — Where conversation routing info comes from. Reply/update/delete flows use envelope automatically; proactive sends need manual.
• authKind — Authentication kind. Default: classicBot. Options: classicBot (Azure Bot Service + Entra App Registration), agent365 (Entra Agent Identity).
• serviceUrl — Bot Connector service URL for the target channel. Required when conversationSource is manual.
• conversationId — Conversation ID. For Teams channels: 19:xxx@thread.tacv2. Required when conversationSource is manual.
• channelId — Azure Bot Service channel. Default: msteams. Options: directline, emulator, msteamscopilot, msteams, webchat.
• activityId — Required only for Reply/Update/Delete against a specific activity. Leave empty for proactive sends.
• fallbackText — Fallback text for the connector card.
• rawActivityOverride — Optional raw JSON override for the constructed Activity body. Must parse to a JSON object.
• identityMode — Only for authKind agent365. Options: autonomous (agent acts as Blueprint app identity), agentUser (agent acts as its own M365 user).
• userSelectorMode — Only for authKind agent365 and identityMode agentUser. Options: byUpn, byObjectId.
• agentUsername — UPN of the agentic user. Required when authKind agent365, identityMode agentUser, and userSelectorMode byUpn.
• agentUserId — Object ID of the agentic user. Required when authKind agent365, identityMode agentUser, and userSelectorMode byObjectId.

Output shape

object

Returns the updated Activity object with conversation reference and acknowledgment status.

Examples

Example 1: Update a connector card in an existing Teams conversation using manual conversation reference.

Set conversationSource to manual, provide serviceUrl and conversationId, supply cardContent JSON, and optionally set channelId, activityId, fallbackText, or rawActivityOverride.

Links

• n8n community nodes installation guide