Plane now connects to Microsoft Teams

Turn Teams messages into work items and keep threads in sync, on self-hosted Plane.

Surya Prashanth and Henit Chobisa

●

20 Oct, 2026

Cover image illustration for the announcement blog post titled "Microsoft Teams meets Plane"

The Microsoft Teams integration connects self-hosted Plane to your Microsoft tenant. Create a work item from any Teams message, link a channel thread to a work item so replies and updates flow both ways, and paste Plane links that open into previews.

In a Teams channel, a work item is created from a customer message with thread sync on: the message's menu, Create Work Item, the form with the sync toggle shown, the card under the message, and a reply arriving in Plane — *In a Teams channel, a work item is created from a customer message with thread sync on, and its card posts under the message*

What's included

Create work items from messages

Open a message's menu in Teams and choose Create Work Item. Pick the project, fill in the details, and a card for the new work item posts as a reply to that message, with Add me to Assignees and View in Plane. On a project with Intake, you can send the request to the intake queue instead.

Thread sync

Link a channel thread to a work item with Link Existing Work Item, or turn on Sync this thread with work item updates when you create one. Replies in the thread become comments in Plane, and changes to fields such as state and priority post back to the thread as a card.

The card for changes made in Plane, here listing two. Rendered from the card template with sample data, not a screenshot of Teams. — *A Work Item Updated card in a Teams thread, listing two changed fields*

Link previews

Paste a link to a work item, project, cycle, module, or page into Teams and it opens into a card with the details. A work item's card lets you assign yourself or open it in Plane.

Bot commands

Mention the Plane bot in a channel to create a work item, or to ask Plane AI a question if Plane AI is set up on your instance.

Connect from workspace settings

A workspace admin connects the Microsoft tenant from Workspace settings, Integrations, Microsoft Teams. Each person then connects their own Microsoft account on the same page.

The Microsoft Teams page in workspace settings, on a test workspace. The tenant is connected and this person has not connected their own account. — *The Microsoft Teams page in workspace settings, with a connected tenant*

Where it helps

Requests that land in a channel

A customer problem gets posted in your team's channel and needs an owner before the conversation moves on. Create the work item from the message itself, and the card under it shows everyone it's tracked.

Release threads people already watch

Link a release thread to its work item, and state and priority changes show up where the team is already reading. Changes made close together arrive as one card, so the thread doesn't fill up with updates.

Work item update card showing state and priority changes synced from Plane to Microsoft Teams. — *A release thread linked to ENG-42, with one Work Item Updated card after two changes in Plane*

Answering from either side

Engineers reply in Teams, and the replies land on the work item in Plane under one comment. Reply to that comment in Plane, and your answer posts back to the thread with your name on it.

Comment written in Plane displayed as a reply card in Microsoft Teams. — *A reply in Teams appears in Plane, and a reply written in Plane appears in the thread as a card*

How thread sync works

Linking a thread adds one comment to the work item, Connected to Microsoft Teams thread. Replies from Teams are saved under that comment, and only replies you write to it in Plane go back to the thread, so other comments on the work item stay in Plane. Field changes are collected and posted to the thread as one card after a short wait.

Diagram showing bidirectional comment sync and batched work item updates between Microsoft Teams and Plane. — *How a linked thread and a work item sync. Replies come in under the linking comment, only replies to it go back, and field changes arrive as one card*

Setup

An instance admin registers an app in Microsoft Entra ID, creates an Azure Bot with the Teams channel on, and uploads the Teams app package. The setup guide walks through each step and the permissions it needs.
The integrations service needs four settings: a client ID, a client secret, your tenant ID, and an app type.
Teams delivers messages to a bot endpoint on the integrations service, so that address has to be reachable from the internet.
The workspace admin who connects the tenant needs a Microsoft account that can grant admin consent. An instance connects to one Microsoft tenant, and that tenant connects to one workspace.

Good to know

You create work items in Teams only in projects where you can create them in Plane. Cards the integration posts are visible to everyone in the chat or channel.
Thread sync works in channel threads, one thread to one work item. Link from the thread's first message. Only replies posted after linking reach Plane.
Each person connects their own Microsoft account before the actions and link previews work for them.
The create form starts empty. The message's text isn't copied into the work item.
Editing or deleting a reply in Teams doesn't change its comment in Plane, and deleting a comment in Plane doesn't remove its card from Teams.
The Docker Compose, Coolify, and Portainer templates don't pass the Teams settings to the integrations service.
Disconnect a tenant from the same settings page. Work items and comments stay in place. Removing the Plane app inside Teams changes nothing in Plane.

Availability

The Microsoft Teams integration is available on the Enterprise Grid plan for self-hosted Plane, Commercial Edition, from v3.2.0. It isn't on Plane Cloud yet. See the setup guide, the integration guide, and the v3.2.0 release notes.