M365 AgentInstall

Summary

Sets the typing indicator for an M365 Agent conversation using configured authentication and conversation routing.

Inputs

• authKind — Authentication method. Defaults to Classic Bot (Azure Bot Service). Select Agent 365 (Entra Agent Identity) for Entra-based agent identities without an Azure Bot resource.
• conversationSource — Where conversation routing info originates. Defaults to From Envelope (uses conversationReference from current item). Select Specify Manually to provide service URL and conversation ID for proactive sends.
• serviceUrl (required) — Bot Connector service URL for the target channel (e.g., https://smba.trafficmanager.net/emea/). Required when conversationSource is Specify Manually.
• conversationId (required) — The conversation ID. For Teams channels this looks like 19:xxx@thread.tacv2. Required when conversationSource is Specify Manually; leave empty when using From Envelope.
• channelId — Azure Bot Service channel the conversation belongs to. Defaults to msteams. Options: Direct Line, Emulator, Microsoft 365 Copilot, Microsoft Teams, Web Chat.
• activityId — Required only for Reply / Update / Delete operations against a specific activity. Leave empty for proactive sends including typing.
• identityMode — Defaults to Autonomous. When authKind is Agent 365, selects whether the agent acts as its Blueprint app identity or as its own M365 user (requires sidecar transport and separate license).
• userSelectorMode — Defaults to By UPN. Applicable when identityMode is Agent User Account. Options: By UPN, By Object ID.
• agentUsername — UPN of the agentic user. Defaults to credential's Default Agent Username. Required when authKind is Agent 365, identityMode is Agent User Account, and userSelectorMode is By UPN.
• agentUserId — Object ID of the agentic user. Required when authKind is Agent 365, identityMode is Agent User Account, and userSelectorMode is By Object ID.

Output shape

The workflow item proceeds with the typing status communicated to the specified conversation.

No additional data is returned beyond the item passthrough. The typing indicator is applied based on the selected authentication, conversation source, and identity configuration.

Examples

Example 1: Typing indicator for a Teams conversation using agent identity

authKind: agent365; identityMode: agentUser; userSelectorMode: byUpn; agentUsername: agent@contoso.com; conversationSource: manual; serviceUrl: https://smba.trafficmanager.net/emea/; conversationId: 19:xxxx@thread.tacv2; channelId: msteams

Links

• n8n community nodes installation guide