Microsoft Teams

Connect Microsoft Teams so your agents can read channel and chat history, respond to @mentions, and reply in-thread.

Audience: IT (the enabler) and builders

What it can do

  • Read. Channel and chat history.
  • Triggers. A channel message that @mentions the workspace Teams app and asks for a Workflow's work starts a run. In a channel with triggers, the request goes to the matching trigger. Elsewhere, the app finds the Workflow that was asked for. Work starts only when the sender has a linked Teams account with permission to operate the Project; see Triggers.
  • Answers. Any other @mention gets an answer in the thread. The app answers as the sender: it sees the Projects they can see and works with their permissions. It reads the earlier messages in the thread, so a follow-up such as "try again" has context.
  • Reply. In-thread only.

This integration does not support Write today.

Channel triggers and Workflow posts use the workspace Teams bot, not this integration. An administrator sets up that bot under Configuration > Microsoft Teams. A Workflow trigger lists the standard channels in the teams where the bot is installed, so builders do not need this integration or a personal Microsoft account to pick one. A trigger on a Teams chat still uses a chat picked in this integration. This integration copies messages from the chats and channels you pick into the Project so agents can read them.

Who connects this

Admin-enabled OAuth. IT registers an application in Microsoft Entra once. After that, a team admin or workspace admin connects the integration for a team or the whole workspace. Builders add it to their Projects without signing in.

IT registers the application in Microsoft Entra

Register an application and grant admin consent for the Teams scopes.

A team or workspace admin connects the integration

Once stage 1 is done, a team admin or workspace admin opens Integrations, selects Connect on the Microsoft Teams card, and signs in with a Microsoft account that can read the chats and channels. In Available to, they choose Team or Workspace. They then pick the chats and channels the integration should read.

Builders add it to their Projects

In the Project context, builders add the integration with Add to project. They do not sign in to Microsoft Teams.

Approve decisions from Teams

A Workflow can send a decision to a Teams channel when it pauses for a person. Add teams_channel with the channel's team ID and channel ID to the notify of a human.request step. When the run pauses there, the Teams bot posts a card with the question, the saved form values, the answer buttons, and an optional note.

A reviewer answers with a button, or selects Open decision to review it in the app. Edits and email review happen through Open decision. The answer records who decided and resumes the same Workflow. When the decision is answered or cancelled, the card updates and its buttons disappear. A later click cannot replace the answer.

Everyone in the channel can see the question and the form values. Choose a channel where that information belongs.

To answer in Teams, a reviewer needs permission to work the Project's Work items and a linked Teams account. To link the account, send the Teams bot a message in a personal chat, open the link it replies with, and sign in if asked.

If a reviewer who has not linked their account selects an answer button, the Teams bot sends them a link in a personal chat, and the card says where to find it. After they link the account, they select the button again.

If the card cannot be delivered, the decision in the app shows the failure. Check the bot connection and the channel in Configuration, then select Retry Teams notification. The Workflow does not rerun. If updating the card fails after the answer, the answer stays recorded, and Retry Teams message update tries again.

Teams decisions need a one-time setup.

Configure the workspace bot

Under Configuration > Microsoft Teams, use the shared bot or select Configure bot to enter your own Azure Bot. For your own bot, paste the Messaging endpoint shown there into the Azure Bot's Configuration > Messaging endpoint.

To choose the name people see in Teams, select Rename app and enter an App name. The name goes into the app package, so rename the app before you download the package. A blank name uses the default.

Connect your Microsoft 365 organization

Select Connect Microsoft 365 organization so activity from your Teams tenant reaches the platform.

Install the app in the destination team

Select Download app package, upload the package in Teams or the Teams admin center, and add the app to the team that owns the channel.