Connecting Microsoft Teams as a Knowledge Source
Surface the knowledge already living in your team's conversations.
Written by Outlearn Documentation
Updated at April 24th, 2026
Table of Contents
Your team communicates in Microsoft Teams every day and a lot of that communication contains useful knowledge: answers to common questions, troubleshooting tips, process explanations, and more. By connecting Microsoft Teams as a source, your agent can tap into that institutional knowledge and use it to answer questions.
In this article, you'll learn:
- What gets synced when you connect Microsoft Teams as a source
- How to connect your Microsoft Teams account
- How to manage the connection
What Gets Connected
When you connect Microsoft Teams as a knowledge source, Outlearn syncs messages and conversations from the channels or threads you authorize. Your data stays in Microsoft Teams - Outlearn reads it, it never modifies or moves it.
Note: Connecting Microsoft Teams as a knowledge source is different from deploying your agent inside Microsoft Teams. This article covers using Microsoft Teams as a source only. To deploy your agent to Microsoft Teams, see Deploying to Microsoft Teams.
How to Connect Microsoft Teams
- Go to the Sources tab.
- Click + Add Knowledge.
- In the Add Knowledge Sources modal, click Team Chats in the left panel.
- Select Microsoft Teams.
- Log in to your Microsoft Teams account when prompted and authorize Outlearn to access your messages.
- Follow the on-screen steps to select which channels or conversations to sync and set accessibility.
After Connecting
Once connected, Microsoft Teams will appear in your Sources list and Outlearn will keep it in sync automatically.
From the Sources list you can:
- Change accessibility using the dropdown next to the source.
- Toggle it on or off using the In Use toggle.
- Resync manually using the three-dot menu.
- Delete the connection using the three-dot menu.
Best Practices
- Be selective about which channels you connect - not every conversation is useful as a knowledge source. Focus on channels where team members share answers, guides, or resolved issues.
- Set accessibility to Internal - team chat content is almost always internal knowledge not suited for public-facing agents.
- Avoid connecting channels with high noise-to-signal ratios (e.g., general chat, off-topic channels) as this can dilute answer quality.