Messaging and email

Microsoft Teams Bot

Connect an Azure Bot registration to start workflows from Microsoft Teams conversations and route team messages into workflow runs and approvals.

01 / Workflows

What you can automate.

The Microsoft Teams Bot connection stores the Azure Bot app ID, app password, and optional tenant ID. It is used for Teams-based conversational channel triggers.

  1. Start workflows from Teams bot conversations.
  2. Route team messages into workflow runs and approvals.
  3. Support tenant-specific or multi-tenant bot registrations.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the Microsoft Teams Bot docs.

Capabilities

  • OAuth2 client credentials
  • Conversational channel triggers
  • Azure Bot registration settings

Data handled

  • Team messages
  • Trigger metadata
  • Conversation context

03 / Availability

In every edition.

Microsoft Teams Bot is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is Microsoft Teams Bot included in my plan?

Yes. Microsoft Teams Bot is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the Microsoft Teams Bot credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in Messaging and email

Put Microsoft Teams Bot to work.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.