Factories > Integrations

Connect Microsoft Teams to your factory

Connect Microsoft Teams to your factory so mentions in standard and shared channels start work and results post back in the same thread.

Connect a factory to Microsoft Teams so your team can send work from channel conversations. Mention the Warp app in a configured standard or shared channel, and the factory picks up the request with conversation context, then posts progress and results back in the same thread.

Prerequisites

Microsoft Teams enabled for your workspace - The Microsoft Teams option appears in factory setup and Settings only when Teams is enabled for your Warp workspace. If you don’t see it, ask a workspace admin or contact sales.
Permission to upload and approve custom Teams apps - A Microsoft Teams admin must upload and approve the Warp app package in the Teams admin center.
Permission to update the factory - Connecting Microsoft Teams changes the factory’s configuration.
A linked Warp account for interactive requests - Anyone who starts work with a mention must link their Microsoft account to an active member of the factory’s Warp workspace.

Connect the factory

You can connect Microsoft Teams while creating a factory, on the communication step, or later from the factory’s Settings. Steps below are grouped by where you perform them.

In the Warp Factories web app

Open factory setup or the factory’s Settings, then choose Microsoft Teams.
Sign in with Microsoft if Warp asks you to link your Microsoft identity. This is only needed once per person.
When Warp shows the setup instructions, download the production app package (warp-microsoft-teams-app.zip). The ZIP contains the Teams app manifest and icons only.

In Microsoft Teams

Ask a Microsoft Teams admin to open the Teams admin center, go to Teams apps > Manage apps, choose Upload new app, select the downloaded ZIP, and approve the app.
In Microsoft Teams, go to Apps > Built for your org, open Warp, and Add it to each Microsoft Teams team the factory should use. Adding the app to a team is what makes that team selectable in Warp.

Back in the Warp Factories web app

Select Microsoft Teams teams, then select at least one channel in each selected team. The channel picker lists standard channels from a ready installation.
Click Enable (or finish factory setup) to attach Microsoft Teams to the factory.

Until a workspace admin binds a newly installed team to your Warp workspace, the team can appear as pending and channel selection stays blocked for that team.

Warp seeds a default teams-app-mentions automation for the teams and channels you selected. To confirm the connection, mention the Warp app in one of those channels and check that a work item starts in the factory’s dashboard.

Configure factory automations for Microsoft Teams

Add a Microsoft Teams trigger to an automation and pick one of these events. To edit filters, see Automations.

App mentioned (app_mention) - Filter by team, channels, authors, and keywords.
Message posted in channel (message_posted) - Filter by team, channels, authors, and keywords.

A mention also emits a message_posted delivery. Don’t point both triggers at the same channels, or one mention can start two runs.

Every Teams trigger requires exactly one Microsoft Teams team and at least one channel. Team and channel filters are inclusion lists only. Keywords and Users are optional.

The channel picker lists standard channels only. Private channels and direct messages are not supported. Shared channels can start and continue work under the rules below; when a shared channel is missing from the picker, include its channel ID in a definition file filter.

For exact event and filter keys in definition files, see triggers.

Shared channel behavior

Shared channels are supported when the Warp app is installed in the host team that owns the channel.

Start with a mention - In a shared channel, mention the Warp app explicitly to start new work. A root message without a bot mention does not start work there.
Host-tenant senders - The person who mentions the app must be a host-tenant user with their Microsoft account linked for that Teams setup. If Warp cannot confirm that identity, it posts a private notice that the message can’t start or continue a task and points them back to Warp.
Continue in-thread - After a shared-channel thread is linked to a factory work item, eligible plain replies can continue that work item when auto-respond to thread replies is on (the default).
History tools - For runs that start in a shared channel, agent thread-history tools are limited to that run’s originating thread and still require a bound host-tenant sender.
Tenant boundary - The shared channel must belong to the Microsoft tenant of the installed Warp app.

Private channels and direct messages remain unsupported.

Use integration-provided tools

When Microsoft Teams is connected, Warp gives factory agents Teams tools automatically: read a channel thread, reply in a thread, post a top-level channel message, and resolve a conversation member. The run doesn’t need to start from Teams.

These are Warp-managed capabilities, separate from MCP servers you configure for cloud agents. Agents cannot list channels, read private channels, send direct messages, add reactions, or upload files. Shared-channel history stays limited to the originating thread for that run.

Start and continue work from Microsoft Teams

Mention the Warp app in a configured channel or thread to start work. The factory replies in the same thread with progress and links to results.

A plain reply continues work only if that thread already has a factory work item. To start new work, mention the app. When auto-respond to thread replies is on, eligible plain replies in an existing factory thread can continue without another mention. In shared channels, new root work still requires an explicit mention.

You can attach files to a request or follow-up. Unsupported files don’t block the text of the request.

Follow work and review outputs

Follow progress in the Teams thread where work started. Reply there to add information while work is active, or to resume later. Work still ends at a pull request for a person to review — see how Warp Factories work.

Who can start work

To start work with a mention, link your Microsoft account to an active member of the factory’s Warp workspace: mention the bot followed by sign in, or help for account commands, or sign out to unlink across Factories in that Microsoft tenant. In a shared channel, that identity must also satisfy the host-tenant checks above.

Work started by an automation runs as the factory agent you chose for it, not as whoever triggered it.

Definitions as code

integrations:
  - type: microsoft-teams

---
enabled: true
agent: foreman
triggers:
  - provider: teams
    event: app_mention
    filter:
      team_ids: [MICROSOFT_GRAPH_TEAM_UUID]
      channel_ids: [19:example@thread.tacv2]
---

Triage the Teams request and continue in the same thread.

team_ids must include exactly one Microsoft Graph team UUID. channel_ids lists Bot Framework channel conversation IDs to listen in, including any shared channel IDs. Optional keywords and user_ids further narrow matching. See factory definition syntax for fields such as autoRespondToThreadReplies.

Troubleshooting and reconnection

The app doesn’t acknowledge a request - Confirm Teams is connected for that factory, you mentioned the Warp app in a configured channel, and your Microsoft account is linked. In a shared channel, confirm the host-tenant requirements above.
A team is missing from setup - In Microsoft Teams, open Apps > Built for your org, open Warp, and Add it to that team. Refresh team selection in Warp. A workspace admin may still need to bind a pending installation.
A channel is missing from an automation - The picker lists standard channels only. For a shared channel, add its channel ID in a factory definition filter.
Microsoft Teams is missing from setup or Settings - Teams appears only when enabled for your Warp workspace. Ask a workspace admin or contact sales.
Installation or upload is pending - Ask a Teams admin to approve the custom app, Add Warp to the team in Teams, then finish selection in Warp.
Two runs start for one mention - Narrow or remove overlapping app-mention and channel-message triggers for the same channels.
An agent can’t post back to Teams - Confirm the factory still declares Microsoft Teams and the installation for that team is ready.

To disconnect Microsoft Teams, remove the integration in factory Settings or the factory definition. Uninstalling the Warp app from a Microsoft Teams team stops new activity from that team.

Privacy

The factory’s app reads messages only in the channels you configure for mentions and automations, and in threads it continues there. Message content and supported attachments are used to run the factory’s work. Linking your Microsoft account maps you to your Warp account. Data is handled per the Warp Privacy Policy.

Connect your factory - Choose the sources that route work into the factory.
Factory automations - Edit trigger filters and avoid overlapping Teams triggers.
Factory definition - Declare microsoft-teams and teams triggers as code.
Slack - The other chat intake path for factories.