> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/chat/microsoft-teams.md). # Microsoft Teams View, respond to, and track customer requests coming from Microsoft Teams. ## Microsoft Teams ### Setup Click into the [Apps Directory](https://app.usepylon.com/apps) from your Pylon dashboard and then click on the Microsoft Teams integration to view setup instructions. #### Channels vs Chats Pylon supports connecting to both Microsoft Teams Channels and Chats. **Channels** * Can either be [shared channels](https://support.usepylon.com/articles/8242890103-how-do-i-set-up-a-microsoft-teams-shared-channel) between your tenant and the customer's tenant, or channels within your tenant with customers added as guest users * Optionally support mirroring conversation to Slack **Chats** * Support group chats with external parties * Due to the nature of chats being a single thread, Pylon will have up to one open ticket per chat at a given time. Once the ticket is closed in Pylon, new conversation will open a new ticket. ### Automatically link new channels to accounts Under **Settings > Customers > Account configuration**, find **External Microsoft Teams channel linking**. Configure **Auto create and link accounts based on Microsoft Teams channel names** with filters for your channel naming convention. Automatic linking applies to standard and shared channels hosted by your tenant and created after you enable the filters. Existing channels aren't backfilled. Private channels, archived channels, and group chats aren't included. Pylon first looks for an existing customer account using external members' email domains, then the account name derived from the channel name. If no account matches, it creates a customer account and links the channel. Channels with multiple customer domains or ambiguous account matches are left unlinked for you to handle manually. Enable **Only create accounts when external users join** to wait for an external member before linking. Channels waiting for members are checked every three hours. ### Usage {% hint style="info" %} Once a Teams channel or chat is linked to a Pylon account, messages from Teams are automatically sent to Pylon's [Views](/pylon-docs/support-workflows/issues/views.md) for tracking and responding. {% endhint %} Pylon's Microsoft Teams integration allows you to view, respond to, and track Microsoft Teams messages from your customers without using Teams yourself. #### Customer Teams channels and chats Pylon watches for customer messages in connected Teams channels and group chats and automatically creates tracked issues within Pylon. Customer issues from Teams are visible in the Kanban board and views alongside your other issues, identifiable by the Microsoft Teams logo on each issue.

Teams issues in the Pylon Kanban board

#### Replying to customers Responding to a Teams issue from Pylon delivers the reply, including any file attachments, directly into the customer's Teams channel or chat. You can also edit a sent reply from Pylon and the edit is reflected in Teams. Customer messages, edits, and reactions made in Teams are tracked on the issue in Pylon. #### (Optional) Mirror conversations to Slack If your team prefers to collaborate in Slack, you can mirror a Teams channel to a Slack channel. Customer messages from Teams appear in the mirrored Slack channel, and messages your team sends in Slack are forwarded back to Teams. This lets users without Pylon access participate in customer conversations from Slack. For setup steps, see [How can I set up Microsoft Teams <> Slack mirroring?](https://support.usepylon.com/articles/4073411219)

Customer Teams messages visible in the mirrored Slack channel

Replies sent in the mirrored Slack channel are forwarded to Teams

{% hint style="info" %} Mirroring is optional. Teams channels and chats can be used with Pylon directly, without configuring a Slack mirror. {% endhint %} #### Internal collaboration Use [internal threads](https://docs.usepylon.com/pylon-docs/support-workflows/issues/internal-threads) to discuss Teams issues privately with your team in Pylon or Slack, without the customer seeing the conversation.

Teams issues bundled in your internal threads channel

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/integrations/chat/microsoft-teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.