--- title: "Connect a circle or a project to Microsoft Teams" description: "Connect a circle or a project to a Microsoft Teams channel: the consent flow, choosing the team and the channel, and how to read the card when delivery stops" category: integrations section: native-integrations type: Tutorial lastUpdated: 2026-09-30 locale: en canonical: https://support.talkspirit.com/en/integrations/connect-a-circle-or-a-project-to-microsoft-teams --- # Connect a circle or a project to Microsoft Teams > **In summary:** open the circle’s settings, then the **Integrations** tab, and connect the **Microsoft Teams** card. Microsoft asks for your consent on its own screen; you then choose the team and the channel back in Talkspirit. Two steps, not one: an install that stops after consent shows **Finish setup** and sends nothing until a channel is chosen. This guide covers Microsoft Teams. What a circle integration sends, and how to read the card, is the same for every chat tool: see [Circle and project integrations](/integrations/circle-and-project-integrations-overview). ## Before you start - You are an administrator of the circle in Talkspirit. - You can grant an application access to your Microsoft tenant. Microsoft asks for this on its own screen, and many organisations restrict it to a tenant administrator: if that is your case, the consent screen will say so rather than fail silently. - You belong to at least one team, with at least one channel you are allowed to post in. The picker says so plainly when neither is true. ## Connect the circle 1. Open the circle’s settings, then the **Integrations** tab. 2. On the **Microsoft Teams** card, select **Enable**. 3. Microsoft shows its consent screen. Approving it returns you to the circle. 4. Back in Talkspirit, choose the **team**, then the **channel**. The channel list stays empty until a team is chosen. The second step is the one people skip. Consent alone connects the account, not the destination: until a channel is chosen the card reads **Finish setup** and nothing is sent. This differs from Slack, where the channel is picked on Slack's own screen and the install arrives complete. ## Choosing where to post The two lists show only what your own Microsoft account can reach. - **This account does not belong to any team**: the account that consented is in no team. Consent again with an account that is. - **This team has no channel you can post in**: the team exists but grants you no channel you may post to. Ask a team owner, or pick another team. Either message is an answer, not a fault: the connection is fine and the destination is not settled yet. ## What gets sent The four governance families described in [Circle and project integrations](/integrations/circle-and-project-integrations-overview), identically to Slack. A circle's connection carries governance activity only: tasks belong to a project, which carries its own connection. A project connects Teams from its settings, under **Notifications**, with the same consent and the same choice of team and channel as a circle. One message differs from Slack: an adopted proposal. - Slack posts that the proposal was adopted. Teams does not. - When the adoption moved roles or circles, Teams posts **Some elements were restructured in** followed by the circle's name, then one line per move, for example "The role Facilitator was moved from Sales to Marketing". The **Open in Talkspirit** button leads to the proposal. - When the adoption moved nothing, Teams posts nothing for it. The circles a role left and joined still receive their own move message. When the proposal's circle is one of them, its channel reads the move twice. Like every Teams message, these sentences are in English. ## When delivery stops The card names the cause, and the three causes need different things from you. | What the card says | What it means | What to do | | --- | --- | --- | | **Sending was interrupted** | A run of deliveries failed: the channel was deleted or archived, or the app lost access to it. | Fix the cause, then try again. The counter resets on the first success. | | **The Microsoft connection has expired** | Access was revoked, or the consent expired. No later attempt can succeed on its own. | Reconnect your Microsoft account. This is the one case where reconnecting is the fix. | | **Notifications are paused on our side** | A fault in Talkspirit, not in your configuration. | Nothing. Our team is alerted automatically and your settings are untouched. | The distinction matters because reconnecting is not a general remedy. On the first row it changes nothing: the tokens were never the problem, and you would come back having re-approved a consent that was already valid. ## What Teams does not do Two things the Slack integration offers and this one does not: - **Tagging a role from the chat tool.** Slack has user groups, which Talkspirit keeps in step with your roles. Teams has no equivalent, so there is nothing to tag. - **Asking Talkspirit from the chat tool.** There is no Teams command matching Slack's `/talkspirit`. Neither affects notifications, which work the same on both. ## What’s next? - [Circle and project integrations](/integrations/circle-and-project-integrations-overview), what is sent, the event families, and reading the card - [Connect a circle or a project to Slack](/integrations/connect-a-circle-or-a-project-to-slack) - [Connect a circle or a project to a Talkspirit group](/integrations/connect-a-circle-or-a-project-to-a-talkspirit-group) - [Send a circle’s or a project’s events to your own webhook URL](/integrations/send-circle-or-project-events-to-your-own-webhook)